Broken processing of 'skipped' status for tests
Bug #1282106 reported by
Artem Roma
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Committed
|
Medium
|
Artem Roma | ||
Bug Description
Info about environment:
- release - 4.1
- fuel-ostf commit sha - "f86abe5544b5ff
Description:
Tests can have status "skipped" which is assigned to them if test run was skipped by rising SkipTest exception that is processed in our custom plugin for nose via type comparison. Mentioned exception can be raised either via calling method skipTest of TestCase class (of unittest or unittest2 modules) or by directly raise unittest2.SkipTest.
And the problem is that type comparison in addError hook of nose plugin is not triggered in second variant which leads to tests having 'error' status instead of 'skipped'.
Additional info:
One can test this bug on test environment for ostf-adapter by launching its functional tests.
| Changed in fuel: | |
| status: | New → In Progress |
| Changed in fuel: | |
| milestone: | 4.1 → 5.0 |
| Changed in fuel: | |
| status: | In Progress → Confirmed |
Revision history for this message
| Openstack Gerrit (openstack-gerrit) wrote Fix proposed to fuel-ostf (master) | #1 |
| Changed in fuel: | |
| status: | Confirmed → In Progress |
| Changed in fuel: | |
| milestone: | 5.0 → 5.1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to fuel-ostf (master) | #2 |
| Changed in fuel: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/