Closed Bug 776917 Opened 13 years ago Closed 13 years ago

Tests should never define constants and call methods in the global scope but in setupModule()

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

With the latest changes to global compartments we have seen that a lot of our tests are failing in getting the elements on a local page. Reason is that HTTP can't load the requested local pages. See bug 767332 comment 12 for more information. So what we should do now is to change all of our tests so we never add code which gets executed when the module is loaded but when setupModule() is called from the runner. I will take this and have a patch tomorrow lately.
As it has been turned out it was not a failure due to global constants. So we can keep as what we have right now and don't have to make those changes yet.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.