It sounds like the censuses in this thread is:
In the long run, we want to kill run_tests.sh in favor of explaining how to
use the underlying tools in a TESTING file.
But in the short term, we should start moving toward using a TESTING file
(such as https://review.openstack.org/#/c/33456/) but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/21/2013 01:44 PM, Joe Gordon wrote:
It sounds like the censuses in this thread is:
In the long run, we want to kill run_tests.sh in favor of
explaining how to use the underlying tools in a TESTING file.
I agree. I'd like to add that 'long
On 13-06-18 04:59 AM, Thierry Carrez wrote:
Personally I would introduce a TESTING file that would describe all
available methods for running tests, and rename/move run_tests.sh to
something less discoverable... so that people looking for ways to run
tests would find TESTING first. Then if
Excerpts from Thierry Carrez's message of 2013-06-18 01:59:57 -0700:
Joe Gordon wrote:
Reasons to keep run_tests.sh:
* there is no possibility to run tests with testtools instead of testr.
This feature allows us to use the debugger.
* in some projects tox doesn't use a testr wrapper to
Hi All,
A patch to move the run_tests.sh script into oslo-incubator (
https://review.openstack.org/#/c/32736/), has brought up the bigger
question of what is the future of './run_tests.sh.'
This seems like a topic that directly affects all developers, so it sounded
like it should be brought to
