db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-14 10:13:05 +02:00
Code Issues Releases Activity
54bc3b454a
pgbackrest/test
History
David Steele 54bc3b454a Cleanup pgPageChecksum() test in postgres/interface module. 
Some of the comments were wrong or inconsistent.

Update TEST_RESULT_U16_HEX() to the less-specific TEST_RESULT_UINT_HEX().
2020-03-06 15:01:50 -05:00
..
certificate New test containers with static test certificates. 2018-11-21 18:13:37 -05:00
code-count Rename "gzip" to "gz". 2020-02-27 12:09:05 -05:00
data Automate generation of WAL and pg_control test files. 2017-11-18 20:02:54 -05:00
expect Add infrastructure for multiple compression type support. 2020-03-06 14:41:03 -05:00
lib/pgBackRestTest Add infrastructure for multiple compression type support. 2020-03-06 14:41:03 -05:00
src Cleanup pgPageChecksum() test in postgres/interface module. 2020-03-06 15:01:50 -05:00
.gitignore Add configure script for improved multi-platform support. 2019-04-26 08:08:23 -04:00
container.yaml Use pkg-config instead of xml2-config for libxml2 build options. 2020-01-24 10:08:05 -07:00
define.yaml Add infrastructure for multiple compression type support. 2020-03-06 14:41:03 -05:00
README.md Fix typos in the documentation. 2019-08-26 12:26:00 -04:00
test.pl Use stock PostgreSQL page checksum implementation. 2020-03-05 14:23:01 -05:00
travis.pl Use pkg-config instead of xml2-config for libxml2 build options. 2020-01-24 10:08:05 -07:00
Vagrantfile Add comments about increasing Vagrantfile disk size. 2019-12-17 21:56:02 -05:00

README.md

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