RFC 011: Impact on other test runners

[drieseng]

Have the changes that were done for RFC 011 been discussed with other test runners?

If I compare the output of the ReSharper test runner in 2026.1.2 between 4.2.3 and 4.3.0-preview.26309.1, then it's clearly not a better experience for users:

4.2.3:

4.3.0-preview.26309.1:

To be honest, I also don't see the added value of the "Assertion failed." fragment.

[Evangelink]

Sadly many IDEs and tools are just scrapping things without asking for a "protocol" or "standard" to be setup which virtually prevents any change on our side. I'd be happy to open something on JetBrains side but they haven't been super collaborative in past.

As for the Assertion failed prefix, it helps with looking for failures in big logs for human and AI reviews as it provides a fixes anchor to search.