QA/improve permission prompt UI: Difference between revisions

QA/improve permission prompt UI (view source)

Revision as of 08:47, 19 December 2016

1,624 bytes added , 19 December 2016

no edit summary

Hani.yacoub

139

edits

@@ Line 29: / Line 29: @@
 == Ownership ==
- What resources are needed, and when (developers, QA, PMs working on the feature)
+'''<big>Development Team</big>''':<br />
+'''<big>Engineering Team</big> - Nightly Testing''':<br />
+[mailto:rares.bologa@softvisioninc.eu Rares Bologa] (irc: RaresB) - PM for QA team <br />
+[mailto:brindusa.tot@softvisioninc.eu Brindusa Tot] (irc: brindusat) - leading QA efforts <br />
+[mailto:hani.yacoub@softvision.ro Hani Yacoub] (irc: hani) - QA <br />
 = Testing summary =
 == Scope of Testing ==
 === In Scope ===
-Detail what is in scope from a testing perspective for the project team.
+This feature purpose is to convert permission notifications to use two buttons instead of the drop-down menu.
+Testing will be done on 4 OSes:
+* Windows 10, Windows 7
+* Mac OS X 10.12
+* Ubuntu 16.04
 === Out of Scope ===
@@ Line 41: / Line 54: @@
 = Requirements for testing =
 == Environments ==
- Specify OSes that need to be covered
+Full testing will be performed on the following OSes:
- Specify Devices that need to be covered
+* Windows 7 and Windows 10
- Specify other configuration/environmental setup needed
+* Mac OS X 10.12
+* Ubuntu 16.04
@@ Line 77: / Line 91: @@
 {| class="wikitable"
 |-
-! Ref !! Function !! Test Objective !! Evaluation Criteria !! Test Type !! Owners
+! Ref !! Function !! Test Objective !! Test Type !! Risk Assessment and Coverage(RAC) !! Owners
 |-
-| 1 || Name of the feature or sub-function being tested || The objective the test is trying to demonstrate || The criteria that will be evaluated to demonstrate the test is successful || Manual/ Automation/ Regression/ Performance/ Usability/ Security/ Telemetry || Eng Team
+| 1 || Improve permission prompt UI display || The new visual design is displayed and the notification functionality is correct || Manual || RAC-1 || Eng Team
 |-
 | 2 || Repeat for each feature/sub-function || || || ||
@@ Line 85: / Line 99: @@
 | 3 || || || || ||
 |}
+== Risk Assessment and Coverage ==
+{| class="wikitable"
+|-
+! ID !! Description / Threat Description !! Covered by Test Objective !!  Magnitude !! Probability !! Priority !! Impact Score
+|-
+| RAC-1 || Mouse and keyboard actions may not be recognized || TO-1 || 2-Moderate || 1-Unlikely || 3-High || 6
+|-
+| RAC-2 || Some Video types are not recognized and played || TO-3 || 3- High|| 2-Possible || 3-High || 18
+|-
+| RAC-3 || Possible performance issues with multiple tabs || TO-4 || 2-Moderate || 2-Possible || 3-High || 12
+|-
+| RAC-4 || After visiting for the first time a tab containing a video, the video starts with a delay || TO-1 || 3-High || 3-Almost Certain || 3-High || 27
+|-
+|}
+'''Values:'''
+* '''Magnitude:''' 1- Low , ''2-Moderate'', '''3-High'''
+* '''Probability:''' 1-Unlikely, ''2-Possible'', '''3-Almost Certain'''
+* '''Priority:''' 1 - Low, ''2-Medium'', '''3-High'''
+'''Impact Score Breakdown:'''
+* An impact value of 1 or 2 would describe an area which although should be covered there aren't expected any discoveries of critical issues.
+* An impact value of 4, 8 or 12 would describe an area in which we expect to find issues but those issues are not expected to be critical.
+* An impact value of 18 or 27 would describe an area on which it is likely to find issues and those issues to be critical or blockers.