We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While experimenting with tarpaulin I ran it on https://github.com/dtolnay/unicode-ident using the following command:
cargo tarpaulin --workspace --out html --out json
It created the two output files as expected and printed the following to the screen:
INFO cargo_tarpaulin::report: Coverage Results: || Tested/Total Lines: || diagram/src/main.rs: 0/15 +0.00% || generate/src/main.rs: 0/84 +0.00% || generate/src/output.rs: 0/6 +0.00% || generate/src/parse.rs: 0/35 +0.00% || generate/src/write.rs: 0/52 +0.00% || src/lib.rs: 12/13 +0.00% || src/tables.rs: 0/20 +0.00% || 5.33% coverage, 12/225 lines covered, +0.00% change in coverage
I looked in the resulting json file, but could not see this summary.
I wonder if there is a way to get this summary in a machine-readable format (e.g. as json)?
If there is no such way yet, then IMHO it would be a good idea to either add it to the json file.
The text was updated successfully, but these errors were encountered:
I've added this in via #1522 and it will be available in the next release!
Sorry, something went wrong.
xd009642
Successfully merging a pull request may close this issue.
While experimenting with tarpaulin I ran it on https://github.com/dtolnay/unicode-ident using the following command:
It created the two output files as expected and printed the following to the screen:
I looked in the resulting json file, but could not see this summary.
I wonder if there is a way to get this summary in a machine-readable format (e.g. as json)?
If there is no such way yet, then IMHO it would be a good idea to either add it to the json file.
The text was updated successfully, but these errors were encountered: