version 0.1.7

Welcome to Scala version 2.11.6 (Java HotSpot(TM) 64-Bit Server VM, Java 1.8.0_45).
Type in expressions to have them evaluated.
Type :help for more information.

scala> import scalaprops._
import scalaprops._

scala> Gen[Int => Int].samples(listSize = 5).map{f => (1 to 10).map(f)} foreach println
Vector(794921487, -117319807, 2147483647, -135116815, -2147483648, 1916507803, 34561382, 1402977518, -2124061576, -1544661226)
Vector(794921487, -117319807, 2147483647, -135116815, -2147483648, 1916507803, 34561382, 1402977518, -2124061576, -1544661226)
Vector(794921487, -117319807, 2147483647, -135116815, -2147483648, 1916507803, 34561382, 1402977518, -2124061576, -1544661226)
Vector(794921487, -117319807, 2147483647, -135116815, -2147483648, 1916507803, 34561382, 1402977518, -2124061576, -1544661226)
Vector(794921487, -117319807, 2147483647, -135116815, -2147483648, 1916507803, 34561382, 1402977518, -2124061576, -1544661226)

With

object AlgorithmCheckerProps extends Scalaprops {

  private val mkLogger = NoopLogger.factory()

  private def checker(sigs: Seq[String], keys: Seq[String]) = {
    new AlgorithmChecker(mkLogger, sigs.map(s => parseAll(expression, s).get).toSet,
      keys.map(s => parseAll(expression, s).get).toSet)
  }

  val `pass a good key algorithm (RSA > 1024)` = Property.exception {
    Property.prop {
      val certificate: Certificate = CertificateGenerator.generateRSAWithSHA256(2048)
      checker(Nil, Seq("RSA keySize < 1024")).check(certificate, emptySet())
      true
    }
  }

}

Running scalapropsOnly com.typesafe.sslconfig.ssl.AlgorithmCheckerProps runs two properties instead of one:

com.typesafe.sslconfig.ssl.AlgorithmCheckerProps$
+- $anonfun$pass a good key algorithm (RSA > 1024)$1  Proven(1,0,LongSeed(1601297310331947)) 3ms
`- pass a good key algorithm (RSA > 1024)  Proven(1,0,LongSeed(1601297342674608)) 0ms

On the current implementation, every Shrink instance must obey the following law, or they might invoke infinite loop at shrinking process:

def shrinkNotContainItself[A](a: A)(implicit s: Shrink[A]): Boolean =
  !s(a).contains(a)

Shrink[Boolean] does not obey the above law for instance.
(In fact Shrink[Boolean].apply(false) == Stream(false))
This prop fails immediately, however shrinking process never stop, so the final result is timeout.

import scalaprops._

object ShrinkTests extends Scalaprops {
  val prop = Property.forAllS[Boolean](_ == true)
}

Tests for checking every Shrink are needed.

• https://github.com/apache/commons-lang/blob/LANG_3_4/src/main/java/org/apache/commons/lang3/RandomStringUtils.java
• https://github.com/msgpack4z/msgpack4z-core/blob/v0.3.2/src/test/scala/msgpack4z/StdSpec.scala#L16-L33

use by-name implicits
scalaz/scalaz@12b69fe

Would it be possible to set up the scalazlaws subproject so that running test would check a few of the laws? Right now it's not totally clear how to hook it all together.

Currently, ignore timeout: Duration parameter in Scala.js, because JavaScript does not have Threads.

• https://github.com/scalaprops/scalaprops/blob/v0.3.2/scalaprops/js/src/main/scala/scalaprops/TestExecutorImpl.scala#L8
• https://github.com/scalaprops/scalaprops/blob/v0.3.2/scalaprops/jvm/src/main/scala/scalaprops/TestExecutorImpl.scala#L28-L29

use WebWrokers or something?

• https://www.w3.org/TR/workers/
• http://lampwww.epfl.ch/~doeraene/scalajs-actors-design.pdf
• https://github.com/sjrd/scala-js-actors
• https://github.com/typesafehub/akka-js
• https://groups.google.com/d/topic/scala-js/dzw7862ezDQ/discussion
• http://stackoverflow.com/q/35905658
• http://stackoverflow.com/q/35926650

WIP https://github.com/scalaprops/scalaprops/compare/native

current status

scala-native 0.2.1 does not support sbt-test-interface

• download (in build-time) scalajs-test-interface_2.12 and apply some hack(remove scala-js specific annotations). use scala-native 0.3.0 test-interface
• auto generate test-main class for native from existing test files.
• or wait scala-native/scala-native#435 ?

some (unresolved/will be fix) issues

• can't compile PropertyTest.scala scala-native/scala-native#679 (can be apply workaround)
• need too many memory scala-native/scala-native#686 fixed in master. wait 0.2.2 or 0.3.0 ?
• some tests fail scala-native/scala-native#695 https://gist.github.com/xuwei-k/91e8f2064943e7866dddaf4fda0475a2#file-gistfile1-txt-L26-L391

version 0.3.5

scalaprops.Gen.chooseLong(0, Int.MaxValue.toLong * 2 + 1).samples()

fce8e4092bdc675eb789b

Could you please publish your excellent Rand / MersenneTwister64 implementations as a zero dependency micro library?

Hi. For what it may be worth, I published updated sxr artifacts under version 1.0.2 which include 2.10/2.11/2.12 so if you want you can upgrade and lose most of the conditional logic in Sxr.scala.

The only self-contained example (one that doesn't reference laws in the scalaz project) is visible for a less than a second in the gif. An example that does not require looking into scalaz's source code would be helpful for quick-starting use of scalaprops.

I'm just checking out this library and have two questions (that go against each other):

1. Are duplicate properties avoided? For example, monad.all inherits apply.all both via bind.all and applicative.all. Is this duplication eliminated?
2. If the answer to question 1. is yes, can I have the same law included twice in a property set, for different aspects of the type class? For example, if I have a Ring, I want to check the monoid laws for both addition and multiplication.

discipline can achieve both of the above, but I find its approach rather cumbersome and fragile, which is why I wrote my own tool, Principled. Principled, however, relies on universal equality (==) of type classes, which is not ideal either (although the worst that can happen is failure to avoid duplicates, when the same type class is instantiated twice with the same arguments, but == returns false).

I wonder if and how scalaprops deals with this problem.