api-tests fail when flavor doesn't exist
Bug #1393558 reported by
Amit Gandhi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Poppy |
Fix Released
|
Medium
|
Amit Gandhi | ||
Bug Description
API tests are failing when the expected flavor does not already exist.
This creates a dependency where the prerequisite has to already be in place. That may not always be the case (e.g. user running api-tests for the first time against a new storage instance).
Instead, the API tests should check if the expected flavor already exists.
If it does not already exist, then the test should attempt to create the new flavor.
If it can't create the new flavor, then the test execution should abort.
If it does create the new flavor, then the tests should continue and run to completion.
| Changed in poppy: | |
| assignee: | nobody → Amit Gandhi (amit-gandhi) |
| status: | New → Confirmed |
| Changed in poppy: | |
| status: | Confirmed → In Progress |
Revision history for this message
| Amit Gandhi (amit-gandhi) wrote | #1 |
| Changed in poppy: | |
| status: | In Progress → Fix Committed |
| Changed in poppy: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in https:/