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.

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

remove _build/propcheck.ctex by default #81

Closed
verrchu opened this issue Jan 29, 2019 · 4 comments
Closed

remove _build/propcheck.ctex by default #81

verrchu opened this issue Jan 29, 2019 · 4 comments

Comments

@verrchu
Copy link

verrchu commented Jan 29, 2019

I have seen warnings for Elixir user to remove the _build/propcheck.ctex file in order to always get fresh results by the generators.
It is superannoying to remove the file by hand every time
Why not just remove it by default?

@evnu
Copy link
Collaborator

evnu commented Jan 29, 2019

For reference, counterexamples were introduced with #10. See #30 were the behaviour you are describing (stale generator results) was discussed.

@alfert
Copy link
Owner

alfert commented Feb 4, 2019

Yes, it is exactly the way, evnu describes. The basic idea behind is that you focus on getting failing properties right and get the always the same counterexample until the properties is no longer failing (i.e. the bug is fixed - assuming that the property is correct and so is the generator).

@verrchu, is your problem that this development approach is not clearly enough stated in the docs or does not fit to your way of development? This feature was introduced to support developing and not annoy developers.

@adkron
Copy link
Contributor

adkron commented Apr 15, 2019

If this is something that won't be changed could we close it so that someone looking for something to work on won't come and read it?

@verrchu
Copy link
Author

verrchu commented Apr 15, 2019

@adkron yes sure
thanks for your help

@alfert alfert closed this as completed Apr 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants