summaryrefslogtreecommitdiff
path: root/testsuite/TODO
diff options
context:
space:
mode:
authorMatt Kraai2001-10-30 23:11:20 +0000
committerMatt Kraai2001-10-30 23:11:20 +0000
commit3889078dbe09a9d85b359e9c0c0c225e0bbea343 (patch)
treee258582c0f14f06750e480e2c244260e79860fd0 /testsuite/TODO
parent999623e9736d21177d1f437679b334e0347a6e0f (diff)
downloadbusybox-3889078dbe09a9d85b359e9c0c0c225e0bbea343.zip
busybox-3889078dbe09a9d85b359e9c0c0c225e0bbea343.tar.gz
Merge test suite.
Diffstat (limited to 'testsuite/TODO')
-rw-r--r--testsuite/TODO23
1 files changed, 23 insertions, 0 deletions
diff --git a/testsuite/TODO b/testsuite/TODO
new file mode 100644
index 0000000..2412631
--- /dev/null
+++ b/testsuite/TODO
@@ -0,0 +1,23 @@
+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).
+
+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.
+
+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?).