Closed Bug 1473103 Opened 2 years ago Closed Last year
Regression test for mozglue DLL blocklist
46 bytes, text/x-phabricator-request
|Details | Review|
We might have been able to catch bug 1472030 before it reached Beta if we had a proper regression test for the DLL blocklist. I noticed that our existing blocklist already contains entries for "mozdllblockingtest.dll" and "mozdllblockingtest_versioned.dll" but a cursory code search doesn't show those libraries actually existing anywhere! In addition to testing some of the essential functionality, I'd also like us to validate that the entire array of blocklist entries is being generated correctly. In particular, I'd like to ensure that if we compare the ArrayLength(gWindowsDllBlocklist) == (the length of the blocklist if we scan it in a while loop searching for the terminating null entry). Carl, since you've already been dabbling in that area with gtests et al, I thought I'd send this your way.
Comment on attachment 8992890 [details] Bug 1473103: Add unit tests for DLL blocklist integrity; r?aklotz Aaron Klotz [:aklotz] has approved the revision.
Attachment #8992890 - Flags: review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/9207b4b0e5db Add unit tests for DLL blocklist integrity; r=aklotz
Is this something we might want to consider for Beta backport or is manual QA sufficient?
I don't see any need to backport this.
You need to log in before you can comment on or make changes to this bug.