Difference between revisions of "IS480 Team wiki: 2017T1 Codezilla Documentation UserTesting"
(2 intermediate revisions by the same user not shown) | |||
Line 32: | Line 32: | ||
[[File:usertestingspace.png|800px|center]] <br> | [[File:usertestingspace.png|800px|center]] <br> | ||
− | == Testing Proceedures == | + | =<div style="background:#000080; padding: 15px; font-weight: bold; line-height: 0.3em; font-size:16px; font-family:helvetica"><font color= #FFFFFF>Testing Proceedures</font></div>= |
+ | <br> | ||
+ | ===<div style="background:#36c; padding: 15px; font-weight: bold; line-height: 0.3em; font-size:16px; font-family:helvetica"><font color= #FFFFFF>Test Objectives and Scope</font></div>=== | ||
=== Testing Objectives and Scope === | === Testing Objectives and Scope === | ||
In every sprint, Team Codezilla conducts testing on every functionality being developed. The aim of ensuring we conduct thorough testing in every sprint is to identify any bugs present. To ensure performance consistency over different platforms, we conduct application testing on the following operating systems and browsers: | In every sprint, Team Codezilla conducts testing on every functionality being developed. The aim of ensuring we conduct thorough testing in every sprint is to identify any bugs present. To ensure performance consistency over different platforms, we conduct application testing on the following operating systems and browsers: | ||
Line 41: | Line 43: | ||
**Google Chrome | **Google Chrome | ||
**Safari | **Safari | ||
− | === Testing Process === | + | ===<div style="background:#36c; padding: 15px; font-weight: bold; line-height: 0.3em; font-size:16px; font-family:helvetica"><font color= #FFFFFF>Testing Process</font></div>=== |
[[File:Codezilla_testplan.png|800px|center]] <br> | [[File:Codezilla_testplan.png|800px|center]] <br> | ||
− | == User Testing 1 | + | <b>Test Cases Created:</b> |
+ | <b>[[Media:codezillatestcase.docx|Our Test Cases]]</b> <br> | ||
+ | =<div style="background:#000080; padding: 15px; font-weight: bold; line-height: 0.3em; font-size:16px; font-family:helvetica"><font color= #FFFFFF>User Testing 1</font></div>= | ||
=== Test Plan === | === Test Plan === | ||
<p> | <p> | ||
Line 91: | Line 95: | ||
<br> | <br> | ||
− | == User Testing 2 | + | =<div style="background:#000080; padding: 15px; font-weight: bold; line-height: 0.3em; font-size:16px; font-family:helvetica"><font color= #FFFFFF>User Testing 2</font></div>= |
=== Test Plan === | === Test Plan === | ||
<p> | <p> | ||
Line 131: | Line 135: | ||
<br> | <br> | ||
− | == User Testing 3 | + | =<div style="background:#000080; padding: 15px; font-weight: bold; line-height: 0.3em; font-size:16px; font-family:helvetica"><font color= #FFFFFF>User Testing 3</font></div>= |
=== Test Plan === | === Test Plan === | ||
<b>Venue:</b> SMU SOL GSR B1-10<br/> | <b>Venue:</b> SMU SOL GSR B1-10<br/> | ||
Line 171: | Line 175: | ||
[[File:codezillauat3changes.png|800px|center]] | [[File:codezillauat3changes.png|800px|center]] | ||
<br> | <br> | ||
− | + | =<div style="background:#000080; padding: 15px; font-weight: bold; line-height: 0.3em; font-size:16px; font-family:helvetica"><font color= #FFFFFF>User Testing 4</font></div>= | |
− | == User Testing 4 | ||
=== Test Plan === | === Test Plan === | ||
<b>Venue:</b> SMU SOL GSR B1-12<br/> | <b>Venue:</b> SMU SOL GSR B1-12<br/> |
Latest revision as of 04:22, 26 November 2017
Testing Proceedures
Test Objectives and Scope
Testing Objectives and Scope
In every sprint, Team Codezilla conducts testing on every functionality being developed. The aim of ensuring we conduct thorough testing in every sprint is to identify any bugs present. To ensure performance consistency over different platforms, we conduct application testing on the following operating systems and browsers:
- Operating Systems
- Windows 10.1
- Mac OS X EI Capitan (10.11.3)
- Browsers Used
- Google Chrome
- Safari
Testing Process
Test Cases Created:
Our Test Cases
User Testing 1
Test Plan
Venue: SMU SIS GSR 2-2
Date: 03 August 2017
Time: 7:30PM
Duration: About 30 minutes per user
Number of Participants: 4
Roles Involved: Project Owner and Resource Offeror
Scope:
- Account Module
- Project Module
- Resource Module
- Search Module
User Test for Project Owner:
Project Owner
User Test for Resource Offeror:
Resource Offeror
Objectives
- To look at the feedback with regards to our User Interface
- To understand any usability problems in the account module, project/ resource module and search modules by observing their behavior
- To improve the account module, project/ resource module and search modules for the web application
Procedures
Participants were given user test instructions based on their profiles. As they go through the tasks, participants are to think aloud while Team Codezilla records down their observations and behaviours. To conclude the session, Team Codezilla will ask questions with regards to their thought process as they navigated through the ImpactLaunch.Space web application.
Key Findings
Overall Results/Comments
- There were several minor issues that could make the process of creating an account and a profile easier
- Users were impressed with the clean user interface and color scheme, as it was easy to navigate and use
- Client was satisfied with the progress made by the Team Codezilla
User Testing 2
Test Plan
Venue: SMU SOL GSR B1-10
Date: 06 October 2017
Time: 11:00AM
Duration: About 30 minutes per user
Number of Participants: 8
Roles Involved: Project Owner and Resource Offeror
Scope:
- Account Module
- Project Request Module
- Resource Request Module
- Project Management Module 1 and 2
User Test for Project Owner:
Project Owner
User Test for Resource Offeror:
Resource Offeror
Objectives
- To look at the feedback with regards to our User Interface for the project management module
- To understand any usability problems for the pledging of resource to projects and the use of the project management space observing their behavior
- To improve the ease of pledging resources to projects and use of the project management space in our web application
Procedures
Participants were given user test instructions based on their profiles. As they go through the tasks, participants are to think aloud while Team Codezilla records down their observations and behaviours. To conclude the session, Team Codezilla will ask questions with regards to their thought process as they navigated through the ImpactLaunch.Space web application.
Key Findings
Overall Results/Comments
- Users were impressed with the clean user interface and color scheme, as it was easy to navigate and use
- Improvement in timing for login and profile creation (Account Module) from UAT1 to UAT2
- Client was satisfied with the progress made by the Team Codezilla, especially for the project management space
User Testing 3
Test Plan
Venue: SMU SOL GSR B1-10
Date: 28 October 2017
Time: 07:00PM
Duration: About 30 minutes per user
Number of Participants: 16
Roles Involved: Project Creator, Volunteer, Administrator
Scope:
- Project Management Module 1 and 2
- Project Matching Module
- Analytics Module
- Administrative Module
User Test for Project creator:
Project Creator
User Test for Volunteer:
Volunteer
User Test for Administrator:
Administrator
Objectives
- To look at the feedback with regards to our User Interface for the admin, analytics, project matching and project management module
- To understand any usability problems for the admin, analytics, project matching and project management module and observing their behavior
- To improve the ease of using the admin, analytics, project matching and project management module in our web application
Procedures
Participants were given user test instructions based on their profiles. As they go through the tasks, participants are to think aloud while Team Codezilla records down their observations and behaviours. To conclude the session, Team Codezilla will ask questions with regards to their thought process as they navigated through the ImpactLaunch.Space web application.
Key Findings
Overall Results/Comments
- Users were impressed with the clean user interface and color scheme, as it was easy to navigate and use
- There is still room for improvement with regards to the project management space.
- Client was satisfied with the progress made by the Team Codezilla. They especially liked the analytics dashboard.
User Testing 4
Test Plan
Venue: SMU SOL GSR B1-12
Date: 09 November 2017
Time: 07:00PM
Duration: About 30 minutes per user
Number of Participants: 16
Roles Involved: Project Creator, Volunteer
Scope:
- Feedback and Ratings Module
- Communications Module
- Project Management Modules 1 and 2
User Test for Project creator:
Project Creator
User Test for Volunteer:
Volunteer
Objectives
- To look at the feedback with regards to our User Interface for the Feedback and Ratings, and Communications module
- To understand any usability problems for the Feedback and Ratings, and Communications module and observing their behaviour
- To improve the ease of using the Feedback and Ratings, and Communications module in our web application
Procedures
Participants were given user test instructions based on their profiles. As they go through the tasks, participants are to think aloud while Team Codezilla records down their observations and behaviours. To conclude the session, Team Codezilla will ask questions with regards to their thought process as they navigated through the ImpactLaunch.Space web application.
Key Findings
Overall Results/Comments
- Users were impressed with the clean user interface and color scheme, as it was easy to navigate and use
- Client was satisfied with the progress made by the Team Codezilla.