Tests that validate mock calls fail randomly

[RaphaelMarcouxCTRL]

Hi,
we have a few tests that seem to fail randomly when executing in our azure devops pipeline.
From what I have observed, it looks like it could be linked to Checking for Received calls on mocks inside a WaitForAssertion() call.

(using NSubstitute)

The tests are of the following format :

• Register a mock service in the DI container
• Render the component
• Trigger an action on the component (ex: click a button)
• cut.WaitForAssertion( a method on the mock service was called with specific arguments )

Is it the right way to do this?
Could it be that making an assertion on a mock instead of the component itself is not how it's supposed to be used?

[egil]

Hi @RaphaelMarcouxCTRL,

You might be doing the right thing, it depends.
Can you share your component under test, the mocked service, and the test itself, along with the exception you are getting on your build pipeline?

[RaphaelMarcouxCTRL]

Thank you so much for your quick reply,
I fiddled with the tests a bit and now it's been a few days since I didn't have test failures so maybe I fixed it?
Will get back to you if I have other troubles.

Thank you for your time and thank you for this wonderful project of yours, it's absolutely fantastic to use.