EMbunit

1. Test case organisation - Use the GUI to create and organise unit test specification

• Each test case has its own set-up and tear-down code
• Put test cases in the same test suite to run them sequentially, one after the other.
• Specify what header files to include and import stub-code directly
• Each complete test suite is stored in a separate XML file.
• Embunit displays the test suite hierarchy. The content of each test case is shown as a list of high-level operations.

2. Test Driven Development (TDD) - Define tests before writing the code.

• All files used or generated by Embunit are text files.
• Test suites and source code can be checked into the version control system and any changes can easily be reviewed using a file comparison utility.

• Allows to specify when you expect an exception to be thrown
• Automatically inserts catch-all exception handling code
• The use of exception handling is optional

• Most embedded C++ compilers do not implement all the features of the C++ language
• Exception handling code can also be disabled, giving full compatibility with the Embedded C++

6. Customising Embunit

• Test results - The example implementations supplied with Embunit use printf() and std::out to report test results.
• Stub code - allows to specify the test "Context" anywhere in a test case. Stub code has access to the "Context" and can take appropriate action.
• Stub code also has access to the test case and test step number