Make omitted --old-iso default to --iso in the automated test suite
Instead of erroring out, let's just make the old Tails ISO be the same as the ISO being tested when --old-iso is omitted. This will sill results in us testing the most important thing we want to test, i.e. that the Tails Installer works in the ISO being tested.
Then we can also remove the
Make --old-iso default to --iso if omitted.
Using the same ISO for the USB upgrade tests most often still does
what we want, e.g. test that the current version of Tails being tested
has a working Tails installer. Hence this seems like a reasonable
default. (Also note that an --old-iso may have changes that make it
impossible to run in the next versions automated test suite, and then
this is almost a requirement.)
#4 Updated by anonym over 4 years ago
I've always wondered why we had that filename check
Well, it seemed like a reasonable sanity check if we require the --old-iso to an earlier edition. That implies that they cannot be the same. Crappy, I know. :)
(and I've often cheated by simply copying the same ISO under another name, to use it as
Me too (to avoid the above "cleverness")! :S