tuitest is a tool to create and run automated tests of text user interfaces. It is meant as a complement to the widespread use of unit tests, and uses concepts known from GUI testing tools with the difference that it applies them specifically to text- and terminal-based user interfaces. It consists of a recorder that records the interaction with an application under tests and generates a Ruby script that replays the same interaction, optionally with the same timing. Ruby replaying is supported through a native Ruby module.
mutest is a micro unit testing framework for C (with some C++ support). It is easy to use and has no dependencies. The idea is simple: a source file is a test suite, and a function is a test case (special functions can be used for test suite initialization and termination) that can can have several checks. Checks comes in 2 flavors: one that only prints an error, and one that terminates the current test case too. A (normally) automated test program run all the test suites and prints some stats. It fails (returns non-zero) if any test suite fails.
Kundo provides a structured, convention based approach for Java builds. Kundo has a pluggable, extensible architecture; it harnesses the power and flexibility of Groovy and Ant to provide a highly configurable Java build framework. Kundo achieves this flexibility with a plug-in architecture that attaches behaviors (provided by Kundo plug-ins) to build lifecycle phases. Kundo consists of a kernel and a set of foundation plug-ins. The kernel is responsible for the orchestration of the multiple collaborators within the build system.
CouchUnit is a JUnit extension that helps administer tests run against CouchDB. It mimics the syntax and feel of DBUnit by helping developers write tests that load XML style datasets to place databases in known states between integration tests. A number of standard operations are used to store and remove CouchDB documents. Any number of documents may be declared within a single CouchUnit dataset.
UnitTH is a lightweight application for generating a comprehensive HTML test history report out of a set of parsed JUnit XML test reports. The historical report collects all JUnit reports and makes it easy to navigate between them. In addition, the report contains a large number of sortable test statistics for test runs, individual test modules, and test cases. A number of graphs are generated and useful trends can very easily be spotted. There are two intended usages for UnitTH. First, it can be useful for unstable and sporadically failing test suites, for which it might sometimes be necessary to run the suite multiple times to be able to make a solid judgment regarding the outcome of the test runs. Second, it can be used for test history reporting in continuous integration like projects.