X-Git-Url: https://git.librecmc.org/?a=blobdiff_plain;f=testsuite%2FTODO;h=b8957f4884c865f15ea56ad8bbf23fe029f68867;hb=bbe514683a43e81cab1d5ccc0436b9aaf984294b;hp=24126318a889ed17de16eb627aa136acaa2da49d;hpb=3889078dbe09a9d85b359e9c0c0c225e0bbea343;p=oweals%2Fbusybox.git

diff --git a/testsuite/TODO b/testsuite/TODO
index 24126318a..b8957f488 100644
--- a/testsuite/TODO
+++ b/testsuite/TODO
@@ -2,22 +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
 something to do, feel free to tackle one or more of the following:
 
-Buildroot support
-	Erik has put together a handy package for constructing and
-	testing busybox called buildroot.  Integrating this into
-	the testsuite would allow for greater test coverage (e.g.,
-	init, mount, and other privileged applications).
+Moving to the new format.
+	The old way was "lots of little tests files in a directory", which
+	doesn't interact well with source control systems.  The new test
+	format is command.tests files that use testing.sh.
 
-BB_FEATURE support
-	BusyBox contains a number of features which are controlled
-	by compile-time defines.  A method to run tests based on
-	these features would be great.
+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
 	Being able to test the functions of libbb individually may
 	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?).