MZMcBride <z(a)mzmcbride.com> writes:
Even if we could say that most users downloading from
SVN are
interested in development, I don't see how that extends to saying that
test suites are required for development. You've lost me.
If a developer breaks a test, ze[1] should fix it. As the tests cover
more and more of the code, the tests should be considered more integral
to development since they provide a nice sanity check on any changes a
developer is likely to make.
The maintenance directory has maintenance tools in it.
I don't think test
suites fall within the category of "maintenance." Like large artwork files,
these seem to be "development" tools that shouldn't be downloaded with
every
phase3 checkout.
Others have already pointed out that this argument could be applied to
other areas of the phase3 tree, but let me add this.
If you measure the size of everything under phase3 and normalize it
against the size of the maintenance/tests directory[2], you come up with
following:
1.000 maintenance/tests/
1.263 resources
1.302 skins
3.964 maintenance
14.949 includes
25.818 languages
That is, the tests directory is only 1/4 of the size of the entire
maintenance directory. The includes directory is almost 15 times larger
than the tests directory and, yes, languages tops them all.
Since we have some developers actively working on the test suite, it
appears that you are more annoyed with the noise during “svn up” rather
than any actual “bloat”.
Mark.
[1]
http://en.wikipedia.org/wiki/Gender-neutral_pronoun
[2] du -sk * maintenance/tests/ | perl -ne 'chomp;($c, $l) = \
m{(\S+)\s+(\S+)}; $w = $c/3652;print sprintf ("%0.3f $l\n", $w);' \
| sort -n
--
http://hexmode.com/
War begins by calling for the annihilation of the Other,
but ends ultimately in self-annihilation.