Async tests

[mackwic]

I don't know. But we should think of it.

Ideas:

• a callback injected by argument in the test ? we may be able to use generic on closure to detect that the test needs this argument ?
• a test_running instance created via another method ? Using signaling ? I dunno
• Be pragmatic and have an optional module which is specific to MIO

[mackwic]

Well, thanks to the glorious Rust community, we have only one type for async.

So it's just a matter of Implementing ExampleResult for Future, and executing the future synchronously when resolving the result.

It's not true async, but the runner don't support parallelism for now, so it's all we can do and it seems good enough for now.

[regexident]

Once #30 (parallelization) gets merged this should be feasible. 💪

[regexident]

Given that with #30 we'd have parallelization I'm wondering if rspec itself should have async-awareness at all.

The futures crate provides "all the pieces" to do async testing (via .await(), e.g.) and my gut tells me that async matching might make for a great micro-crate on its own, disconnected from rspec. This would bring convenience APIs for async testing not only to rspec, but also rust's native tests, e.g.

Would you agree, @mackwic?

[mackwic]

Well, now that I think of it, a test could have multiple assertions.
We can't resolve the Futures from ExampleResult because there is only one return value (which will be resolved) and the other will be let appart...

So, yes. Async asserts may be the way to go. The other advantage I see in an external crate is to limit the scope and keep experimenting without troubling the stabilization of rspec.

I don't like the idea of a separated, async version of it anyway. That's ugly.

[mackwic]

I'll make an organization, so that we can mutualize crates easily.

[regexident]

So, yes. Async asserts may be the way to go. The other advantage I see in an external crate is to limit the scope and keep experimenting without troubling the stabilization of rspec.

I agree.

I'll make an organization, so that we can mutualize crates easily.

I saw it, that's great!

[cataggar]

Rust async has come a long way in the last 5 years. Is it possible to use with this project?

[mackwic]

It is possible but it won't be easy, you will have to add `block_on` everywhere. The async story is still a kind of mess, there is not enough power in the types to do anything generic like a testing library so I don't see any progress on this front soon. Sorry :/ Le ven. 9 sept. 2022 à 05:50, Cameron Taggart ***@***.***> a écrit :

…

Rust async has come a long way in the last 5 years. Is it possible to use with this project? — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEIIC7VX3OZKGQZWNP4CK3V5KXZJANCNFSM4CKNT7TA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[vittorius]

Hey. Are there any plans regarding this library feature? Or any vision in general?