Closed Bug 604364 Opened 11 years ago Closed 5 years ago
Software update tests should be able to test watershed releases
There are situations when we have to run the update step multiple times instead of only once. Here some fictive examples: 4.0 beta4 build 1 -> 4.0 beta4 build 3 -> 4.0 beta5 build1 3.5.14 -> 3.5.15 -> 3.6.11 We need a kind of state machine, which is not available yet. Means we have to wait for the mozmill implementation.
Move of Mozmill Test related project bugs to newly created components. You can filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Product: Testing → Mozilla QA
Version: Trunk → unspecified
Is this complete?
Whiteboard: [mozmill-update] → [mozmill-update][needs mozmill 2]
This is finally unblocked so that we can get started to work on it. It should be done within the next 6 weeks.
Priority: -- → P2
Whiteboard: [mozmill-update][needs mozmill 2] → [update]
We want to support this with Marionette tests. So we can hopefully address it soon once bug 1129843 has been landed.
QA Contact: hskupin
Summary: Software update tests should be able to test multiple update steps → Software update tests should be able to test watershed releases
This feature is actually not wanted anymore. To test watershed releases multiple ondemand update tests would have to be triggered in mozmill-ci.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.