Torture-testing Backup and Archive Programs: Things You Ought to Know But Probably Would Rather Not

[braian87b]

to see: http://www.coredumps.de/doc/dump/zwicky/testdump.doc.html

[reactive-firewall]

Oh this looks fun ... I'll see about hacking out a test script for these if no one else is working on it
🤔 ... um ... but first ... IS anyone already working on this? ... if so stop me from re-inventing

[reactive-firewall]

I think this calls for some CI testing (🎉 I'm so excited)

So that it's documented somewhere:

CI Testing is great for ensuring code works and changes don't introduce regressions to tested code (caveat: test coverage)

Issues that this could help:

• hardlinks not working #190
• Backup of / is not cron friendly #181
• exclude folders not working #183
• Expiration strategy not deleting oldest backup #175 ?
• Source folder with spaces #172
• FYI MacOS Catalina may break your backups if configured from / #157
• does not find prevous backup when paths have spaces in them #116
• Improve error handling design #115
• ShellCheck indicates some issues #89

most basic test logic:

• use github's actions (I'm on it)

Tests to start creating:

• Static tests:
  • A file with a large hole in it.
  • A file that contains a hole and a block's worth of nulls.
  • Files with funny characters in their file names.
  • 1025 hard links to the same file.
  • 2911 hard links to different files.
  • Files with long names.
  • Symbolic links to long names.
  • Symbolic links to names with funny characters in them.
  • Unreadable and unwriteable files.
  • Unreadable and unwriteable directories with normal files in them.
  • A named pipe.
  • A device.

[reactive-firewall]

😥 No one stopped me before I got to starting on this issue .... 🤓 SO I prepared a PR #205 for testing ... reviews welcome!