HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T2 box.us Test Plans"

From IS480
Jump to navigation Jump to search
 
(27 intermediate revisions by 3 users not shown)
Line 57: Line 57:
  
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 80%;"><span style="color: White"> '''User Acceptance Test'''  </span></div></p>=
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 80%;"><span style="color: White"> '''User Acceptance Test'''  </span></div></p>=
'''Expected User Acceptance:''' 5 April 2013
+
'''User Acceptance:''' 5 April 2013
 +
'''User Acceptance Final Verification:''' 12 April 2013
 +
<br/>
  
 
'''User Acceptance Test Plan'''
 
'''User Acceptance Test Plan'''
* Test Cases:  
+
* Test Cases (5 April 2013):  
# [[Media:UAT-NPO-.xls | Test Cases for NPO users]]
+
# [[Media:UAT-NPO-.xls | Test Cases - NPO]]
# [[Media:UAT-VOL-.xls | Test Cases for Volunteer users]]
+
# [[Media:UAT-VOL-.xls | Test Cases - Volunteer]]
# [[Media:UAT-Empact-.xls| Test Cases for Empact users]]
+
# [[Media:UAT-Empact-.xls| Test Cases - Empact]]
* Briefing Script
+
 
 +
* Test Cases (12 April 2013):
 +
# [[Media:EMUAT-Final_Verification-.xls | Test Cases for UAT final verificiation]]
 +
 
 +
* Scenario-based Instructions and Exceptional cases
 +
# [[Media:Scenarios-Based Instructions (Registration).docx | Registration]]
 +
# [[Media:Scenario-Based Instructions (Task).docx | Task]]
 +
# [[Media:Scenario-Based Instructions (Questions).docx | Question]]
 +
# [[Media:Execeptional Cases.docx | Exceptional Cases]]
 +
 
 
* UAT Issue List
 
* UAT Issue List
 
#[https://docs.google.com/spreadsheet/ccc?key=0AkfA68G0St4NdHRXbWJlRC1sVnJpVFBUcXFlLW1pQUE&usp=sharing UAT Issue List Google Spreadsheet(http://www.bit.ly/UATIssueList]
 
#[https://docs.google.com/spreadsheet/ccc?key=0AkfA68G0St4NdHRXbWJlRC1sVnJpVFBUcXFlLW1pQUE&usp=sharing UAT Issue List Google Spreadsheet(http://www.bit.ly/UATIssueList]
#[https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdGVwbjgwVUg0WUxsYTF6MnN0UzVXY2c&usp=sharing UAT Pilot Test Issue List]
+
 
 +
{|align="center"
 +
|[[Image:BOXUSUAT.jpg|500px|Version 2]]
 +
|}
 +
 
 +
 
 +
 
 +
<b>Managing Defects</b><br/>
 +
 
 +
{|align="center"
 +
|[[Image:Boxus_UAT_Defect_Lifecycle.png|500px|UAT Defect Lifecycle]]
 +
|}
 +
 
 +
*Note: BA refers to the facilitators in the UAT test
 +
* All defects are highlighted onto a separate issue list.
 +
* The list is collated and sent to Empact to prioritise based on issues.
 +
* Bugs are fixed immediately
 +
 
 +
<b>Recording Issues</b><br/>
 +
 
 +
Issues are recorded in a separate issue list on [https://docs.google.com/spreadsheet/ccc?key=0AkfA68G0St4NdHRXbWJlRC1sVnJpVFBUcXFlLW1pQUE#gid=0 Google Docs]
  
  
Line 75: Line 106:
 
* [http://austin.iiba.org/download/utp.doc User Acceptance Test Plan Template]
 
* [http://austin.iiba.org/download/utp.doc User Acceptance Test Plan Template]
 
* [http://www.batimes.com/articles/uat-tips-and-templates.html Soft-side of UAT]
 
* [http://www.batimes.com/articles/uat-tips-and-templates.html Soft-side of UAT]
 +
 +
== Pre-UAT Testing ==
 +
 +
 +
 +
'''Pre-UAT Testing 1'''
 +
*[https://wiki.smu.edu.sg/is480/Image:BoxusUAtttt-VOL-.xls Pre-UAT Volunteer Testing 1]
 +
*[https://wiki.smu.edu.sg/is480/Image:BoxUSEMPACTT.xls Pre-UAT Empact Testing 1]
 +
*[https://wiki.smu.edu.sg/is480/Image:BoxusUAT-NPO-.xls Pre-UAT NPO Testing 1]
 +
 +
'''Pre-UAT Testing 2'''
 +
*[https://wiki.smu.edu.sg/is480/Image:Part2UAT-VOL-.xls Pre-UAT Volunteer Testing 2]
 +
*[https://wiki.smu.edu.sg/is480/Image:Part2UAT-Empact-.xls Pre-UAT Empact Testing 2]
 +
*[https://wiki.smu.edu.sg/is480/Image:Part2UAT-NPO-.xls Pre-UAT NPO Testing 2]
 +
 +
'''Pre-UAT Testing 3'''
 +
*[https://wiki.smu.edu.sg/is480/Image:UAT-Final_Verficiation-.xls Pre-UAT Testing(Failed cases only)]
  
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 80%;"><span style="color: White"> '''Deployment Testing'''  </span></div></p>=
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 80%;"><span style="color: White"> '''Deployment Testing'''  </span></div></p>=
  
 +
[[Image:Boxus_Deployment_Plan.png |500px|Deployment Plan]] <br/>
 
We have deployed our system to the live server since 11th of March 2013!
 
We have deployed our system to the live server since 11th of March 2013!
 
{| class="wikitable centered"
 
{| class="wikitable centered"
Line 89: Line 138:
 
Release 0.1
 
Release 0.1
 
|style="vertical-align:text-top"|
 
|style="vertical-align:text-top"|
Task Management
+
*Task Management
User Management  
+
*User Management  
Questions
+
*Questions
Feedback Form
+
*Feedback Form
Dashboard(NPO)
+
*Dashboard(NPO)
  
 
|-
 
|-
Line 101: Line 150:
 
Release 0.2
 
Release 0.2
 
|style="vertical-align:text-top"|
 
|style="vertical-align:text-top"|
Task Management
+
*Task Management
User Management(partial)  
+
*User Management(partial)  
Questions
+
*Questions
Dashboard
+
*Dashboard
Statistics
+
*Statistics
Improvements from Release 0.1
+
*Improvements from Release 0.1
  
 
|-
 
|-
Line 114: Line 163:
 
Release 0.3
 
Release 0.3
 
|style="vertical-align:text-top"|
 
|style="vertical-align:text-top"|
Task Management
+
*Task Management
User Management(partial)  
+
*User Management(partial)  
Questions
+
*Questions
Notifications
+
*Notifications
Improvements from Release 0.2
+
*Improvements from Release 0.2
  
 
|-
 
|-
 
|style="vertical-align:text-top"|
 
|style="vertical-align:text-top"|
04/04/2013
+
02/04/2013
 
|style="vertical-align:text-top"|
 
|style="vertical-align:text-top"|
 
Release 0.4
 
Release 0.4
 
|style="vertical-align:text-top"|
 
|style="vertical-align:text-top"|
All features released
+
*All features released
Improvements from Release 0.3
+
*Improvements from Release 0.3
  
 
|-
 
|-
 
|style="vertical-align:text-top"|
 
|style="vertical-align:text-top"|
04/04/2013
+
11/04/2013
 
|style="vertical-align:text-top"|
 
|style="vertical-align:text-top"|
 
Release 0.5
 
Release 0.5
 
|style="vertical-align:text-top"|
 
|style="vertical-align:text-top"|
Final version for Final Verification
+
*Final version for Final Verification
Improvements from Release 0.4
+
*Improvements from Release 0.4
  
 
|-
 
|-
 
|}
 
|}
 +
 +
'''Collated Issues From All Deployments''': [[Media:BoxusIssuesReleasees.xlsx | Collated Deployment Testing Issues]]
  
 
'''Deployment testing 1'''
 
'''Deployment testing 1'''
Line 209: Line 260:
 
*[https://wiki.smu.edu.sg/is480/Image:-box.us-_Iteration_10_Integration_test_%28NPO%29.docx Integration Testing for Iteration 10 - NPO View]
 
*[https://wiki.smu.edu.sg/is480/Image:-box.us-_Iteration_10_Integration_test_%28NPO%29.docx Integration Testing for Iteration 10 - NPO View]
  
 +
'''Iteration 11-14''': Testings are done as deployment testing
  
 
'''Bug Log'''
 
'''Bug Log'''
*[https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdFh6eXB3VmtpYmljVGN2Y19oajdtRWc Bug Log(Google Docs)]
+
*[https://docs.google.com/spreadsheet/ccc?key=0AsGBoq64IRhgdFh6eXB3VmtpYmljVGN2Y19oajdtRWc#gid=3 Bug Log(Google Docs)]
  
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 80%;"><span style="color: White"> '''Heuristic Evaluation'''  </span></div></p>=
 
=<p><div class="NavHead" style="background-color:#2F55A4;-moz-border-radius:4px; text-align: left; padding: 5px; font-size: 80%;"><span style="color: White"> '''Heuristic Evaluation'''  </span></div></p>=
Line 333: Line 385:
 
{| border="0"
 
{| border="0"
 
|width="500px" padding="20px"|  
 
|width="500px" padding="20px"|  
[[Image:UT2_Photo.jpg|600px|UT 2 Photo]]
+
[[Image:Box.usUT2.jpg|480px|User Test 1]]
 
|width="500px" padding="20px"|  
 
|width="500px" padding="20px"|  
We conducted our 2nd User Testing with the future users of the Volunteer Matching system. <br/>
+
We conducted our 2nd user testing to try out our newly added features and at to see how users would respond to them. <br/>
 
 
'''User's feedback'''
 
# "Generally easy to use"
 
# "Can be more user-centric instead of Empact-centric"
 
# "Clean interface"
 
  
'''For Further Actions'''
+
'''Interesting Findings'''
# Refer to UT2 Follow Up Action.
+
# Users thought changing email and password is inside profile
  
 +
'''Actions Taken'''
 +
# Success Messages to be more descriptive
 +
# Clearer images used for buttons
 +
# Login button to be near the sign up button
 +
# Refer to UT2 follow up actions
 
<br/>
 
<br/>
  
Line 351: Line 403:
 
|width="500px" padding="20px"|  
 
|width="500px" padding="20px"|  
 
|}
 
|}
 
  
  

Latest revision as of 14:08, 22 April 2013

degree=90
HOME   PROJECT OVERVIEW     PROJECT MANAGEMENT   DOCUMENTATION  
         

User Acceptance: 5 April 2013 User Acceptance Final Verification: 12 April 2013

User Acceptance Test Plan

  • Test Cases (5 April 2013):
  1. Test Cases - NPO
  2. Test Cases - Volunteer
  3. Test Cases - Empact
  • Test Cases (12 April 2013):
  1. Test Cases for UAT final verificiation
  • Scenario-based Instructions and Exceptional cases
  1. Registration
  2. Task
  3. Question
  4. Exceptional Cases
  • UAT Issue List
  1. UAT Issue List Google Spreadsheet(http://www.bit.ly/UATIssueList
Version 2


Managing Defects

UAT Defect Lifecycle
  • Note: BA refers to the facilitators in the UAT test
  • All defects are highlighted onto a separate issue list.
  • The list is collated and sent to Empact to prioritise based on issues.
  • Bugs are fixed immediately

Recording Issues

Issues are recorded in a separate issue list on Google Docs


Resources

Pre-UAT Testing

Pre-UAT Testing 1

Pre-UAT Testing 2

Pre-UAT Testing 3

Deployment Plan
We have deployed our system to the live server since 11th of March 2013!

Date Description Features Released

11/03/2013

Release 0.1

  • Task Management
  • User Management
  • Questions
  • Feedback Form
  • Dashboard(NPO)

18/03/2013

Release 0.2

  • Task Management
  • User Management(partial)
  • Questions
  • Dashboard
  • Statistics
  • Improvements from Release 0.1

25/03/2013

Release 0.3

  • Task Management
  • User Management(partial)
  • Questions
  • Notifications
  • Improvements from Release 0.2

02/04/2013

Release 0.4

  • All features released
  • Improvements from Release 0.3

11/04/2013

Release 0.5

  • Final version for Final Verification
  • Improvements from Release 0.4

Collated Issues From All Deployments: Collated Deployment Testing Issues

Deployment testing 1

Deployment testing 2

Deployment testing 3

Deployment testing 4

Deployment testing 5

Testing will be done at the end of every iterations with the use of test cases. If there is any bugs found during the testing, it will be logged in the Bug Log.

Iteration 4


Iteration 5


Iteration 6


Iteration 7


Iteration 8


Pre User Testing 1 Integration Testing (Iteration 9)


Iteration 9


Iteration 10

Iteration 11-14: Testings are done as deployment testing

Bug Log

We will be inviting our SIS experts to help us critique the usability issues in our Web application!


Heuristic evaluations will follow the How to Conduct a Heuristic Evaluation and Ten Usability Heuristics readings by Jakob Nielsen.

Using Nielsen's ten heuristics, evaluators will list as many usability issues as possible. It is less important that the evaluators worry about exactly which heuristic the usability issues occur in.

The heuristics are there to help evaluators find a variety of different types of usability issues. For each usability issue found, the evaluator should capture a description of the issue written as concisely and as specifically as possible.


We are also using Nielsen' Severity Ratings for Usability Problems in our Heuristic Evaluation.


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


Heuristic Evaluation 1

Heuristics Evaluation 1

We conducted our 1st Heuristic Evaluation where we get our SIS experts, that is those who have taken or are currently taking Interaction Design and Prototyping (IS306) to critique and evaluate the usability issues of our web application.

User's feedback

  1. "Log in was easy"
  2. "More confirmation message needed"
  3. "Question UI is good"
  4. "It can be even more intuitive"

For Further Actions

  1. Based on UT2 Follow Up Actions



Documentation for Heuristic Evaluation

Documentation Results Followup Actions


  • As our UT2 was held a few days after our midterms presentation, we have decided to tackle all the usability issues in our UT2 Follow Up Actions.

We conduct user testing to see how do our stakeholders respond to the application that we have built.

User Test 2

User Test 1

We conducted our 2nd user testing to try out our newly added features and at to see how users would respond to them.

Interesting Findings

  1. Users thought changing email and password is inside profile

Actions Taken

  1. Success Messages to be more descriptive
  2. Clearer images used for buttons
  3. Login button to be near the sign up button
  4. Refer to UT2 follow up actions




Documentation for User Test 2

For User Test 2, we made use of templates taken from Usability.gov.

The web provides us with good information regarding user testing!

Documentation Results Followup Actions


User Test 1

User Test 1

We conducted our 1st user testing to try out the new features and at the same time to also test how would the users respond to the system. Until then, there was no information about how would the different users react to the system.

Interesting Findings

  1. Questions module was not intuitive enough
  2. Task matching results could displayed in a more interactive way

Actions Taken

  1. Touched up Question module
  2. Finalized a user interface template
  3. Revamped the entire structure of how the Task module was being managed.



Documentation for User Test 1

Documentation Results Followup Actions