aboutsummaryrefslogtreecommitdiff
path: root/testsuite
AgeCommit message (Collapse)Author
2006-04-27Re-wordwrap the new tests, and fix seq.c to pass them.Rob Landley
2006-04-27- add two regression tests for seq.Bernhard Reutner-Fischer
"seq two arguments equal, arbitrary negative step" fails but should pass..
2006-04-19Patch from Jean Wolter:Rob Landley
it looks like the introduced support for character classes and equivalence classes is not correct. The attached patch tries to fix some symptoms and tries to make tr behave like gnu tr for the added test cases. The patch  - removes if clauses with side effects  - fixes handling of buffer pointer (strcat added characters to the    buffer without increasing the buffer pointer)  - re-arranges character classes to match ASCII order regards, Jean
2006-04-18- typo: s/derefernce/dereference/gBernhard Reutner-Fischer
Thanks to P.J. Day.
2006-04-18- add typo s/deamon/daemon/gBernhard Reutner-Fischer
2006-04-18- add grep for typo s/algorithic/algorithmic/gBernhard Reutner-Fischer
2006-04-16add a check for obsolete headersMike Frysinger
2006-04-16add some tests for common typos and for obsolete functionsMike Frysinger
2006-04-04Avoid spurious error message. (Technically applet order should be "SKIPPED"Rob Landley
when you move the testsuite directory outside of busybox and run it, but as long as the test doesn't fail we're ok.)
2006-04-01work outside of the srctreeMike Frysinger
2006-04-01new test for source code sanityMike Frysinger
2006-04-01move source code tests out into a sep file rather than just ↵Mike Frysinger
disabling/breaking them
2006-04-01remove bogus "Mike Frysinger
2006-04-01silence error if busybox.links doesnt exist and run tests that begin with "all_"Mike Frysinger
2006-03-22Fix "seq 1 1".Rob Landley
2006-03-18Make the new chroot environment creation infrastructure more flexible aboutRob Landley
non-absolute paths.
2006-03-18My mount testsuite. Not automatically run at the moment, need to figure outRob Landley
how to (optionally) supply User Mode Linux to runtests.
2006-03-16More test updates.Rob Landley
2006-03-16Redo test suite to be able to test more than one command at a time. EliminateRob Landley
$COMMAND environment variable, instead put full command line (including command to run) in second argument. Modify $PATH to have test versions of commands at start of path. (Also more infrastructure for testing as root, work in progress...)
2006-03-09I'm about to introduce tests that need to run as root (like mount.tests),Rob Landley
meaning we want to run them in a chroot environment. To help with this, I worked out a utility function that makes it really easy to set up a chroot environment.
2006-03-01When gnu fails this one we shouldn't let it _hang_...Rob Landley
2006-03-01Yet more sed tests. Passing these is a to-do item for 1.1.2 or 1.2, not aRob Landley
1.1.1 issue.
2006-02-24Add a test suite for seq.Rob Landley
2006-02-23Lots of tests the fix to sed needs to pass...Rob Landley
2006-02-22test to make sure applets are in alphabetical orderMike Frysinger
2006-02-16Putting together OPTIONFLAGS, sed needs the global flag to handle multipleRob Landley
options.
2006-02-16When setting an environment variable by piping something into grep, backquotesRob Landley
can be useful. Also tweak an if case to be more portable.
2006-01-25use LC_ALL, not LANG, for forcing CMike Frysinger
2006-01-25ignore whitespaceTim Riker
2006-01-25LANG=C should helpTim Riker
2005-11-10Ok, I've converted the contents of the "testing/sed" directory into a Rob Landley
sed.tests file. My brain hurts now. (Lots of boggling at sed minutiae and corner cases and going "why is gnu giving that output". The behavior of N and n with regard to EOF are only understandable if you read the Open Group spec, not if you read the sed info page, by the way...) Some of the existing sed tests are just nuts. For example, sed-next-line is testing for our behavior (which is wrong), and would fail if run against gnu sed (which was getting it right. Again, this was a spec-boggling moment, with much head scratching. I've got to add a debug mode where the stuff output by the p command is a different color from the stuff output by normal end of script printing (when not suppressed by -n).) As for sed-handles-unsatisifed-backrefs: what is this test trying to _do_? I ran it against gnu sed and got an error message, and this behavior sounds perfectly reasonable. (It _is_ an unsatisfied backref.) The fact we currently ignore this case (and treat \1 as an empty string) isn't really behavior we should have a test depend on for success. The remaining one is sed-aic-commands, which is long and complicated. I'm trying to figure out if I should chop this into a number of smaller tests, or if having one big "does-many-things" test is a good idea. In any case, the _next_ step is to go through the Open Group standard and make tests for every case not yet covered. (And there are plenty. There are few comments in the file already.) Plus I have notes about corner cases from development that I need to collate and put into here. This file is maybe the first 1/3 of a truly comprehensive sed test. Rob
2005-11-07It was a bit out of date.Rob Landley
2005-11-07Fix the test suite so that individual *.tests files can be run alaRob Landley
COMMAND=sort ./sort.tests So we can compare against non-busybox versions, and possibly our testsuite will be useful to somebody like the Linux Test Project someday. Redid testing.sh to add new command, "optional", to skip tests that require certain features. (use: `optional FEATURE_SORT_BIG`, or `optional ""` to stop skipping.) Note that optional is a NOP if the environment variable "OPTIONFLAGS" is blank, so although we're marking up the tests with busybox specific knowledge, it doesn't interfere with running the tests without busybox. Moved setting the "OPTIONFLAGS" environment variable to runtest. Philosophy: busybox-specific stuff belongs in runtest; both testing.sh and the tests themselves should be as busybox-agnostic as possible. Moved detecting that a command isn't in busybox at all (hence skipping the entire command.tests file) to runtests. Rationale: optional can't currently test for more than one feature at a time, so if we clear anything with optional "" we might perform tests we don't want to. Marked up busybox.tests to know which tests need CAT enabled. Fixed up other tests to be happy with new notation. I suspect egrep should be appended to grep. It's a sub-feature, really...
2005-10-06- add a few basic tests for pidof(8)Bernhard Reutner-Fischer
2005-10-06- support make check V=1 to run the checks in verbose modeBernhard Reutner-Fischer
- pass verbose from runtest to testing.sh
2005-09-24cleanup option parsingMike Frysinger
2005-09-23- remove dangling symlinks after the runsBernhard Reutner-Fischer
- check if the temporary directory containing the links exists rather than unconditionally creating it for every single applet.
2005-09-23- set executable bitBernhard Reutner-Fischer
2005-09-23- introduce variable _BB_CONFIG_DEP to the new test harness.Bernhard Reutner-Fischer
This is used to see if given tests should be run (are available) or not. Print "UNTESTED: descr" if the applet or feature is not available. - add _BB_CONFIG_DEP to existing new.tests - move old grep test to new test infrastructure and add a few more test for grep.
2005-09-20Get "make check" ($srcdir) to work with the new testsuite.Rob Landley
2005-09-20The testsuite/links directory wasn't being created.Rob Landley
2005-09-14Test full susv3 spec for uniq (except internationalization).Rob Landley
I think this covers it. We fail two corner cases, both of which are explicit violations of the spec, and both of which gnu passes.
2005-09-07Don't comment warnings. Don't put #warnings about warnings. _FIX_ warnings.Rob Landley
This fixes the warning, and makes the binary smaller out of sheer pique. (Yes, since Manuel did this one it's nice tight code that took several attempts to shrink, but I was ticked.) Add the start of a test for uniq; this is about the first 1/3 of the tests we need for full susv3 coverage of uniq.
2005-09-05Regarding 11330: when you fix a bug that the testsuite doesn't catch, addRob Landley
a test case to the test suite.
2005-09-04Remove trailing crud from busybox.tests. (Sleep deprivation strikes again...)Rob Landley
2005-09-04General cleanup of command line parsing to allow "busybox" to work as a prefix.Rob Landley
(I.E. any argv[0] that starts with "busybox" winds up in busybox_main().) Added testing/busybox.tests which tests the following permutations: ./busybox ./busybox-suffix ./busybox cat ./busybox-suffix cat ./busybox --help ./busybox-suffix --help ./busybox --help cat ./busybox-suffix --help cat ./busybox --help unknown ./busybox-suffix --help unknown ./unknown Also repair the test suite so ./runtest calls the ".tests" scripts properly. Note: you can now go "busybox busybox busbox ls -l" and it'll take it. The new code is pretty generic. I can block that if anybody can come up with a good reason to...
2005-09-02This goes along with the new testsuite code...Rob Landley
2005-09-02Working on a new test harness. Moved the sort tests into it.Rob Landley
2005-05-18Patch from Colin Watson (mangled slightly by Rob Landley):Rob Landley
This patch implements the 'T' command in sed. This is a GNU extension, but one of the udev hotplug scripts uses it, so I need it in busybox anyway. Includes a test; 'svn add testsuite/sed/sed-branch-conditional-inverted' after applying.
2004-10-08egor duda writes:Eric Andersen
Hi! I've created a patch to busybox' build system to allow building it in separate tree in a manner similar to kbuild from kernel version 2.6. That is, one runs command like 'make O=/build/some/where/for/specific/target/and/options' and everything is built in this exact directory, provided that it exists. I understand that applyingc such invasive changes during 'release candidates' stage of development is at best unwise. So, i'm currently asking for comments about this patch, starting from whether such thing is needed at all to whether it coded properly. 'make check' should work now, and one make creates Makefile in build directory, so one can run 'make' in build directory after that. One possible caveat is that if we build in some directory other than source one, the source directory should be 'distclean'ed first. egor