QA/Firefox3/Strategy: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 15: Line 15:
* Stress Tests Deliverables
* Stress Tests Deliverables
* Accessibility Tests Deliverables
* Accessibility Tests Deliverables
* Bug Verifications Deliverables
* Distribution Tests Deliverables
* Distribution Tests Deliverables
* L10N Test Deliverables
* L10N Test Deliverables
* Updates Test Deliverables
* Updates Test Deliverables
* Bug Verifications Deliverables


== Areas not Covered ==
== Areas not Covered ==
Line 137: Line 137:
Test results will be tracked via automation through eggplant and jesse's fuzzer tools.  There are a few security tests also tracked in litmus to be ran manually.  Also a handful of security bugs in bugzilla have test cases to be ran independently.  (example: [https://bugzilla.mozilla.org/show_bug.cgi?id=389106 Bug 389106])
Test results will be tracked via automation through eggplant and jesse's fuzzer tools.  There are a few security tests also tracked in litmus to be ran manually.  Also a handful of security bugs in bugzilla have test cases to be ran independently.  (example: [https://bugzilla.mozilla.org/show_bug.cgi?id=389106 Bug 389106])


=== Stress Testing ===
=== Stress Tests Deliverables ===
* failover litmus scenarios (eg. Pulling out the plug on download)
* failover litmus scenarios (eg. Pulling out the plug on download)


=== Accessibility Test Deliverables ===
=== Accessibility Tests Deliverables ===
;Summary
;Summary


Line 155: Line 155:
Test cases will exist in litmus and the public wiki.  Any issues found will be tracked in bugzilla.
Test cases will exist in litmus and the public wiki.  Any issues found will be tracked in bugzilla.


=== Bug Verifications ===
=== Bug Verifications Deliverables ===
;Summary
;Summary


Confirmed users
6,361

edits