VPNaaS Functional job test module discovery
Bug #1445056 reported by
Paul Michali
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
High
|
Paul Michali | ||
Bug Description
With the current functional job setups, if there are import errors in test modules, the errors will be silently ignored and tests not invoked. Apparently there is an issue with the unittest package and import errors.
Because VPNaaS has two reference driver implementations currently, and they each require a different test setup and have test cases that differ, there are two functional jobs, of which each tests different modules.
Need to switch to unittest2, or modify the method used to discovery modules to run in the functional jobs.
| Changed in neutron: | |
| assignee: | nobody → Paul Michali (pcm) |
| status: | New → In Progress |
| Changed in neutron: | |
| milestone: | none → liberty-1 |
| importance: | Undecided → High |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to neutron-vpnaas (master) | #1 |
| Changed in neutron: | |
| status: | In Progress → Fix Committed |
| Changed in neutron: | |
| status: | Fix Committed → Fix Released |
| Changed in neutron: | |
| milestone: | liberty-1 → 7.0.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0782a2ba25cd8fc
Author: Paul Michali <email address hidden>
Date: Wed Apr 15 17:52:25 2015 -0400
VPNaaS: Refactor functional tests to use discover
Reworking so that modules with import errors are not silently
ignored (which was happening when using unitttest for loading
modules).
Verified that for each of the two functional jobs, the associated
modules are tested (some driver specific, some common).
Change-Id: I240a66cddb64de
Closes-Bug: #1445056