Steven Weerdenburg

Update: I tried my hand at an `IResolvableConstraint` and `IConstraint` in order to support a signature like `Assert.That(TActual, IResolvableConstraint)` so that we could get compile-time wiring to an overload when...

Sorry, a combination of busy work schedule and jetlag kept me from chiming in earlier. I agree this is a tough one to solve, and that the best chance could...

I've gotten much closer on this failure: > 1) Failed : NUnit.Framework.Tests.Constraints.EqualConstraintTests.SameValueDifferentTypeExactMessageMatch It looks like there's some special formatting and handling in the non-generic `EqualConstrainResult` that this test relies on....

That error message discrepancy failure is now fixed. I'll have to do some digging on the others but I see it's using the built-in `Equals()` method when trying to compare...

I don't have a strong preference over framework, but I also like this idea. I found this after seeing a slack discussion from a bit ago about if we produced...

I recall trying to chip away at these as well as the Explicit tests a while back for similar noise-related reasons. I must not have made much progress, but I...

A separate instance of this was investigated under a duplicate issue, #4160 The following repros were used there to investigate: - https://github.com/nunit/nunit3-vs-adapter.issues/tree/master/nunit/Issue4160 - https://github.com/nunit/nunit3-vs-adapter.issues/pull/5

Closing as a duplicate of https://github.com/nunit/nunit/issues/4589

This was closed as a duplicate of #4589 , however the underlying issue there proved to be a parsing issue introduced in a prereleaes of NUnit 4.0. As this issue...

I came across this issue while searching for "numerics". It's been a while since there was any activity. I'm a little unclear from the discussion, is there a change we...