Rev | Line | |
---|
[20] | 1 | This testsuite is quite obviously a work in progress. As such, |
---|
| 2 | there are a number of good extensions. If you are looking for |
---|
| 3 | something to do, feel free to tackle one or more of the following: |
---|
| 4 | |
---|
| 5 | Moving to the new format. |
---|
| 6 | The old way was "lots of little tests files in a directory", which |
---|
| 7 | doesn't interact well with source control systems. The new test |
---|
| 8 | format is command.tests files that use testing.sh. |
---|
| 9 | |
---|
| 10 | Every busybox applet needs a corresponding applet.tests. |
---|
| 11 | |
---|
| 12 | Full SUSv3 test suite. |
---|
| 13 | Let's make the Linux Test Project jealous, shall we? Don't just |
---|
| 14 | audit programs for standards compliance, _prove_ it with a regression |
---|
| 15 | test harness. |
---|
| 16 | |
---|
| 17 | http://www.opengroup.org/onlinepubs/009695399/utilities/ |
---|
| 18 | |
---|
| 19 | Some tests need root access. |
---|
| 20 | It's hard to test things like mount or init as a normal user. |
---|
| 21 | Possibly User Mode Linux could be used for this, or perhaps |
---|
| 22 | Erik's buildroot. |
---|
| 23 | |
---|
| 24 | libbb unit testing |
---|
| 25 | Being able to test the functions of libbb individually may |
---|
| 26 | help to prevent regressions. |
---|
Note: See
TracBrowser
for help on using the repository browser.