jerry gay wrote:
Should we even require all of these tests to be ran by default? These
tests should never fail for a user compiling a release version of
parrot, so should they need to test them? They're good for developers,
but only developers.
until we stop actively developing major subsystems we should be
running these tests regularly. no test should fail for a user
compiling a release version of parrot. should we run any tests at all?
of course.
I concur that the user shouldn't get failing tests for things like
whitespace at the end of lines. More importantly, the user shouldn't be
wasting time running tests for coding standards and documentation. How
about a 'make devtest' target that runs standards/doc tests first, and
then the ordinary 'make test' target?
It would require all developers to get into the habit of running 'make
devtest' instead of 'make test', but that's not a heavy burden.
Allison
