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
c64c9c0590
pgbackrest/test
History
Cynthia Shang c64c9c0590 Add backup management functions to InfoBackup. 
Allow current backups to be listed and deleted.

Also expose some constants required by expire and stanza-* commands.

Contributed by Cynthia Shang.
2019-06-17 06:59:06 -04:00
..
certificate New test containers with static test certificates. 2018-11-21 18:13:37 -05:00
code-count v2.14: Bug Fix and Improvements 2019-05-20 11:51: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 Refactoring path support in the storage module. 2019-05-26 12:41:15 -04:00
lib/pgBackRestTest Use retries to wait for test S3 server to start. 2019-06-13 17:58:33 -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 Add backup management functions to InfoBackup. 2019-06-17 06:59:06 -04:00
.gitignore Add configure script for improved multi-platform support. 2019-04-26 08:08:23 -04:00
container.yaml Update test containers with PostgreSQL minor releases and liblz4. 2019-04-24 13:23:32 -04:00
define.yaml Add HTTP client cache. 2019-06-11 10:48:22 -04:00
README.md Add admonitions to documentation renderers. 2018-12-30 16:40:20 +02:00
test.pl Fix build.flags being removed on each build. 2019-05-31 18:37:31 -04:00
travis.pl Use the git log to ease release note management. 2019-05-22 18:54:49 -04:00
Vagrantfile Revert removal of aws cli in 3e1b06ac. 2019-06-10 15:52:51 -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