1
0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-14 10:13:05 +02:00
pgbackrest/test
David Steele 14d2f8b86c Reword misleading message in stack trace when parameter buffer is full.
The prior message stated that there had been a buffer overrun which is not true since the code prevents that.

In fact, this message means the parameter buffer filled while building the parameter list. Rather than display a partial list we output this message instead.

Also remove !!! which by convention we use as a marker for code that needs attention before it can be committed to master.
2018-11-14 08:11:11 -05:00
..
code-count Merge crypto/random module into crypto/crypto. 2018-11-06 20:04:16 -05: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 Limit usable Buffer size without changing allocated size. 2018-11-08 16:48:33 -05:00
lib/pgBackRestTest Clarify comment about main.c being excluded from unit testing. 2018-11-14 08:08:26 -05: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 Reword misleading message in stack trace when parameter buffer is full. 2018-11-14 08:11:11 -05:00
.gitignore Update primary test environment (Vagrant and Docker) to Ubuntu 18.04. 2018-06-06 15:52:28 -04:00
container.yaml New test containers. 2018-11-08 21:41:41 -05:00
define.yaml Add constant macros to String object. 2018-11-10 09:37:12 -05:00
README.md Rename db-* options to pg-* and backup-* options to repo-* to improve consistency. 2018-02-03 18:27:38 -05:00
test.pl New, concise coverage report for C. 2018-11-11 17:32:42 -05:00
travis.pl Document generator improvements. 2018-06-10 14:13:56 -04:00
Vagrantfile New test containers. 2018-11-08 21:41:41 -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 Process Max:

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

Note that 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 that pg-version is only applicable to the full test in the backup module.

Iterate All Possible Test Combinations:

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