Closed Bug 647561 Opened 14 years ago Closed 13 years ago

Ensure Adblock Plus filterset loaded during Talos performance testing

Categories

(Testing :: Talos, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: emorley, Unassigned)

References

Details

From: http://blog.mozilla.com/addons/2011/04/01/improving-add-on-performance/comment-page-1/#comment-152084 When Adblock Plus is being tested, it currently doesn't have a filterset loaded, which means the results produced are not representative of real-word usage. Similar to bug 639898, it would be helpful to know what about:config prefs need to be set on startup, to ensure that the test run is performed with the EasyList filterset active (presuming it's the most used compared to say Fanboy's list). So... Wladimir: What about:config prefs need to be set to ensure Easylist (or whichever you prefer) is loaded during the tests? Alice: Would you be ok including them in the addon.config file that was created in bug 639898? Thanks!
It won't work with about:config prefs. You need a file adblockplus/patterns.ini in the profile that has the necessary data. And "necessary data" probably means all EasyList data - I doubt that you want to download it during testing. Please also note that the first startup isn't representative for Adblock Plus - the first time Adblock Plus needs to save patterns.ini (will happen on shutdown if for example a webpage is browsed to that had filter hits) it will also save cache files that should speed up next startup quite significantly. So it really isn't trivial...
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
[Blocking Requested - why for this release]:
blocking-b2g: --- → 2.1?
talos doesn't run on b2g, removing the blocking b2g flag
blocking-b2g: 2.1? → ---
You need to log in before you can comment on or make changes to this bug.