TestDrivenDevelopment

Test Driven Development

Testing

UnitTesting and AutomatedTesting will be included in the DeveloppementProcess as early as possible, that is when the KernelLoader and later the MicroKernel and other subsequent modules developpement will start.

TestSuites will be developped for each module, and if necessary - which I see as mandatory in fact - for each routine in each module.

Test messages should have a standard format, indicating which TestSuite they belong to, which test is run, which results were expected, obtained, etc and 'ok' if the test is successful, 'ko' otherwise.

eg: BootSector:AX value:expected 1000 obtained 2000:ko

This would allow a simple grep to extract some subsets of an AutomatedTesting session log.

unit tests and testsuites

• Each unit tests belong to a testsuite
• A testsuite is made of one or more unit tests
• A test suite is always made a target in a makefile
• A DosEmu test suite is launched only if it has been correctly compiled.
• An emulator hosted test suite is launched only if the corresponding disk image has been correctly generated
• A test suite always exits with a success (0) return code. Thus make won't see errors in testsuites.
• A unit test show it success (Ok) of failure (Ko) on its stdout
• Each unit test outputs only onto stdout
• Each Unit test log output is formated as follows : tag TestSuite UnitTest OKKO message, where
• tag is 'UT'
• TestSuite is the name of the current test suite
• UnitTest is the name of the unit test currently executed
• OKKO is 'Ok' in case of success, or 'Ko' in case of failure
• message is specific to the unit test (eg: expected value/obtained value)

Red/Yellow/Green bar

A tool will be developped to list the unit tests which failed during their last execution, and some statistics like:

• number of failed unit tests per test suite (red bar)
• number of successful unit tests per test suite (green bar)
• number of red, yellow, green test suites (a yellow bar is a testsuite tainted red and green)

The job of this tool is to

1 grep ^UT from the make log file

2 compute RG tests count and ratios

3 compute RYG test suites count and ratios

Note for later

UnitTesting has border effects onto the code being tested. These effects must be forseen when possible, and taken into account while building the TestSuites

Links: HomePage