Kristoffer Haugsbakk <code@xxxxxxxxxxxxxxx> writes: > #!/bin/sh > cd t > # Every test run together with `setup` should pass > for i in $(seq 1 42) > do > ./t7900-maintenance.sh --quiet --run=setup,$i || return 1 > done && It is kind-of surprising that with only 8 patches you can reach such a state, but ... > # The tests that used to depend on each other should still pass > # when run together > ./t7900-maintenance.sh --quiet --run=setup,30,31 && ... this puzzles me. What does it mean for tests to "depend on each other"? Does this mean running #31 with or without running #30 runs under different condition and potentially run different things? One might argue that, in an ideal world, our tests should work when any non-setup tests are omitted (so, instead of $i above, you'll have an arbitrary subsequence of 1..42 and your tests still pass), and it may be a worthy goal, but at the same time, it may be a bit impractical, as setting things up is costly, but what you can do in the common "setup" will be very small. Or you'll have so much "recovering from damage" in test_when_finished for each test that makes such untangling of dependencies too costly.
