this implicit def is necessary when the expression is at the start of the spec
this implicit def is necessary when the expression is at the start of the spec
this implicit def is necessary when the expression is at the start of the spec
this implicit def is necessary when the expression is at the start of the spec
execute a ScalaCheck property
execute a ScalaCheck property
execute a PartialFunction as a ScalaCheck property
execute a PartialFunction as a ScalaCheck property
transform a Function returning a MatchResult (or anything which can be converted to a Prop) as a ScalaCheck property
transform a Function returning a MatchResult (or anything which can be converted to a Prop) as a ScalaCheck property
default parameters.
default parameters. Uses ScalaCheck default values and doesn't print anything to the console
default parameters to display pretty messages
default parameters to display pretty messages
Default values for ScalaCheck parameters
Default values for ScalaCheck parameters
factory object to create parameters with verbose = true
flush the content if necessary
flush the content if necessary
transform a function returning a boolean to a property by appending forAll
transform a function returning a boolean to a property by appending forAll
transform a function returning a boolean to a property by appending forAll
transform a function returning a boolean to a property by appending forAll
transform a function returning a boolean to a property by appending forAll
transform a function returning a boolean to a property by appending forAll
this implicit def is necessary when the expression is at the start of the spec The startDepth and offsets are special tweakings to make sure we get the right line in that specific case
this implicit def is necessary when the expression is at the start of the spec The startDepth and offsets are special tweakings to make sure we get the right line in that specific case
this implicit def is necessary when the expression is at the start of the spec
this implicit def is necessary when the expression is at the start of the spec
Values which can be used as Symbol aliases to specify ScalaCheck parameters
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
Values which can be used as Symbol aliases to specify ScalaCheck parameters
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
Values which can be used as Symbol aliases to specify ScalaCheck parameters
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
Values which can be used as Symbol aliases to specify ScalaCheck parameters
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
Values which can be used as Symbol aliases to specify ScalaCheck parameters
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
Values which can be used as Symbol aliases to specify ScalaCheck parameters
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
Values which can be used as Symbol aliases to specify ScalaCheck parameters
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
Values which can be used as Symbol aliases to specify ScalaCheck parameters
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
print an object with no newline
print an object with no newline
print stacktraces
print stacktraces
print several objects according to a format string (see Console.
print several objects according to a format string (see Console.printf)
print an object with a newline
print an object with a newline
this implicit def is necessary when the expression is at the start of the spec
this implicit def is necessary when the expression is at the start of the spec
this implicit def is necessary when the expression is at the start of the spec
this implicit def is necessary when the expression is at the start of the spec
this implicit def is necessary when the expression is at the start of the spec
this implicit def is necessary when the expression is at the start of the spec
factory object to create parameters with verbose = false
set specific execution parameters on a Property
set specific execution parameters on a Property
Values which can be used as Symbol aliases to specify ScalaCheck parameters
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
Values which can be used as Symbol aliases to specify ScalaCheck parameters
The naming is a bit different, in order to keep short names for frequent use cases
- minTestsOk == minSuccessfulTests
- maxDiscarded == maxDiscardedTests
- minSize and maxSize keep their name
The ScalaCheck trait can be used to access ScalaCheck matchers