Skip to content
Snippets Groups Projects
Commit 06c9a9d6 authored by Iustin Pop's avatar Iustin Pop
Browse files

Add note about running individual test cases


This was asked a few times offline, so let's document it.

Signed-off-by: default avatarIustin Pop <iustin@google.com>
Reviewed-by: default avatarMichael Hanselmann <hansmi@google.com>
parent b07afbb3
No related branches found
No related tags found
No related merge requests found
...@@ -141,6 +141,29 @@ for example, in bash via ``.bashrc``:: ...@@ -141,6 +141,29 @@ for example, in bash via ``.bashrc``::
or in emacs via ``completion-ignored-extensions`` (run ``M-x or in emacs via ``completion-ignored-extensions`` (run ``M-x
customize-var completion-ignored-extensions``). customize-var completion-ignored-extensions``).
Running individual tests
~~~~~~~~~~~~~~~~~~~~~~~~
When developing code, running the entire test suite can be
slow. Running individual tests is possible easily for unit-tests, less
so for shell-tests (but these are faster, so it shouldn't be needed).
For Python tests::
$ export PYTHONPATH=$PWD
$ python ./test/ganeti.%mytest%
For Haskell tests::
$ make htest/test && ./htest/test -t %pattern%
Where ``pattern`` can be a simple test pattern (e.g. ``comma``,
matching any test whose name contains ``comma``), a test pattern
denoting a group (ending with a slash, e.g. ``Utils/``), or more
complex glob pattern. For more details, see the documentation (on the
`test-framework homepage
<http://batterseapower.github.com/test-framework/>`_).
Packaging notes Packaging notes
=============== ===============
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment