Open Source Software Testing Tools

Keploy is a functional testing toolkit for developers. It generates E2E tests for APIs (KTests) along with mocks or stubs(KMocks) by recording real API calls. KTests can be imported as mocks for consumers and vice-versa. Merge KTests with unit testing libraries(like Go-Test, JUnit..) to track combined test coverage. KMocks can also be referenced in existing tests or use anywhere (including any testing framework). KMocks can also be used as tests for the server. Keploy is added as a middleware to your application that captures and replays all network interaction served to the application from any source. Keploy has native interoperability as it integrates with popular testing libraries like go-test, junit. Code coverage will be reported with existing plus KTests. It'll also be integrated in CI pipelines/infrastructure automatically if you already have go-test, junit integrated.

OpenCover is a free and open source code coverage tool for .NET 2 and above (Windows OSs only - no MONO), with support for 32 and 64 processes and covers both branch and sequence points. It uses the profiler API that is currently only available to .NET Frameworks running on the Windows platform. OpenCover is an attempt at building a code coverage utility that addresses certain issues in maintaining PartCover support for 64-bit processes.

Jest is a delightful, comprehensive JavaScript testing framework that works right out of the box for most JavaScript projects. It works on projects that use Babel, TypeScript, Angular, React, Node and so much more! It works fast and simple, capturing snapshots either alongside your tests or embedded inline to make testing and tracking changes over time a whole lot easier. Jest is designed to ensure the correctness of any JavaScript codebase. It has a great API, is well maintained and well documented, and can be extended to meet your exact requirements. Simply put, Jest just makes testing delightful!

EclEmma is a free Java code coverage tool for Eclipse, available under the Eclipse Public License. It brings code coverage analysis directly into the Eclipse workbench. The EclEmma project is also the home of the JaCoCo code coverage library which is the technical back-end for EclEmma and also has integrations with many other build and software quality tools.

JSCover is a tool that measures code coverage for JavaScript programs. It is an enhanced Java implementation of the excellent JSCoverage tool.

A Unibasic Code Coverage tool. It produces formatted HTML reports on the statement coverage of selected source files. Designed for UniData but should is being ported to UniVerse (still in development, but compiles and works on demonstration programs).

BeCover is a Java code coverage tool based on source-code analysis. The main goal is to keep it small and fast, so using it as a plugin in the common IDE's can be achieved.

This project provides a meaningful way to increase code coverage of your jUnit and TestNG tests. Unit testing Java Beans can be a tedious task. The goal of this project is to provide an automated way to unit test the getters and setters of a class.

An eclipse plugin for code coverage visualization of JUnit Tests. Especially useful for test-first development. Supported coverages include block coverage and all-uses coverage (Data Flow Analysis).

Easy Coverage is a tool that can dynamically generate unit tests to perform basic verifications, thus leaving more time for the developers. When writing unit tests, developers often have to write the same elementary verifications over and over for most classes. This is tedious and error-prone, and keeps developers away from writing more meaningful unit tests. Easy Coverage is extensible and highly configurable. It can work as a standalone product, or be used with JUnit, which is highly recommended. Support for TestNG is planned. If you want to get started, you should go to the wiki and the quick start.

An integrated testing framework, covering test case generation, execution, bug reporting, code coverage and coding conventions. Currently This is a module suite for netbeans IDE, integrating some open source PHP Testing Tools

Intern is a complete test system for JavaScript designed to help you write and run consistent, high-quality test cases for your JavaScript libraries and applications. It can be used to test any JavaScript code. Intern is minimally prescriptive and enforces only a basic set of best practices designed to ensure your tests stay maintainable over time. Its extensible architecture allows you to write custom test interfaces, executors, and reporters to influence how your tests run & easily integrate with your existing coding environment. Intern also comes with Grunt tasks so it can be quickly added to existing Grunt-based workflows, and is designed to work out-of-the-box with popular continuous integration services like Jenkins and Travis CI. Intern can run unit tests in most browsers that support ECMAScript 5, including mobile browsers on Android and iOS, and in Node 6+. Note that Internet Explorer 9 is not supported.

JUnitMetrics is a tool that enables to measure basic JUnit and Cactus tests metrics (like number of tests, assertions, number of executed assertions). It is great, complementary solution to code coverage tools and mutation testers.

This profiler (JRE 1.5.0 only) uses JVMTI and native bytecode instrumentation for the analysis of the heap, reachable objects, execution time, garbage collection efficiency, code coverage and thread contention. No preparation steps required in build.

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.

Camlp4 extension to check code coverage of any OCaml code

Measure how directly your classes are tested by JUnit. Unlike traditional code coverage tools, PEA considers and measures whether the code covered ran as a direct call from a test, or indirectly via chained calls.

PHPCoverage is an open-source tool for measuring and reporting code coverage provided by the test suite of a PHP application. PHPCoverage can instrument and record the line coverage information for any PHP script at runtime.

Extends Cobertura to measure and report on code covered by unit tests in same package. Also adds improved reporting features, including measuring code coverage against a coverage policy.

A toolbox for testing SQL. Currently, SQL Spelunk includes code coverage analysis and calling stored procedures in a rolled-back transaction from SQL and JUnit.

STUBborn C is a tool that allows you to create a module test framework for SW modules developed in C. The framework includes: Stubs needed to link the module; A sample Makefile to build, run tests and check code coverage; Test templates using CUnit.

Code Coverage tool for C++ and C# applications

NetBeans module that provides JaCoCo code coverage (Java7 compatible). For Ant based JavaSE projects. Maven and Gradle support may be added later. WARNING: Binary files have been removed. They're now on a NetBeans update center. Please check https://github.com/jonathanlermitage/tikione-jacocoverage#download-stable-and-dev-builds for details. ~Jonathan Lermitage <jonathan.lermitage@gmail.com>

Tiria is a eclipse-plugin to view code coverage data (e.g. from cobertura) within the IDE. Main objective of the plugin is to show how the code coverage changes during project progress.

ZK Unit extends JUnit to test your ZK project: ZUL pages, composers, event handlers, constraints and more. Use ZKUnit for test driven development, to achieve code coverage and integration with a continous build system.