QA/Platform/Graphics/Betabreakers/Firefox 48
The purpose of this testrun is to ensure disabling WARP (bug 1260507,bug 1260944) did not regress graphics rendering and performance.
Contents
Systems
Systems to be tested will be tracked in this spreadsheet.
Testing
Preamble
We are looking for the following issues when they occur in Firefox 48 but not in Firefox 47:
- hangs or visibly slow performance
- visible glitches in the UI outside of the video
- crashes (be sure to submit the crash report)
- if a test fails (eg. timeout, never loads, etc)
- Note: Only report issues that occur in Firefox 48 but do not occur in Firefox 47.
- Note: Failures in Firefox 47 should be used as the baseline and noted in the spreadsheet.
If you encounter an issue, file a bug report with the following information and then carry on with your testing:
- a detailed description of the issue with steps to reproduce
- a copy of about:support as a plain-text attachment
- a link to any crash reports you submitted (retrievable from the about:crashes page)
- Note: Only file bug reports for behaviours where Firefox 48 is clearly worse than Firefox 47.
- Note: Only file one bug report per issue. If multiple systems experience similar symptoms, please attach the system information to the existing bug report.
Once you've completed all testing please go back and carry on the investigation of any bug report(s) you filed.
Can the issue be reproduced with Firefox 48?
- Yes: Can the issue be reproduced in Firefox 49?
- Yes: Can the issue be reproduced in Firefox 46?
- Yes: Can the issue be reproduced in another browser? (Win 7/8 test Chrome and IE, Win 10 test Chrome and Edge)
- Yes: Update the bug noting which browsers are affected
- No: Update the bug noting which browsers are not affected
- No: Use mozregression to narrow down the regression range
- Yes: Can the issue be reproduced in another browser? (Win 7/8 test Chrome and IE, Win 10 test Chrome and Edge)
- No: Use mozregression to narrow down the fix range
- Yes: Can the issue be reproduced in Firefox 46?
- No: Update the bug noting the issue is not reproducible
The Test
- 1. Establish a baseline with Firefox 47
- Install Firefox 47.0a2 (32-bit or 64-bit)
- Run installer and select customize
- Put the install in a custom directory (C:\Betabreakers48 for purposes of this example)
- Do not allow Firefox to start when the installation completes
- Start Firefox with a new profile:
- Change directory to the folder where you installed Firefox: cd C:\Betabreakers48
- Run firefox.exe: firefox.exe -P -no-remote - This will bring up our profile selector window.
- Use the "Create Profile" button to create a profile new profile
- Once the profile is created, select it, and then click "Start Firefox"
- Load the about:support page and copy the GPU Accelerated Windows and WebGL Renderer fields from the Graphics section to this document
- 2. Play some WebGL demos and make note of how well the demos perform
- 3. Re-test after updating to Firefox 48
- Go to the About dialog (found via the Help menu) to install any updates
- Restart Firefox when prompted to do so
- Load the about:support page once Firefox restarts
- Verify that the Version field in Application Basics reads 48.0a2
- Copy the Compositing and WebGL Renderer fields from the Graphics section to this document
- Play the same demos as you did in Step 2 and assess whether the demos perform better or worse than Firefox 47
- If you encounter an issue
File a bug report following the instructions in the Preamble, add the Bug ID to this document and continue testing once the report is on file.
Bugs
Bugs reported and tagged with betabreakers-fx46 appear automatically below
No results.
0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);