1
0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-14 10:13:05 +02:00
pgbackrest/test
David Steele 9457e15347 New manifest format.
* All files and directories linked from PGDATA are now included in the backup. By default links will be restored directly into PGDATA as files or directories. The --link-all option can be used to restore all links to their original locations. The --link-map option can be used to remap a link to a new location.

* Removed --tablespace option and replaced with --tablespace-map-all option which should more clearly indicate its function.

* Added detail log level which will output more information than info without being as verbose as debug.
2016-04-14 22:50:02 -04:00
..
data Implemented issue #26: Info command. 2015-06-13 18:25:49 -04:00
expect New manifest format. 2016-04-14 22:50:02 -04:00
lib/pgBackRestTest New manifest format. 2016-04-14 22:50:02 -04:00
lint Working on #174: Get Perl Critic to pass on stern 2016-02-23 09:39:37 -05:00
README.md Fixed typos in test documentation. 2016-01-10 21:07:07 -05:00
test.pl New simpler configuration and consistent project/exe/path naming. 2016-04-14 09:30:54 -04:00
Vagrantfile Closed #173: Add static source code analysis 2016-02-23 09:25:22 -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