-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Testing Platform Support #3094
Comments
I'll add that it may be possible to get indirect support today by using the VSTest Bridge extension, which I haven't tested but assume would enable TUnit support today. |
We are working on it, but it is a very large feature. We have to reimplement a lot of vstest features ourselves because mstest runner assumes to be self contained in the test project and this doesn't really work for us since stryker is the executing binary. A start was made by an intern at #2988 As far as I know the test framework has to provide support for vstest, and TUnit could do this using the vstest bridge if they choose. |
I'm currently working on this. I'll take TUnit into account as well. Would be nice if we could support that. |
Awesome, I didn't realise that this was being worked on, and how much work it is. I'm going to do some experimentation and see what I can get working today with TUnit, |
Remaining issues ## Coverage * `dotnet run --coverage` doesn't run the VSTest target so ReportGenerator can't be hooked * `dotnet test --coverage` fails with MSB1001: Unknown switch ## Stryker * Currently not supported for Microsoft.Testing.Platform, see stryker-mutator/stryker-net#3094
Remaining issues ## Coverage * `dotnet run --coverage` doesn't run the VSTest target so ReportGenerator can't be hooked * `dotnet test --coverage` fails with MSB1001: Unknown switch ## Stryker * Currently not supported for Microsoft.Testing.Platform, see stryker-mutator/stryker-net#3094
Remaining issues ## Coverage * `dotnet run --coverage` doesn't run the VSTest target so ReportGenerator can't be hooked * `dotnet test --coverage` fails with MSB1001: Unknown switch ## Stryker * Currently not supported for Microsoft.Testing.Platform, see stryker-mutator/stryker-net#3094
Remaining issues * GitHub action: how to replace GitHubActionsTestLogger? See microsoft/testfx#4365 * HTML logger: could not find an equivalent for Microsoft.Testing.Platform * Stryker: currently not supported for Microsoft.Testing.Platform, see stryker-mutator/stryker-net#3094
Remaining issues * GitHub action: how to replace GitHubActionsTestLogger? See microsoft/testfx#4365 * HTML logger: could not find an equivalent for Microsoft.Testing.Platform * Stryker: currently not supported for Microsoft.Testing.Platform, see stryker-mutator/stryker-net#3094
Today Stryker has support for VSTest as the test runner, and this is what is commonly used today by various testing frameworks.
However Microsoft have built a new replacement call the Microsoft Testing Platform, which is being adopted by all of the major players (MSTest, NUnit, xUnit).
While many of these frameworks will support both runner engines for a good while, there are also new testing frameworks that are only support on the new testing platform (the excellent TUnit for example).
It would be amazing if Stryker.NET add support for this as a new runner option.
The text was updated successfully, but these errors were encountered: