mirror of
https://github.com/kevingruesser/bootstrap-vz.git
synced 2025-08-22 09:50:37 +00:00
f62c8ade99
Up until now I didn't see the point of using spaces for indentation. However, the previous commit (a18bec3) was quite eye opening. Given that python is an indentation aware language, the amount of mistakes that went unnoticed because tabs and spaces were used at the same time (tabs for indentation and spaces for alignment) were unacceptable. E101,W191 have been re-enable in the tox flake8 checker and the documentation has been modified accordingly. The following files have been left as-is: * bootstrapvz/common/assets/extlinux/extlinux.conf * bootstrapvz/common/assets/init.d/expand-root * bootstrapvz/common/assets/init.d/generate-ssh-hostkeys * bootstrapvz/common/assets/init.d/squeeze/generate-ssh-hostkeys * bootstrapvz/plugins/docker_daemon/assets/init.d/docker * bootstrapvz/providers/ec2/assets/bin/growpart * bootstrapvz/providers/ec2/assets/grub.d/40_custom * bootstrapvz/providers/ec2/assets/init.d/ec2-get-credentials * bootstrapvz/providers/ec2/assets/init.d/ec2-run-user-data * docs/_static/taskoverview.coffee * docs/_static/taskoverview.less * tests/unit/subprocess.sh
22 lines
709 B
ReStructuredText
22 lines
709 B
ReStructuredText
The testing framework consists of two parts:
|
|
The unit tests and the integration tests.
|
|
|
|
The `unit tests <unit>`__ are responsible for testing individual
|
|
parts of bootstrap-vz, while the `integration tests <integration>`__ test
|
|
entire manifests by bootstrapping and booting them.
|
|
|
|
Selecting tests
|
|
---------------
|
|
To run one specific test suite simply append the module path to tox:
|
|
|
|
.. code-block:: sh
|
|
|
|
$ tox -e unit tests.unit.releases_tests
|
|
|
|
Specific tests can be selected by appending the function name with a colon
|
|
to the modulepath -- to run more than one tests, simply attach more arguments.
|
|
|
|
|
|
.. code-block:: sh
|
|
|
|
$ tox -e unit tests.unit.releases_tests:test_lt tests.unit.releases_tests:test_eq
|