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 Targeted Property-Based Testing #70
Comments
Correct. I have an WIP feature branch already in my local repo, which I should publish. I would like to get PRs on that. |
I will be happy to help out |
@zkessin, I published my current state of work on this on its own branch and I am open for reviews, PRs and the like. Currently the tests fail. Any hints why and what to do are more than welcome. |
Awesome, I will take a look in the next few days if I have a chance |
I updated the branch. What works now is the level example with Generally, I am struggling with the entire concept. The idea of having properties with a negative logic (if they fail, everything is fine) irritates me. And to find a useful metric expressed in a real number to optimise for and which is related with the correctness of software in general, is by no means obvious and I doubt if this is generally a valid approach. It reminds to program synthesis with genetic algorithms in the 90ies: is a sorting algorithm which sorts in 95% of all cases correctly better than an algorithm with sorts only in 94% of all cases? So, what to optimise for? But it might be that I look from the wrong point of view on this approach. If anybody can explain in which cases the targeted approach helps, I would be delighted. |
Just to copy the final comment from #77:
It it available in the master now, a new release hex is coming soon. |
We should work to include the new features of PropER 1.3
The text was updated successfully, but these errors were encountered: