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
a029eba8d5
pgbackrest/test
History
David Steele a029eba8d5 Use a macro instead of a nested struct to create common String variables. 
This makes the code a bit less obfuscated while still ensuring that these variables will be common to both String structures.
2019-04-16 13:18:30 -04:00
..
certificate New test containers with static test certificates. 2018-11-21 18:13:37 -05:00
code-count v2.12: C Implementation of Archive Push 2019-04-11 09:14:22 -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 The archive-push command is implemented entirely in C. 2019-03-29 13:26:33 +00:00
lib/pgBackRestTest Fix compile flag accidentally removed in 5ee8388f. 2019-04-10 13:37:24 -04:00
lint Silence some perl critic warnings. 2017-04-10 17:23:39 -04:00
package Update primary test environment (Vagrant and Docker) to Ubuntu 18.04. 2018-06-06 15:52:28 -04:00
src Use a macro instead of a nested struct to create common String variables. 2019-04-16 13:18:30 -04:00
.gitignore Allow I/O read interface to explicitly request blocking reads. 2018-11-23 12:01:36 -05:00
container.yaml New test containers with static test certificates. 2018-11-21 18:13:37 -05:00
define.yaml Migrate backupRegExp() to C. 2019-04-15 08:29:25 -04:00
README.md Add admonitions to documentation renderers. 2018-12-30 16:40:20 +02:00
test.pl Only run test-level stack trace by default for unit-tested modules. 2019-02-27 17:09:19 +02:00
travis.pl Document generator improvements. 2018-06-10 14:13:56 -04:00
Vagrantfile Add command for removing all Docker containers to the Vagrantfile. 2019-03-15 22:18:56 +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