The Fressia Project is an effort to develop a framework for testing automation. It's intended for users (testers) who want a simple tool that can be used just out of the box. It was originally conceived as part of the QA efforts at the US National Optical Astronomy Observatory. It has been delivered to the community because, despite it still being at early stages, it has proven to be a useful general purpose testing tool. It is designed to provide functional testing, system testing, system integration testing, white (black) box testing, automated regression testing, acceptance testing, etc.
Zadok is a multi-language test suite runner. It is designed to run small test programs written in one of the programming or scripting languages that it understands, compare their output to what is expected, and determine a pass or fail. Tests are grouped into suites for conceptual organization purposes.
Mistletoe is a JUnit extension intended for integration testing. In technical terms, it is a JUnit test suite runner presenting the test results via HTTP as a Web page. Mistletoe, when incorporated within an application, will help diagnose integration issues. For example, an application that runs perfectly in the developer's environment may not run properly in the production environment due to configuration errors and connectivity issues. Instead of perusing log files, or looking at stack traces, mistletoe will run a user-specified series of tests and present the results in the form of a Web page served by the application itself. Since the tests are run within the context of the deployed application, given an appropriate test suite, you can home in on integration problems quickly and conveniently.
The Java Engine for Testing (JET) is a system for running distributed automated tests. It has been used by Sun for testing the High Availability DataBase (HADB), JavaDB, PostgreSQL, Memcached, and the MySQL Cluster Manager. JET should be a good way to write your tests if the product you want to test is distributed or has a client/server architecture, if it is natural for you to write the tests in Java, and if you want to invest time in developing tests and abstractions for later reuse.
Citrus is a test framework written in Java that enables automated integration testing of message-based enterprise SOA applications. The tool can easily simulate surrounding systems across various transports and protocols (e.g. JMS, SOAP WebServices, HTTP, TCP/IP, etc.) in order to perform end-to-end use case testing. Citrus provides strong validation mechanisms for XML message contents and allows you to build complex testing logic such as sending and receiving messages, database validation, automatic retries, variable definitions, dynamic message contents, error simulation, and many more.
Simple Fuzzer is a very simple fuzzer. It is reminiscent of easy-fuzz from 2004, written by priest of the priestmasters. His layout for building a fuzzy test was a "script" file with a preamble, setting some basic state and variables followed by the "meat and potatoes" tests. This approach was borrowed for Simple Fuzzer.
cipra is a simple, TAP-compatible Unit Testing Framework for C++. It's written in 100% standard C++11 and is only a couple of header files, making it easy to include in your C++11 project. TAP, the Test Anything Protocol, is a standard output format for software unit test frameworks which was originally designed for Perl, but can serve other languages. It has a rich number of tools ("harnesses") which parse TAP-formatted output and do useful things with it. TAP, however, is equally human-readable. The name cipra (pronounced /ˈʃi.pɾaː/ "SHEE-prah") comes from the lojban phrase "lo cipra", which means "the test". It is properly written with an initial minuscule "c", even when at the start of a sentence.