Skip to content
New issue

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

Programmatic support for doctests? #27

Open
epage opened this issue Mar 8, 2019 · 4 comments
Open

Programmatic support for doctests? #27

epage opened this issue Mar 8, 2019 · 4 comments
Labels
enhancement Improve the expected question Uncertainty is involved

Comments

@epage
Copy link
Contributor

epage commented Mar 8, 2019

Doctests are tricky because they are creating code, and binaries, on the fly.

This is important for

  • Proper unit test reporting in cargo-suity
  • Code coverage reporting
  • We could integrate skeptic (testing readmes) with a shipped binary, not slowing people down
@epage epage added enhancement Improve the expected question Uncertainty is involved labels Mar 8, 2019
@epage
Copy link
Contributor Author

epage commented Mar 8, 2019

As suspected, cargo test delegates to rustdoc for doctests, populating all the hard-to-discover flags :(

https://github.com/rust-lang/cargo/blob/master/src/cargo/ops/cargo_test.rs#L129

@epage
Copy link
Contributor Author

epage commented Mar 8, 2019

@epage
Copy link
Contributor Author

epage commented Mar 8, 2019

brson's work on skeptic might be reused to cover both skeptic and doctests

See budziq/rust-skeptic#18 (comment)

@epage
Copy link
Contributor Author

epage commented Jun 3, 2019

Looks like taurplin has taken a crack at solving the doctest problem

See xd009642/tarpaulin#13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improve the expected question Uncertainty is involved
Projects
None yet
Development

No branches or pull requests

1 participant