-
Notifications
You must be signed in to change notification settings - Fork 157
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 MS Test 2 #340
Comments
What doesn't work here? You should be able to use one of the portable FsCheck version. |
Even |
No, but last time that was looked at mstest just doesn't support that kind of extensibility. You're better of using Has this changed in MSTest 2? If it's .NET core support you're after, that is being looked at separately: #293. |
It is related. |
Like I said, afaik MSTest has no extension points. |
Since I don't really see how to support the wish here because of how MSTest works, I'm closing this. |
@kurtschelfthout I noticed MSTest v2 now has https://github.com/Microsoft/testfx-docs/blob/master/RFCs/003-Customize-Running-Tests.md . I played with it yesterday and it seems to me that by writing a proper implementation for If you agree, can we reopen this ticket? I would like to work on this. |
Sure. |
@lukas-lansky do you have anything to present to the community? |
Is it possible on context of v3.0 release? |
It's a separate project (like FsCheck.Xunt/NUnit) so it isn't related to any particular release or version - can be added at pretty much any time. Still have no plans or intention to work on this myself though. |
I wrote an MSTest extension. It started out for private use, but I recently introduced it into one of my work projects too. Works well so far, but there are open issues. Beware that it targets .net6 only. However, feel free to open an issue if there's the need to target other framework versions. |
Thanks @Andreas-Dorfer! You are most welcome to add a few lines to FsCheck's docs, e.g. here: https://github.com/fscheck/FsCheck/blob/master/docs/index.fsx#L11 |
The text was updated successfully, but these errors were encountered: