[openstack-dev] How to turn tempest CLI tests into python-*client in-tree functional tests
Robert Collins
robertc at robertcollins.net
Wed May 6 07:59:11 UTC 2015
On 14 February 2015 at 10:26, Joe Gordon <joe.gordon0 at gmail.com> wrote:
> Digging through the logs this originated from this bug:
> https://bugs.launchpad.net/tempest/+bug/1260710
>
> Its probably not needed everywhere and in all the clients.
So I've looked more closely at this.
Its actually an antipattern. It tells testr that tests are appearing
and disappearing depending on what test entry point a user runs each
time.
testr expects the set of tests to only change when code changes.
So, I fully expect that this pattern is going to lead to wtf moments
now, and likely more in future.
Whats the right forum for discussing the pressures that lead to this
hack, so we can do something that works better with the underlying
tooling, rather than in such a disruptive fashion?
-Rob
--
Robert Collins <rbtcollins at hp.com>
Distinguished Technologist
HP Converged Cloud
More information about the OpenStack-dev
mailing list