When i run the UnitTest example it passes where it should fail about coyote

[tbertenshaw]

yeah i get that (or i did after scratching my head for a bit). Would make sense to add that line below the console. So its obvious, as it wasn't when i was trying to work out what i was missing.

[tbertenshaw]

Glad I could help. Does anyone monitor the samples repo? I did a similar quick clarification pr there. Hope its ok microsoft/coyote-samples#10 From: Pantazis Deligiannis <[email protected]> Sent: 16 July 2020 15:42 To: microsoft/coyote <[email protected]> Cc: timbo <[email protected]>; Mention <[email protected]> Subject: Re: [microsoft/coyote] When i run the UnitTest example it passes where it should fail (#38) Totally, great suggestion! And thanks for the PR, I will merge later today. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#38 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAPKXEV7VY5K3GE6LPL7LC3R34GTVANCNFSM4O2ETYWA>.

[akashlal]

@tbertenshaw End you test RunCoyoteTest with the following to tell xunit what you're testing for:

Assert.True(report.NumOfFoundBugs == 0);

Then you will see the test fail.

[pdeligia]

That's right, @tbertenshaw the Specification.Assert is currently only recognized by the TestingEngine of Coyote (or by the coyote test tool, if you run it from command line), and not from xUnit (or other unit testing frameworks). When Specification.Assert fails, its going to trigger a failure in the testing engine, but then you need to assert it as Akash said above to fail your unit test.

[pdeligia]

Totally, great suggestion! And thanks for the PR, I will merge later today.

[pdeligia]

Awesome, that looks like a great fix too, thanks! Yes, we are monitoring that repo (and we try updating it frequently, e.g. .whenever we push a new nuget package out, or if we come up with a new sample).

[pdeligia]

Closing this one as its resolved.