Closed Bug 634907 Opened 9 years ago Closed 9 years ago

need way for mozmill tests to start up without accounts

Categories

(Thunderbird :: Testing Infrastructure, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED
Thunderbird 3.3a3

People

(Reporter: Bienvenu, Assigned: rain1)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

For testing the setup instrumentation code, it would be very helpful to have a way for mozmill tests to start up without the accounts pre-setup, so we can simulate initial run after download. 

Sid has already come up with a patch for this, which works great for my purposes. If you add a wrapper.py file containing NO_ACCOUNTS = True to your test directory, your profile won't have accounts pre-setup at load.
So we already have an option to pre-load a prefs.js file (see migration-from-tb2), I'm not convinced that its necessary to add a no accounts option considering you can just create your own prefs.js for the directory.
(In reply to comment #1)
> So we already have an option to pre-load a prefs.js file (see
> migration-from-tb2), I'm not convinced that its necessary to add a no accounts
> option considering you can just create your own prefs.js for the directory.

My understanding is that the pre-loaded custom prefs js file is additive, not replacing the existing prefs.js file, and in any case, the existing prefs.js file is loaded last, so whatever is in there wins. And that's the file that has the accounts set up.
Standard8 and I talked about this - he was suggesting overwriting the prefs.js file with my own prefs.js file w/o the account manager settings. I believe I convinced him that was a bit fragile, because every time someone changes the prefs in runtest.py, they'd need to make a similar change to my test.
Yeah, that sounds right.
so who should review this? Standard8?
Attachment #513134 - Flags: review?(bugzilla)
Blocks: 632639
Comment on attachment 513134 [details] [diff] [review]
sid's working patch

>+        # Do not allow fonts to be upgraded
>+        'mail.font.windows.version': 1
...
>-        # Do not allow fonts to be upgraded
>-        'mail.font.windows.version': 2

Is this change intentional, if so why?
Good catch -- no, it isn't intentional. I think it was still 1 when I sent bienvenu the patch, but I changed it to 2 later in the tree. When the patch was rebased the deletion was updated but the addition wasn't.
Comment on attachment 513134 [details] [diff] [review]
sid's working patch

r=Standard8 with the previously mentioned item fixed.

sid, could you land this?
Attachment #513134 - Flags: review?(bugzilla) → review+
https://hg.mozilla.org/comm-central/rev/4c46f52d847d
Status: NEW → RESOLVED
Closed: 9 years ago
OS: Windows 7 → All
Hardware: x86 → All
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 3.3a3
You need to log in before you can comment on or make changes to this bug.