012405a33b
* Fixed an issue where the expire command would refuse to run when explicitly called from the command line if the db-host option was set. This was not an issue when expire was run after a backup, which is the usual case. * Option handling is now far more strict. Previously it was possible for a command to use an option that was not explicitly assigned to it. This was especially true for the backup-host and db-host options which are used to determine locality. Reported by Chris Barber. |
||
|---|---|---|
| .. | ||
| data | ||
| expect | ||
| lib/pgBackRestTest | ||
| lint | ||
| README.md | ||
| test.pl | ||
| Vagrantfile | ||
pgBackRest
Regression, Unit, & Integration Testing
Introduction
pgBackRest uses Docker to run tests and generate documentation. Docker's light-weight virualization provides the a good balance between proper OS emulation and performance (especially startup)
A Vagrantfile is provided that contains the complete configuration required to run pgBackRest tests and build documentation. If Vagrant is not suitable then the Vagrantfile still contains the configuration steps required to build a test system.
Note that this is not required for normal operation of pgBackRest.
Testing
The easiest way to start testing pgBackRest is with the included Vagrantfile.
Build Vagrant and Logon:
cd test
vagrant up
vagrant ssh
The vagrant up command may take some time as a number of Docker containers must also be built. The vagrant ssh command automatically logs onto the VM.
Run All Tests:
/backrest/test/test.pl
Run Tests for a Specific OS:
/backrest/test/test.pl --vm=co6
Run Tests for a Specific OS and Module:
/backrest/test/test.pl --vm=co6 --module=backup
Run Tests for a Specific OS, Module, and Test:
/backrest/test/test.pl --vm=co6 --module=backup --test=full
Run Tests for a Specific OS, Module, Test, and Run:
/backrest/test/test.pl --vm=co6 --module=backup --test=full --run=1
Run Tests for a Specific OS, Module, Test, and Thread Max:
/backrest/test/test.pl --vm=co6 --module=backup --test=full --thread-max=4
Note that thread-max is only applicable to the synthetic and full tests in the backup module.
Run Tests for a Specific OS, Module, Test, Thread Max, and Database Version:
/backrest/test/test.pl --vm=co6 --module=backup --test=full --thread-max=4 --db-version=9.4
Note that db-version is only applicable to the full test in the backup module.
Iterate All Possible Test Combinations:
/backrest/test/test.pl --dry-run