Rain
Oh yeah, we should definitely use that field (and do use it in some other places, though it might get remapped with build archive/reuse). Maybe `$CARGO_TARGET_DIR/nextest` is not how it...
A thing I did realize is that if the target dir is created by us as part of running tests out of an archive, then the temporary directory will typically...
I've listed out a general way we can make behavior changes: https://nexte.st/book/stability.html#making-behavior-changes
Hi there, thanks for the report! `cargo nextest run -E 'test(~two_concurrent_writers)'` (or just `cargo nextest run -E 'test(two_concurrent_writers)'` is correct. In your case it looks like this is happening because...
Ah yeah, I can see that being confusing! One way to fix this would be to implement https://github.com/nextest-rs/nextest/issues/800.
Hi there -- No, there are no immediate plans for nextest to support this. I think the way forward would be for `wasm-pack` to add a `nextest` command, just like...
Hi! At the moment, no it's not. That seems like a deficiency, though, and I think one that should be fixed in nextest. I think we can do something like:...
Note that you are going to run into https://github.com/nextest-rs/datatest-stable/issues/8 as the number of files grows. If you or someone else would like to fix it, help would be greatly appreciated!
Thanks for the report! Ah I see, yes we should try and obey test groups while tests are being listed.
@janosimas Setup scripts should address that use case: https://nexte.st/book/setup-scripts.html