[
https://issues.apache.org/jira/browse/ZEST-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493917#comment-14493917
]
Niclas Hedhman commented on ZEST-18:
------------------------------------
>From Marcel (marrs);
Some research about it on-line, with the goal of a) understanding how it works
and b) finding a good Java implementation:
http://stackoverflow.com/questions/576901/have-you-used-quickcheck-in-a-real-project
- especially the first answer is valuable
There is a Scala implementation called “ScalaCheck” http://www.scalacheck.org/
There is a Java library that supports ScalaCheck/QuickCheck:
https://github.com/functionaljava/functionaljava /
http://www.functionaljava.org/
Another implementation is: https://bitbucket.org/blob79/quickcheck
Three Java ports are mentioned here:
http://stackoverflow.com/questions/22712961/what-is-the-difference-between-agitar-and-quickcheck-property-based-testing
https://bitbucket.org/blob79/quickcheck (as found above)
http://www.jcheck.org/ (on SF, not updated for 2 years now, 0.1 version)
https://github.com/pholser/junit-quickcheck/ looks more promising.
Blog entries, still need to read them:
http://theyougen.blogspot.nl/2010/11/alternative-test-approach-quickcheck.html
http://www.theoryinpractice.net/post/83902909195/quickcheckng
https://blog.srcclr.com/property-based-testing-for-java/
http://java.dzone.com/articles/property-based-testing-spock
https://www.uni-marburg.de/fb12/ps/teaching/ss11/sw-analysis/quickcheck.pdf
(german, states that a combination of QuickCheck and Pex (C#) would be ideal)
https://weblogs.java.net/blog/editors/archives/2009/06/quickcheck_for.html
podcast: http://www.functionalgeekery.com/episode-10-paul-holser/ (the first
half is more interesting than the last, to me at least)
Another Java implementation: http://yaqc4j.sourceforge.net/
Guice based: https://code.google.com/p/guickcheck/ …code seems very basic
Similar, related links:
http://www.bodden.de/clara/ - Clara (CompiLe-time Approximation of Runtime
Analyses) is a novel research framework for the implementation of hybrid
typestate analyses, which use static analyses to partially evaluate runtime
monitors for typestate properties. — has plenty of docs on the site
> QuickCheck instead of JUnit
> ---------------------------
>
> Key: ZEST-18
> URL: https://issues.apache.org/jira/browse/ZEST-18
> Project: Zest
> Issue Type: Improvement
> Environment: Java 8
> Reporter: Sandro Martini
> Labels: java8, sandbox, test
>
> To better fix/identify problems in multi-thread execution contexts, verify if
> write (additional) Unit Tests but with dedicated libraries (more specific
> than JUnit), like QuickCheck or one of others similar (for example see even
> ScalaCheck).
> Note that usually many libraries for this require Java 8.
> As repository use Zest-sandbox (maybe in a feature branch), so it would be
> simpler to evolve/integrate/remove later in Zest code base.
> For more info, see related thread in our dev mailing list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
