This repository was archived by the owner on Dec 29, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 19
Feature proposal: Run examples as top level concept, with compilation profile #96
Labels
Comments
In light of #86, do you see value in keeping this issue open? |
Yeap -- even after implementing #86, there's no quick way to run an example and insert the compilation profile. |
Oh, I missed the part about running examples. |
I, too, would like to be able to quickly use an example for a command to test. I would like to suggest an |
4 tasks
Fixed by #108 |
I'm publishing 0.6.1 right now. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Hiya, I really like
assert_cli
, thanks for making such a useful crate!Since I'm a fan of "automatically test everything, so I know when I break things", I have automated tests for my examples, and control them through arguments or
stdin
. For example:Now, because
cargo run --example example_name
always runs the example in thedebug
profile, to make sure I don't double compile when I'm testing myrelease
profile build, I can do something like this:Since I would be replicating this functionality across a number of crates, I was wondering whether you'd like this to go in
assert_cli
(is it in line with what this crate is intended to cover), otherwise I can make an intermediate crate.Edit: just noticed the conditional compilation for the profile is also mentioned in #86.
The text was updated successfully, but these errors were encountered: