Audience
Developers searching for an advanced Code Coverage solution
About cloverage
Cloverage uses clojure.test by default. If you prefer use midje, pass the --runner :midje flag. (In older versions of Cloverage, you had to wrap your midje tests in clojure.test's deftest. This is no longer necessary.) For using eftest, pass the --runner :eftest flag. Optionally you could configure a runner passing :runner-opts with a map in project settings. Other test libraries may ship with their own support for Cloverage external to this library; see their documentation for details.
Other Popular Alternatives & Related Software
Zuar Runner
Utilizing the data that's spread across your organization shouldn't be so difficult! With Zuar Runner you can automate the flow of data from hundreds of potential sources into a single destination. Collect, transform, model, warehouse, report, monitor and distribute: it's all managed by Zuar Runner.
Pull data from Amazon/AWS products, Google products, Microsoft products, Avionte, Backblaze, BioTrackTHC, Box, Centro, Citrix, Coupa, DigitalOcean, Dropbox, CSV, Eventbrite, Facebook Ads, FTP, Firebase, Fullstory, GitHub, Hadoop, Hubic, Hubspot, IMAP, Jenzabar, Jira, JSON, Koofr, LeafLogix, Mailchimp, MariaDB, Marketo, MEGA, Metrc, OneDrive, MongoDB, MySQL, Netsuite, OpenDrive, Oracle, Paycom, pCloud, Pipedrive, PostgreSQL, put.io, Quickbooks, RingCentral, Salesforce, Seafile, Shopify, Skybox, Snowflake, Sugar CRM, SugarSync, Tableau, Tamarac, Tardigrade, Treez, Wurk, XML Tables, Yandex Disk, Zendesk, Zoho, and more!
Learn more
blanket.js
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.
Learn more
Coverage.py
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.
Learn more
Coverlet
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.
Learn more
Pricing
Starting Price:
Free
Free Version:
Free Version available.
Integrations
Company Information
cloverage
github.com/cloverage/cloverage
Videos and Screen Captures
Other Useful Business Software
Custom VMs From 1 to 96 vCPUs With 99.95% Uptime
Live migration and automatic failover keep workloads online through maintenance. One free e2-micro VM every month.
Product Details
Platforms Supported
Windows
Mac
Linux
Training
Documentation
Support
Online
