8a4396e3d3
This commit switches the Tempest CLI commands to internally use stestr instead of testrepository. At this point in time the testrepository project is effectively unmaintained and stestr was a fork started to have an actively maintained test runner. It also focuses on being a dedicated python test runner, instead of an abstract test runner interface for any tests that emit subunit. Besides the bug fixes and other improvements included with stestr, this switch provides a number of advantages for tempest. Primarily stestr has a real python API for invoking the test runner directly from python. This means we can simplify the wrapper code to simply call a function instead of building out a set of CLI arguments and passing that to the CLI processor. Co-Authored-By: Matthew Treinish <mtreinish@kortar.org> Depends-On: Ic1fa3a98b6bcd151c489b078028687892655a19b Depends-On: I3855aad5ce129ec8ccb87c05f7aa709b74070efe Depends-On: https://review.openstack.org/529490/ Change-Id: I6f5fa7796c576b71c4a0dde66896974a8039a848
14 lines
682 B
YAML
14 lines
682 B
YAML
---
|
|
features:
|
|
- The Tempest CLI commands have switched from calling testrepository internally
|
|
to use stestr instead. This means that all of the features and bug fixes from
|
|
moving to stestr are available to the tempest commands.
|
|
|
|
upgrade:
|
|
- Tempest CLI commands will no long rely on anything from testr. This means any
|
|
data in existing testr internals that were being exposed are no longer
|
|
present. For example things like the .testr directories will be silently
|
|
ignored. There is a potential incompatibility for existing users who are
|
|
relying on test results being stored by testr. Anything relying on previous
|
|
testr behavior will need to be updated to handle stestr.
|