db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-12 10:04:14 +02:00
Code Issues Releases Activity
893ae24284
pgbackrest/test
History
David Steele 893ae24284 Add timeout to walSegmentFind(). 
Keep trying to locate the WAL segment until timeout.  This is useful for the check and backup commands which must wait for segments to arrive in the archive.
2019-07-31 19:58:57 -04:00
..
certificate New test containers with static test certificates. 2018-11-21 18:13:37 -05:00
code-count Rename control/control module to control/common. 2019-07-31 11:35:58 -04:00
data Automate generation of WAL and pg_control test files. 2017-11-18 20:02:54 -05:00
docker Use a prebuilt s3 server container for documentation and tests. 2018-06-12 13:43:15 -04:00
expect Fix incorrect offline upper bound for ignoring page checksum errors. 2019-07-11 09:13:56 -04:00
lib/pgBackRestTest Allow modules to be included for testing without requiring coverage. 2019-07-25 20:15:06 -04:00
patch Add Perl interface to C PgQuery object. 2019-07-25 17:05:39 -04:00
src Add timeout to walSegmentFind(). 2019-07-31 19:58:57 -04:00
.gitignore Add configure script for improved multi-platform support. 2019-04-26 08:08:23 -04:00
container.yaml Add Perl interface to C PgQuery object. 2019-07-25 17:05:39 -04:00
define.yaml Rename control/control module to control/common. 2019-07-31 11:35:58 -04:00
README.md Add admonitions to documentation renderers. 2018-12-30 16:40:20 +02:00
test.pl Remove clang static analysis. 2019-07-05 18:34:15 -04:00
travis.pl Remove clang static analysis. 2019-07-05 18:34:15 -04:00
Vagrantfile Add PostgreSQL query client. 2019-07-25 14:50:02 -04:00

README.md

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