Jakub Jareš

Yes. Right now ReflectorHelper is a mashup of direct reflection calls and cached reflection calls, and a jungle of calls in between the internal and public methods in that class,...

Just be aware that people hate banners these days, so please keep it short.

The new implementation for the cache is storing inherited and non-inherited attributes separately, fixing the issue that @Evangelink found out in his investigation. Using version 3.5.0-preview.24317.3 does not reproduce the...

Using the repro seemed difficult in our setup, because it relies on 2 assemblies. So I am testing the root cause rather than the symptom.

I can see this working nicely with async local as well. it would be nice to allow soft assertions by setting that affects more than one test, and have a...

There are 2 instanced of where IDs are generated for each test, which in total take 20% of execution, plus other interactions with ObjectModel (such as adding traits to traits...

Managed name and getting test id were the places where I saw it. https://github.com/microsoft/testfx/blob/main/src/Adapter/MSTest.TestAdapter/ObjectModel/TestMethod.cs#L74 https://github.com/microsoft/testfx/blob/main/src/Adapter/MSTest.TestAdapter/ObjectModel/UnitTestElement.cs#L294 https://github.com/microsoft/testfx/blob/main/src/Adapter/MSTest.TestAdapter/ObjectModel/UnitTestElement.cs#L334 https://github.com/microsoft/vstest/tree/main/src/Microsoft.TestPlatform.AdapterUtilities The source code is here.

I think the same concept exists in Nunit, https://docs.nunit.org/articles/nunit/writing-tests/attributes/explicit.html. In my view this should map to a skipped test + reason in TestExplorer. This way it is not making the...

> I would keep current and future IDEs representation and behavior out of the discussion, I think that the platform should be written without specific "caller" implementation in mind, Sorry...

> @nohwnd can you confirm that the new built-in ux won't go mad if an in-progress won't match a complete? yes, it does not care.