FluentAssertions Failed Assertions Cause the Test Runner to Crash and/or Mark as Passed
I have run into some difficulty after upgrading to SpecRun.Runner 3.9.31 from 1.8.5, with SpecFlow version 3.9.40 and FluentAssertions 5.10.3. Randomly when an assertion fails, I get FluentAssertions.Execution.AssertionFailedException which causes the test runner to crash and it reports the test as a pass. FluentAssertions no longer seems to be recognizing that there is still a test framework and the test runner isn't handling this exception nicely. Is anyone else experiencing this issue and if so, what is the best workaround? I don't want to roll back to older versions if possible, and wrapping everything in try/catches and then attempting to override the test status doesn't sound maintainable in a large test project.
Please sign in to leave a comment.
Comments
0 comments