Some extensions (this is at least is the case of the Fidesfit-client extension) may want to check the presence of a user password (stored in the login manager) at startup (when the browser window loads) and open a mandatory configuration window the user has to fill in.
If this password is programmatically set in the setupModule function, it's already too late, the extension is already loaded and the configuration window will be opened at the beginning of each Mozmill test, which will be very tedious, impractical.
One solution is to use the Mozmill "--profile" option with a profile directory containing a specially filled signons.sqlite file, along with its key3.db file, that only contains the needed dummy login+password for the specific tests. This works.
But it isn't really resilient, since it's based on how this information is stored. And so far I've only tested this on Linux (maybe logins + passwords are stored differently for example on Windows leveraging possible builtin secure store there).
So a practical Mozmill enhancement would be to be able to specify a password file (containing login and password pairs), either in JSON or .ini format, as an option to Mozmill.
That has already been filed as bug 568943 a while back.
(In reply to comment #1)
> That has already been filed as bug 568943 a while back.
Yes kind of. But this new ticket is really more focused and with a usecase.
The use case is clear since the beginning of bug 568943. I made a comment over there. So please let us focus on the initial bug request.
*** This bug has been marked as a duplicate of bug 568943 ***