Closed
Bug 1530271
Opened 6 years ago
Closed 6 years ago
Regression testing for preferences tab
Categories
(Thunderbird :: Preferences, defect)
Thunderbird
Preferences
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird 67.0
People
(Reporter: darktrojan, Assigned: darktrojan)
References
Details
Attachments
(1 file, 1 obsolete file)
|
(deleted),
patch
|
mkmelin
:
review+
|
Details | Diff | Splinter Review |
I'm working on a suite of tests for the preferences tab. Currently our only test that things are as they should be is a calendar mozmill test that could be failing for a number of other reasons.
So far I've created functions that test check boxes and radio buttons are working as they should be, including any other bits of UI are disabled as appropriate. I'm doing a Try run and will post for review when that is successful.
|
Assignee | |
Comment 1•6 years ago
|
||
Try run is good.
Attachment #9046290 -
Flags: review?(mkmelin+mozilla)
|
|
Assignee | |
Comment 2•6 years ago
|
||
Attachment #9046290 -
Attachment is obsolete: true
Attachment #9046290 -
Flags: review?(mkmelin+mozilla)
Attachment #9048004 -
Flags: review?(mkmelin+mozilla)
|
||
Comment 3•6 years ago
|
||
Comment on attachment 9048004 [details] [diff] [review]
1530271-preferences-tests-2.diff
Review of attachment 9048004 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good, but at least locally the tests fail. r=mkmelin if/when they work on our servers
Attachment #9048004 -
Flags: review?(mkmelin+mozilla) → review+
|
|
Assignee | |
Comment 4•6 years ago
|
||
Possibly that's because I've been doing this alongside bug 1527770. I'm not sure if I've run this version of the patch without the one on that bug.
Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/b0760df47d16
Regression testing for the preferences tab; r=mkmelin
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Updated•6 years ago
|
Target Milestone: --- → Thunderbird 67.0
You need to log in
before you can comment on or make changes to this bug.
Description
•