Free unit testing software for linux

QUnitTester is a Qt4 binary unit tester.
Everyone who uses JUnitTesting knows about the "green bar". Qt has great possibilities for Unit Testing but i missed the green bar.
If you want to know more about Unit Testing in Qt take a look at: http://doc.trolltech.com/4.2/qtestlib-manual.html
and http://doc.trolltech.com/4.2/qtestlib-tutorial.html
The software doesnt much yet. It only runs all tests...
INSTALL:
qmake (from qt 4, in (k)ubuntu for example qmake-qt4)
make
as root: make install
USAGE:
Write your testclass and compile it. Start the program and click on Test Binary...
Choose the compiled binary.
Click on start.
Enhancements:
- Possibility to use options
- Select test(s) to run

Eunit project is an Erlang test suite tool, inspired by agile development ideas.
Usage:
Launch example unit test with:
erl -config sys.config
and then
eunit:run([eunit_examples], {suffix, "_test"}).
Enhancements:
- This release is a complete rewrite.
- Writing unit tests should now be simpler than with the previous version.
- This release can also be used with the Aegis configuration management system for continuous integration.

Folding@Gnome project is an applet is a GUI that keeps track of the background protein folding progress done by Folding@Home

The Folding@Gnome applet is merely a GUI in which you can adjust your Folding@Home settings and view the folding progress. Folding@Home is a background process that uses spare CPU cycles to calculate the folding of proteins. For more info, please visit Stanfords Folding@Home homepage.

p-unit is a framework for benchmarking performance. The project records memory consumption and execution time, and generates results in the form of plain text, image, and PDF file. Users can also easily register their own reporters by implementing PUnitEventList.
Test Suite and Test Class
Test suite and test class are two important concepts in p-unit. p-unit does not require any special type for a test class, so every class can be a test class. Of course, it includes junit test cases. There is one special interface for special p-unit only test class - p-unitTest. p-unit executes a normal test as following procedure:
invoke setUp if there is.
invoke the test method.
invoke tearDown method.
Noticed that setUp and tearDown will also be regarded as a part of performance test. If you dont want to count them into performance data, you need to implement p-unitTest interface, which will be executed as:
invoke setUpBeforeWatchers.
invoke setAfterWatchers.
invoke the test method.
invoke tearDownBeforeWatchers.
invoke tearDownAfterWatchers.
As the name suggests, you can put the setUp and tearDown code into the setUpBeforeWatchers and tearDownAfterWatchers.
Time/Memory Record
p-unit records the memory and time consumption of running a test method. There is a "watcher" concept in p-unit, which supervises the status during running the test method. By default, memory watcher and time watcher are installed. p-unit supports user-defined watcher too. The user only needs to implement the Watcher interface and register it to p-unit method runner.
Enhancements:
- Changes to adopt the Apache License 2.0.
- A customized watcher infrastructure to make it possible to report results from test cases.
- A new EventListener that sets public test fields on start up.

GNU/Linux Desktop Testing Project (GNU/LDTP) is aimed at producing high quality test automation framework and cutting-edge tools that can be used to test GNU/Linux Desktop and improve it.
GNU/Linux Desktop Testing Project uses the "Accessibility" libraries to poke through the applications user interface. The framework has tools to generate "AppMap" by reading through the user interface components of an application. The framework also has tools to record test-cases based on user-selection on the application.
GNU/LDTP core framework uses "AppMap" and the recorded "test-cases" to test an application and gives the status of each test-case as output.
As of now, GNU/LDTP can test any GNOME application which are accessibility enabled, Mozilla, OpenOffice.org, any Java application (should have a UI based on swing) and KDE 4.0 applications based on QT 4.0 (based on the press releases by KDE).
We encourage you to join the project and help us to create robust, reliable and stable test tool/framework for Linux Desktops.
Main features:
- LDTP concepts are derived from Software Automation Framework Support
- LDTP supports verification of actions performed (GuiExist, VerifyState, etc) - API Reference
- Writing test scripts are very easy, the script writer need not know about the object hierarchy
- CPU / Memory performance monitoring of application-under-test can be measured - Class pstats
- From the XML log, we can gather HTML report using XSLT
- Group based execution, which provides precise control on the flow of test-script execution - Gldap XML
- Scripts can be written as a reusable component and for that the datas can be stored / retrieved in XML - Data XML
- User-friendly Text Editor with syntax highlighting for generating and grouping test data Howto use LDTP Editor
- Objects are identified both statically and dynamically
Enhancements:
- Now automation scripts can be written without using time.sleep.
- A particular object and its child can be remapped in a window.
- Memory leaks were fixed.

AppsUnit toolkit assists with the testing of your Oracle e-business suite code. It tests views, PL/SQL packages, concurrent requests, and more.
No software needs to be installed on the application server. Results are made available as a PDF report.
Enhancements:
- The example test kit is available for download.
- The suite uses some of the apps foundation views as an example.
- These views are unit tested, and the results are available as HTML and PDF reports.

GUnit is a C unit testing framework in the spirit of JUnit. GUnit framework incorporates an easy-to-use GUI based on the GNOME libraries, as well as support for Hildon UI (maemo.org).
Installation:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- A broken pkg-config file was fixed.

Test::Unit is the main PerlUnit testing framework.

SYNOPSIS

This package provides only the project version number, copyright texts, and a framework overview in POD format.

This framework is intended to support unit testing in an object-oriented development paradigm (with support for inheritance of tests etc.) and is derived from the JUnit testing framework for Java by Kent Beck and Erich Gamma. To start learning how to use this framework, see Test::Unit::TestCase and Test::Unit::TestSuite. (There will also eventually be a tutorial in Test::Unit::Tutorial.

However Test::Unit::Procedural is the procedural style interface to a sophisticated unit testing framework for Perl that . Test::Unit is intended to provide a simpler interface to the framework that is more suitable for use in a scripting style environment. Therefore, Test::Unit does not provide much support for an object-oriented approach to unit testing.