Steven Weerdenburg

@nunit/framework-team Is anyone up to reviewing this? It's a large PR but is mostly cherry picks and should sync a few large pieces of work between the two branches

I like this idea. While slightly different from the initial use case, there's some times where I'm writing independent assertions where `Assert.Multiple()` is helpful, but other times I want it...

@CharliePoole You mentioned having updated the documentation, but I admit I'm having a hard time finding where we document it. At least nothing on https://docs.nunit.org/articles/nunit/writing-tests/attributes/setupfixture.html jumps out to me. Do...

Thanks @CharliePoole ! Agreed, it won't "fix" or change anything here, but I noticed that the `AttributeUsage` props are sometimes mentioned in issues as a way some infer how the...

This is a bit of an interesting edge case you've found @Dimension4 NUnit does a lot of magic internally to help make comparisons easier, one of which is that if...

I believe this affects BCL types too, which I don't know if we want to require custom formatters for. Compare the following failure messages for `string[]` and `ImmutableArray` ```csharp [Test]...

This came up at work yesterday. Another thing which could be helpful to document when we do this is to describe the reasons why the constraint model is recommended.

I agree using `Assert.Inconclusive` is not ideal here, especially if that's a value which doesn't apply in a given scenario, but I'm wondering if there's a built-in way here to...

That's an interesting idea. A couple things off the top of my head we'd have to consider: 1. For things like `RandomAttribute`, would we keep trying until we generate a...

Thanks @ssrmm I agree this is an unusual scenario but I understand why you would ask it. My concern here with adding this is that it would make NUnit's handling...