You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using crates for parameterized testing doesn't allow me to run the individual tests using the "Run Test" action. I can run the entire set of tests in the module, but not a single method.
The reason for this is because the tests are run with --exact but the name provided is not the exact test name, since the exact test name is ultimately generated.
Without --exact if there would be a test called foo and foobar, trying to run foo would run both. It would be better to keep passing --exact, but implement expansion of attribute proc macros.
9128: feat: expand procedural attribute macros r=jonas-schievink a=jonas-schievink
This adds experimental support for attribute macros. They can be enabled by setting `rust-analyzer.experimental.procAttrMacros` to `true`.
Known issues:
* Tokens aren't remapped, presumably because we edit the input syntax tree (this causes IDE features to not work inside items with attribute macros on them)
* Macro errors aren't reported correctly
Closes#8971Fixes#8964 / la10736/rstest#120Fixes#2984Fixes#5412Fixes#6029Fixes#6687#6740 is still not fixed – we now expand `#[proc_macro_hack]`, but fail to expand the resulting `proc_macro_call!()` macro.
Co-authored-by: Jonas Schievink <jonasschievink@gmail.com>
Using crates for parameterized testing doesn't allow me to run the individual tests using the "Run Test" action. I can run the entire set of tests in the module, but not a single method.
The reason for this is because the tests are run with
--exact
but the name provided is not the exact test name, since the exact test name is ultimately generated.For example, given the test:
Running this will execute:
Whilst the exact test name is
users::model::user_id::tests::failed_parse::blank
(And an additional test function for each occurrence oftest_case
)If I use the "Run Test" action on the module as a whole, it executes without the
--exact
flag and thus works.The text was updated successfully, but these errors were encountered: