1
0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-14 10:13:05 +02:00
pgbackrest/test
David Steele 2c1687721e Fix issue where specifying log-level-stderr > warn would cause a local/remote process to error on exit due to output found on stderr when none was expected.
The max value for a local/remote process is now error since there's no reason for these processes to emit warnings.

Reported by Clinton Adams.
2018-03-19 13:08:42 -04:00
..
data Automate generation of WAL and pg_control test files. 2017-11-18 20:02:54 -05:00
expect Port most of Config::Config::configLoad() from Perl to C. 2018-03-12 11:25:20 -04:00
lib/pgBackRestTest Use clang for static code analysis during lint testing. 2018-03-18 13:32:19 -04:00
lint Silence some perl critic warnings. 2017-04-10 17:23:39 -04:00
package Add Debian 9 to test suite. 2017-06-27 18:29:48 -04:00
src Fix issue where specifying log-level-stderr > warn would cause a local/remote process to error on exit due to output found on stderr when none was expected. 2018-03-19 13:08:42 -04:00
.gitignore Container build improvements: 2017-06-24 10:59:00 -04:00
README.md Rename db-* options to pg-* and backup-* options to repo-* to improve consistency. 2018-02-03 18:27:38 -05:00
test.pl Use clang for static code analysis during lint testing. 2018-03-18 13:32:19 -04:00
travis.pl Use clang for static code analysis during lint testing. 2018-03-18 13:32:19 -04:00
Vagrantfile Create a master list of errors in build/error.yaml. 2018-02-08 16:11:47 -05:00

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 Process Max:

/backrest/test/test.pl --vm=co6 --module=backup --test=full --process-max=4

Note that process-max is only applicable to the synthetic and full tests in the backup module.

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 that pg-version is only applicable to the full test in the backup module.

Iterate All Possible Test Combinations:

/backrest/test/test.pl --dry-run