On 11/9/09 15:00, [email protected] wrote:
3. With these in mind, it is not clear that we need to be textually
breaking up and reassembling the Domita tests, unless we plan to
break it up into chunks (files) smaller than the five or six I
noted in my first point. If we do that, we might end up with an
unmanageably large number of files, so I don't think it would be a
good idea.
I like one test per file because it makes it easier to
isolate one test when trying to work on a problem,
and because it bypasses some commit-merge problems.
Anytime people are appending things to a file
simultaneously, there's a merge conflict that needs
to be resolved manually.
What problem do you see with a large number of files?
The gcc testsuite is a large collection of pretty small
files, many of them only a dozen or so lines.
Recombining all the single tests into one mega-test
seems fine for now, but it probably won't scale,
since domita_test is already close to hitting the
"this script is taking too long" on some browsers.
So I think at some point the tests should be
split into subdirs, where each subdir would be
combined into a subdir-mega-test that would be run
individually by the test driver.
