On Wed, 6 May 2015, Robert Collins wrote:
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?
I'd appreciate here (that is on this list) because from my
perspective there are a lot of embedded assumptions in the way testr
does things and wants the environment to be that aren't immediately
obvious and would perhaps be made more clear if you could expand on
the details of what's wrong with this particular hack.
I tried to come up with a specific question here to drive that
illumination a bit more concretely but a) not enough coffee yet b)
mostly I just want to know more detail about the first three
paragraphs above.
Thanks.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
