Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
Deep Cover strives to be the premier tool for Ruby code coverage, delivering enhanced accuracy for both line and branch coverage metrics. It serves as a seamless alternative to the standard Coverage library, providing a clearer picture of code execution. A line is deemed covered only when it has been fully executed, and the optional branch coverage feature identifies any branches that remain untraveled. The MRI implementation considers all methods available, including those created through constructs like define_method and class_eval. Unlike Istanbul's method, DeepCover encompasses all defined methods and blocks when reporting coverage. Although loops are not classified as branches within DeepCover, accommodating them can be easily arranged if necessary. Even once DeepCover is activated and set up, it requires only a minimal amount of code loading, with coverage tracking starting later in the process. To facilitate an easy migration for projects that have previously relied on the built-in Coverage library, DeepCover can integrate itself into existing setups, ensuring a smooth transition for developers seeking improved coverage analysis. This capability makes DeepCover not only versatile but also user-friendly for teams looking to enhance their testing frameworks.
Description
LuaCov serves as a straightforward coverage analysis tool for Lua scripts. By running a Lua script with the luacov module activated, it produces a statistics file detailing the execution count for each line within the script and its associated modules. This statistics file is then processed by the luacov command-line tool to create a report, enabling users to identify untraversed code paths, which is essential for assessing the thoroughness of a test suite. The tool offers a variety of configuration options, with the default settings found in src/luacov/defaults.lua, representing the global defaults. For those needing project-specific configurations, they can create a Lua script that either sets options as global variables or returns a table containing specific options, saving this file as .luacov in the project directory where luacov is executed. For instance, such a configuration could specify that only the foo module and its associated submodules should be included in the coverage analysis, indicating that these are located within the src directory. This flexibility allows developers to fine-tune their coverage analysis to better align with their project needs.
API Access
Has API
API Access
Has API
Pricing Details
Free
Free Trial
Free Version
Pricing Details
Free
Free Trial
Free Version
Deployment
Web-Based
On-Premises
iPhone App
iPad App
Android App
Windows
Mac
Linux
Chromebook
Deployment
Web-Based
On-Premises
iPhone App
iPad App
Android App
Windows
Mac
Linux
Chromebook
Customer Support
Business Hours
Live Rep (24/7)
Online Support
Customer Support
Business Hours
Live Rep (24/7)
Online Support
Types of Training
Training Docs
Webinars
Live Training (Online)
In Person
Types of Training
Training Docs
Webinars
Live Training (Online)
In Person
Vendor Details
Company Name
DeepCover
Country
United States
Website
github.com/deep-cover/deep-cover
Vendor Details
Company Name
LuaCov
Website
github.com/lunarmodules/luacov