Assert.Multiple and Assert.EnterMultipleScope don't make sense for test code using the try-parse pattern

[Bartleby2718]

I think NUnit.Analyzers is too aggressive in recommending Assert.Multiple and Assert.EnterMultipleScope for code following the Try-Parse pattern.

It doesn't make too much sense to group the following assertions into a single Assert.Multiple scope

Assert.That(TryConstructSomething(x, y), Is.True);
Assert.That(y, Is.EqualTo(z));

bool TryConstructSomething(object x, [NotNullWhen(returnValue: true) out object y);

because there's no point in moving on to the second assertion when the first assertion is true.

To reduce (since we probably can't eliminate) a false positive like this, perhaps we can check if any the actual parameters in the assertions came from the out parameter of a previous assertion.

[manfred-brands]

Note that in this case y is not an out parameter. The attribute only indicates it is not null.
Did you forget the out keyword?

But yes, we could try to detect a Try pattern as being a method having a bool return and an out parameter with a NotNullWhen attribute.

[Bartleby2718]

Oops, yeah I missed the out keyword. Just updated the description!