On Thursday 18 June 2009 17:38:49 Rob Landley wrote: > On Thursday 18 June 2009 09:35:32 Mike Frysinger wrote: > > On Thursday 18 June 2009 07:33:48 David Krakov wrote: > > > * I've seen some tests compare with GNU tools output - does it > > > require a specific version of GNU utilities? > > > > we only care about the latest versions. that means some tests may have > > been written for older versions and so fail with latest ones. > > An implementation is not a standard, especially where different gnu tool > versions give different results.
the latest version of a GNU tool is the the GNU standard > > or they're > > written for the latest and so it is expected they'll fail on older ones. > > we should document in the test the last known tested GNU version, but we > > should always be targeting the latest GNU releases. > > We should not be testing against gnu tools. considering we're implementing GNU features, yes we should. the entire point of these features is to replicate the GNU functionality. and tests are designed exactly to make sure the functionality remains working. > The test suite should run and > produce usable results on a system that _only_ has busybox installed. these things are not mutually exclusive. no GNU tools -> GNU tests are skipped. > > > Though there are tests that can be used for this objective, the test > > > suite is lacking a simple way to mark existing tests with some kind of > > > a flag like POSIXTEST. How do you propose to do that? > > > > i think we should split the tests so that POSIX and GNU conformance is > > kept separate. > > Annotating existing tests which what context they test is useful. > Splitting the test suite into separate scripts means each one now gets half > as much attention. how the scripts are organized is irrelevant to "attention". whether they get executed is relevant. my suggestion of splitting the tests was to keep things organized and easily skipped when GNU functionality was not available ... it did not imply we would stop running the tests. -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
