-
Notifications
You must be signed in to change notification settings - Fork 17
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
Unit Test Library #34
Comments
I am familiar with |
I've used If we want to use |
@tlycken FsCheck is something I'd definitely recommend on this project - it'll catch many corner cases that we won't think of naturally. |
I really like using |
FWIW, I think the decision should be up to whoever starts implementing some tests. If you're about to start working on something, use whatever you feel comfortable with. And if you're not first on the ball, but dislike what you find, you can always submit an issue and/or PR to discuss the relative merits of whatever you're unhappy with vs whatever you want to replace it with. So far there's been a couple of discussions around what tool chain to use for testing, and several people have vouched for Xunit, Expecto, FsCheck and Unquote; anything using a combination of some of these has a very high probability of being accepted by all. That doesn't mean that these are the only options, though - anything that runs from |
Expecto has a VS test runner add in as well AFAIK. |
This seems to be the best way to run Expecto through |
Expecto has VS adapter https://github.com/adamchester/expecto-adapter |
Shall we have a discussion on unit testing libraries? @forki mentioned
Expecto
in the readme. I haven't used it but I'd be keen it to give it a try. Thoughts?The text was updated successfully, but these errors were encountered: