With recent builds on trunk we do no longer support and ship the default plugin. That said we will have to update the Mozmill test so it will use the test plugin instead. The proposal is to: 1. Have 32-bit and 64-bit versions for all platforms available in our repository 2. Copy the files into the plugins folder before the test 3. Execute the JS command plugins.refresh() to register the plugin 4. Run the test 5. Remove the plugin files 6. Execute the JS command plugins.refresh() to hopefully unregister the plugin We will also have to update out test page.
You'll have to build the test plugin yourself. It isn't built for optimized builds.
(In reply to comment #1) > You'll have to build the test plugin yourself. It isn't built for optimized > builds. And that also implies different versions for 32-bit and 64-bit builds, right? How can i programmatic check if we run a 64-bit build? The UA isn't really helpful at least on OS X.
Mass move of Mozmill Test related project bugs to newly created components. You can filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Component: Add-ons Manager → Mozmill Tests
Product: Toolkit → Mozilla QA
QA Contact: add-ons.manager → mozmill-tests
Version: Trunk → unspecified
Can this be marked RESOLVED WONTFIX? This test is 1.9.2-only. Otherwise, what needs to be done to get it fixed?
Summary: [mozmill] Update testDisableEnablePugin.js to use the test plugin instead of the default plugin → Update testDisableEnablePugin.js to use the test plugin instead of the default plugin
In current branches we only run this test if a plugin has been installed on the users system. So given the complication of compiling it correctly and supplying it to the testers system, I would agree with a wontfix.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.