Merge lp:~fgimenez/snappy/failover-with-fake-update into lp:~snappy-dev/snappy/snappy-moved-to-github
| Status: | Merged |
|---|---|
| Approved by: | Leo Arias on 2015-07-14 |
| Approved revision: | 573 |
| Merged at revision: | 578 |
| Proposed branch: | lp:~fgimenez/snappy/failover-with-fake-update |
| Merge into: | lp:~snappy-dev/snappy/snappy-moved-to-github |
| Diff against target: |
36 lines (+9/-3) 2 files modified
_integration-tests/tests/common/common.go (+8/-2) _integration-tests/tests/failover/failover_test.go (+1/-1) |
| To merge this branch: | bzr merge lp:~fgimenez/snappy/failover-with-fake-update |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Leo Arias | 2015-07-09 | Approve on 2015-07-14 | |
|
Review via email:
|
|||
Commit Message
Always use fake update for failover.
Description of the Change
Always use fake update for failover.
If we are using one image with an already available update (for instance, when validating the RC), the current CallUpdate method first does the update and, if didn't returned anything, the fake update.
Then, depending on the availability of an actual update the failover tests after the successful reboot can end on the current version (there was an update available and we didn't the fake) or the current version minus one (there wasn't an available update and we did the fake).
Because we cannot control the availability of an update to have a controlled state we should do always a fake update, moreover we are not testing here the update itself, but the failover capabilities.
| Leo Arias (elopio) wrote : | # |
ok, I finally got to see this running after enabling the whole suite in the other branch. Land land land!


I don't want to delay this anymore. Looks good, and having more control over the tests makes a lot of sense.