this syntax allows to declare auto examples with { .
this syntax allows to declare auto examples with { ... }.eg in mutable specifications
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
A value can be tested against another with the === operator.
A value can be tested against another with the === operator. It is equivalent to writing a must_== b
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
this method can be overriden to throw exceptions when checking the match result
this method can be overriden to throw exceptions when checking the match result
execute a ScalaCheck property
execute a ScalaCheck property
this method can be overriden to throw exceptions when checking the result
this method can be overriden to throw exceptions when checking the result
an Expectable with a description function
an Expectable with a description function
an Expectable with a description
an Expectable
an Expectable with a function to show the element T
specific implicits for datatables
specific implicits for datatables
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
describe a value with the aka method
describe a value with the aka method
factory object to create parameters with verbose = true
explicit call The result type is different from the eg method to create examples in order to avoid an overloading error
explicit call The result type is different from the eg method to create examples in order to avoid an overloading error
explicit call.
explicit call. The result type is different from the eg method to create examples in order to avoid an overloading error
explicit call
explicit call
explicit call
explicit call
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
get the description from the source file
get the description from the source file
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
this method can be overriden to intercept the transformation of a MatchResult to a Result
this method can be overriden to intercept the transformation of a MatchResult to a Result
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
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