polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niclas Hedhman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZEST-18) QuickCheck instead of JUnit
Date Tue, 14 Apr 2015 11:24:12 GMT

    [ https://issues.apache.org/jira/browse/ZEST-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493919#comment-14493919

Niclas Hedhman commented on ZEST-18:

>From Paul Merlin;

The only project that seems to have been down the shrinking road so far
is FunctionalJava [5].

[1] https://github.com/pholser/junit-quickcheck/issues/32
[2] Nothing about shrinking in https://bitbucket.org/blob79/quickcheck
[3] Shrinking mentioned in TODO as 'Simplification' http://www.jcheck.org/
[4] http://sourceforge.net/projects/qc4j/
[5] https://functionaljava.ci.cloudbees.com/job/master/javadoc/fj/test/package-summary.html

> 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

View raw message