With the help of the mozmill-restart command line wrapper we can run restart tests against Firefox. While creating a test for extension installing I miss a way to pass values from the first test to a successive one, e.g. when I install an extension in test1.js I wanna check for it in test2.js. But since I don't know which extension has been installed in test2.js I can only check for the existence of an extension but not if the correct one has been installed. Mikeal, could we implement something that would allow to pass values back to the python script and which will resent to Mozmill for successive tests?
Priority: -- → P2
This shouldn't be too hard, but the persistence would be limited to objects that are JSON serializable.
That sounds good. Something we could consider for Mozmill 1.3?
Does this block any particular test you want to write?
Not yet. I use constants so far. That why we have time for a fix.
Mikeal, it would be great to get this fixed so we can use that way to pass the build id to the next test. Otherwise I will have problems to verify the update.
Whiteboard: [mozmill-1.3?] → [mozmill-1.2.1]
Mikeal, it would be really really helpful for me for the update tests when we can get this feature in. I need a way to check if the offered update has been correctly installed. Therefor I need some values from test1.js in test2.js.
Severity: normal → major
Whiteboard: [mozmill-1.2.1] → [mozmill-1.2.2]
Committed r548 In your test module there is now an object named "persisted", any attributes you set on it must be JSON serializable and it will be available in every test across a test run.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Ok with r549 and r550 we had to add two more fixes. Now it works fine. Thanks Mikeal!
Status: RESOLVED → VERIFIED
Whiteboard: [mozmill-1.2.2] → [verified-mozmill-1.2.2][mozmill-doc-needed]
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.