|Dieter Verhelst a17c68563b Dont gather facts||2 years ago|
|clients||2 years ago|
|extra_opts||2 years ago|
|generic_files||2 years ago|
|lamp||2 years ago|
|mgt||2 years ago|
|multiple||2 years ago|
|README.md||2 years ago|
Ansible 2.4 or higher
Molecule 2.17.0 or higher
Docker host (local or remote through shell environment)
All scenarios run the same tests by default defined in generic_tests. If a test applies to a certain group only, group filtering is done through testinfra with the ansible:// url. Eg:
testinfra_hosts = ["ansible://borgbackup_servers"]
Verify the borg-binary is present
Verifies if all the required parameters are present on the client to perform a backup. It verifies an already existing backup has run and if it has succeeded.
Verifies if the restore functionality works correctly.
Verifies if all server-related configurations are in place and if the backup is working from a server perspective.
This tests spins up supported platforms and verifies the basic functionality of both server and client with the generic_tests on a number of platforms and linux distributions.
borgbackup_appendonly: borgbackup_servers: borgbackup_include: borgbackup_passphrase:
Testing whether backing up to multiple targets works properly.
Verify if both pre and post commands are configured at backup time and are run.
Verify if both inclusion and exclusion of folders is working as expected
Verify a basic lamp setup meaning making sure /var/www/ and automysqlbackup is configured properly and backed up.
As an extra preparation, apache2 and automysqlbackup are installed for verification.
backup_pre_commands: needs to be extended with automysqlbackup borgbackup_include: need to contain both /var/www and /var/lib/automysqlbackup
Testing whether the management-station functionality works and all clients are listed.
borgbackup_management: borgbackup_management_user: borgbackup_management_sshkey:
A restore is tested by default in every scenario by the use of the side-effect playbook. generic_files/side_effect.yml