Michel Feinstein

> Ah. > > That's currently possible in flutter_test via `runAsync`. > > ``` > await tester.runAsync(() { > // Code runs in normal event loop > }); > ```...

It leads to flaky tests, its docs explains a bit why it should be avoided if possible.

Because besides being very cumbersome, making the log code harder to read, it will also won't work of you are logging strings, since you can't expand a string.

I think the Metadata parameter should be an `Object?` as well, to keep it consistent with the rest of the API.

I think you will have better changes to get this to be approved if you didn't change the formatting.

@grouma can your example be used for `Stream`? @natebosch yeah, I see your point, it does fill a bit of an antipattern, but at the same time `doesNotEmitFor(Duration)` sounds useful...

@grouma thanks, but for my use case, @natebosch solution was better as I had to call a method to trigger the emission.

No, I just stopped using WSL.

I am using navigation 2.0 with the go_router already, I will explore more your suggestion, thanks.

With the `Test` attribute it works....but not with the `TestCase` attribute:  Even though the Test Explorer does show the completed successful tests with a check mark: