Steven Weerdenburg
Steven Weerdenburg
I found the need for something like this earlier today. My use case is what was called out by the title: namely the need to apply IWrapSetUpTearDown to all tests...
True. If we use a method-based approach, I wonder if we'd want to allow that to be configurable. ``` Assert.FailFast(AssertMultipleScope.Immediate); Assert.FailFast(AssertMultipleScope.All); ``` To me the name `FailFast()` implies it should...
I find the idea of something like this intriguing too: ```csharp public class MultipleAssertContext { public MultipleAssertContext? ParentContext { get; } public int FailureCount { get; } public int TotalFailureCount...
I could see `TestExecutionContext` making sense for this. Did you have anything in particular in mind?
I think the introduction of the `AssertionScope` also makes this a bit easier to exit the test method early based on arbitrary criteria as the individual assertions no longer need...
I encountered the need for this myself within NUnit's our test suite as I've been trying to add a test to cover https://github.com/nunit/nunit/issues/4246 In that case I would seek to...
Agreed, I like the idea of params array too so that the culture strings can be kept separate. For test names, that's the part I've been struggling to wrap my...
I rushed completion of that last message, but I'd be very curious to hear other's thoughts on ideas
@maettu-this recently found a need for this too in #4691
The idea from #3985 could also likely help here.