Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
Coverage.py serves as a powerful utility for assessing the code coverage of Python applications. It tracks the execution of your program, recording which segments of the code have been activated, and subsequently reviews the source to pinpoint areas that could have been executed yet remained inactive. This measurement of coverage is primarily utilized to evaluate the efficacy of testing efforts. It provides insights into which portions of your code are being tested and which are left untested. To collect data, you can use the command `coverage run` to execute your test suite. Regardless of how you typically run your tests, you can incorporate coverage by executing your test runner with the coverage tool. If the command for your test runner begins with "python," simply substitute the initial "python" with "coverage run." To restrict coverage evaluation to only the code within the current directory and to identify files that have not been executed at all, include the source parameter in your coverage command. By default, Coverage.py measures line coverage, but it is also capable of assessing branch coverage. Additionally, it provides information on which specific tests executed particular lines of code, enhancing your understanding of test effectiveness. This comprehensive approach to coverage analysis can significantly improve the quality and reliability of your codebase.
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
Yes
API Access
Has API
No
Integrations
Codecov
Yes
C
Yes
Django
Yes
HTML
Yes
JSON
Yes
Lua
No
Mako
Yes
Python
Yes
SQLite
Yes
Tidelift
Yes
Integrations
Codecov
Yes
C
No
Django
No
HTML
No
JSON
No
Lua
Yes
Mako
No
Python
No
SQLite
No
Tidelift
No
Pricing Details
Free
Free Trial
No
Free Version
Yes
Pricing Details
Free
Free Trial
No
Free Version
Yes
Deployment
Web-Based
No
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
Yes
Mac
Yes
Linux
Yes
Chromebook
No
Deployment
Web-Based
No
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
Yes
Mac
Yes
Linux
Yes
Chromebook
No
Customer Support
Business Hours
No
Live Rep (24/7)
No
Online Support
Yes
Customer Support
Business Hours
No
Live Rep (24/7)
No
Online Support
Yes
Types of Training
Training Docs
Yes
Webinars
No
Live Training (Online)
No
In Person
No
Types of Training
Training Docs
Yes
Webinars
No
Live Training (Online)
No
In Person
No
Vendor Details
Company Name
Coverage.py
Country
United States
Website
coverage.readthedocs.io/en/7.0.0/
Vendor Details
Company Name
LuaCov
Website
github.com/lunarmodules/luacov