QA/Desktop Firefox/Nightly Testing/Q4 2013
From MozillaWiki
< QA | Desktop Firefox | Nightly Testing
Contents
Manual Testing (Paul Silaghi)
P1: Australis
Ensure 0 blockers to Australis migrating to Aurora in Firefox 29
- [DONE] Daily exploratory testing of Australis in Nightly
- [DONE] Compatibility testing for the top-50 add-ons
- [DONE] Daily triage of incoming and fixed Australis bugs on Nightly
- [DONE] Hand-off Australis testing to Cornel for Aurora migration
P1: WebRTC
- Firefox 29 Nightly Week 2 AppRTC Sign-off
- Firefox 29 Nightly Week 1 AppRTC Sign-off
- Firefox 28 Nightly Week 6 AppRTC Sign-off
- Firefox 28 Nightly Week 5 AppRTC Sign-off
- Firefox 28 Nightly Week 4 AppRTC Sign-off
- Firefox 28 Nightly Week 3 AppRTC Sign-off
Bugs:
- [ON TRACK] bug 936034 Sound is distorted on one side on 1:1 call
P2: Games
Ensure Games demos do not regress in Firefox Nightly
- [DONE] Weekly sign-off of Games demos in Firefox Nightly desktop builds (details)
P3: Shumway
P4: Nightly Features
Automation (Mihaela Velimiroviciu)
P1: Australis
- [DONE] Refactor Mozmill tests to work with Australis builds
- [DONE] Daily triage of Mozmill testruns against Australis builds in mozilla-central
P2: Holly
- [DONE] Refactor Mozmill tests to work daily against Holly builds
- [DONE] Daily triage of Mozmill testruns against Holly builds in mozilla-central
P3: Feature Coverage
- [MISSED] App Manager
- [DROPPED] CSS Inheritance changes
- [DROPPED] HTTP Backend Cache
- [DROPPED] Interface for predictive actions
- [DROPPED] Metro: Enable history swipe animations by default
- [MISSED] SocialAPI: Allow multiple workers
- [DROPPED] WebGL Shader Editor
General Process
- Work with Feature Owner and Developer to determine which manual tests and/or user stories are not covered by automation
- Anything requiring a restart and or testing localization will be the responsibility of the Feature Owner to work out with Automation Development via a Mozmill Tests bug
- Anything else will be the responsibility of Mihaela to work out with the developer
- The feature will be considered covered when all user stories have either automation or manual test coverage
- The long-term goal is to have Feature Owners take on the responsibility of all automation with Mihaela working as a code reviewer, adviser, and educator