Closed Bug 1088534 Opened 11 years ago Closed 7 years ago

Add a test to verify that basic Firefox operations work ok with the enabled complete theme or persona

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: cosmin-malutan, Assigned: mihaelav)

Details

(Whiteboard: [sprint])

Attachments

(1 file)

We need to cover the last step from the moztrap below to have full automation coverage. My suggestion is to make it a mozmill tests, since we have libraries for all the steps needed, and for chrome we have the helper functions in diffrent head.js files and it will be harder to develop the tests https://moztrap.mozilla.org/manage/case/11507/
This cannot be a browser-chrome test? None of those actions require a restart or shotcuts.
It can, it was only a suggestion.
If we don't have specific requirements for a Mozmill test, we should always think about a browser chrome or mochitest first. Those will be run per check-in and will inform about regressions immediately. Only if it cannot be done as such a test, Mozmill would be an option.
Assignee: nobody → mihaela.velimiroviciu
Status: NEW → ASSIGNED
Whiteboard: [sprint]
I will continue here.
Assignee: mihaela.velimiroviciu → andreea.matei
QA Contact: hskupin → mihaela.velimiroviciu
Attached patch v1Splinter Review
try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=b3f924381b71 Gijs, can you please help with reviewing this or suggest someone else who can? Thank you!
Assignee: andreea.matei → mihaela.velimiroviciu
Attachment #8546722 - Flags: review?(gijskruitbosch+bugs)
Comment on attachment 8546722 [details] [diff] [review] v1 Review of attachment 8546722 [details] [diff] [review]: ----------------------------------------------------------------- Why the head.js changes? The functions don't seem in use, and most of them are already in there in one form or another (esp. waitFor). The summary also talks about complete themes, not just lightweight themes. You'd need a restart for complete themes, so probably you need The patch also relies on theme.xpi from a wildly different directory, which seems a little scary... Finally, is it really useful to do this kind of testing in an automated way? I expect that if the manual tests found issues before, it's because there was a human sitting in front of the computer that could also see and think. I'm much more skeptical about the kind of testing this code does to find similar issues... All in all I would be inclined to wontfix. :-\
Attachment #8546722 - Flags: review?(gijskruitbosch+bugs)
(In reply to :Gijs Kruitbosch from comment #6) > The summary also talks about complete themes, not just lightweight themes. > You'd need a restart for complete themes, so probably you need ... a marionette test.
Mozmill is dead, WONTFIX the remaining bugs.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: