On 11/9/09 17:12, [email protected] wrote:
... 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.
We merge JUnit files with multiple all the time.
and it's annoying there too, but happens less often,
since junit tests are file-per-class. domita_test is
everything browser-side. in principle every caja change
should be observable in a browser test. there are about
130 junit class files. I don't really see a way of
splitting domita_test into 100 or so conceptual units
that are larger than the consolidation already done by
putting multiple asserts in a single test function.
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.
Yeah -- despite what I said above, I have no real objective objection.
So why not? Let's try it.
ok.
I don't think there are any modifications for me to make.
unless I forgot something, I'm now waiting for Mike Samuel
to say 'lgtm'.
http://codereview.appspot.com/129059/show
