It was a bit out of date.

git-svn-id: svn://busybox.net/trunk/busybox@12177 69ca8d6d-28ef-0310-b511-8ec308f3f277

1 files changed, 18 insertions, 10 deletions

diff --git a/testsuite/TODO b/testsuite/TODO
index ced571595..b8957f488 100644
--- a/testsuite/TODO
+++ b/testsuite/TODO
@@ -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
 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.
+
+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?).