Closed Bug 932347 Opened 12 years ago Closed 9 years ago

Make add-on tests teardown method less fragile

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect, P4)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jfrench, Unassigned, Mentored)

References

(
URL
)

Details

(Whiteboard: [lang=js][good first bug])

Split off from comment https://bugzilla.mozilla.org/show_bug.cgi?id=923720#c36 in bug 923720. We'd like the order all teardown calls in any Addon tests: a) in a consistent order in every test to help readability and comprehension b) locate the addonsManager.close() after any preference teardown action
It's not only about the refactoring but also how we close the add-on manager. As of now we don't ignore failures so if that line comes first we do not execute the remaining lines of code. I think that we should add true as parameter to the close method too.
Priority: P5 → P4
Summary: Order Addon teardowns consistently and correctly → Make add-on tests teardown method less fragile
I haven't had time to look at this bug, so unassigning myself in case someone else wants to take it.
Assignee: tojonmz → nobody
Status: ASSIGNED → NEW
Mentor: hskupin
Whiteboard: [mentor=whimboo][lang=js][good first bug] → [lang=js][good first bug]
I want to work on this bug. I am completely new here
Mentor: hskupin → andreea.matei
Hi Aniket, thanks for your interest in this bug. Here's the documentation for you to get familiar with mozmill tests: https://developer.mozilla.org/en-US/docs/Mozilla/QA/Mozmill_tests You'll find there how to install mozmill and clone a mozmill-tests repository, as well as configure your mercurial settings.
Mozmill tests are no longer in use. So closing this bug.
Status: NEW → RESOLVED
Closed: 9 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.