-
Notifications
You must be signed in to change notification settings - Fork 80
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
Support Microsoft.Testing.Platform
for xunit v2
#416
Comments
If this can be done without breaking xUnit.net v3 Edit: The |
I would also be interested to know what the adoption blockers are for users who cannot use v3. |
Do you have documentation on the breaking changes? |
Most of the breaking changes should be here: https://xunit.net/docs/getting-started/v3/migration And there's also a What's New page that can be helpful for people moving: https://xunit.net/docs/getting-started/v3/whats-new |
Hi @bradwilson,
we could have some team that are interested to onboard the new testing platform but they're stuck at the moment with xunit v2.
We did integration with v3 already, I wonder if it could be fine to you if we take the integration of the v2 using the bridge(that won't add more dependencies than what you saw in v2) to have same/similar experience also for users that cannot at the moment move to v3. Let's say have v2 onboarded like MSTest and nUnit and v3 that's anyway a breaking change with the new experience.
The idea is to do something like #403 under your "supervision", we create the PRs and you do the review, so you don't have to spend coding time on it.
cc: @pavelhorak
The text was updated successfully, but these errors were encountered: