1c8c755e81
Our test suite originated when package layering was still being developed, but now that that's mature, the logic where layering tests are distinct makes less sense. The `basic` test had grown to really be a collection of many miscellaneous things. Let's make that more explicit. Further, let's avoid having each test suite grow too large; when a single test fails we don't have an easy way to rerun just that test, so a crude way to have faster local iteration is to split into groups. My plan is to reintroduce a `basic` test that covers the basics of all functionality - update, deploy, layering, etc. The advanced/corner cases of layering like the `rm -rf /` test would still live in a `test-layering.sh` or so. Closes: #1336 Approved by: jlebon |
||
---|---|---|
.. | ||
fetch-journal.sh | ||
install.sh | ||
multitest.py | ||
overlay.sh | ||
sync.sh | ||
test-autoupdate.sh | ||
test-cached-rpm-diffs.sh | ||
test-db.sh | ||
test-download-only.sh | ||
test-initramfs.sh | ||
test-kernel-args.sh | ||
test-layering-basic.sh | ||
test-layering-gpg.sh | ||
test-layering-local.sh | ||
test-layering-non-root-caps.sh | ||
test-layering-relabel.sh | ||
test-layering-relayer.sh | ||
test-layering-rpmdb.sh | ||
test-layering-scripts.sh | ||
test-layering-unified.sh | ||
test-livefs.sh | ||
test-misc-1.sh | ||
test-misc-2.sh | ||
test-override-kernel.sh | ||
test-override-local-replace.sh | ||
test-override-remove.sh | ||
test-rojig-client.sh | ||
test.sh |