Prev: Invalid greeting from from master CVS server
Next: devel/subversion
From: Christopher Key on 5 Jul 2010 12:29
At the moment, many ported applications/libraries provide some form of
regression testing, but very few ports actually expose this via the
standard regression-test target. The regression-test target will be
called by tinderbox if available, and should also make debugging
misbehaving ports easier.

Attached is a patch which aims to remedy this situation.

Firstly, it simplifies the creation of a regression-test target, with
the addition of a REGRESSION_TEST_TARGET variable. For audio/flac for
example, this means that:
regression-test: build
@cd ${WRKSRC}; ${SETENV} ${MAKE_ENV} ${MAKE} check

can be replaced with:
REGRESSION_TEST_TARGET= check

Secondly, rather more aggressively, it assumes that anything using
GNU_CONFIGURE or PERL_CONFIGURE implements a check or test target
respectively, and sets REGRESSION_TEST_TARGET accordingly. As far as I
am aware, these target are always present, although it is not guaranteed
that any tests will actually be run. Most perl modules do provide
tests, but gnu software seems less likely to do so. If no useful
testing will be performed, the automatic creation of a regression-test
target can be overridden by setting REGRESSION_TEST_TARGET to an empty
string.

The attached patch probably isn't doing things in the correct places, or
doing them in them in the correct way, but does work to illustrate the
intent. Any feedback on concept or implementation would be much
appreciated.

Kind regards,

Christopher Key
 | 
Pages: 1
Prev: Invalid greeting from from master CVS server
Next: devel/subversion