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
Use --exact flag when generating run configuration for a single test #943
Comments
@matklad this issue still up for grabs, and if so, are you able to point me in the right direction? |
The issue is still actual and up for grab. If you try to run a single test named mod test {
#[test]
fn test(){
println!("test");
}
#[test]
fn test321(){
println!("test321");
}
} both test will be run instead. I think it's located here. |
@vlad20012 do you think you can assign this job to me - happy to take it on! Few questions though. What is the development workflow for this? Or is it pretty standard dev workflow for Intellij plugins? |
I'm sorry, I could not understand the question. Could you please clarify it? However, perhaps you can find the answer in the CONTRIBUTING.md :) |
@maraisr And yes, you can grab the issue anytime :) |
Doesn't look like Using the above code block and running: $ cargo test ::test321
Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
Running target/debug/deps/rust-9d6b4d08e5c8e0ac
running 1 test
test test::test321 ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 1 filtered out Only executes the one test anyway? |
@maraisr try to run test named |
@vlad20012 I see! $ cargo test ::test
Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
Running target/debug/deps/rust-9d6b4d08e5c8e0ac
running 2 tests
test test::test ... ok
test test::test321 ... ok
test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out but then why does this fail? $ cargo test ::test --exact
error: Unknown flag: '--exact'
Usage:
cargo test [options] [--] [<args>...] My cargo version: cargo 0.22.0-nightly |
@maraisr, |
Hi! I've created pull request #1868 for this issue. Please, have a look. |
I guess this issue can be closed since the pull request #1868 has been merged. |
rust-lang/rust#38181
The text was updated successfully, but these errors were encountered: