HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2013T2 GENShYFT Documentation User"

From IS480
Jump to navigation Jump to search
Line 41: Line 41:
 
| style="padding:0.4em; font-size:150%; background-color:#FFFFFF;  border-bottom:4px solid #2f2929; border-top:5px solid #2f2929; text-align:center; color:#828282" width="10%" | [[IS480_Team_wiki:_2013T2_GENShYFT_Documentation_proto  | <font color="#000000" size=2><b>Prototype</b></font>]]
 
| style="padding:0.4em; font-size:150%; background-color:#FFFFFF;  border-bottom:4px solid #2f2929; border-top:5px solid #2f2929; text-align:center; color:#828282" width="10%" | [[IS480_Team_wiki:_2013T2_GENShYFT_Documentation_proto  | <font color="#000000" size=2><b>Prototype</b></font>]]
  
|}
+
|}<br />
 +
<br />
 +
=Regression Test=
 +
Adhering to the advice given by reviewers during Mid Term Review, we leveraged on the Automated Testing capabilities of Singpath and further extended it.<br /><br />
 +
 
 +
Although there are many different ways to implement the scripts for automated testing, we have decided on the one that is the most cost-effective in terms of resources required - E2E test<br />
 +
<br />
 +
 
 +
'''Automated E2E Tests'''<br />
 +
 
 +
As our features in Singpath is already on the Live Server since Mid Terms, our development work may affect the existing codes and the most obvious indication that Singpath broke is not so much on the logic, but the view/display layer (User Interface). <br />
 +
<br />
 +
To the end users, the pages will simply not load/show if there is something wrong with our code, to address that issue, we have specifically zeroed in to write additional test scripts to cover all of our pages.<br />
 +
<br />
 +
How it works is that the test scripts are written into a file within the application, and will be executed when it is sent to Travis CI, a distributed continuous integration service used to build and test projects hosted at GitHub, which is the repository that we have been using for the development of Singpath. <br />
 +
 
 +
Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to build the project and run tests.  Travis CI will also build and run pull requests. When that process has completed, it will notify a developer in the way it has been configured to do so[6] — for example, by sending an email containing the test results (showing success or failure). <br />
 +
 
 +
What this means is that every time we commit and send a pull request, the test script is run automatically and we will be shown a result whether something in our new codes 'broke' the application. With this, we are confident to say that every time we push new changes to the live site, the view/display layer will always render.
  
 
<br/>
 
<br/>
<font size="3">
+
=User Testing=
===<div style="background: #000000; padding: 15px; font-weight: bold; line-height: 0.3em"><font color= #FFFFFF>User Testing</font></div>===
 
 
<!--Please click [[Media:GENShYFT Test Plan 140221.pdf|here]] for our Test Plan.<br />-->
 
<!--Please click [[Media:GENShYFT Test Plan 140221.pdf|here]] for our Test Plan.<br />-->
  
Line 94: Line 111:
 
|
 
|
 
|[[Media:GENShYFT_Observations.pdf|Observations]]<br />
 
|[[Media:GENShYFT_Observations.pdf|Observations]]<br />
[[Media:GENShYFT_SecSchSurveyResults.pdf|Sec Sch Post Tournament Survey Results]]<br />
+
Sec Sch Post Tournament Survey<br />
 +
Unable to administer survey; require clearance by sponsor IDA<br /><br />
 
Tournament proceeded smoothly without hiccups
 
Tournament proceeded smoothly without hiccups
 
|-
 
|-

Revision as of 10:27, 13 April 2014

GENShYFT IS480 1314 Logo.jpg


Home   Project Overview   Project Management   Documentation   The Team


Overview   Diagrams   User Testing   Presentation   Prototype



Regression Test

Adhering to the advice given by reviewers during Mid Term Review, we leveraged on the Automated Testing capabilities of Singpath and further extended it.

Although there are many different ways to implement the scripts for automated testing, we have decided on the one that is the most cost-effective in terms of resources required - E2E test

Automated E2E Tests

As our features in Singpath is already on the Live Server since Mid Terms, our development work may affect the existing codes and the most obvious indication that Singpath broke is not so much on the logic, but the view/display layer (User Interface).

To the end users, the pages will simply not load/show if there is something wrong with our code, to address that issue, we have specifically zeroed in to write additional test scripts to cover all of our pages.

How it works is that the test scripts are written into a file within the application, and will be executed when it is sent to Travis CI, a distributed continuous integration service used to build and test projects hosted at GitHub, which is the repository that we have been using for the development of Singpath.

Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to build the project and run tests. Travis CI will also build and run pull requests. When that process has completed, it will notify a developer in the way it has been configured to do so[6] — for example, by sending an email containing the test results (showing success or failure).

What this means is that every time we commit and send a pull request, the test script is run automatically and we will be shown a result whether something in our new codes 'broke' the application. With this, we are confident to say that every time we push new changes to the live site, the view/display layer will always render.


User Testing

Method Details Documents Results
Lab Experiment

Heuristic Evaluation

Date: 11/2/2014

Participants: 15
Location: SMU SIS GSR 2-5
Objective: Functionality Test and Heuristic Evaluation
Photo Gallery

Tester's Package A
Tester's Package B
Script
Heuristic Evaluation
Questionnaire
Observer's Guide

UAT 1 & HE 1 Test Results

Field Study

Sample Survey

Date: 19/3/2014

In-class Tournament Held [Real Life Use Case]
Participants: 30
Location: SMU SIS SR 3-2 (IS429 Week 11 Class)
Objective: Load Test to ensure Singpath can handle an entire class of concurrent users
[Pictures here!]

Observations

Observation - Load Test Successful

Field Study Date: 21/3/2014

Actual Tournament Held [Real Life Use Case]
Participants: 20 Secondary School students (Actual Users)
Location: SMU SIS SR 2-1
Objective: Field Study to observe users interaction with Singpath in an uncontrolled environment
[Pictures here!] Part 1
[Pictures here!] Part 2

Observations

Sec Sch Post Tournament Survey
Unable to administer survey; require clearance by sponsor IDA

Tournament proceeded smoothly without hiccups

Field Study

Judgement Study
Sample Survey

Date: 29/3/2014

Actual Tournament Held [Real Life Use Case]
Participants: 35 JC/High School Students (Actual Users)
Location: SMU SIS SR 2-1
Objective: Field Study to observe users interaction with Singpath in an uncontrolled environment
[Pictures here!]

Observations

JC Post Tournament Survey Results
Tournament proceeded smoothly without hiccups

Field Study

Judgement Study
Sample Survey

Date: 29/3/2014

Actual Tournament Held [Real Life Use Case]
Participants: 29 Poly Students (Actual Users)
Location: SMU SIS SR 2-1
Objective: Field Study to observe users interaction with Singpath in an uncontrolled environment
[Pictures here!]

Observations

Poly Post Tournament Survey Results
Tournament proceeded smoothly without hiccups