emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

It was a bit out of date.

Browse Source
This commit is contained in:
Rob Landley 2005-11-07 09:06:34 +00:00
parent 48c6157eb9
commit c98a359a16
1 changed files with 18 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
testsuite/TODO
View File

@ -2,17 +2,25 @@ This testsuite is quite obviously a work in progress. As such,
there are a number of good extensions. If you are looking for there are a number of good extensions. If you are looking for
something to do, feel free to tackle one or more of the following: something to do, feel free to tackle one or more of the following:
Buildroot support Moving to the new format.
Erik has put together a handy package for constructing and The old way was "lots of little tests files in a directory", which
testing busybox called buildroot. Integrating this into doesn't interact well with source control systems. The new test
the testsuite would allow for greater test coverage (e.g., format is command.tests files that use testing.sh.
init, mount, and other privileged applications).
Every busybox applet needs a corresponding applet.tests.
Full SUSv3 test suite.
Let's make the Linux Test Project jealous, shall we? Don't just
audit programs for standards compliance, _prove_ it with a regression
test harness.
http://www.opengroup.org/onlinepubs/009695399/utilities/
Some tests need root access.
It's hard to test things like mount or init as a normal user.
Possibly User Mode Linux could be used for this, or perhaps
Erik's buildroot.
libbb unit testing libbb unit testing
Being able to test the functions of libbb individually may Being able to test the functions of libbb individually may
help to prevent regressions. help to prevent regressions.
Standardization
This testsuite is totally bastardized. It would be better
to use an existing test framework, such as dejagnu, greg,
or a XUnit clone (shunit?).