Skip to content
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.

Sign up for GitHub

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

Jump to bottom

What should we do with Pex? #5

Open
gsvgit opened this issue Aug 24, 2015 · 2 comments
Open

What should we do with Pex? #5

gsvgit opened this issue Aug 24, 2015 · 2 comments
Labels
CourseWork2 question ready

Comments

@gsvgit
Copy link
Member

gsvgit commented Aug 24, 2015 •
edited
Loading

Really. What should we do?

  • Remove it in order to make library compatible with mono, .NET Core, etc
  • Migrate to VS-2015 IntelliTest
  • Migrate to FsCheck
  • Something else?
@gsvgit gsvgit mentioned this issue Jul 24, 2016
Open
@dzmitry-lahoda
Copy link

It Pex can be replaced with FsCheck which seems to be work on core?

@gsvgit
Copy link
Member Author

gsvgit commented Sep 12, 2017

@asd-and-Rizzo , may be you are right. FsCheck is a good candidate for testing framework. Did you know any ways to automate migration from Pex to FsCheck?

@gsvgit gsvgit mentioned this issue Sep 5, 2018
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CourseWork2 question ready
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gsvgit @dzmitry-lahoda