QA/Test Plan Template: Difference between revisions

QA/Test Plan Template (view source)

Revision as of 15:23, 3 December 2015

111 bytes removed , 3 December 2015

→‎Test Areas

Brindusa.tot

533

edits

@@ Line 173: / Line 173: @@
 |-
 | Private Window
-|style="text-align:center;" | {{mdone|}} ||
+|style="text-align:center;" | ||
 |-
 | Multi-Process Enabled
-|style="text-align:center;" | {{mprog|}} ||
+|style="text-align:center;" |  ||
 |-
 | Multi-process Disabled
-|style="text-align:center;" | {{mnotstarted|}} ||
+|style="text-align:center;" |  ||
 |-
 | Theme (high contrast)
-|style="text-align:center;" | ||
+|style="text-align:center;" |  ||
 |-
 | '''UI'''
@@ Line 188: / Line 188: @@
 |-
 | Mouse-only operation
-|style="text-align:center;" |  || Regular testing
+|style="text-align:center;" |  ||
 |-
 | Keyboard-only operation
@@ Line 203: / Line 203: @@
 |-
 | Usability and/or discoverability testing
-|style="text-align:center;" |  ||?? What exactly should you had thinking??
+|style="text-align:center;" |  || Is this user friendly or not?
 |-
@@ Line 210: / Line 210: @@
 |-
 | Help/support interface required
-|style="text-align:center;" |  ||do you refer here if there is page with user guide for the feature?
+|style="text-align:center;" |  || Make sure link to support/help page exist and is easy reachable.
 |-
 | Support documents planned(written)
-|style="text-align:center;" |  || do you refer here if there is any document user guide for the feature?
+|style="text-align:center;" |  || Make sure support documents are written and are correct.
 |-
@@ Line 229: / Line 229: @@
 |-
 | Affects first-run or onboarding
-|style="text-align:center;" |  || Florin/Lawrence are investigating if there is a dedicated QA for this, or we should test? This shouldn’t be tested only on Beta? It could be added with yes/no and if there is other person assigned just add the name into the details.
+|style="text-align:center;" |  || Florin/Lawrence are investigating if there is a dedicated QA for this, or we should test? Should be an yes/no and if is yes should add in detail column the team/person assigned.
 |-
 | Does this affect partner builds? Partner build testing
-|style="text-align:center;" |  || yes/no options, eventualy add comment with details about who will lead testing
+|style="text-align:center;" |  || yes/no options, add comment with details about who will lead testing
 |-
 | ''' Enterprise '''
-||  ||  please advise, specific testing should be done for ESR builds?
+||  ||  Raise up the topic to developers to see if they are expecting to work different on ESR builds
 |-
 | Enterprise administration
@@ Line 271: / Line 271: @@
 |-
 | ''' Add-ons '''
-||  || please give more details – if add-ons are available for testing feature?
+||  || If add-ons are available for testing feature, or is current feature will affect some add-ons, then API testing should be done for the add-on.
 |-
 | Addon API required?
@@ Line 287: / Line 287: @@
 |-
 | ''' Security '''
-||  || as we know, security is in charge of Matt Wobensmith. Should we contact his team to see if security testing is necessary for current feature? Should add in checklist with comment: contact Matt?
+||  || Security is in charge of Matt Wobensmith. We should contact his team to see if security testing is necessary for current feature.
 |-
 | 3rd-party security review