--no-clean option speeds up repeating test execution by skipping the cleanup
process before and after testing.
Typical use case command could look like
./runtests.py -vv --no-clean --name integration.modules.ssh
In addition to traditional file system path test discovery it is
useful to run a test by stating it's dotted python path. For example,
this will only run the cmdmod integration tests from the
module suite::
$ runtests.py -n tests.integration.modules.cmdmod
The option parsing logic has changed without affecting the test
invocation commandline interface.
So, it should be possible to invoke tests like this:
python tests/runtests.py -u #only run unit tests
python tests/runtests.py -m #only run module tests
python tests/runtests.py #run all tests
python tests/runtests.py -v #run all tests with verbose output
python tests/runtests.py -vu #run unit tests with verbose output
Integration tests requiring a salt master and daemon were seperated
from pure unit tests. For now both are run with runtest.py. In
the future it could take arguments for which type of tests to run.
After a great deal of thought, I feel that the only way to reliably run
a test suite it to start a minion and master, and condition the data to
reflect the literal returns (take out the transport overhead).
This commit is the initial push towards this method of unit testing,
these test will be able to acctually test every aspect of salt.
This allows for tests to be written without too much change from the
normal unittest workflow. Now they should use the 'saltunittest'
namespace and we will need to import anything we need from the original
'unittest' or 'unittest2' namespace.
