|
|
Line 41: |
Line 41: |
| | | |
| ==Test Plan== | | ==Test Plan== |
− | [[Image:Zora_Testing3.JPG|600px]]<br> | + | [[Image:Zora_Testing3.JPG|700px]]<br> |
| <br> | | <br> |
| | | |
− | [[Image:Zora_Testing7.jpg|400px]]<br> | + | [[Image:Zora_Testing7.jpg|500px]]<br> |
| <br> | | <br> |
| | | |
− | [[Image:Zora_Testing8.JPG|400px]]<br> | + | [[Image:Zora_Testing8.JPG|500px]]<br> |
| | | |
| ==Test Cases== | | ==Test Cases== |
Revision as of 15:16, 8 November 2013
|
Home
|
Project Overview
|
Project Management
|
Documentation
|
|
|
|
|
Test Methodology
Test Plan
Test Cases
Click here to view Administration Test Case file.
Click here to view Claim Test Case file.
Click here to view Leave Test Case file.
Click here to view Remuneration Test Case file.
Click here to view Login/Logout Test Case file.
Test Outcome
Heuristic Evaluation 1
Testers are the expert evaluators. They used the following heuristic and severity ratings, as shown below, to evaluate our application
Heuristics
|
Severity Ratings
|
1. Visibility of system status
2. Match between system and the real world
3. User control and freedom
4. Consistency and standards
5. Error prevention
6. Recognition rather than recall
7. Flexibility and efficiency of use
8. Aesthetic and minimalist design
9. Help users recognize, diagnose, and recover from errors
10. Help and documentation
Not related to any heuristic
|
0 = I don't agree that this is a usability problem
1 = Cosmetic problem only
2 = Minor usability problem
3 = Major usability problem
4 = Usability catastrophe
|
Images taken during the evaluation
Yun Xi bringing Hui Shia through the remuneration part of the project |
Mei Zhen explaining our prototype to Jing Yi |
Yun Xi going through the prototype with Eng Sen
|
Yi Xian going through our prototype to Ken Khoon
|
Results obtained from the evaluation conducted
User Testing 1
Steps takenn to conduct user testing 1
Post-Test
Identify:
- Goals of the test
- Scope of the test
- Participant Profile
Decides on:
- Testing set up (venue, time etc.)
Prepare:
- Testing items and documents
Recruit Testers
- Testers to read the study script
During-Test
- Give user informed form to testers
- Give task instructions to testers
- Give interview form to testers
- Observe and fill up Observation Form
- Give Questionnaire to testers to fill up while testing
Post-Test
- Consolidate Feedbacks
- Analyze Results
- Maintain a Response Plan
- Implement feedback in UT1 and test again in upcoming UT2
Results obtained from the testing conducted
The following table shows the summary results for quantitative data analysis in terms of the number of time taken for various functions, clicks, bugs and question asked:
Data
|
Pilot Participant
|
Participant 1
|
Participant 2
|
Participant 3
|
|
|
|
|
|
General Data
|
Age
|
24
|
50
|
23
|
26
|
Occupation
|
Student
|
Administrator
|
Student
|
Accountant
|
Test Duration
|
30 mins
|
2 hrs
|
33 mins
|
29 mins
|
Browser
|
Google Chrome
|
Google Chrome
|
Google Chrome
|
Google Chrome
|
Experienced in HRMS (Y/N)
|
Y
|
Y
|
N
|
N
|
Remuneration (Quantitative Data Analysis)
|
Time taken to generate all payment slip
|
25 seconds
|
50 seconds
|
15 seconds
|
25 seconds
|
Time taken to update payment status
|
10 seconds
|
1 minute
|
15 seconds
|
10 seconds
|
Total number of clicks to finish this module
|
3
|
5
|
5
|
5
|
Total number of question asked
|
1
|
3
|
2
|
2
|
Total number of bug found
|
0
|
0
|
0
|
0
|
Claims (Quantitative Data Analysis)
|
Time taken to submit new claims
|
2 minutes
|
1 minute
|
1 minute
|
30 seconds
|
Time taken to validate submitted claims
|
1 minute
|
20 seconds
|
30 seconds
|
20 seconds
|
Time taken to approve/ reject submitted claims
|
10 seconds
|
10 seconds
|
5 seconds
|
10 seconds
|
Time taken to view claim status
|
5 seconds
|
10 seconds
|
5 seconds
|
6 seconds
|
Time taken to generate claim slip
|
5 seconds
|
10 seconds
|
10 seconds
|
25 seconds
|
Total number of clicks to finish this module
|
17
|
16
|
18
|
17
|
Total number of question asked
|
5
|
3
|
1
|
7
|
Total number of bug found
|
2
|
0
|
1
|
1
|
Leave(Quantitative Data Analysis)
|
Time taken to apply leave
|
2 minutes
|
1 minute
|
1 minute
|
25 seconds
|
Time taken to edit leave
|
30 seconds
|
40 seconds
|
1 minute
|
35 seconds
|
Time taken to approve/reject leave
|
20 seconds
|
30 seconds
|
30 seconds
|
10 seconds
|
Time taken view leave that are being approved
|
10 seconds
|
30 seconds
|
10 seconds
|
5 seconds
|
Total number of clicks to finish this module
|
10
|
11
|
12
|
11
|
Total number of question asked
|
4
|
1
|
2
|
3
|
Total number of bug found
|
0
|
0
|
0
|
0
|
Category
|
Pilot Participant
|
Participant 1
|
Participant 2
|
Participant 3
|
Navigation/Login/Overall look
|
- Ugly layout for navigation bar
|
- Poor navigation bar where links are hard to find
- Suggest to have vertical links instead
- Suggest for navigation bar links to be clicked instead of hover
|
- Mouse-over very sensitive for the navigation bar
- Navigation bar too long
|
|
Remuneration
|
- Not a need to have prompt message for update payment status
|
- Suggest to have the Month the payslip is on to be at the top of the payslip
- Suggest to include basic pay in the pay slip
|
- Payslip description is a bit vague
- Include basic pay in pay slip
|
- Basic salary not shown in payslip
|
Claims
|
- Upload button is redundant
|
- Unclear table headings
- Unable to view claim submitted
- Incorrect naming of button of "Generate Pay Slip", it should be "Generate Claim Slip"
|
- Add or remove row button inserted at the bottom of table
- Button is wrongly named. Should be “Generate claim slip” instead
|
- Adding new row to submit another claim is not clear
- The value for the button is wrong. It should be Generate Claim slip
|
Leave
|
- Cannot find arrow on selection on calendar
- Inconsistent spelling
|
- System should calculate the number of days taken and make it more obvious
- Suggest "Confirm" button to calculate balance if leave is approved
- Radio button look like bullet point
|
- Radio button should be white when unclicked
- Page is very clustered with a lot of information
- Button size not standardize
|
- Calendar is not working properly
- Too many things cramped into one page
- Naming not good
- Button size not standardize
|