Open Source Windows Code Coverage Tools - Page 2

This is a silly little command line tool for sexy ANSI fonts in the console. Give your cli some love. cfonts detects what colors are supported on your platform. It sets a level of support automatically. In cfonts you can override this by passing in the FORCE_COLOR environment variable. All settings are optional and shown here with their default. You can use cfonts in your project without the direct output to the console. The package comes with a bunch of unit tests that aim to cover 100% of the code base. For more details about the code coverage check out coveralls.

Catberry is an isomorphic framework for building universal front-end apps using components, Flux architecture and progressive rendering. Catberry builds a bundle for running the application in a browser as a Single Page Application. Cat-Components – similar to web-components but organized as directories, can be rendered on the server and published/installed as NPM packages. The entire architecture of the framework is built using the Service Locator pattern, which helps to manage module dependencies and create plugins, and Flux, for the data layer. Search crawler receives a full page from the server. The whole state of the application is restored from URL. Server-side progressive rendering based on node.js streams and parallel rendering of components in a browser. The framework is well-tested (code coverage is about 90%) and it is already used in production.

Sonar offers a single cohesive solution with a consistent set of metrics and hundreds of static analysis rules to detect your coding issues early. Plus fast and high-precision analysis means high value, low noise, and reliable results always. A single solution for dozens of popular languages, development frameworks and IaC platforms. Our powerful language-specific analysis not only detects coding issues but also helps you understand what's wrong and how to fix it. Our publicly available ruleset includes thousands of rules covering various issue categories and language standards. Open the rule in SonarQube / SonarCloud, scroll down and (in case the rule has parameters), you can configure the parameters for each Quality Profile the rule is part of. Standalone NuGet packages can be configured the same way as SonarLint in connected mode.

A code coverage console app for wrapping MsTest executed tests for Visual Studio for Testers. The app extracts coverage data from a binary (*.coverage) file, generated by MsTest into an XML file which can be used in your build process.

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).

EL4Ant is a light and efficient build system based on Apache Ant. A project is described in XML as modules with transitive dependencies. Features are provided thanks to plugins: Java execution, JUnit reports, EMMA code coverage, Eclipse integration...

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.

A minimal skeleton for building testable React apps using Babel. The design goals are to use fewer tools (no yeoman, gulp, bower, etc...) Babel 6 with Webpack and Hot Loader. Fast testing with mocked-out DOM. Import CSS files as class names. Separate smart and dumb components. No specific implementation of Flux or data fetching patterns. A core philosophy of this skeleton app is to keep the tooling to a minimum. For this reason, you can find all the commands in the scripts section of package.json. This leverages React Hot Loader to automatically start a local dev server and refresh file changes on the fly without reloading the page. It also automatically includes source maps, allowing you to browse code and set breakpoints on the original ES6 code. Build minified app for production using the production shortcut.

A boilerplate application for building RESTful APIs Microservice in Node.js using express and mongoose in ES6 with code coverage and JsonWebToken Authentication. Helps you stay productive by following best practices. Follows Airbnb's Javascript style guide. JavaScript code linting is done using ESLint, a pluggable linter tool for identifying and reporting on patterns in JavaScript. Uses ESLint with eslint-config-Airbnb, which tries to follow the Airbnb JavaScript style guide. Supports code coverage of ES6 code using istanbul and mocha. Code coverage reports are saved in the coverage/directory post yarn test execution. Open coverage/lcov-report/index.html to view the coverage report. yarn test also displays code coverage summary on the console. Code coverage can also be enforced overall and per file as well, configured via .istanbul.yml.

gcov-eclipse is an Eclipse plug-in that will extend CDT to provide code-coverage testing to C/C++ projects by using the gcov program. It will integrate into the CDT's launch and managed build system.

Visualize the distribution of code coverage in your project. This helps to identify code areas with high and low coverage. Useful when you have a large project with lots of files and packages. This 2D image-hash of your project should be more representative than a single number. For each module, the node representing the greatest version (i.e., the version chosen by Go's minimal version selection algorithm) is colored green. Other nodes, which aren't in the final build list, are colored grey — by the official Go team. Use to find unexpected dependencies or visualize the project. Works best for a small number of packages, for large projects use grep to narrow down subgraph. Collect all the licenses or check if you can use the project for example in a proprietary or commercial environment. Tell Go compiler which versions of upstreams to include in your build. Tell all users of your module how to deal with versions of your module.

A cross platform Http web server developed using C++. Agile methodology with emphasis on :- 1. Good Design 2. Object Oriented Programming 3. Refactoring 4. Static/Dynamic Analysis, Unit-testing, Code Coverage 5. Software Engineering best practices.

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

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.

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.

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.

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.

A python SDK for managing Nebula container orchestrator. First, get NebulaPythonSDK onto your machine, now use it in your code. Nebula container orchestrator aims to help devs and ops treat IoT devices just like distributed Dockerized apps. It aim is to act as Docker orchestrator for IoT devices as well as for distributed services such as CDN or edge computing that can span thousands (possibly even millions) of devices worldwide and it does it all while being open-source and completely free. Nebula imposes no limits on the scale of the cluster, each component in it is designed to scale out to allow millions of workers to be managed by it. Designed to connect to devices that are spread around the globe Nebula is tolerant of network connection issues and will resync the device when it reconnects. With a single API call you can deploy a new container version to managed devices around the globe in minutes.

Camlp4 extension to check code coverage of any OCaml code