Open Source Windows Code Coverage Tools - Page 3

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.

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

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.

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.

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

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.

Unzip buildtemplate and you will have a project set up with ant/junit/verifydesign/code coverage all out of the box. It is a great way to get started and then add to the build.xml as you go. netbuildtemplate is for .net and has nant/nunit/NCover, etc.

Coberclipse is a eclipse plugin for Corbertura. It will instrument the classes during the build and show the code coverage after executing unit test cases.

Code Coverage Tool For Oracle PL/SQL

Build powerful, scalable applications, with minimal overhead and full out-of-the-box functionality. Originally developed to handle Walmart’s Black Friday scale, hapi continues to be the proven choice for enterprise-grade backend needs. When you npm install @hapi/hapi, every single line of code you get has been verified. You never have to worry about some deep dependency being poorly maintained (or handed over to someone sketchy). hapi is the only leading node framework without any external code dependencies. None. hapi has been pushing the envelope on quality from day one. It was the first node framework to require and achieve 100% code coverage across every dependency – when everyone thought it was crazy. Every hapi feature is designed to make the platform easier and more intuitive to use. That means there’s no need to hack things together, experiment to see what *might* work, or try to figure out hidden internals. There is no “magic” – the code does what you expect.

xCover is a C/C++ library that uses low-impact syntactic signalling to detect code coverage in a code base at runtime