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
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?
Robert Collins firstname.lastname@example.org
HP Converged Cloud