Ummm … you mean solution (2) with the name Legacy_Tests/, yes? I.e. (as I put it earlier) “Legacy_Test/ and Test2/ → Test/”. That is my (current) favorite. (Solution (3) included deleting Test/; of course, it is in a version control system, so it would not really gone, but would be that much harder to poke at.)

When I started Test2, I went through all the old Test files, which are
mostly unhelpfully named test1, test2 ... test40, and tried to figure
out what the purpose of each test was; if I could figure it out, and if
it was still relevant, I added content to one of the (hopefully more
helpfully-named) files in Test2. Since then, Syd and I have come across
a couple of instances where Test caught something that Test2 didn't, and
remedied that, as well as adding some new components for newer features.

However, when I look in Test2 now, I see that there is now a file called
test-382.xml which is a "testcase for #382 and PR #475". That filename
is unhelpful, so before we make any change we should see if that test
can be integrated into any other file, or if not, renamed to reflect its
purpose (which seems to be to test that index elements in heads are not
turned into TOC entries, I think). The corresponding output file
test-382.html should also be renamed. I think this test should actually
be integrated into testStructure1.xml, which already checks TOC-building.

I also think we should add some more detailed documentation that would
help to avoid the proliferation of anonymous and mysterious test files
in the future, as well as helping people to debug issues caught by the
tests.

Is anyone else aware of anything missing from Test2?