28959a3f31
Previous to this patch, having a config like the following would not
work properly:
- link:
~/a: ~/b
This was because the '~' was expanded on the left hand side (the link
target), but not the right hand side (the link source). It was necessary
to use a workaround like this:
- link:
~/a: $HOME/b
This was because variable expansion was being done, but user expansion
was not being done.
This commit adds support for using '~' in the link source.
|
||
|---|---|---|
| .. | ||
| tests | ||
| .editorconfig | ||
| .gitignore | ||
| README.md | ||
| Vagrantfile | ||
| driver-lib.bash | ||
| test | ||
| test-lib.bash | ||
| test_travis | ||
README.md
Testing
Dotbot testing code uses Vagrant to run all tests inside a virtual machine to have tests be completely isolated from the host machine. The test driver relies on the Sahara plugin to snapshot and roll back virtual machine state. The tests are deterministic, and each test is run in a virtual machine with fresh state, ensuring that tests that modify system state are easily repeatable.
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.