Difference between revisions of "IS480 Team wiki:2017T1 Ducky King User Testing 1"
Tcgan.2015 (talk | contribs) |
Tcgan.2015 (talk | contribs) (→UAT 3) |
||
(19 intermediate revisions by 4 users not shown) | |||
Line 34: | Line 34: | ||
{| style="background-color:white; text-transform: uppercase; font-size:14px; font-weight: bold; text-align:center; padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0" | | {| style="background-color:white; text-transform: uppercase; font-size:14px; font-weight: bold; text-align:center; padding: 5px 0 0 0;" width="100%" height=50px cellspacing="0" cellpadding="0" valign="top" border="0" | | ||
− | | style="vertical-align:top;width: | + | | style="vertical-align:top;width:15.28%;" | <div style="padding: 3px;line-height: wrap_content; border-bottom:1px dashed #FF7505; font-family:helvetica"> [[IS480_Team_wiki:2017T1 Ducky King Personas and Scenario | <font color =#FF7505><b>Personas & Scenarios</b></font>]] |
− | | style="vertical-align:top;width: | + | | style="vertical-align:top;width:11.28%;" | <div style="padding: 3px;line-height: wrap_content; border-bottom:1px dashed #FF7505; font-family:helvetica"> [[IS480_Team_wiki:2017T1 Ducky King Diagrams | <font color =#FF7505><b>Diagrams</b></font>]] |
− | | style="vertical-align:top;width: | + | | style="vertical-align:top;width:14.28%;" | <div style="padding: 3px;line-height: wrap_content; border-bottom:1px dashed #FF7505; font-family:helvetica"> [[IS480_Team_wiki:2017T1 Ducky King Meeting Minutes | <font color =#FF7505><b>Meeting Minutes</b></font>]] |
− | | style="vertical-align:top;width: | + | | style="vertical-align:top;width:11.28%;" | <div style="padding: 3px;line-height: wrap_content; border-bottom:1px dashed #FF7505; font-family:helvetica"> [[IS480_Team_wiki:2017T1 Ducky King Technology | <font color =#FF7505><b>Technology</b></font>]] |
<!-- Current Page --> | <!-- Current Page --> | ||
− | | style="vertical-align:top;width: | + | | style="vertical-align:top;width:14.28%;" | <div style="padding: 3px;line-height: wrap_content; border-bottom:5px solid #FF7505; font-family:helvetica"> [[IS480_Team_wiki:2017T1 Ducky King User Testing| <font color =#535353><b>User Testing</b></font>]] |
− | | style="vertical-align:top;width: | + | | style="vertical-align:top;width:15.28%;" | <div style="padding: 3px; font-weight: bold; text-align:center; line-height: wrap_content; border-bottom:1px dashed #FF7505; font-family:helvetica"> [[IS480_Team_wiki:2017T1 Ducky King Project Deliverables | <font color =#FF7505><b>Project Deliverables</b></font>]] |
+ | |} | ||
− | |||
<!--Sub Header End--> | <!--Sub Header End--> | ||
Line 54: | Line 54: | ||
| style="vertical-align:top;width:25%;" | <div style="padding: 3px;line-height: wrap_content; border-bottom:1px dashed #FF7505; font-family:helvetica"> [[IS480_Team_wiki:2017T1 Ducky King User Testing| <font color =#FF7505><b>Internal Testing</b></font>]] | | style="vertical-align:top;width:25%;" | <div style="padding: 3px;line-height: wrap_content; border-bottom:1px dashed #FF7505; font-family:helvetica"> [[IS480_Team_wiki:2017T1 Ducky King User Testing| <font color =#FF7505><b>Internal Testing</b></font>]] | ||
− | | style="vertical-align:top;width:25%;" | <div style="padding: 3px; line-height: wrap_content; border-bottom:5px solid #FF7505; font-family:helvetica"> [[IS480_Team_wiki:2017T1 Ducky King User Testing 1 |<font color =#535353><b> | + | | style="vertical-align:top;width:25%;" | <div style="padding: 3px; line-height: wrap_content; border-bottom:5px solid #FF7505; font-family:helvetica"> [[IS480_Team_wiki:2017T1 Ducky King User Testing 1 |<font color =#535353><b>FlowLabs Middleware</b></font>]] |
+ | |||
+ | | style="vertical-align:top;width:25%;" | <div style="padding: 3px;line-height: wrap_content; border-bottom:1px dashed #FF7505; font-family:helvetica"> [[IS480_Team_wiki:2017T1 Ducky King User Testing 2| <font color =#FF7505><b>FlowAdmin</b></font>]] | ||
|} | |} | ||
− | == | + | <br> |
+ | [[File:FlowAdmin UAT Header.png|center]] | ||
+ | <br> | ||
+ | |||
+ | == <div style="background: #FF7504; padding: 15px; font-weight: bold; line-height: 0.3em; font-size:18px; font-family:helvetica" ><font color= #FFFFFF>UAT 1</font></div> == | ||
+ | |||
=== Test Plan === | === Test Plan === | ||
− | <div style="font-family: Verdana; | + | <div style="font-family: Verdana;"> |
<p> | <p> | ||
<b>Venue:</b> Flow Labs Office @ 165 Telok Ayer Street<br/> | <b>Venue:</b> Flow Labs Office @ 165 Telok Ayer Street<br/> | ||
Line 72: | Line 79: | ||
=== Objectives=== | === Objectives=== | ||
− | <div style="font-family: Verdana; | + | <div style="font-family: Verdana;> |
<p> | <p> | ||
<ul> | <ul> | ||
Line 82: | Line 89: | ||
=== Scope of UAT 1=== | === Scope of UAT 1=== | ||
− | <div style="font-family: Verdana; | + | <div style="font-family: Verdana;"> |
<p> | <p> | ||
<ul> | <ul> | ||
Line 98: | Line 105: | ||
=== Procedures === | === Procedures === | ||
+ | <div style="font-family: Verdana"> | ||
+ | <p> | ||
+ | Participants are given a consent form to sign prior to the testing. Once signed, they will be given the test instructions, and they are to think aloud and ask questions as they follow through the instructions given for the user testing. Team Ducky King will be there to record down the participants’ comments. Participants will complete a post-test questionnaire at the end of their user testing. Team Ducky King will conclude the user testing by asking the participants questions with regards to Flow Middleware platform. | ||
+ | </p> | ||
+ | </div> | ||
<center> | <center> | ||
{|class="wikitable" style="font-family: Verdana; background-color:#FFFFFF; width: 1000px;" align="center" | {|class="wikitable" style="font-family: Verdana; background-color:#FFFFFF; width: 1000px;" align="center" | ||
Line 110: | Line 122: | ||
|- | |- | ||
|style="text-align: center;"| 2 | |style="text-align: center;"| 2 | ||
− | |style="text-align: left;"| Participants should be able to | + | |style="text-align: left;"| Participants should be able to shortlist auctions and proceed to negotiation stage |
|style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | ||
|- | |- | ||
|style="text-align: center;"| 3 | |style="text-align: center;"| 3 | ||
− | |style="text-align: left;"| Participants should be able to | + | |style="text-align: left;"| Participants should be able to bid on an auction |
|style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | ||
|- | |- | ||
|style="text-align: center;"| 4 | |style="text-align: center;"| 4 | ||
− | |style="text-align: left;"| | + | |style="text-align: left;"| Participants should be able to cancel an auction |
|style="text-align: left;"| Goal reached. Participant were able to complete the tasks. | |style="text-align: left;"| Goal reached. Participant were able to complete the tasks. | ||
|- | |- | ||
|style="text-align: center;"| 5 | |style="text-align: center;"| 5 | ||
− | |style="text-align: left;"| Participants should be able to | + | |style="text-align: left;"| Participants should be able to cancel a bid |
|style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | ||
|- | |- | ||
|style="text-align: center;"| 6 | |style="text-align: center;"| 6 | ||
− | + | |style="text-align: left;"| Participants should be able to update a bid during open stage | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |style="text-align: left;"| Participants should be able to | ||
− | |||
− | |||
− | |||
− | |||
|style="text-align: left;"| Goal reached. Participant was able to complete the tasks. | |style="text-align: left;"| Goal reached. Participant was able to complete the tasks. | ||
|- | |- | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
</center> | </center> | ||
Line 183: | Line 172: | ||
=== Overall Results/Comments === | === Overall Results/Comments === | ||
+ | <div style="font-family: Verdana; "> | ||
+ | <p> | ||
+ | <ul> | ||
+ | <li>Implementing stringent validation rules</li> | ||
+ | <li>To return more meaningful JSON response for readability</li> | ||
+ | <li>Sponsor is satisfied with the team’s progress</li> | ||
+ | </ul> | ||
+ | </p> | ||
+ | </div> | ||
− | == | + | == <div style="background: #FF7504; padding: 15px; font-weight: bold; line-height: 0.3em; font-size:18px; font-family:helvetica" ><font color= #FFFFFF>UAT 2</font></div> == |
=== Test Plan === | === Test Plan === | ||
− | <div style="font-family: Verdana; | + | <div style="font-family: Verdana; "> |
<p> | <p> | ||
<b>Venue:</b> Flow Labs Office @ 165 Telok Ayer Street<br/> | <b>Venue:</b> Flow Labs Office @ 165 Telok Ayer Street<br/> | ||
− | <b>Date:</b> | + | <b>Date:</b> 9 October 2017<br/> |
− | <b>Time:</b> | + | <b>Time:</b> 4.30PM<br/> |
− | <b>Duration:</b> ~ | + | <b>Duration:</b> ~ 30 minutes per user<br/> |
− | <b>Number of Participants for FlowLabs Middleware:</b> | + | <b>Number of Participants for FlowLabs Middleware:</b> 3<br/> |
− | <b>User Test:</b> Instructions can be found [https://drive.google.com/drive/folders/ | + | <b>User Test:</b> Instructions can be found [https://drive.google.com/drive/u/0/folders/0BxzKKmVovZrnRkt4dlpjMjdpcUk here] <br/> |
</p> | </p> | ||
</div> | </div> | ||
=== Objectives=== | === Objectives=== | ||
− | <div style="font-family: Verdana; | + | <div style="font-family: Verdana; "> |
<p> | <p> | ||
<ul> | <ul> | ||
− | <li>To | + | <li>To let the participants understand how additional functionalities for the middleware are might potentially affect integration with the front end application</li> |
− | |||
− | |||
</ul> | </ul> | ||
</p> | </p> | ||
</div> | </div> | ||
− | === Scope of UAT | + | === Scope of UAT 2=== |
− | <div style="font-family: Verdana | + | <div style="font-family: Verdana"> |
<p> | <p> | ||
<ul> | <ul> | ||
− | <li> | + | <li>Authenticate before any action</li> |
− | <li> | + | <li>Create Auctions</li> |
+ | <li>Create Bids</li> | ||
+ | <li>View Auctions</li> | ||
+ | <li>View Bids</li> | ||
+ | <li>Cancel Auctions</li> | ||
+ | <li>Cancel Bids</li> | ||
+ | <li>Update Bid</li> | ||
+ | <li>Update Auction Status</li> | ||
+ | <li>View Winning Bid Price and Volume</li> | ||
</ul> | </ul> | ||
</p> | </p> | ||
Line 219: | Line 223: | ||
=== Procedures === | === Procedures === | ||
− | <div style="font-family: Verdana; | + | <div style="font-family: Verdana;"> |
<p> | <p> | ||
− | Participants are given a consent form to sign prior to the testing. Once signed, they will be given the test instructions, and they are to think aloud as they follow through the instructions given for the user testing. Team Ducky King will be there to record down the participants’ behaviours. Participants will complete a post-test questionnaire at the end of their user testing. Team Ducky King will conclude the user testing by asking the participants questions with regards to their behaviours and thought process as they navigate through | + | Participants are given a consent form to sign prior to the testing. Once signed, they will be given the test instructions, and they are to think aloud as they follow through the instructions given for the user testing. Team Ducky King will be there to record down the participants’ behaviours. Participants will complete a post-test questionnaire at the end of their user testing. Team Ducky King will conclude the user testing by asking the participants questions with regards to their behaviours and thought process as they navigate through FlowLabs Middleware. |
</p> | </p> | ||
</div> | </div> | ||
Line 232: | Line 236: | ||
|- | |- | ||
|style="text-align: center;"| 1 | |style="text-align: center;"| 1 | ||
− | |style="text-align: left;"| | + | |style="text-align: left;"| Participants should be able to authenticate themselves |
− | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks | + | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. |
|- | |- | ||
|style="text-align: center;"| 2 | |style="text-align: center;"| 2 | ||
− | |style="text-align: left;"| | + | |style="text-align: left;"|Participants should be able to create an auction using JWT tokens |
+ | |style="text-align: left;"|Goal reached. Participants were able to complete the tasks. | ||
+ | |- | ||
+ | |style="text-align: center;"| 3 | ||
+ | |style="text-align: left;"| Participants should be able to shortlist bids and proceed to negotiation stage using JWT tokens | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | ||
+ | |- | ||
+ | |style="text-align: center;"| 4 | ||
+ | |style="text-align: left;"| Participants should be able to shortlist bids and proceed to completed stage using JWT tokens | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | ||
+ | |- | ||
+ | |style="text-align: center;"| 5 | ||
+ | |style="text-align: left;"| Participants should be able to bid on an auction using JWT tokens | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | ||
+ | |- | ||
+ | |style="text-align: center;"| 6 | ||
+ | |style="text-align: left;"| Participants should be able to cancel an auction using JWT tokens | ||
|style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | ||
|- | |- | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"| 7 |
− | |style="text-align: left;"| | + | |style="text-align: left;"| Participants should be able to cancel a bid using JWT tokens |
+ | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | ||
+ | |- | ||
+ | |style="text-align: center;"| 8 | ||
+ | |style="text-align: left;"| Participants should be able to update a bid during open stage using JWT tokens | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | ||
+ | |- | ||
+ | |style="text-align: center;"| 9 | ||
+ | |style="text-align: left;"| Participants should be able to get the winning price and volume from completed auctions using JWT tokens | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | ||
+ | |- | ||
+ | |style="text-align: center;"| 10 | ||
+ | |style="text-align: left;"| Participants will input the auction data into postman and encountered a validation error | ||
|style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | |style="text-align: left;"| Goal reached. Participants were able to complete the tasks. | ||
|} | |} | ||
Line 250: | Line 282: | ||
|- | |- | ||
! style="color:#ecf0f1; background-color:#FF7504;" width="100pt" | Functions | ! style="color:#ecf0f1; background-color:#FF7504;" width="100pt" | Functions | ||
− | ! style="color:#ecf0f1; background-color:#FF7504;" width="400pt" | | + | ! style="color:#ecf0f1; background-color:#FF7504;" width="400pt" | Users' Comment |
! style="color:#ecf0f1; background-color:#FF7504;" width="500pt" | Changes to be made | ! style="color:#ecf0f1; background-color:#FF7504;" width="500pt" | Changes to be made | ||
|- | |- | ||
− | |style="text-align: center;"| User | + | |style="text-align: center;"| Function Refinement |
− | |style="text-align: left;"| Participants | + | |style="text-align: left;"| Sponsor requested the need for the index to process events in batches |
− | |style="text-align: left;"| | + | |style="text-align: left;"| Ducky King development team will process and break down the events into sizeable batches for processing before saving/updating the database |
+ | |- | ||
+ | |} | ||
+ | </center> | ||
+ | |||
+ | === Overall Results/Comments === | ||
+ | <div style="font-family: Verdana; "> | ||
+ | <p> | ||
+ | <ul> | ||
+ | <li>Sponsor is extremely satisfied with the team’s progress and achievement</li> | ||
+ | </ul> | ||
+ | </p> | ||
+ | </div> | ||
+ | |||
+ | == <div style="background: #FF7504; padding: 15px; font-weight: bold; line-height: 0.3em; font-size:18px; font-family:helvetica" ><font color= #FFFFFF>UAT 3</font></div> == | ||
+ | === Test Plan === | ||
+ | <div style="font-family: Verdana; "> | ||
+ | <p> | ||
+ | <b>Venue:</b> Flow Labs Office @ 165 Telok Ayer Street<br/> | ||
+ | <b>Date:</b> 17 November 2017<br/> | ||
+ | <b>Time:</b> 4.30PM<br/> | ||
+ | <b>Duration:</b> ~ 30 minutes per user<br/> | ||
+ | <b>Number of Participants for FlowLabs Middleware:</b> 3<br/> | ||
+ | <b>User Test:</b> Instructions can be found [https://drive.google.com/open?id=1Xj0nqrDDeot0uVft7LtD02TCR70fI-Lr here] <br/> | ||
+ | </p> | ||
+ | </div> | ||
+ | |||
+ | === Objectives=== | ||
+ | <div style="font-family: Verdana; "> | ||
+ | <p> | ||
+ | <ul> | ||
+ | <li>To let the participants ascertain the adequacy of information provided by middleware api provided through relating to the FlowLabs platform requirements</li> | ||
+ | <li>Ensure participants are able to read the logs and identify the root problem of the error logs</li> | ||
+ | </ul> | ||
+ | </p> | ||
+ | </div> | ||
+ | |||
+ | === Scope of UAT 3=== | ||
+ | <div style="font-family: Verdana"> | ||
+ | <p> | ||
+ | <ul> | ||
+ | <li>Authenticate before any action</li> | ||
+ | <li>Create Auctions</li> | ||
+ | <li>Create Bids</li> | ||
+ | <li>View Auctions</li> | ||
+ | <li>View Bids</li> | ||
+ | <li>Cancel Auctions</li> | ||
+ | <li>Cancel Bids</li> | ||
+ | <li>Update Bid</li> | ||
+ | <li>Update Auction Status</li> | ||
+ | <li>View Winning Bid Price and Volume</li> | ||
+ | <li>View Logs and Action Implementation</li> | ||
+ | </ul> | ||
+ | </p> | ||
+ | </div> | ||
+ | |||
+ | === Procedures === | ||
+ | <div style="font-family: Verdana;"> | ||
+ | <p> | ||
+ | Participants are given a consent form to sign prior to the testing. Once signed, they will be given the test instructions, and they are to think aloud as they follow through the instructions given for the user testing. Team Ducky King will be there to record down the participants’ behaviours. Participants will complete a post-test questionnaire at the end of their user testing. Team Ducky King will conclude the user testing by asking the participants questions with regards to their behaviours and thought process as they navigate through FlowLabs Middleware. | ||
+ | </p> | ||
+ | </div> | ||
+ | <center> | ||
+ | {|class="wikitable" style="font-family: Verdana; background-color:#FFFFFF; width: 1000px;" align="center" | ||
+ | |- | ||
+ | ! style="color:#ecf0f1; background-color:#FF7504;" width="100pt" | S/N | ||
+ | ! style="color:#ecf0f1; background-color:#FF7504;" width="400pt" | Goals | ||
+ | ! style="color:#ecf0f1; background-color:#FF7504;" width="500pt" | Reached? | ||
+ | |- | ||
+ | |style="text-align: center;"| 1 | ||
+ | |style="text-align: left;"| Participants should be able to get all variables via middleware API required for FlowLabs platform MAIN page | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables | ||
+ | |- | ||
+ | |style="text-align: center;"| 2 | ||
+ | |style="text-align: left;"|Participants should be able to get all variables via middleware API required for FlowLabs platform DASHBOARD <Our Auctions> page | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables | ||
+ | |- | ||
+ | |style="text-align: center;"| 3 | ||
+ | |style="text-align: left;"| Participants should be able to get all variables via middleware API required for FlowLabs platform DASHBOARD <Our Bids> page | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables | ||
+ | |- | ||
+ | |style="text-align: center;"| 4 | ||
+ | |style="text-align: left;"| Participants should be able to get the winning price and volume from completed auctions via middleware API required for FlowLabs | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables | ||
+ | |- | ||
+ | |style="text-align: center;"| 5 | ||
+ | |style="text-align: left;"| Participants should be able match all the input fields on the <New Auction> page to the parameters required by Postman | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables | ||
+ | |- | ||
+ | |style="text-align: center;"| 6 | ||
+ | |style="text-align: left;"| Participants should be able match all the input fields on the <New Bid> page to the parameters required by Postman | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables | ||
+ | |- | ||
+ | |style="text-align: center;"| 7 | ||
+ | |style="text-align: left;"| Participants should be able to match all the input fields on the <Update Bid> page to the parameters required by Postman | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables | ||
+ | |- | ||
+ | |style="text-align: center;"| 8 | ||
+ | |style="text-align: left;"| Participants should be able to pass the checkboxes ticked for bids selection to Postman | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables | ||
|- | |- | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"| 9 |
− | |style="text-align: left;"| Participants | + | |style="text-align: left;"| Participants will input the auction data into postman, encountered a validation error and are able to understand the logs to find the root of the problem |
− | |style="text-align: left;"| | + | |style="text-align: left;"| Goal reached. Participants were able to understand the error logs and take any measures required |
|- | |- | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"| 10 |
− | |style="text-align: left;"| Participants | + | |style="text-align: left;"| Participants will input the wrong auction address into postman while creating new bid and are able to understand the logs to find the root of the problem |
− | |style="text-align: left;"| | + | |style="text-align: left;"| Goal reached. Participants were able to understand the error logs and take any measures required |
+ | |- | ||
+ | |style="text-align: center;"| 11 | ||
+ | |style="text-align: left;"| Participants will input the wrong public key into postman while updating auction and are able to understand the logs to find the root of the problem | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to understand the error logs and take any measures required | ||
+ | |- | ||
+ | |style="text-align: center;"| 12 | ||
+ | |style="text-align: left;"| Participants should be able to identify database connection errors from the logs to find the root of the problem | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to understand the error logs and take any measures required | ||
+ | |- | ||
+ | |style="text-align: center;"| 13 | ||
+ | |style="text-align: left;"| Participants should be able to identify blockchain connection errors from the logs to find the root of the problem | ||
+ | |style="text-align: left;"| Goal reached. Participants were able to understand the error logs and take any measures required | ||
|} | |} | ||
+ | </center> | ||
+ | === Key Findings === | ||
+ | <center> | ||
{|class="wikitable" style="font-family: Verdana; background-color:#FFFFFF; width: 1000px;" align="center" | {|class="wikitable" style="font-family: Verdana; background-color:#FFFFFF; width: 1000px;" align="center" | ||
|- | |- | ||
! style="color:#ecf0f1; background-color:#FF7504;" width="100pt" | Functions | ! style="color:#ecf0f1; background-color:#FF7504;" width="100pt" | Functions | ||
− | ! style="color:#ecf0f1; background-color:#FF7504;" width="400pt" | | + | ! style="color:#ecf0f1; background-color:#FF7504;" width="400pt" | Users' Comment |
! style="color:#ecf0f1; background-color:#FF7504;" width="500pt" | Changes to be made | ! style="color:#ecf0f1; background-color:#FF7504;" width="500pt" | Changes to be made | ||
|- | |- | ||
− | |style="text-align: center;"| | + | |style="text-align: center;"| API Refinement |
− | |style="text-align: left;"| Sponsor requested for a | + | |style="text-align: left;"| Sponsor requested the need for public_key to be included when adding a new bid |
− | |style="text-align: left;"| | + | |style="text-align: left;"| Ducky King development team will include the required parameter into the API |
− | + | |- | |
+ | |style="text-align: center;"| API Refinement | ||
+ | |style="text-align: left;"| Sponsor requested the need for pagination of the information returned via the API | ||
+ | |style="text-align: left;"| Ducky King development team will paginate the information into different segments before returning the information back to FlowLabs platform | ||
+ | |- | ||
|} | |} | ||
</center> | </center> | ||
=== Overall Results/Comments === | === Overall Results/Comments === | ||
+ | <div style="font-family: Verdana; "> | ||
+ | <p> | ||
+ | <ul> | ||
+ | <li>Sponsor is happy that the API design is very intuitive and very scalable for their usage </li> | ||
+ | </ul> | ||
+ | </p> | ||
+ | </div> | ||
+ | |||
+ | |||
+ | |||
<!--/ Current Page --> | <!--/ Current Page --> |
Latest revision as of 17:38, 20 November 2017
UAT 1
Test Plan
Venue: Flow Labs Office @ 165 Telok Ayer Street
Date: 15 August 2017
Time: 4.30PM
Duration: ~ 15 minutes per user
Number of Participants for FlowLabs Middleware: 3
User Test: Instructions can be found here
Objectives
- To let the participants verify if the core functionalities for the middleware are suitable for integration with the front end application
- To identify missing functionality
Scope of UAT 1
- Create Auctions
- Create Bids
- View Auctions
- View Bids
- Cancel Auctions
- Cancel Bids
- Update Bid
- Update Auction Status
Procedures
Participants are given a consent form to sign prior to the testing. Once signed, they will be given the test instructions, and they are to think aloud and ask questions as they follow through the instructions given for the user testing. Team Ducky King will be there to record down the participants’ comments. Participants will complete a post-test questionnaire at the end of their user testing. Team Ducky King will conclude the user testing by asking the participants questions with regards to Flow Middleware platform.
S/N | Goals | Reached? |
---|---|---|
1 | Participants should be able to create an auction. | Goal reached. Participants were able to complete the tasks.. |
2 | Participants should be able to shortlist auctions and proceed to negotiation stage | Goal reached. Participants were able to complete the tasks. |
3 | Participants should be able to bid on an auction | Goal reached. Participants were able to complete the tasks. |
4 | Participants should be able to cancel an auction | Goal reached. Participant were able to complete the tasks. |
5 | Participants should be able to cancel a bid | Goal reached. Participants were able to complete the tasks. |
6 | Participants should be able to update a bid during open stage | Goal reached. Participant was able to complete the tasks. |
Key Findings
Functions | Users' Comment | Changes to be made |
---|---|---|
Function Refinement | Sponsor requested for the endpoints to not accept any inputs that are prone to manipulation. | Ducky King development team reduce any required user inputs and allow the inputs to be abstracted from the database. |
Function Refinement | Sponsor highlighted the need for the auction winner’s details to be easily accessible on the blockchain. | Ducky King development team will process and break down the bid details and only allow auction winner’s non-sensitive information to be available on the blockchain. |
Function Refinement | Sponsor requested add more endpoints for the frontend layer to easily query winning bids’ detail sorted by time. | Ducky King development team will add new functions and endpoints to allow the winning bids’ details to be easily queried. |
Function Refinement | Sponsor requested that the endpoints return JSON payload of a certain format. | Ducky King development team reduce any required user inputs and allow the inputs to be abstracted from the database. |
Overall Results/Comments
- Implementing stringent validation rules
- To return more meaningful JSON response for readability
- Sponsor is satisfied with the team’s progress
UAT 2
Test Plan
Venue: Flow Labs Office @ 165 Telok Ayer Street
Date: 9 October 2017
Time: 4.30PM
Duration: ~ 30 minutes per user
Number of Participants for FlowLabs Middleware: 3
User Test: Instructions can be found here
Objectives
- To let the participants understand how additional functionalities for the middleware are might potentially affect integration with the front end application
Scope of UAT 2
- Authenticate before any action
- Create Auctions
- Create Bids
- View Auctions
- View Bids
- Cancel Auctions
- Cancel Bids
- Update Bid
- Update Auction Status
- View Winning Bid Price and Volume
Procedures
Participants are given a consent form to sign prior to the testing. Once signed, they will be given the test instructions, and they are to think aloud as they follow through the instructions given for the user testing. Team Ducky King will be there to record down the participants’ behaviours. Participants will complete a post-test questionnaire at the end of their user testing. Team Ducky King will conclude the user testing by asking the participants questions with regards to their behaviours and thought process as they navigate through FlowLabs Middleware.
S/N | Goals | Reached? |
---|---|---|
1 | Participants should be able to authenticate themselves | Goal reached. Participants were able to complete the tasks. |
2 | Participants should be able to create an auction using JWT tokens | Goal reached. Participants were able to complete the tasks. |
3 | Participants should be able to shortlist bids and proceed to negotiation stage using JWT tokens | Goal reached. Participants were able to complete the tasks. |
4 | Participants should be able to shortlist bids and proceed to completed stage using JWT tokens | Goal reached. Participants were able to complete the tasks. |
5 | Participants should be able to bid on an auction using JWT tokens | Goal reached. Participants were able to complete the tasks. |
6 | Participants should be able to cancel an auction using JWT tokens | Goal reached. Participants were able to complete the tasks. |
7 | Participants should be able to cancel a bid using JWT tokens | Goal reached. Participants were able to complete the tasks. |
8 | Participants should be able to update a bid during open stage using JWT tokens | Goal reached. Participants were able to complete the tasks. |
9 | Participants should be able to get the winning price and volume from completed auctions using JWT tokens | Goal reached. Participants were able to complete the tasks. |
10 | Participants will input the auction data into postman and encountered a validation error | Goal reached. Participants were able to complete the tasks. |
Key Findings
Functions | Users' Comment | Changes to be made |
---|---|---|
Function Refinement | Sponsor requested the need for the index to process events in batches | Ducky King development team will process and break down the events into sizeable batches for processing before saving/updating the database |
Overall Results/Comments
- Sponsor is extremely satisfied with the team’s progress and achievement
UAT 3
Test Plan
Venue: Flow Labs Office @ 165 Telok Ayer Street
Date: 17 November 2017
Time: 4.30PM
Duration: ~ 30 minutes per user
Number of Participants for FlowLabs Middleware: 3
User Test: Instructions can be found here
Objectives
- To let the participants ascertain the adequacy of information provided by middleware api provided through relating to the FlowLabs platform requirements
- Ensure participants are able to read the logs and identify the root problem of the error logs
Scope of UAT 3
- Authenticate before any action
- Create Auctions
- Create Bids
- View Auctions
- View Bids
- Cancel Auctions
- Cancel Bids
- Update Bid
- Update Auction Status
- View Winning Bid Price and Volume
- View Logs and Action Implementation
Procedures
Participants are given a consent form to sign prior to the testing. Once signed, they will be given the test instructions, and they are to think aloud as they follow through the instructions given for the user testing. Team Ducky King will be there to record down the participants’ behaviours. Participants will complete a post-test questionnaire at the end of their user testing. Team Ducky King will conclude the user testing by asking the participants questions with regards to their behaviours and thought process as they navigate through FlowLabs Middleware.
S/N | Goals | Reached? |
---|---|---|
1 | Participants should be able to get all variables via middleware API required for FlowLabs platform MAIN page | Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables |
2 | Participants should be able to get all variables via middleware API required for FlowLabs platform DASHBOARD <Our Auctions> page | Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables |
3 | Participants should be able to get all variables via middleware API required for FlowLabs platform DASHBOARD <Our Bids> page | Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables |
4 | Participants should be able to get the winning price and volume from completed auctions via middleware API required for FlowLabs | Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables |
5 | Participants should be able match all the input fields on the <New Auction> page to the parameters required by Postman | Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables |
6 | Participants should be able match all the input fields on the <New Bid> page to the parameters required by Postman | Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables |
7 | Participants should be able to match all the input fields on the <Update Bid> page to the parameters required by Postman | Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables |
8 | Participants should be able to pass the checkboxes ticked for bids selection to Postman | Goal reached. Participants were able to get the required variables for FlowLabs platform and there were no lacking variables |
9 | Participants will input the auction data into postman, encountered a validation error and are able to understand the logs to find the root of the problem | Goal reached. Participants were able to understand the error logs and take any measures required |
10 | Participants will input the wrong auction address into postman while creating new bid and are able to understand the logs to find the root of the problem | Goal reached. Participants were able to understand the error logs and take any measures required |
11 | Participants will input the wrong public key into postman while updating auction and are able to understand the logs to find the root of the problem | Goal reached. Participants were able to understand the error logs and take any measures required |
12 | Participants should be able to identify database connection errors from the logs to find the root of the problem | Goal reached. Participants were able to understand the error logs and take any measures required |
13 | Participants should be able to identify blockchain connection errors from the logs to find the root of the problem | Goal reached. Participants were able to understand the error logs and take any measures required |
Key Findings
Functions | Users' Comment | Changes to be made |
---|---|---|
API Refinement | Sponsor requested the need for public_key to be included when adding a new bid | Ducky King development team will include the required parameter into the API |
API Refinement | Sponsor requested the need for pagination of the information returned via the API | Ducky King development team will paginate the information into different segments before returning the information back to FlowLabs platform |
Overall Results/Comments
- Sponsor is happy that the API design is very intuitive and very scalable for their usage