QA/Goals/2015q1: Difference between revisions

Jump to navigation Jump to search
Line 67: Line 67:
== Firefox ==
== Firefox ==
=== E10s ===
=== E10s ===
* {{ok|<small>[lizzard, juanb]</small> - Establish baselines for automated-test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}}  
* {{done|<small>[lizzard, juanb]</small> - Establish baselines for automated-test coverage, crash-stats, add-on compatibility, and memory footprint for e10s Nightly and track them throughout Q1.}}
* {{ok|<small>[lizzard, juanb]</small> - Improve the automated-test coverage for E10s-enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}
** We did this for addons, automated tests, and crash stats. Memory footprint did not seem like a reliable metric to track at this time given the amount of work required and the amount of variability in the data.
* {{risk|<small>[lizzard, juanb]</small> - Improve the automated-test coverage for E10s-enabled builds by turning on tests for a new platform and ensuring bugs filed for perma-fails.}}
** This is {{bug|1122901}}. It is now in the hands of the automation team and the releng team and while we are pushing on it, it's not entirely in our control anymore.
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve add-on compatibility testing for e10s}}
* {{ok|<small>[lizzard, juanb]</small> - Engage community to help improve add-on compatibility testing for e10s}}
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa
** milestones/deliverables: https://etherpad.mozilla.org/e10s-strategy-qa
Confirmed users
3,816

edits

Navigation menu