1
0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-14 10:13:05 +02:00
pgbackrest/test
David Steele f8b47997a3 Closed #127: More sanity checking for --delta restores
Added checks for `--delta` and `--force` restore options to ensure that the destination is a valid $PGDATA directory. pgBackRest will check for the presence of `PG_VERSION` or `backup.manifest` (left over from an aborted restore). If neither is found then `--delta` and `--force` will be disabled but the restore will proceed unless there are files in the $PGDATA directory (or any tablespace directories) in which case the operation will be aborted.
2016-02-05 23:03:29 -05:00
..
data Implemented issue #26: Info command. 2015-06-13 18:25:49 -04:00
lib/BackRestTest Closed #127: More sanity checking for --delta restores 2016-02-05 23:03:29 -05:00
log Closed #127: More sanity checking for --delta restores 2016-02-05 23:03:29 -05:00
README.md Fixed typos in test documentation. 2016-01-10 21:07:07 -05:00
test.pl Closed #163: Document Generation Issue 2016-01-22 18:01:21 -05:00
Vagrantfile Text execution improvements: 2016-01-09 08:21:53 -05:00

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 that 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 Thread Max:

/backrest/test/test.pl --vm=co6 --module=backup --test=full --thread-max=4

Note that thread-max is only applicable to the synthetic and full tests in the backup module.

Run Tests for a Specific OS, Module, Test, Thread Max, and Database Version:

/backrest/test/test.pl --vm=co6 --module=backup --test=full --thread-max=4 --db-version=9.4

Note that db-version is only applicable to the full test in the backup module.

Iterate All Possible Test Combinations:

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