QA/improve permission prompt UI: Difference between revisions

QA/improve permission prompt UI (view source)

Revision as of 13:39, 6 January 2017

396 bytes removed , 6 January 2017

no edit summary

Hani.yacoub

139

edits

@@ Line 93: / Line 93: @@
 ! Ref !! Function !! Test Objective !! Test Type !! Risk Assessment and Coverage(RAC) !! Owners
 |-
-| 1 || Improve permission prompt UI display || The new visual design is displayed and the notification functionality is correct || Manual || RAC- || Eng Team
+| 1 || Improve permission prompt UI display || The new visual design is displayed and the notification functionality is correct || Manual || RAC-1, RAC-4 || Eng Team
 |-
-| 2 || Improve permission prompt UI functionality || The basic functions(Save-don't save, Share-don't share, Allow-don't allow and always remember my decision) all work properly || Manual || RAC- || Eng Team
+| 2 || Improve permission prompt UI functionality || The basic functions(Save-don't save, Share-don't share, Allow-don't allow and always remember my decision) all work properly || Manual || RAC-1 || Eng Team
 |-
-| 3 || Different permission prompt types || Validate that new permission prompt design works correctly on different permission prompt types || Manual || RAC- || Eng Team
+| 3 || Different permission prompt types || Validate that new permission prompt design works correctly on different permission prompt types || Manual || RAC-2 || Eng Team
 |-
-| 4 || Performance is acceptable in case of multiple tabs and doesn't crash the browser || The objective the test is trying to demonstrate that new permission prompt design works correctly when on multiple tabs or windows || Manual || RAC- || Eng Team
+| 4 || Performance is acceptable in case of multiple tabs and doesn't crash the browser || The objective the test is trying to demonstrate that new permission prompt design works correctly when on multiple tabs or windows || Manual || RAC-3 || Eng Team
 |-
 | 5 || Accessibility || Testing for accessibility includes:
@@ Line 105: / Line 105: @@
 - Screen Reader validation<br />
 - Keyboard-only
-|| Manual || RAC- || Eng Team
+|| Manual || RAC-1 || Eng Team
 |}
@@ Line 204: / Line 204: @@
 = References =
 * List and links for specs
-   List and links for available specs - documents, user stories, specifications
+   Permission prompt specs - ???
-* Meta bug
+* Meta bug [https://bugzilla.mozilla.org/show_bug.cgi?id=1282768 1282768]
 = Testcases =
@@ Line 369: / Line 369: @@
 == Test suite ==
-  Full Test suite - Link with the gdoc, follow the format from [https://docs.google.com/spreadsheets/d/1N8dGK_uenhfcM9cEPC3HPHmi0jFN98FWtL2DuszrfLY/edit#gid=0 link]
+  Full Test suite - in TestRail at [https://testrail.stage.mozaws.net link]
- Smoke Test suite - Link with the gdoc, follow the format from [https://docs.google.com/spreadsheets/d/1N8dGK_uenhfcM9cEPC3HPHmi0jFN98FWtL2DuszrfLY/edit#gid=0 link]
- Regression Test suite - Link with the gdoc - if available/needed.
 = Bug Work =
@@ Line 404: / Line 402: @@
 Check list
 * All test cases should be executed
-* Has sufficient automated test coverage (as measured by code coverage tools) - coordinate with RelMan
 * All blockers, criticals must be fixed and verified or have an agreed-upon timeline for being fixed (as determined by engineering/RelMan/QA)