Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create automated tests #19

Open
Tracked by #197
tasket opened this issue Jan 4, 2019 · 1 comment
Open
Tracked by #197

Create automated tests #19

tasket opened this issue Jan 4, 2019 · 1 comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed testing
Milestone

Comments

@tasket
Copy link
Owner

tasket commented Jan 4, 2019

A good testing regime could include the following:

  • Perform an initial backup
  • Verify volume
  • Perform an incremental backup
  • Verify volume
  • Prune first backup
  • Verify volume
  • Diff volume (cross-check with source vol data)

Changing program_name in the code could allow the test data set to be created under a different base folder name without interfering with real-life backup data.

@tasket tasket added help wanted Extra attention is needed good first issue Good for newcomers testing labels Jan 4, 2019
@tasket tasket added this to the v0.4 milestone Jan 2, 2020
@tasket tasket modified the milestones: v0.4, v0.8, v0.9 Jun 14, 2023
@tasket tasket mentioned this issue May 20, 2024
8 tasks
@DemiMarie
Copy link

Other areas I recommend testing:

  1. Deliberately tamper with the archive, and check that the tampering is detected on restore.
  2. Attempt to roll back the archive to an earlier version, and test that this is detected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed testing
Projects
None yet
Development

No branches or pull requests

2 participants