QA/Platform/Graphics/Firefox 40
Jump to navigation
Jump to search
Suggested Systems
NOTE: Target systems with ANGLE WebGL renderer in about:support::Graphics
- Run tests once with the latest GPU driver available and a second time with whichever older driver version you have access.
| System | Platform | CPU | GPU |
|---|---|---|---|
| Lothar | Windows 7 32-bit | Intel C2D 2.13GHz | NVidia GeForce 7300LE 256MB |
| Marwyn | Windows 7 64-bit | AMD Phenom II X4 3.00GHz | AMD Radeon HD3450 256MB |
| Vader | Windows 8.1 64-bit | Intel Core i5-460M 2.53GHz | Intel HD / NVidia Geforce GT 420M 1024MB hybrid |
| Onyxia | Windows XP SP3 | AMD Athlon64 X2 4200+ 2.20GHz | 2x nVidia GeForce 7950 GT 512MB SLI |
| Ertan | Windows 7 64-bit | AMD A8-3500M 1.50GHz | AMD Radeon IGP 6620G |
| Surface 1-2 | Windows 8.1 64-bit | Intel Core i5-3317U 2.53GHz | Intel HD Graphics 4000 1720MB (shared) |
Instructions
Set up the test environment
- 1. Install Firefox
- Download https://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-aurora/firefox-40.0a2.en-US.win32.installer.exe
- Run installer and select customize
- Put the install in a known directory (C:\Aurora for purposes of this example)
- Do NOT allow it to launch Firefox at the end of the install
- 2. Disable the automatic updater
- Open C:\Aurora\defaults\pref\channel-prefs.js in a text editor
- Change the line reading pref("app.update.channel", "release"); to pref("app.update.channel", "foobar");
- Save and Close the text file
- 3. Launch Firefox with a clean profile
- Run cmd.exe
- Change directory to the folder where you installed Firefox: cd C:\Aurora
- 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"
- 4. Make sure e10s is enabled
- Menu button > Options > General > Enable E10S (multi-process) should be checked
- If not, check the box and restart Firefox
Tests
- Play one of the game demos for 15 minutes, keeping an eye out for visual/audible/control issues and crashes.
- if you hit an issue with e10s on, retest the demo with e10s disabled
- if you hit an issue with e10s off, retest the demo in Chrome
- file bug reports for issues that only reproduce in Firefox with e10s on
- be sure you're retesting from scratch (assets are cached on first run)
Results
- System, game tested, results