Assert params' order in Service Chain tests is incorrect
Bug #1418737 reported by
Sumit Naiksatam
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Group Based Policy |
In Progress
|
Medium
|
Sumit Naiksatam | ||
Bug Description
The order needs to be (expected_result, actual_result), where is most cases in:
its the reverse. This creates a lot of confusion when debugging failed tests.
| summary: |
- Assert params order in Service Chain tests is incorrect + Assert params' order in Service Chain tests is incorrect |
| Changed in group-based-policy: | |
| status: | Confirmed → In Progress |
| Changed in group-based-policy: | |
| milestone: | kilo-gbp-1 → kilo-gbp-2 |
| tags: | added: juno-backport-potential |
| Changed in group-based-policy: | |
| milestone: | kilo-gbp-2 → kilo-gbp-3 |
| Changed in group-based-policy: | |
| milestone: | kilo-gbp-3 → next |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on group-based-policy (master) | #1 |
To post a comment you must log in.
Change abandoned by Sumit Naiksatam (<email address hidden>) on branch: master
Review: https:/
Reason: Old patch, probably not needed, can be revived if needed.