Youssef Victor
Youssef Victor
We have it internal already here: https://github.com/microsoft/testfx/blob/cd0fd625fd72bad3483d2665ae04f18fc0c65bed/src/Adapter/MSTestAdapter.PlatformServices/Services/TestContextImplementation.cs#L113 I think it's much easier to use it directly this way. Benefits: - No need to inject it via constructor or property -...
This issue tracks few ideas for improving the performance of MSTest. - [ ] We shouldn't do any serialization for parameterized tests if appdomain is disabled. This will be v4...
yes, there are probably more optimizations that can be done in the terminal logger, e.g. getting rid of the flatException type (if you did not do that already) _Originally posted...
As we keep adding more and more analyzers, I would like us to make sure they are written in a performant way and that we are not slowing down the...
Similar to https://github.com/microsoft/testfx/pull/6867 @nohwnd
Arcade testing infrastructure allows projects to set `TestArchitectures` property. This property can have multiple values semicolon-separated, and it will cause `RunTests` target to run for each architecture. - VSTest.targets -...
Today we have this usage: https://github.com/microsoft/testfx/blob/f548433961344ee1629c5b04c35d99efc9fdd860/src/Platform/Microsoft.Testing.Platform/Microsoft.Testing.Platform.csproj#L96-L110 That breaks build incrementality very badly as we are always writing the file after `PrepareForBuild`, causing CoreCompile to always be considered not up-to-date. One...
At least for MTP, we need that in microsoft/testfx. See https://github.com/microsoft/testfx/pull/6140 for context. Basically, we run official builds with Arcade, but PRs/public builds with `dotnet test`, and we want to...
I don't know if some exists already for VSTest, but at least for MTP there is no integration tests. Test scenarios to cover: - TestRunnerName - `MSTest` (with EnableMSTestRunner) -...