Confirmed users
3,816
edits
QA/Goals/2014q4: Difference between revisions
→Firefox
| Line 126: | Line 126: | ||
== Firefox == | == Firefox == | ||
* {{ | * {{done|<small>[mschifer]</small> Work on doing fewer verifications since they don't seem to be effective, and use the time saved for exploratory testing.}} | ||
** Hypothesis: We will still produce releases just as high quality but will be able to find more interesting bugs sooner in the development cycles. | ** Hypothesis: We will still produce releases just as high quality but will be able to find more interesting bugs sooner in the development cycles. | ||
** Hypothesis: We will be able to use our fledgling churn metrics to guide where and when to do verifications for non-security bugs (all security bugs continue to be verified if possible). | ** Hypothesis: We will be able to use our fledgling churn metrics to guide where and when to do verifications for non-security bugs (all security bugs continue to be verified if possible). | ||
* {{ | * {{done|<small>[lizzard]</small> Clarify/standardize/improve how we do QA for Firefox through the entire release process. Have a fairly standard wiki template for each Firefox channel that we can use for tracking and for our daily workflow. We can support community better in helping us (and support each other) better if we have a good transparent window into how QA works across each "train"}} | ||
* {{ | * {{done|<small>[mschifer]</small> Develop a system to measure development pace for SV Automation (similar to FxTeam) so we can establish a historical baseline and begin to measure an increase pace of automated test development}} | ||
== Web QA == | == Web QA == | ||