1
0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-12 10:04:14 +02:00
pgbackrest/test
David Steele dbb1248bfb Implement TEST_RESULT_*() macros with functions, mostly.
The prior macros had grown over time to be pretty significant pieces of code that required a lot of compile time, though runtime was efficient.

Move most of the macro code into functions to reduce compile time, perhaps at a slight expense to runtime.  The overall performance benefit is 10-15% so this seems like a good tradeoff.

Add TEST_RESULT_UINT_INT() to safely compare uint to int with range checking.
2020-03-22 20:44:51 -04:00
..
certificate New test containers with static test certificates. 2018-11-21 18:13:37 -05:00
code-count Update code classification and remove XS definition. 2020-03-14 18:30:24 -04:00
data Automate generation of WAL and pg_control test files. 2017-11-18 20:02:54 -05:00
expect Add lz4 compression support. 2020-03-10 14:45:27 -04:00
lib/pgBackRestTest Fix space lost in d70ca259. 2020-03-22 14:18:16 -04:00
patch Configure and make improvements. 2020-03-13 09:07:57 -04:00
src Implement TEST_RESULT_*() macros with functions, mostly. 2020-03-22 20:44:51 -04:00
.gitignore Move coverage results to test/result. 2020-03-14 15:29:42 -04:00
container.yaml Add lz4 compression support. 2020-03-10 14:45:27 -04:00
define.yaml Added redacted manifest to testBackupValidate(). 2020-03-18 10:10:10 -04:00
README.md Fix typos in the documentation. 2019-08-26 12:26:00 -04:00
test.pl Add --clean and --clean-only options to test.pl. 2020-03-22 13:46:30 -04:00
travis.pl Build contributing documentation on Travis CI. 2020-03-21 18:45:58 -04:00
Vagrantfile Build contributing documentation on Travis CI. 2020-03-21 18:45:58 -04: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