JCov Alternatives

Sahi Pro is a no-code test automation tool for web, desktop, mobile, and SAP applications. Sahi Pro empowers business testers and automation engineers to streamline their test automation processes. Sahi Pro reduces the time, effort, and complexity involved in test automation, making it an ideal choice for various domains including automobile, healthcare and BFSI. Features: 1. Non-flaky Test Execution - For reliable test results and reduced time wastage in analysis of false-positives or false-negatives. 2. Supports Multiple Technologies - Achieve end to end automation across technologies. 3. No-code Automation - Enable non-technical business testers to automate. 4. Integrations - Integrate and work with your existing ecosystem. Testers using Sahi Pro easily automate complex tests without writing code. With Sahi Pro, you can achieve faster release cycles, improved software quality, & reduced costs. Our customers love Sahi Pro for its speed, flexibility, and ease of use.

Testsigma is a low-code end-to-end software testing platform that works out of the box. It's built to enable modern Product teams to collaboratively plan, develop, execute, analyze, debug, and report on their automated testing—for websites, native Android and iOS apps, and APIs. Testsigma test scripts are code-agnostic. While the platform itself is built with Java, you can write test scripts in simple English or use the Test Recorder to generate airtight test scripts for websites and native mobile apps. You can also use the test recorder on your own device farm/grid or on Testsigma's built-in device lab on the cloud. The platform has built-in visual testing, parametrized or data-driven testing, 2FA testing, and more advanced features for easy test automation. Our AI automatically fixes unstable elements and test steps, identifies and isolates regression-affected scripts, and provides suggestions to help you find and fix test failures.

Testim is the fastest path to resilient end-to-end tests—codeless, coded or both. Testim lets you create amazingly stable codeless tests that leverage our AI, but also the flexibility to export tests as code. You can leverage Testim’s modern JavaScript API and your IDE to debug, customize or refactor tests. Store them in your version control system to keep them in sync with branches and run tests on every commit. Run parallel, cross-browser tests on our test cloud or Selenium-compatible grids while integrating with your CI and dev tools to run smoke tests on pull requests, end-to-end tests on release candidates, or full regression suites on a schedule. Customers like Microsoft, Salesforce, NetApp, Wix, and JFrog run millions of tests on Testim each month. Learn more on our website and sign up for your free account!

CloudQA offers a powerful no-code/low code automation platform to speed up regression testing OR continuous monitoring of web applications. Type, click, and interact with your site as you normally would. Our recorder captures all of your actions as you navigate your site. No worrying about complexities like nested iFrames or dynamic elements. Intuitive and intelligent script maintenance - Manage tests/monitoring scripts with visual editor, as it creates a dynamic test model that is updated to reflect changes in your application. Automate complex steps with simple JavaScript & select variable data sets. With automation accelerators you require no setup, no infrastructure & no lock-in. Get high volume parallel, scalable & collaborative testing in cloud. Out of the box support for legacy & latest web technologies. See live execution of your tests, share summary & detailed reports with screenshots. Integrate with your tech stack and setup custom notifications.

Advanced fuzzing solution that combines guided fuzzing with symbolic execution, a patented technology from CMU. Mayhem is an advanced fuzz testing solution that dramatically reduces manual testing efforts with autonomous defect detection and validation. Deliver safe, secure, reliable software with less time, cost, and effort. Mayhem’s unique advantage is in its ability to acquire intelligence of its targets over time. As Mayhem’s knowledge grows, it deepens its analysis and maximizes its code coverage. All reported vulnerabilities are exploitable, confirmed risks. Mayhem guides remediation efforts with in-depth system level information, such as backtraces, memory logs, and register state, expediting issue diagnosis and fixes. Mayhem utilizes target feedback to custom generate test cases on the fly -- meaning no manual test case generation required. Mayhem offers access to all of its test cases to make regression testing effortless and continuous.

JaCoCo is a free code coverage library for Java, which has been created by the EclEmma team based on the lessons learned from using and integrating existing libraries for many years. The master branch of JaCoCo is automatically built and published. Due to the test-driven development approach, every build is considered fully functional. See the change history for the latest features and bug fixes. SonarQube code quality metrics of the current JaCoCo implementation are available on SonarCloud.io. Integrate JaCoCo technology with your tools. Use JaCoCo tools out of the box. Improve the implementation and add new features. There are several open-source coverage technologies for Java available. While implementing the Eclipse plug-in EclEmma the observation was that none of them are really designed for integration. Most of them are specifically fit to a particular tool (Ant tasks, command line, IDE plug-in) and do not offer a documented API that allows embedding in different contexts.

OpenCppCoverage is an open-source code coverage tool for C++ under Windows. The main usage is for unit testing coverage, but you can also use it to know the executed lines in a program for debugging purposes. Support compiler with a program database file (.pdb). Just run your program with OpenCppCoverage, no need to recompile your application. Exclude a line based on a regular expression. Coverage aggregation, to run several code coverages and merge them into a single report. Requires Microsoft Visual Studio 2008 or higher for all editions including the Express edition. It should also work with the previous version of Visual Studio. You can run the tests with the Test Explorer window.

NCover Desktop is a Windows application that helps you collect code coverage statistics for .NET applications and services. After coverage is collected, Desktop displays charts and coverage metrics in a browser-based GUI that allows you to drill all the way down to your individual lines of source code. Desktop also allows you the option to install a Visual Studio extension called Bolt. Bolt offers built-in code coverage that displays unit test results, timings, branch visualization and source code highlighting right in the Visual Studio IDE. NCover Desktop is a major leap forward in the ease and flexibility of code coverage tools. Code coverage, gathered while testing your .NET code, shows the NCover user what code was exercised during the test and gives a specific measurement of unit test coverage. By tracking these statistics over time, you gain a concrete measurement of code quality during the development cycle.

Coverage.py is a tool for measuring code coverage of Python programs. It monitors your program, noting which parts of the code have been executed, then analyzes the source to identify code that could have been executed but was not. Coverage measurement is typically used to gauge the effectiveness of tests. It can show which parts of your code are being exercised by tests, and which are not. Use coverage run to run your test suite and gather data. However you normally run your test suite, and you can run your test runner under coverage. If your test runner command starts with “python”, just replace the initial “python” with “coverage run”. To limit coverage measurement to code in the current directory, and also find files that weren’t executed at all, add the source argument to your coverage command line. By default, it will measure line (statement) coverage. It can also measure branch coverage. It can tell you what tests ran which lines.

Balance your effort spent on writing applications and test code. Use the most sophisticated code coverage tool for Java and Groovy. OpenClover measures code coverage for Java and Groovy and collects over 20 code metrics. It not only shows you untested areas of your application but also combines coverage and metrics to find the riskiest code. The Test Optimization feature tracks which test cases are related to each class of your application code. Thanks to this OpenClover can run tests relevant to changes made in your application code, significantly reducing test execution time. Do testing getters and setters bring much value? Or machine-generated code? OpenClover outruns other tools in its flexibility to define the scope of coverage measurement. You can exclude packages, files, classes, methods, and even single statements. You can focus on testing important parts of your code. OpenClover not only records test results but also measures individual code coverage for every test.

We help you deliver code confidently by showing which parts of your code aren’t covered by your test suite. Free for open-source repositories. Pro accounts for private repositories. Instant sign-up through GitHub, Bitbucket, and Gitlab. Maintaining a well-tested codebase is mission-critical. Figuring out where your tests are lacking can be painful. You're already running your tests on a continuous integration server, so shouldn't it be doing the heavy lifting? Coveralls works with your CI server and sifts through your coverage data to find issues you didn't even know you had before they become a problem. If you're just running your code coverage locally, you won't be able to see changes and trends that occur during your entire development cycle. Coveralls lets you inspect every detail of your coverage with unlimited history. Coveralls takes the pain out of tracking your code coverage. Know where you stand with your untested code. Develop with confidence that your code is covered.

BMC Compuware Xpediter is a family of debuggers and interactive analysis tools for COBOL, Assembler, PL/I, and C programs that helps developers quickly understand applications, make changes, and fix problems in a secure environment—even if they’re unfamiliar with the source code. Xpediter enables developers to get into an interactive test session with minimal effort and quickly move applications into production with greater confidence. See line-by-line code execution and control all aspects of program execution and data. Use Code Coverage to see proof of execution and view metrics on multi-platform applications. Access Abend-AID diagnostic capabilities from within a debugging session. See a graphical view of source code through an integration with Topaz for Program Analysis. Leverage Topaz for Total Test for building a comprehensive portfolio of automated virtualized test cases. Intercept and debug mainframe transactions initiated remotely.

Actionable test coverage for Ruby and GitHub. Checks and insights to help your team ship healthy code while saving time on PR reviews. Stop focusing on getting to 100% test coverage. Reduce pull request defects by telling when the changed code is untested before it's deployed to production. The CI server runs tests and uploads coverage data to UndercoverCI. That's the only required post-install setup step! We scan the PR diff and verify local test coverage for each updated class, method, and block because an absolute percentage check is not enough. Reveal untested methods and blocks, find unused code paths, and improve your test suite. Install UndercoverCI's hosted GitHub App or explore the Ruby gems family. Fully-featured GitHub App code review integration with quick setup for your organization. The UndercoverCI project and related Ruby gems are entirely open-source and free to use locally and in your CI/CD workflows.

Develop healthier code. Improve your code review workflow and quality. Codecov provides highly integrated tools to group, merge, archive, and compare coverage reports. Free for open source. Plans starting at $10/user per month. Ruby, Python, C++, Javascript, and more. Plug and play into any CI product and workflow. No setup required. Automatic report merging for all CI and languages into a single report. Get custom statuses on any group of coverage metrics. Review coverage reports by project, folder and type test (unit tests vs integration tests). Detailed report commented directly into your pull request. Codecov is SOC 2 Type II certified, which means a third-party audits and attests to our practices to secure our systems and your data.

For many years Atlassian Clover has provided Java and Groovy developers a reliable source for code coverage analysis. This dependability has allowed us to focus our development efforts on delivering new features and improvements to our core offerings, including Jira Software, Bitbucket, and others. All of this has lead to our decision to open source Clover, what we believe is the best way to give Clover the focus and attention it deserves. Developers are ready and eager to contribute to Clover as they have with our other open-source projects including the IDE connectors and dozens of libraries. Although Clover is already a powerful code coverage tool we’re excited to see what the community will do to make it thrive.

Testwell CTC++ is a powerful instrumentation-based code coverage and dynamic analysis tool for C and C++ code. With certain add-on components CTC++ can be used also on C#, Java and Objective-C code. Further, again with certain add-on components, CTC++ can be used to analyse code basically at any embedded target machines, also in very small ones (limited memory, no operating system). CTC++ provides Line Coverage, Statement Coverage, Function Coverage, Decision Coverage, Multicondition Coverage, Modified Condition/Decision Coverage (MC/DC), Condition Coverage. As a dynamic analysis tool, CTC++ shows the execution counters (how many times executed) in the code, i.e. more than a plain executed/not executed information. You can also use CTC++ to measure function execution costs (normally time) and to enable function entry/exit tracing at test time. CTC++ is easy to use.

PHPUnit requires the dom and json extensions, which are normally enabled by default. PHPUnit also requires the pcre, reflection, and spl extensions. These standard extensions are enabled by default and cannot be disabled without patching PHP’s build system and/or C sources. The code coverage report feature requires the Xdebug (2.7.0 or later) and tokenizer extensions. Generating XML reports requires the xmlwriter extension. Unit Tests are primarily written as a good practice to help developers identify and fix bugs, to refactor code and to serve as documentation for a unit of software under test. To achieve these benefits, unit tests ideally should cover all the possible paths in a program. One unit test usually covers one specific path in one function or method. However a test method is not necessarily an encapsulated, independent entity. Often there are implicit dependencies between test methods, hidden in the implementation scenario of a test.

Coco® is a multi-language code coverage tool. Automatic source code instrumentation is used to measure test coverage of statements, branches and conditions. Executing a test suite against an instrumented application produces data that can later be analyzed. This analysis can be used to understand how much of the source code has been hit by tests, which additional tests need to be written, how the test coverage changed over time and more. Identify redundant tests, untested or dead code. Identify the impact of a patch on the code and code coverage & your testing. Coco supports statement coverage, branch coverage, MC/DC and other levels. Linux, Windows, RTOS and others. Using GCC, Visual Studio, embedded compilers and more. Choice of different report formats (text, HTML, XML, JUnit, Cobertura). Coco can also be integrated with various build, test and CI frameworks like JUnit, Jenkins and SonarQube.

Gcov is an open-source code-coverage tool.

Meet Agile development cycles while maintaining high-quality code. Use Jtest’s comprehensive set of Java testing tools to ensure defect-free coding through every stage of software development in the Java environment. Streamline Compliance With Security Standards. Ensure your Java code complies with industry security standards. Have compliance verification documentation automatically generated. Release Quality Software, Faster. Integrate Java testing tools to find defects faster and earlier. Save time and money by mitigating complicated and expensive problems down the line. Increase Your Return From Unit Testing. Achieve code coverage targets by creating a maintainable and optimized suite of JUnit tests. Get faster feedback from CI and within your IDE using smart test execution. Parasoft Jtest integrates tightly into your development ecosystem and CI/CD pipeline for real-time, intelligent feedback on your testing and compliance progress.

MarathonITE makes it easy to create GUI tests. You can quickly automate your functional tests and regression tests. MarathonITE has an open and flexible architecture based on open source projects like Marathon, Ruby and Selenium. MarathonITE makes creating, maintaining and executing automated test scripts easy. MarathonITE provides excellent ROI for your test teams. Some of the powerful features of MarathonITE include: Intelligent recording and replay, flexible and configurable object map, selenium/WebDriver bindings for Java™ applications. MarathonITE is a professional tool for creating and executing automated tests through GUI for applications developed using Java/Swing™, Java/Fx™ and Web technologies. MarathonITE provides Selenium/WebDriver bindings for Java application runtime to provide flexible and powerful API to interact with the applications and create GUI tests. Test automation is a combination of two activities – testing and software development.

Automating the creation and deployment of component test harnesses, test stubs and test drivers is a cinch thanks to OneTest Embedded. With a single click from any development environment, one can profile memory and performance, analyze code coverage and visualize program execution behavior. Additionally, OneTest Embedded helps be more proactive in debugging, while identifying and assisting in fixing code before it breaks. Allows for a virtual cycle of test generation, while executing, reviewing and testing improvement to rapidly achieve full test coverage. One click is all it takes to build, execute on the target, and generate reports. Helps preempt performance issues and program crashes. Additionally, can be adapted to work with custom memory management methods used in embedded software. Provides visibility on thread execution and switching to develop a deep understanding of the behavior of the system under test.

BullseyeCoverage is an advanced C++ code coverage tool used to improve the quality of software in vital systems such as enterprise applications, industrial control, medical, automotive, communications, aerospace and defense. The function coverage metric gives you a quick overview of testing completeness and indicates areas with no coverage at all. Use this metric to broadly raise coverage across all areas of your project. Condition/decision coverage provides detail at the control structure level. Use this metric to attain high coverage in specific areas, for example during unit testing. C/D coverage provides better detail than statement coverage or branch coverage, and provides much better productivity than more complex coverage metrics.

Maximize your throughput and only release clean code SonarCloud automatically analyzes branches and decorates pull requests. Catch tricky bugs to prevent undefined behavior from impacting end-users. Fix vulnerabilities that compromise your app, and learn AppSec along the way with Security Hotspots. With just a few clicks you're up and running right where your code lives. Immediate access to the latest features and enhancements. Project dashboards keep teams and stakeholders informed on code quality and releasability. Display project badges and show your communities you're all about awesome. Code Quality and Code Security is a concern for your entire stack, from front-end to back-end. That’s why we cover 24 languages including Python, Java, C++, and many others. Transparency makes sense and that's why the trend is growing. Come join the fun, it's entirely free for open-source projects!

JavaScript test coverage made simple. Istanbul instruments your ES5 and ES2015+ JavaScript code with line counters, so that you can track how well your unit-tests exercise your codebase. The nyc command-line-client for Istanbul works well with most JavaScript testing frameworks, tap, mocha, AVA, etc. First-class support of ES6/ES2015+ using babel-plugin-Istanbul. Support for the most popular JavaScript testing frameworks. Support for instrumenting subprocesses, using the nyc command-line interface. Adding coverage to your mocha tests could not be easier. Now, simply place the command nyc in front of your existing test command. nyc's instrument command can be used to instrument source files outside of the context of your unit tests. nyc is able to show you all Node processes that are spawned when running a test script under it. By default, nyc uses Istanbul's text reporter. However, you may specify an alternative reporter.

NCrunch tracks your code coverage in real-time, showing this in markers next to your code. This makes it easy to track where your coverage is heavy or light. NCrunch was designed with big complex projects in mind. We've spent the last 12 years optimising and scaling the NCrunch system to meet the needs of real-world systems consisting of millions of lines of code and many thousands of tests. NCrunch tracks all sorts of test related data, and it uses it to give you the most important feedback as fast as possible. Tests that you have recently impacted with your code changes are prioritised for execution using sophisticated and high performance IL-based change mapping. NCrunch can offload build and test work to other computers for processing. Farm tasks out to connected machines or scale into the cloud. Processing resources can be shared between developers allowing teams to pool their testing resources.

Our platform uses various security techniques, including coverage-guided and feedback-based fuzz testing, to automatically generate millions of test cases that trigger hard-to-find bugs deep within your application. This white-box approach protects against edge cases and speeds up development. Advanced fuzzing engines generate inputs that maximize code coverage. Powerful bug detectors check for errors during code execution. Uncover true vulnerabilities only. Get the input and stack trace as proof, so you can reliably reproduce errors every time. AI white-box testing uses data from all previous test runs to continuously learn the inner-workings of your application, triggering security-critical bugs with increasingly high precision.

jscoverage tool, both node.js and JavaScript support. Enhance the coverage range. Use mocha to load the jscoverage module, then it works. jscoverage will append coverage info when you select list or spec or tap reporter in mocha. You can use covout to specify the reporter, like HTML, and detail. The detail reporter will print the uncovered code in the console directly. Mocha runs test case with jscoverage module. jscoverage will ignore files while listing in covignore file. jscoverage will output a report in HTML format. jscoverage will inject a group of functions into your module exports. default jscoverage will search covignore in the project root. jscoverage will copy exclude files from the source directory to the destination directory.

This module provides code coverage metrics for Perl. Code coverage metrics describe how thoroughly tests exercise code. By using Devel::Cover you can discover areas of code not exercised by your tests and determine which tests to create to increase coverage. Code coverage can be considered an indirect measure of quality. Devel::Cover is now quite stable and provides many of the features to be expected in a useful coverage tool. Statement, branch, condition, subroutine, and pod coverage information is reported. Statement and subroutine coverage data should be accurate. Branch and condition coverage data should be mostly accurate too, although not always what one might initially expect. Pod coverage comes from Pod::Coverage. If Pod::Coverage::CountParents is available it will be used instead.

The LDRA tool suite is LDRA’s flagship platform that delivers open and extensible solutions for building quality into software from requirements through to deployment. The tool suite provides a continuum of capabilities including requirements traceability, test management, coding standards compliance, code quality review, code coverage analysis, data-flow and control-flow analysis, unit/integration/target testing, and certification and regulatory support. The core components of the tool suite are available in several configurations that align with common software development needs. A comprehensive set of add-on capabilities are available to tailor the solution for any project. LDRA Testbed together with TBvision provide the foundational static and dynamic analysis engine, and a visualization engine to easily understand and navigate standards compliance, quality metrics, and code coverage analyses.

Codacy is an automated code review tool that helps identify issues through static code analysis, allowing engineering teams to save time in code reviews and tackle technical debt. Codacy integrates seamlessly into existing workflows on your Git provider, and also with Slack, JIRA, or using Webhooks. Users receive notifications on security issues, code coverage, code duplication, and code complexity in every commit and pull request along with advanced code metrics on the health of a project and team performance. The Codacy CLI enables running Codacy code analysis locally, so teams can see Codacy results without having to check their Git provider or the Codacy app. Codacy supports more than 30 coding languages and is available in free open-source, and enterprise versions (cloud and self-hosted). For more see https://www.codacy.com/

A seamless JavaScript code coverage library. Blanket.js is a code coverage tool for JavaScript that aims to be easy to install, easy to use, and easy to understand. Blanket.js can be run seamlessly or can be customized for your needs. JavaScript code coverage compliments your existing JavaScript tests by adding code coverage statistics (which lines of your source code are covered by your tests). Parsing the code using Esprima and node-falafel, and instrumenting the file by adding code tracking lines. Connecting to hooks in the test runner to output the coverage details after the tests have been completed. A Grunt plugin has been created to allow you to use Blanket like a "traditional" code coverage tool (creating instrumented copies of physical files, as opposed to live-instrumenting). Runs the QUnit-based Blanket report headlessly using PhantomJS. Results are displayed on the console, and the task will cause Grunt to fail if any of your configured coverage thresholds are not met.

An open-source Ruby library for automating tests. Watir interacts with a browser the same way people do, clicking links, filling out forms, and validating text. It requires Ruby 2.6+ and Selenium 4.0 which was just released last week. It’s been a long road since Watir 6.0 was released almost 5 years ago. That version was a substantial reenvision of Watir’s default approach to automation, especially as it relates to Selenium. It was designed to combine the original philosophy of Watir with the power of Selenium. Watir 7 is mostly just a much more stable and performant implementation of that vision. When developing a gem intended to be used with Watir, you can run your code with WatirSpec to make sure that requiring your code does not break something else in Watir. Watir code is tested on Linux with the latest versions of supported browsers and all active Ruby versions. Watir code is run through Coveralls to encourage PRs to ensure all paths in their code have tests associated with them.

Xdebug is an extension for PHP, and provides a range of features to improve the PHP development experience. A way to step through your code in your IDE or editor while the script is executing. An improved var_dump() function, stack traces for notices, warnings, errors, and exceptions to highlight the code path to the error. Writes every function call, with arguments and invocation location to disk. Optionally also includes every variable assignment and return value for each function. Allows you, with the help of visualization tools, to analyze the performance of your PHP application and find bottlenecks. Shows which parts of your code base are executed when running unit tests with PHPUnit. Installing Xdebug with a package manager is often the fastest way. You can substitute the PHP version with the one that matches the PHP version that you are running. You can install Xdebug through PECL on Linux & macOS with Homebrew.

Cobertura is a free Java tool that calculates the percentage of code accessed by tests. It can be used to identify which parts of your Java program are lacking test coverage. It is based on jcoverage. Cobertura is free software. Most of it is licensed under the GNU GPL, and you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. Please review the file LICENSE.txt included in this distribution for further details.

Try your first CodeRush feature right now and see instantly just how powerful it is. Refactoring for C#, Visual Basic, and XAML, with the fastest test .NET runner available, next generation debugging, and the most efficient coding experience on the planet. Quickly find symbols and files in your solution and easily navigate to code constructions related to the current context. CodeRush includes the Quick Navigation and Quick File Navigation features, which make it fast and easy to find symbols and open files. Using the Analyze Code Coverage feature, you can discover what parts of your solution are covered by unit tests, and find the at-risk parts of your application. The Code Coverage window shows percentage of statements covered by unit tests for each namespace, type, and member in your solution.

Codase hosts huge amount of open source codes providing a much better coverage, as it covers codes usually hidden inside compressed files and source control repositories, where general search engines fail to find and index. In addition, Codase only indexes and searches high quality codes with every line of code literally validated and compiled by intelligent and powerful source code analysis engine. Codase is a privately held company based in silicon valley, founded by Dr. Huihong Luo and other veterans. We are a group of innovative and passionate professionals with diverse technologies, business background and proven track of records. We are committed to make Codase the world's best search engine for source codes in terms of features, quality, performance and code coverage. If you are a developer, you may find Codase useful, since improving your coding productivity is our goal.

Save time and money by finding and fixing defects earlier. Reduce the effort and cost of delivering high-quality software by preventing more complicated and expensive problems down the line. Ensure your C# or VB.NET code complies with a wide range of safety and security industry standards, including the requirement traceability mandated and the documentation required to verify compliance. Parasoft's C# testing tool, Parasoft dotTEST, automates a broad range of software quality practices for your C# and VB.NET development activities. Deep code analysis uncovers reliability and security issues. Code coverage, requirements traceability, and automated compliance reporting helps achieve compliance for security standards and safety-critical industries.

TOP Testing Suite from R Systems is an easy to use, automated test solution for end-to-end testing, evaluation, and validation of telecom services. With TOP Testing Suite, you can rapidly automate telecom protocol or software test plans, reduce regression testing time from days to minutes and enable continuous testing in line with Agile and DevOps practices. R Systems’ TOP Testing Suite uses an intuitive web-based graphical user interface (GUI) to enable you to efficiently define and manage a broad range of test plans, aggregate the results, and view the reports. Our comprehensive suite of testing tools is a modular, multi-protocol solution based on the JMeter platform, with open-source elements and custom developed R Systems plug-ins.

Cerberus Testing is a low-code software testing automation enabling continuous testing at scale. Using the solution you can remove years of implementing an internal testing framework. The product enables you to quickly iterate through your testing lifecycle, from test repository, execution, reporting and analytics. The solution allows the collaboration of the teams from the use-cases definition to the test case execution on the variety of browsers, devices, apps and APIs. You can leverage your own or external robots infrastructure to execute your test at scale, enabling you to focus on your business value. It supports various integrations for speed of implementation such as Jenkins, Bitbucket, Slack, Kafka. It is available and maintained in open-source by various digital and retail players such as La Redoute, Decathlon, Adeo, and Norauto.

Appvance IQ (AIQ) delivers transformational productivity gains and lower costs in both test creation and execution. For test creation, it offers both AI-driven (fully machine-generated tests) and also 3rd-generation, codeless scripting. It then executes those scripts through data-driven functional, performance, app-pen and API testing — for both web and mobile apps. AIQ’s self-healing technology gives you complete code coverage with just 10% the effort of traditional testing systems. Most importantly, AIQ finds important bugs autonomously, with little effort. No coding, scripting, logs or recording required. AIQ is easy to integrate with your current DevOps tools and processes. Appvance IQ was developed by a pioneering team who envisioned a better way to test. Their innovative vision has been made possible by applying differentiated, patented AI methods to test creation while leveraging today’s high-availability compute resources for massive levels of parallel execution.

LuaCov is a simple coverage analyzer for Lua scripts. When a Lua script is run with the luacov module loaded, it generates a stats file with the number of executions of each line of the script and its loaded modules. The luacov command-line script then processes this file generating a report file which allows one to visualize which code paths were not traversed, which is useful for verifying the effectiveness of a test suite. LuaCov includes several configuration options, which have their defaults stored in src/luacov/defaults.lua. These are the global defaults. To use project specific configuration, create a Lua script setting options as globals or returning a table with some options and store it as .luacov in the project directory from where luacov is being run. For example, this config informs LuaCov that only foo module and its submodules should be covered and that they are located inside src directory.

DeepSource helps you automatically find and fix issues in your code during code reviews, such as bug risks, anti-patterns, performance issues, and security flaws. It takes less than 5 minutes to set up with your Bitbucket, GitHub, or GitLab account. It works for Python, Go, Ruby, and JavaScript. DeepSource covers all major programming languages, Infrastructure-as-Code, secrets detection, code coverage, and more. You won't need any other tool to protect your code. Start building with the most sophisticated static analysis platform for your workflow and prevent bugs before they end up in production. Largest collection of static analysis rules in the industry. Your team's central hub to track and take action on code health. Put code formatting on autopilot. Never let your CI break on style violations. Automatically generates and applies fixes for issues in a couple of clicks.

TestUnity is a provider of software testing services. We help companies release their software with confidence and assurance. We test your applications from various perspectives to assure the best feasible coverage. Be it any type of testing, or any type of interface to be tested, or be it a traditional package to be tested, we have the correct solution custom build for you. Ensures that the modifications did not introduce new errors into the existing codes by employing an efficient regression testing approach. Add stability to your core functions and produce more by employing our API and microservices testing. Accelerate testing on your project with scriptless, AI-based, no-code approach features of Tricentis TOSCA. Get access to the best possible type of test data for testing in production by leveraging our services. Boost your operational efficiency by eliminating human intervention and automating repetitive business processes with a software bot.

It works with .NET Framework on Windows and .NET Core on all supported platforms. Coverlet supports coverage for deterministic builds. The solution at the moment is not optimal and need a workaround. If you want to visualize coverlet output inside Visual Studio while you code, you can use the following addins depending on your platform. Coverlet also integrates with the build system to run code coverage after tests. Enabling code coverage is as simple as setting the CollectCoverage property to true. The coverlet tool is invoked by specifying the path to the assembly that contains the unit tests. You also need to specify the test runner and the arguments to pass to the test runner using the --target and --targetargs options respectively. The invocation of the test runner with the supplied arguments must not involve a recompilation of the unit test assembly or no coverage result will be generated.

grcov collects and aggregates code coverage information for multiple source files. grcov processes .profraw and .gcda files which can be generated from llvm/clang or gcc. grcov also processes lcov files (for JS coverage) and JaCoCo files (for Java coverage). Linux, macOS and Windows are supported.

Deep Cover aims to be the best coverage tool for Ruby code. More accurate line coverage, and branch coverage. It can be used as a drop-in replacement for the built-in Coverage library. It reports a more accurate picture of your code usage. In particular, a line is considered covered if and only if it is entirely executed. Optionally, branch coverage will detect if some branches are never taken. MRI considers every method defined, including methods defined on objects or via define_method, class_eval, etc. For Istanbul output, DeepCover has a different approach and covers all def and all blocks. DeepCover doesn't consider loops to be branches, but it's easy to support them if needed. Even after DeepCover is required and configured, only a very minimal amount of code is actually loaded and coverage is not started. To make it easier to transition for projects already using the builtin Coverage library deep-cover can inject itself into those tools.

Diffblue Cover analyzes your existing Java program and writes unit regression tests that reflect the current behavior of the code. The CLI tool works 100% autonomously, configuring itself from your Maven or Gradle environment. By bringing automation to the test-writing process, the CLI tool provides a speed boost for organizations that are working towards achieving DevOps goals like CI/CD. Since it fits into a CI pipeline, the CLI tool protects the whole codebase from regressions by shifting testing left. Diffblue Cover's unit regression tests run fast and verify new code changes immediately, helping users detect undesirable changes in the code’s behavior as early as possible, when they're the quickest, easiest, and cheapest to fix. And tests are automatically maintained, saving teams even more time.

dotCover is a .NET unit testing and code coverage tool that works right in Visual Studio and in JetBrains Rider, helps you know to what extent your code is covered with unit tests, provides great ways to visualize code coverage, and is Continuous Integration ready. dotCover calculates and reports statement-level code coverage in applications targeting .NET Framework, .NET Core, Mono for Unity, etc. dotCover is a plug-in to Visual Studio and JetBrains Rider, giving you the advantage of analyzing and visualizing code coverage without leaving the code editor. This includes running unit tests and analyzing coverage results right in the IDEs, as well as support for different color themes, new icons and menus. dotCover comes bundled with a unit test runner that it shares with another JetBrains tool for .NET developers, ReSharper. dotCover supports continuous testing, a modern unit testing workflow whereby dotCover figures out on-the-fly which unit tests are affected by your code changes.

Velocity provides in-depth, contextual analytics that equip engineering leaders to support stuck team members, address team roadblocks, and streamline engineering processes. Actionable metrics for engineering leaders. Velocity turns data from commits and pull requests into the insights you need to make lasting improvements to your team’s productivity. Quality: Automated code review for test coverage, maintainability and more so that you can save time and merge with confidence. Receive automated code review comments on your pull requests. Our 10-point technical debt assessment provides real-time feedback, so you can save time and focus on what matters in your code review discussions. Get test coverage right, every time. See coverage line by line within diffs. Never merge code without sufficient tests again. At a glance, identify frequently changed files that have inadequate coverage and maintainability issues. Track your progress against measurable goals, day-by-day.