352
edits
B2G/QA/Device Test Plan/Graphics: Difference between revisions
Jump to navigation
Jump to search
→Communicate with Graphics team
(→Tasks) |
|||
| Line 44: | Line 44: | ||
=== Communicate with Graphics team === | === Communicate with Graphics team === | ||
* Graphics Bug Triage: monitor incoming [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=Graphics%20Blocking%20%2F%20Blocking%20Candidates&sharer_id=499933&list_id=10565678 blocking-nominated] bugs, and provide feedback during the triage session. Blocking criteria are: | |||
::* '''Feature regressing''' | |||
::* '''Blocking the successful completion of common use case''' | |||
::* '''Risk of causing data loss, system freeze, or major user frustration''' | |||
::* '''Obvious rendering issues or performance issues such as checkerboarding or screen refresh issue''' | |||
Any graphics bugs that fall under one or more of above criteria should be nominated(with '''?''' flag) for the upcoming release in the '''b2g-release''' field. If a bug does not satisfy any of above criteria, mark it with ''''backlog'''' flag. | |||
* Discuss with Graphics team about each active features for FxOS (from [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 graphics features backlog]) for possible areas of weakness and test strategy. When a feature becomes active and FxOS relevant, it should be discussed. Record findings in Bugzilla and use them for testing when the feature is completed. | * Discuss with Graphics team about each active features for FxOS (from [https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AnKFEBp1-VyqdFNfRlZmV0ExM0VvZGMxNThWX0d6LWc&usp=drive_web#gid=0 graphics features backlog]) for possible areas of weakness and test strategy. When a feature becomes active and FxOS relevant, it should be discussed. Record findings in Bugzilla and use them for testing when the feature is completed. | ||