db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2025-01-18 04:58:51 +02:00
Code Issues Releases Activity
pgbackrest/test
History
David Steele 18b62a4220 Only run test-level stack trace by default for unit-tested modules. 
This amends 70c30dfb which disabled test tracing in general.

Instead, only enable test tracing by default for modules that are being unit tested. This saves lots of time but still ensures that test tracing is working and helps with debugging in unit tests.

Also rename the option to --debug-test-trace for a clarity.
2019-02-27 17:09:19 +02:00
..
certificate
New test containers with static test certificates.
2018-11-21 18:13:37 -05:00
code-count
Rename common/io/handle module to common/io/handleWrite.
2019-01-06 14:37:39 +02: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
Create test matrix for mock/stanza to increase coverage and reduce tests.
2019-02-24 07:42:41 +02:00
lib/pgBackRestTest
Only run test-level stack trace by default for unit-tested modules.
2019-02-27 17:09:19 +02: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
Rename test modules for consistency.
2019-02-23 18:51:52 +02: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
Create test matrix for mock/stanza to increase coverage and reduce tests.
2019-02-24 07:42:41 +02: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
Update URL for Docker install.
2018-12-03 12:41:53 -05: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