nested stack error path test coverage lacking
Bug #1195310 reported by
Steven Hardy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Heat |
Fix Released
|
Low
|
Liang Chen | ||
Bug Description
Ref:
https:/
I tried to write a test to cover that one line of error-path in nested stack creation - it's actually quite hard due to the nestedness and coroutine magic, so like a true engineer I gave up and moved on to something easier ;)
Raising this to track figuring out the cleanest way to add coverage and avoid errors like the one captured in the patch above.
Revision history for this message
| Thomas Herve (therve) wrote | #1 |
| Changed in heat: | |
| milestone: | none → havana-3 |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in heat: | |
| assignee: | nobody → Liang Chen (cbjchen) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to heat (master) | #2 |
| Changed in heat: | |
| status: | Triaged → In Progress |
| Changed in heat: | |
| milestone: | havana-3 → havana-2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to heat (master) | #3 |
| Changed in heat: | |
| status: | In Progress → Fix Committed |
| Changed in heat: | |
| status: | Fix Committed → Fix Released |
| Changed in heat: | |
| milestone: | havana-2 → 2013.2 |
To post a comment you must log in.
Relatedly, it should be easy to adapt the create test for the suspend case.