#Firefox 40.0.3 for mac update#
#Firefox 40.0.3 for mac verification#

Use the latest Nightly build to confirm the bug reproduces.

The following tracks triage and testing of incoming, unconfirmed bug reports.

Untriaged Bugs - ensure bugs are actionable and in the correct component.

Top Crashes - ensure the highest ranked crashes have actionable bug reports which are in progress.

Ensure new and explosive crashes have actionable bug reports which are in progress.

This section tracks bugs representing the most urgent stability issues.

Report this information to the bug and remove the qawanted keyword.

Use the latest build of this Firefox version and test until you've discovered the information necessary.

Read it and make sure you understand what information is needed ( this may be steps or URLs to reproduce, a regression range, or something else altogether).

Choose a bug to test from the list below.

The following tracks bugs which have requests for urgent QA assistance.

#Firefox 40.0.3 for mac verification#

Pivotal bugs may need verification during each beta cycle. A big part of this work currently is going through the test results to figure out why test failures occurred (infrastructure, tests themselves, actual Firefox bug).

#Firefox 40.0.3 for mac update#

We create config files for the update tests, check their validity on mciconf and run them on at least two channels for each beta release cycle. QA analyzes the results of functional, remote, and update tests running on jenkins. Communication with the release coordination, release engineering, and automation teams is key. Reference (and migration / signoff plan: )Дuring the Beta cycle, there are at least 9 beta releases. Should have testing plans for features that we know may be turned off /on conditionally.Track feature milestones (for example the e10s tracking flags.).Conditional signoff for merge: (date, who signed off)Д¬ontinue triaging incoming bugs with community help.What, if any, conditions would actually block or delay the move to aurora?.We should encourage the use of 'feature' or verification needed keywords/flags.Continue assigning QA contact, verification + or -? What do we want to do with the iteration process.(Different for startup, plugin, crashes or specific platforms) We should decide on a threshold for 'crisis' level crash spikes/crash rates.Each topcrash should have a developer assigned, a QA contact, and tracking + or.e10s will be ready to move to Aurora if all bugs marked with tracking-e10s:m6+ and lower are fixed in Nightly. The earlier we can get these bug reports into shape for developers to prioritize them and work on them, the more likely they'll be fixed by release in April.Дuring the 40 Nightly cycle we will be working to help determine the state of the Electrolysis (e10s) project. Meet the entire QA team and hear what they're working on!Дuring the 6 weeks that Firefox 40 is on the Nightly channel, QA will focus on helping with the Firefox iteration planning, as well as with crash reporting and triaging newly reported bugs. Meet the Desktop QA team and hear what they're working on Raise quality concerns with the Release Management team Review testing and sign off every beta release MilestoneД¬onduct daily stability and bug triage, ensure features are ownedД¬onduct testing to ensure Firefox 40 Aurora builds are okay, sign off for updates on FridayД¬ontinue daily stability and bug triage, ensure features are tested Please consult the Rapid Release Calendar for more information. Our current walkthrough of the release and QA process might be changing due to recent reorgs. This is intended to be a minimal set of information to help Firefox QA understand and communicate the quality of upcoming releases. This page is to track testing of Firefox 40 from mozilla-central (Nightly) through to mozilla-release.