Should tests that test multiple things be broken into individual files?

[dstorey]

Currently a number of test files include a few tests. An example would be header, for when it is the root header that should get the banner role, and the nested header that shouldn't. Another would be sub and sup being in the same file.

Should we break these up into one pass/fail test per file, so that it is easier for implementers, and clearer if a full test case passes or fails? It would make the resources section clearer too, as it'd only include the spec link for the one thing being tested.

[stevefaulkner]

Should we break these up into one pass/fail test per file, so that it is easier for implementers, and clearer if a full test case passes or fails?

sure, there are some tests such as the table tests which could be broken down further also