QA/MergeCompatibilityTesting/BlocklistTest-12-2011: Difference between revisions
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
* [https://wiki.mozilla.org/Blocklisting/Testing Test Procedure] | * [https://wiki.mozilla.org/Blocklisting/Testing Test Procedure] | ||
* [https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers List of Blocked Graphics Cards/Drivers] | * [https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers List of Blocked Graphics Cards/Drivers] | ||
* [https://docs.google.com/spreadsheet/ccc?key=0AmwBbtTVVjHsdF9oMU8wWHZRTGJiTk1wNkFnWUNMdmc&hl=en_US#gid=0 Complete Summary of What's Blocked] | |||
Revision as of 03:51, 7 December 2011
Blocklist Testing Dec 2011
Overview and motivation
From doug's email: 11-23-11
I've made some changes to driver blocklisting recently which hit every platform and enable a downloadable blocklist on them. There are tons of edge cases here which I don't have the hardware to test and I think this would benefit from a proper QA run; it would be pretty bad if there were mistakes here, since users could be blocked from features even if their drivers are fine, and others could be allowed to use features that are supposed to be blocked. This whole effort is done primarily to allow blocklisting Android devices, but as a side effect, other OS's can now use this system.
- For reference here are the bugs relevant to this:
- 668004- Generalize the downloaded GPU blacklist to non-Windows platforms
- 699482 - Talos complains about GfxDriverInfo static constructors, they might slow down startup
- 704710 - Refactor GfxDriverInfo/GfxInfo(Base) to support string device and vendor IDs
- 689598 - Implement downloadable device blacklisting for Android
- 700124 - Attempting to use JNI in child process [@ mozilla::AndroidBridge::EnsureJNIThread
Test Plan
Here's a link to a wiki that contains some vital information for our block-list testing: