Difference between revisions of "IS480 Team wiki:2017T1 Ducky King User Testing"
Jump to navigation
Jump to search
Tcgan.2015 (talk | contribs) |
|||
(17 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--> | ||
+ | |||
+ | |||
+ | {| 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: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| <font color =#535353><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 1 |<font color =#FF7505><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:Ducky King Internal testing.png|center]] | ||
+ | <br> | ||
+ | <!--Testing Tables Start--> | ||
+ | |||
+ | <div style="background: #FF7504; padding: 15px; font-weight: bold; line-height: 0.3em; text-indent: 15px; font-size:18px; font-family:helvetica" align="center"><font color= #FFFFFF>Test Plan</font></div> | ||
+ | <div width="100%" align="center"> | ||
+ | {| class="wikitable" style="border-spacing: 0; margin: 1em auto;" | ||
+ | |- | ||
+ | |- | ||
+ | | style="text-align:center; padding: 5px;background:#FFA30E;color:white;" | | ||
+ | '''Who is responsible for testing?''' | ||
+ | | style=" padding: 5px;" | | ||
+ | '''Quality Assurance (QA)''' is responsible for executing the test plan in every Sprint. | ||
+ | #The QA can assign team member specific roles for a set of test cases. | ||
+ | #QA is to ensure that the bugs are resolved during the Sprint. | ||
+ | #He/She is to report to the Project Manager should there be any deviations. | ||
+ | |- | ||
+ | | style="text-align:center; padding: 5px;background:#FFA30E;color:white;" | | ||
+ | '''When to do it?''' | ||
+ | | style=" padding: 5px;" | | ||
+ | There are '''3 environments''' which testing will be conducted in: | ||
+ | #During Development (Day 1 - 7) | ||
+ | ##During development, the QA will construct test cases and test the features using testrpc. | ||
+ | ##For development, the developers will connect to the Staging Environment for the Ethereum Network | ||
+ | #Staging (Day 8 - 11) | ||
+ | ##Database and Used wallets will be Purged | ||
+ | ##Regression Testing | ||
+ | #Production (Day 12 - 14) | ||
+ | ##Regression Testing | ||
+ | |- | ||
+ | | style="text-align:center; padding: 5px;background:#FFA30E;color:white;" | | ||
+ | '''Test Setup''' | ||
+ | | style=" padding: 5px;" | | ||
+ | Virtual Machines are hosted on Digital Ocean. The machines are delegated specific roles, as agreed between the Team and the Sponsor. | ||
+ | |||
+ | Local Testing: testrpc, Ethereum Network in Staging Environment | ||
+ | |||
+ | Automated testing: Truffle, MochaJS | ||
+ | |||
+ | Regression Testing: done by QA via Postman for API | ||
+ | *Use respective test cases to test the features | ||
+ | |- | ||
+ | | style="text-align:center; padding: 5px;background:#FFA30E;color:white;" | | ||
+ | '''When to fix bugs?''' | ||
+ | | style=" padding: 5px;" | | ||
+ | Bugs are to be '''resolved ideally within the same Sprint.''' However, it will depend on the criticality as well. | ||
+ | #Before Iteration ends during allocated day in Schedule | ||
+ | #Ensure bug metrics to be fixed accordingly | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | [[File:DK_Test_Lifecycle.png|center]] | ||
+ | |||
+ | [[File:DuckyKing Footer.png|center]] |
Latest revision as of 04:05, 15 November 2017
Test Plan
Who is responsible for testing? |
Quality Assurance (QA) is responsible for executing the test plan in every Sprint.
|
When to do it? |
There are 3 environments which testing will be conducted in:
|
Test Setup |
Virtual Machines are hosted on Digital Ocean. The machines are delegated specific roles, as agreed between the Team and the Sponsor. Local Testing: testrpc, Ethereum Network in Staging Environment Automated testing: Truffle, MochaJS Regression Testing: done by QA via Postman for API
|
When to fix bugs? |
Bugs are to be resolved ideally within the same Sprint. However, it will depend on the criticality as well.
|