HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2018T1 analyteaka usertesting"

From IS480
Jump to navigation Jump to search
 
Line 35: Line 35:
 
| style="vertical-align:top;width:14%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:3px solid #7D5B53; "> [[IS480_Team_wiki:_2018T1_ analyteaka_usertesting | <font color="#35332E"><b>USER TESTING</b></font>]]  
 
| style="vertical-align:top;width:14%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:3px solid #7D5B53; "> [[IS480_Team_wiki:_2018T1_ analyteaka_usertesting | <font color="#35332E"><b>USER TESTING</b></font>]]  
 
| style="vertical-align:top;width:14%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_deliverables | <font color="#35332E"><b>DELIVERABLES</b></font>]]
 
| style="vertical-align:top;width:14%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_deliverables | <font color="#35332E"><b>DELIVERABLES</b></font>]]
| style="vertical-align:top;width:14.28%;" | <div style="padding: 0px; font-weight: bold font-family:Century Gothic; text-align:center; line-height: wrap_content; font-size:85%; border-bottom:1px"> [[IS480_Team_wiki:_2018T1_ analyteaka_technical | <font color="#35332E"><b>TECHNICAL DOCUMENTATION</b></font>]]
 
 
|}
 
|}
 
<!--SUB MENU-->
 
<!--SUB MENU-->

Latest revision as of 14:43, 9 October 2018

Analyteaka Header.png


HOME

ABOUT US

PROJECT OVERVIEW

PROJECT MANAGEMENT

DOCUMENTATION



Analyteaka UserTestingRound1.png
Analyteaka UserTestingRound2.png
Analyteaka UserTestingRound3.png
Analyteaka Testplan.png

Objective and Scope

User testing is conducted on every functionality that has been implemented and completed till date. The objective of testing in every iteration is to

1) identify the presence of bugs

2) any irregularities in the application that were not previously discovered by the developers in the development phase

3) user’s behaviour and expectation and

4) Accuracy of the data .


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 High Sierra (10.13.5) / Windows 10.1  
    	Browsers 
    •	Google Chrome 

Testing Procedure

The team ensure that functionalities implemented in the application are of the highest quality, by pushing codes that are tested to be working properly with the other modules. Hence, reducing the potential occurrence of bugs.

We also dedicated 1-2 days at the end of each iteration for manual final testing, locally and on Google Cloud. The team’s quality assurance will test out each module to ensure the integration was completed successfully. If bugs/errors has been identified, the quality assurance will alert the PM and update the bug-tracking excel sheet.

Testing Schedule

Integration and testing of the application occur simultaneously, allowing a more efficient, time-effective way of testing and ensuring the system isn’t broken.

Analyteaka Footer Transparent.png