Difference between revisions of "IS480 Team wiki: 2013T2 Zora Testing"
Line 1,202: | Line 1,202: | ||
!style = "width: 22%; background:#66CCCC; color:black;"|'''Feedback''' | !style = "width: 22%; background:#66CCCC; color:black;"|'''Feedback''' | ||
!style = "width: 23%; background:#66CCCC; color:black;"|'''Reason for Not Implementing''' | !style = "width: 23%; background:#66CCCC; color:black;"|'''Reason for Not Implementing''' | ||
+ | !style = "width: 23%; background:#66CCCC; color:black;"|'''Proposed Decision''' | ||
|- | |- |
Revision as of 21:56, 11 April 2014
Home | Project Overview | Project Management | Documentation | |
---|---|---|---|---|
Contents
Test Methodology
Test Plan
Test Cases
Click here to view Login/Logout Test Case file.
Click here to view Remuneration Test Case file.
Click here to view Claim Test Case file.
Click here to view Leave Test Case file.
Click here to view Training & Development Test Case file.
Click here to view Performance Management & Appraisal Test Case file.
Click here to view Administration 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
Results obtained from the evaluation conducted
User Test 1
Steps taken 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:
Category | Pilot Participant | Participant 1 | Participant 2 | Participant 3 |
---|---|---|---|---|
Navigation/Login/Overall look |
|
|
|
|
Remuneration |
|
|
|
|
Claims |
|
|
|
|
Leave |
|
|
|
|
User Test 2
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:
Category | Pilot Participant | Participant 1 | Participant 2 | Participant 3 | Participant 4 |
---|---|---|---|---|---|
Navigation/Login/Overall look |
|
|
|
|
|
Claim |
|
|
|
|
|
Leave |
|
|
|
|
|
Remuneration |
|
|
|
|
|
Performance & Appraisal |
|
|
|
|
|
System Administration |
|
|
|
|
|
Response Plan (Implement)
S/N | Functionality | Feedback | Proposed Solution | Proposed Decision |
---|---|---|---|---|
Claim | ||||
1 | Submit Claim | User tend to click "Add Claim" instead of "Submit Claim" | Will shift the "Add Claim" button to somewhere else" | Implement |
2 | validate Claim & Approve/Reject Claim | User cannot find where to view the claim receipt | Make the "view" link bigger and more distinct | Implement |
Leave | ||||
1 | Apply Leave | User is unsure of how to upload more than 1 files while applying for leave that require supporting documents | Have a short instruction before the upload file field (i.e. Hold down CTRL button to select multiple options) | Implement |
2 | Apply Leave | User is unsure of what to put in the "Date To" field to apply leave on the same day | When user selects the date in "Date From" field, the same date should be repopulated in the "Date To" field | Implement |
3 | Apply Leave/Record Leave | User tends to type the date instead of choosing the date using the datepicker leading to the wrong format being input | Have a short instruction before the "Date To" and "Date From" field to indicate the date format and give an example of it | Implement |
4 | User should be able to view leave of their colleagues in the same department so that they can plan how to cover up leave | Have a separate "View Leave" page for users to view leave of people from the same department | Make the "view" link bigger and more distinct | Implement |
Remuneration | ||||
1 | View Personal Payslip tab | User feel that it is hard to navigate to view personal payment record link when it is at the bottom | Change the arrangement for the links under remuneration tab | Implement |
2 | View payslip | User finds that the less part of the payslip can be more obvious with a "-" sign | Include the "-" sign in the PDF payslip | Implement |
3 | View payslip | Instead of month only, should include year as well in the payslip | Include the year | Implement |
Performance & Appraisal | ||||
1 | Edit Salary Increment | User does not click the "Save" button when revising the salary increment amont. As a result, the amount approved is not the revised amount. It is not obvious that the "Save" button should be clicked before submitting the form | In the event the increment value is not saved, the user should not be allowed to approve the increment request | Implement |
2 | View Scheduled Salary Increment/Scheduled Bonus | Currently the "Scheduled salary increment" and "Scheduled Bonuses" tables reside on the same page ("View Scheduled Increments/Bonus"). This can be confusing to the user as he/she is unable to distinguish between scheduled salary increments and scheduled bonuses | Change the colours of the tables to differentiate between scheduled salary increments and scheduled bonuses | Implement |
3 | Submit Appraisal | Placement of "Submit Appraisal" and "Clear" buttons. Button placements are different from other modules. Not intuitive and users may get confused | Standardize position of buttons across modules | Implement |
4 | Submit Appraisal | When an appaisal has been submitted successfully, it is not obvious to the user | Display a successful appraisal submission message | Implement |
System Administration | ||||
1 | Manage Leave | Change default no. of leave --> User unsure of change is successful cos there is no popup or anything | Display a successful update message | Implement |
2 | Create/Edit Profile | Remind the user the DOB format to type. User unsure of what to type. The date thing also must select super long ago. super troublesome for them | Display a date format beside the field | Implement |
Navigation | ||||
1 | Navigation | In the navigation bar, users tend to click on menu items which display sub-menus, this results in the menu options being minimize. Selection of sub-menu items require users to hover over the main menu items and then clicking the sub-menus items | Enable the navigation bar to support both hover and click functionality. In both instances, the sub-menu will be displayed and the menu will not be minimized | Implement |
Login | ||||
1 | Error message | Error message for login is black in colour | Error message for login should be red in colour | Implement |
2 | Active status | Account with inactive status can login | Account with inactive status should not be able login | Implement |
Changes made from User Test 2 Feedbacks | |||
---|---|---|---|
Claims | |||
Leave | |||
Remuneration | |||
Performance Management & Appraisal |
Quantitative Feedback Analysis | ||
---|---|---|
Ease of Use | ||
Overall Layout |
User Test 2 Analysis |
---|
Response Plan (Not Implementing)
S/N | Functionality | Feedback | Reason for Not Implementing | Proposed Decision |
---|---|---|---|---|
Leave | ||||
1 | Approve/Reject Leave | People in the department should have the authority of approving/rejecting the leave the user sends | The sponsor of the project mentioned that the line manager should be the only one approving. He should know if anyone in the department rejects to that particular leave on a particular day in case of any project that arises. Hence, according to the business logic, only the line manager should have the authority to approve/reject leave | Not Implementing |
2 | Apply Leave | User takes quite a while to find the leave balance on the "Apply Leave" page | As the task instruction explicitly mention to the tester to check on the leave balance, tester might not know that it can be checked in the "Apply Leave" page. Moreover, it is only 1 out of 5 of the user that mentioned that. However, everyone eventually managed to find the leave balance when they are applying leave | Not Implementing |
Remuneration | ||||
1 | Payslip | Suggestion: For payslip, put signature and date | The payslip is followed closely to the current payslip that the company is using | Not Implementing |
Performance & Appraisal | ||||
1 | Create/Edit Profile | User should have the option to edit Appraisal once submitted | Client explicitly mentioned that Appraisals should not be edited once submitted | Not Implementing |