ostestr --no-discover does not create subunit file
Bug #1597111 reported by
Luz Cazares
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-testr |
Fix Released
|
Undecided
|
Luz Cazares |
Bug Description
Having os-testr V.0.7.0 installed
When using ostestr with --no-discover option. TCs are successfully run but results file under .testrepository is not created.
Underneath ostestr, it is running command: "python -m subunit.run" instead of "testr run.
In order to keep consistency with testr, the expectation would be to store resulting subunit file unser .testrepository. This is writing the output to disk and pass it to stdout or subunit-trace at the same time.
Changed in os-testr: | |
status: | New → Confirmed |
assignee: | nobody → Luz Cazares (luz-cazares) |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/339189
Review: https:/