1
0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-14 10:13:05 +02:00
pgbackrest/test
David Steele e4716ee036 Improve diff output in tests.
Always compare expected vs actual (in that order) and give a hint in the error message to indicate what should be added and what removed.
2019-12-07 17:02:41 -05:00
..
certificate New test containers with static test certificates. 2018-11-21 18:13:37 -05:00
code-count v2.19: C Migrations and Bug Fixes 2019-11-12 15:51:28 -05:00
data Automate generation of WAL and pg_control test files. 2017-11-18 20:02:54 -05:00
expect Use more general error code when tablespace linked into PGDATA. 2019-12-02 10:49:25 -05:00
lib/pgBackRestTest Fix backup labels in mock/all resume integration tests. 2019-12-06 11:48:41 -05:00
src Improve diff output in tests. 2019-12-07 17:02:41 -05:00
.gitignore Add configure script for improved multi-platform support. 2019-04-26 08:08:23 -04:00
container.yaml Only install specific lcov version when required. 2019-11-22 19:25:49 -05:00
define.yaml Remove obsolete Perl archive code. 2019-11-26 17:16:45 -05:00
README.md Fix typos in the documentation. 2019-08-26 12:26:00 -04:00
test.pl Error when specified vm is invalid. 2019-10-17 14:00:18 +02:00
travis.pl Allow parameters to be passed to travis.pl. 2019-10-15 17:19:42 +02:00
Vagrantfile Only install specific lcov version when required. 2019-11-22 19:25:49 -05:00

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

Iterate All Possible Test Combinations:

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