2d10293d04
Bug Fixes: * Fix remote timeout in delta restore. When performing a delta restore on a largely unchanged cluster the remote could timeout if no files were fetched from the repository within protocol-timeout. Add keep-alives to prevent remote timeout. (Reported by James Sewell, Jens Wilke.) * Fix handling of repeated HTTP headers. When HTTP headers are repeated they should be considered equivalent to a single comma-separated header rather than generating an error, which was the prior behavior. (Reported by donicrosby.) Improvements: * JSON output from the info command is no longer pretty-printed. Monitoring systems can more easily ingest the JSON without linefeeds. External tools such as jq can be used to pretty-print if desired. (Contributed by Cynthia Shang.) * The check command is implemented entirely in C. (Contributed by Cynthia Shang.) Documentation Improvements: * Document how to contribute to pgBackRest. (Contributed by Cynthia Shang.) * Document maximum version for auto-stop option. (Contributed by Brad Nicholson.) Test Suite Improvements: * Fix container test path being used when --vm=none. (Suggested by Stephen Frost.) * Fix mismatched timezone in expect test. (Suggested by Stephen Frost.) * Don't autogenerate embedded libc code by default. (Suggested by Stephen Frost.) |
||
|---|---|---|
| .. | ||
| certificate | ||
| code-count | ||
| data | ||
| expect | ||
| lib/pgBackRestTest | ||
| src | ||
| .gitignore | ||
| container.yaml | ||
| define.yaml | ||
| README.md | ||
| test.pl | ||
| travis.pl | ||
| Vagrantfile | ||
pgBackRest
Regression, Unit, & Integration Testing
Introduction
pgBackRest uses Docker to run tests and generate documentation. Docker's light-weight virtualization 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: 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 Process Max:
/backrest/test/test.pl --vm=co6 --module=backup --test=full --process-max=4
NOTE: process-max is only applicable to the
syntheticandfulltests in thebackupmodule.
Run Tests for a Specific OS, Module, Test, Process Max, and Database Version:
/backrest/test/test.pl --vm=co6 --module=backup --test=full --process-max=4 --pg-version=9.4
NOTE: pg-version is only applicable to the
fulltest in thebackupmodule.
Iterate All Possible Test Combinations:
/backrest/test/test.pl --dry-run