Open Source Unit Testing Tools

A modern, C++-native, test framework for unit-tests, TDD and BDD - using C++14, C++17 and later (C++11 support is in v2.x branch, and C++03 on the Catch1.x branch). Catch2 is mainly a unit testing framework for C++, but it also provides basic micro-benchmarking features and simple BDD macros. Catch2's main advantage is that using it is both simple and natural. Test names do not have to be valid identifiers, assertions look like normal C++ boolean expressions, and sections provide a nice and local way to share set-up and tear-down code in tests. You are on the devel branch, where the v3 version is being developed. v3 brings a bunch of significant changes, the big one being that Catch2 is no longer a single-header library. Catch2 now behaves as a normal library, with multiple headers and separately compiled implementation.

Most test frameworks for C require a lot of boilerplate code to set up tests and test suites -- you need to create a main, then register new test suites, then register the tests within these suites, and finally call the right functions. This gives the user great control, at the unfortunate cost of simplicity. Criterion follows the KISS principle, while keeping the control the user would have with other frameworks. Supports parameterized tests and theories. Progress and statistics can be followed in real time with report hooks. TAP output format can be enabled with an option. Runs on Linux, FreeBSD, macOS, and Windows (Compiling with MinGW GCC and Visual Studio 2015+). If you'd like to see Criterion included in your favorite distribution, please reach out to their package maintainers team. A default entry point is provided, no need to declare a main unless you want to do special handling.

FORTRAN Unit Test Framework, written in FORTRAN 95. So that all FORTRAN features can be tested. FRUIT has assertion, fixture, setup, teardown, report, spec, driver generation. Rake used as build tool. Tutorials at http://fortranxunit.wiki.sourceforge.net The core testing part is in FORTRAN, this part can be used independent of the Ruby codes. The Ruby code is to make fixtures and reports easier. Rake is to build the project elegantly. This project also demonstrate a new way to build mixed language code in an alternative way than Make. Most of the FORTRAN are important in nature, used in nuclear and aerospace codes, etc, and maintained and written actively. Please help to bring TDD practices to the FORTRAN community. The change could be very hard, personally, I quit, since I could not make the change. I hope your organization will be successful. Enjoy a cup of fruit while maintaining FORTRAN ! Andrew Hang Chen and other maintainers who feel importance of TDD in cr

The VBScript Development Kit (VDK) is a VBScript compliant development library to be used in any host that has support for Windows Script Host (WSH). Modelled after the Java Development Kit (JDK), the VDK adds programming features/concepts prevalent in other higher order programming languages such as Java, C#, etc. The VDK provides rapid development capabilities by providing out of the box support for many common programming activities e.g., string manipulation and handling, file manipulation, logging, external code file importing, doc comments, etc While VBScript is considered a legacy language with no support from Microsoft, the language is still being used in production systems like UFT and QTP. The VDK has been tested and used in mainstream WSH hosts such as wscript.exe, cscript.exe, QTP and UFT. Visit our website: https://vbscript-development-kit.sourceforge.io for tutorials, VDK script examples and support.

pFUnit is now hosted and developed on GitHub. And will be completely removed from sourceforge on January 01, 2020 Please use: https://github.com/Goddard-Fortran-Ecosystem/pFUnit GitHub has been the primary host for some time now, but with the release of pFUnit 4.0 earlier in 2019, the sourceforge site is very out of date.

FUnit is the first generation xUnit testing tool to leverage the custom metadata capabilities of the Flex mxmlc compiler. The tag-based attribute model of FUnit makes it the most intuitive unit-testing framework ever created for the Flex platform.

NatUnit is a Unit-Test-Framework for Natural. Natural is a 4GL programming language from Software AG (SAG).

AsUnit is the only open-source unit test framework that supports Flash Players 6, 7, 8 and 9.

BugEye is an XML-based unit test creation framework. Being XML-based, it can be easily translated to almost any language. The current translations are C#, Java, JavaScript, and Visual Basic. Future translations include C++, Python, Perl, and PHP.

Cue is a Unit Testing Framework for C. This framework supports making and execution of the unit test for C programs. Cue aims at the framework that beginner of Test First Programming or XP(eXtream Programming) can easily use.

C++ unit testing framework, very cutdown compared to CppUnit but very simple and implemented entirely using header files.

A test framework for penetration testing Java classes and methods with randomized parameters and testing the results.

JsUnit is a unit testing framework for client-side JavaScript in the tradition of the XUnit frameworks. Development began in 2001. As of 11/28/2009, development has moved to GitHub: http://github.com/pivotal/jsunit

Marigold is an in-container "scenario-based" white-box unit-testing framework for J2EE applications that permits direct testing of business logic and data-access layers, and separates test-data from test-code.

NUnit is a unit-testing framework for all .Net languages. Initially ported from JUnit, the current production release, version 3, has been completely rewritten with many new features and support for a wide range of .NET platforms. NUnit is intended to be extensible. We can't do everything for everybody but we want to make it reasonably easy to extend NUnit. In many cases, users will be able to implement a special feature outside of our scope by simply creating a new attribute that embeds the required logic. In other cases, particularly in extending the engine, we rely on a plugin architecture. When running tests in a separate process, the console and gui runners make use of the NUnit Agent program, nunit-agent.exe. Although not directly run by users, nunit-agent does load and execute tests and users need to be aware of it, especially when debugging is involved.

NovaProva is a unit testing framework for C (and later C++). In other words it discovers tests, runs them in various ways, detects failures in them, and reports the failures out to a human. There are many other such frameworks for many languages, see http://en.wikipedia.org/wiki/XUnit Notably, we use the CUnit today in the Cyrus IMAP server, and it was CUnit's many pain points that inspired my work on NovaProva.

Otter Unit Test Framework is a tool which performs automated Unit Test in .NET 4,0 or above applications. It works similarly to the JUnit and it used as part of the application being tested, in MS Web or C# Developer 2010. Older versions (00.05 and below) were developed for MS Visual Studio 2005 and can still be downloaded. For them, a MS Visual Studio Plugin was developed and in the project´s home page you can find its documentation.

qooxdoo is a universal JavaScript framework that enables you to create applications for a wide range of platforms. With its object-oriented programming model, you build rich, interactive applications (RIAs), native-like apps for mobile devices, light-weight traditional web applications or even applications to run outside the browser. You leverage its integrated tool chain to develop and deploy applications of any scale while taking advantage of modern web technologies like HTML5 and CSS3, its comprehensive feature set, and a state-of-the-art GUI toolkit. qooxdoo is open source under liberal licenses, led by a dedicated developer team, with a vibrant community. Qooxdoo offers a wide range of widgets and UI components, plus powerful server I/O communication. Built-in unit testing framework with unit tests across the API and User Interface testing.

R Unit test framework R functions implementing a standard Unit Testing framework, with additional code inspection and report generation tools

RIMUnit, an xUnit based unit-testing framework, allows developers to write better-quality Java code while developing applications for the BlackBerry® smartphone.

Robolectric is the industry-standard unit testing framework for Android. With Robolectric, your tests run in a simulated Android environment inside a JVM, without the overhead of an emulator. Running tests on an Android emulator or device is slow! Building, deploying, and launching the app often takes a minute or more. That’s no way to do TDD, there must be a better way. Robolectric is a framework that brings fast and reliable unit tests to Android. Tests run inside the JVM on your workstation in seconds. Robolectric is built using Gradle. Both IntelliJ and Android Studio can import the top-level build.gradle file and will automatically generate their project files from it. Robolectric supports running tests against multiple Android API levels. The work it must do to support each API level is slightly different, so its shadows are built separately for each. If you would like to live on the bleeding edge, you can try running against a snapshot build.

ScUnit is a robust unit testing framework for Scala.

Standalone test spies, stubs and mocks for JavaScript. Works with any unit testing framework. As before, Sinon.JS provides utilities that help test frameworks reduce the boiler-plate. As of Sinon 10 we stopped maintaining compatibility with legacy browsers. Instead, we focus on compatibility with evergreen browsers, Node.js LTS versions and recent Safari versions. The most up-to-date reference on which runtimes and browsers we support can be found by looking at our compatibility docs. Fake timers are synchronous implementations of setTimeout and friends that Sinon.JS can overwrite the global functions with to allow you to more easily test code using them. A test spy is a function that records arguments, return value, the value of this and exception thrown (if any) for all its calls. There are two types of spies: Some are anonymous functions, while others wrap methods that already exist in the system under test. Mocks should only be used for the method under test.

This is a template application that implements a "conversational" extended persistence context: with Spring and Maven: - Annotation-driven Hibernate mappings - Configuration of the AOP-based service layer - A unit- and integration-test framework

Test Monkey has been renamed to BugEye. Please goto http://sourceforge.net/projects/bugeye.