Open Source Code Coverage Tools - Page 3

A Gradle plugin that auto-creates and configures JaCoCo code coverage tasks for each Android app/module variant, saving you from manual setup across build types and flavors.

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.

It is a JavaDoc and comment coverage tool. It check the quality of JavaDoc and comments in Java source files. The output is like the EMMA Java code coverage.

Javelina is an advanced code coverage tool that uses dynamic instrumentation to minimize the overhead for collecting coverage data. Additionally, Javelina allows the application of logical operations to code coverage data.

A web-based courseware system for programming courses. Provides support for on-line submission testing, static analysis, code coverage, peer and instructional code reviews and grading. Works with projects in any programming language.

A quick C++ template for modern CMake projects aimed to be an easy-to-use starting point. This is my personal take on such a type of template, thus I might not use the best practices or you might disagree with how I do things. Any and all feedback is greatly appreciated! Modern CMake configuration and project, which, to the best of my knowledge, uses the best practices. An example of a Clang-Format config, inspired from the base Google model, with minor tweaks. This is aimed only as a starting point, as coding style is a subjective matter, everyone is free to either delete it (for the LLVM default) or supply their own alternative. Static analyzers integration, with Clang-Tidy and Cppcheck, the former being the default option. Doxygen support, through the ENABLE_DOXYGEN option, which you can enable if you wish to use it. Unit testing support, through GoogleTest (with an option to enable GoogleMock) or Catch2. Code coverage, enabled by using the ENABLE_CODE_COVERAGE op.

Setting up a new C++ project usually requires a significant amount of preparation and boilerplate code, even more so for modern C++ projects with tests, executables and continuous integration. This template is the result of learnings from many previous projects and should help reduce the work required to setup up a modern C++ project. Installable target with automatic versioning information and header generation via PackageProject.cmake. Automatic documentation and deployment with Doxygen and GitHub Pages. Eventually, you can remove any unused files, such as the standalone directory or irrelevant github workflows for your project. Feel free to replace the License with one suited for your project. To keep the template modular, all subprojects derived from the library have been separated into their own CMake modules. This approach makes it trivial for third-party projects to re-use the projects library code.

NCoverCop is a custom NAnt task that fails your build when your code coverage drops by using NCover. It also tells you what code has become untested. This promotes TDD. See NAnt [http://nant.sourceforge.net/] and NCover [http://www.ncover.com/]

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.

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.

Java Web Application Stack built on top of Wicket, Spring, Hibernate/Ibatis, Jetty, HSQLDB, Junit, functional testing (Selenium), code coverage(Cobertura), DB Migration and CI. Its intent is to provide a rapid method for creating java web new projects

A simple but feature-rich starter boilerplate for creating your own universal app. It built on the top of React, Redux, React Router and Express. Includes all the hot stuff and modern web development tools such as Redux Toolkit, TypeScript, Webpack, Babel, PostCSS, React Refresh, Jest and React Testing Library. See the “Features” section for other awesome features you can expect. They're several React frameworks today, however this is a DIY-oriented start-kit. It shows you how to build a universal web app from scratch and how to test it. Redux Toolkit is the official, opinionated, batteries-included toolset for efficient Redux development. It includes several utility functions that simplify the most common Redux use cases. In a word, we can do more work with less code, start from the tutorial to learn more about it.

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.

Program handling file operations when interfacing embedded system by serial port. Main intention for creation of this program was getting files with code coverage out of the embedded system memory.

Code coverage for Ruby with a powerful configuration library and automatic merging of coverage across test suites. SimpleCov is a code coverage analysis tool for Ruby. It uses Ruby's built-in Coverage library to gather code coverage data, but makes processing its results much easier by providing a clean API to filter, group, merge, format, and display those results, giving you a complete code coverage suite that can be set up with just a couple lines of code. SimpleCov/Coverage track covered ruby code, gathering coverage for common templating solutions like erb, slim and haml is not supported. In most cases, you'll want overall coverage results for your projects, including all types of tests, Cucumber features, etc. SimpleCov automatically takes care of this by caching and merging results when generating reports, so your report actually includes coverage across your test suites and thereby gives you a better picture of blank spots.

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.

A code coverage tool for x10 using Jacoco

The conversion performance is close to handwriting code. The object types can be automatically converted. All data types will be verified to ensure type-safe during the conversion process. There is no need to make the model class inherit from other base class. This library contains only 5 files. Docs and unit testing, 100% docs coverage, 99.6% code coverage. You can map a json key (key path) or an array of json key (key path) to one or multiple property name. If there's no mapper for a property, it will use the property's name as default.

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.

bcov is a code coverage tool similar to gcov. Unlike gcov, it does not require recompiling the project for coverage. Coverage is determined by using temporary breakpoints, which causes minimal overhead. gcov produces a lcov style coverge report.

BUILD & RUN - to build a jar file, run maven's lifecycle task "mvn clean install". - run it with cmd: "java -jar {csvviewer-with-dependencies.jar} -f {path-to-csv} HELP - get help on possible startup params with "java -jar {csvviewer,jar} --help IMPORTANT NOTES If you want to change anything, look at the task description of rené first to ensure it's not against the task's rules. Please use the InteliJ code coverage report, to respect the 100% coverages on the main classes: - Commander - Paging - Reader - Viewer Do NOT check-in any IDE (.eclipse, .idea) or build files (target)