d2913e6cee
Some distributions such as Arch Linux no longer install `which` by default through the base package (see https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/). The maintainers have explained why `command -v` is superior: https://www.reddit.com/r/archlinux/comments/de1er6/arch_linux_news_base_group_replaced_by_mandatory/f2v8uhu/. |
||
|---|---|---|
| .. | ||
| tests | ||
| .editorconfig | ||
| .gitignore | ||
| driver-lib.bash | ||
| README.md | ||
| test | ||
| test-lib.bash | ||
| test_travis | ||
| Vagrantfile | ||
Testing
Dotbot testing code uses Vagrant to run all tests inside a virtual machine to have tests be completely isolated from the host machine.
Installing the Test environnement
Debian-based distributions
- Install the test requirements
sudo apt install vagrant virtualbox
- Install Dotbot dependencies
git submodule update --init --recursive
macOS
-
Install the test requirements
-
Install Dotbot dependencies
git submodule update --init --recursive
Running the Tests
Before running the tests, the virtual machine must be running. It can be
started by running vagrant up.
The test suite can be run by running ./test. Selected tests can be run by
passing paths to the tests as arguments to ./test.
Tests can be run with a specific Python version by running ./test --version <version> - for example, ./test --version 3.4.3.
When finished with testing, it is good to shut down the virtual machine by
running vagrant halt.