Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
Tarpaulin serves as a tool for reporting code coverage specifically designed for the cargo build system, drawing its name from a durable cloth typically employed to protect cargo on ships. At present, it effectively provides line coverage, though it may still exhibit some minor inaccuracies in its output. Significant efforts have been made to enhance its compatibility across various projects, yet unique combinations of packages and build configurations can lead to potential issues, so users are encouraged to report any discrepancies they encounter. Additionally, the roadmap offers insights into upcoming features and improvements. On Linux systems, Tarpaulin utilizes Ptrace as its default tracing backend, which is limited to x86 and x64 architecture; however, this can be switched to llvm coverage instrumentation by specifying the engine as llvm, which is the default method on Mac and Windows platforms. Furthermore, Tarpaulin can be deployed in a Docker environment, making it a practical solution for users who prefer not to run Linux directly but still wish to utilize its capabilities locally. This versatility makes Tarpaulin a valuable tool for developers looking to improve their code quality through effective coverage analysis.
Description
This plugin generates detailed coverage reports that offer more functionality compared to merely using coverage run. It includes support for subprocess execution, allowing you to fork or run tasks in a subprocess while still obtaining coverage seamlessly. Additionally, it integrates with xdist, enabling the use of all pytest-xdist features without sacrificing coverage reporting. The plugin maintains consistent behavior with pytest, ensuring that all functionalities provided by the coverage package are accessible either via pytest-cov's command line options or through coverage's configuration file. In rare cases, a stray .pth file might remain in the site packages after execution. To guarantee that each test run starts with clean data, the data file is cleared at the start of testing. If you wish to merge coverage results from multiple test runs, you can utilize the --cov-append option to add this data to that of previous runs. Furthermore, the data file is retained at the conclusion of testing, allowing users to leverage standard coverage tools for further analysis of the results. This additional functionality enhances the overall user experience by providing better management of coverage data throughout the testing process.
API Access
Has API
API Access
Has API
Integrations
Codecov
Python
CodeShip
Coverage.py
Docker
GitHub
HTML
Jenkins
Microsoft Azure
Rust
Integrations
Codecov
Python
CodeShip
Coverage.py
Docker
GitHub
HTML
Jenkins
Microsoft Azure
Rust
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
Tarpaulin
Website
crates.io/crates/cargo-tarpaulin
Vendor Details
Company Name
Python
Country
United States
Website
pypi.org/project/pytest-cov/