Skip to content

Update ScalaCheck website #41

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ <h1>Generator-driven property checks</h1>
To use generator-driven property checks, you must mix in trait <a href="@latestScaladoc/#org.scalatest.prop.GeneratorDrivenPropertyChecks"><code>GeneratorDrivenPropertyChecks</code></a> (or import the
members of its companion object). If you are also using table-driven property checks, you can mix in
trait <a href="@latestScaladoc/#org.scalatest.prop.PropertyChecks"><code>PropertyChecks</code></a>,
which extends both <code>GeneratorDrivenPropertyChecks</code> and <a href="@latestScaladoc/#org.scalatest.prop.TableDrivenPropertyChecks"><code>TableDrivenPropertyChecks</code></a>. Generator-driven property checks uses <a href="http://code.google.com/p/scalacheck/">ScalaCheck</a>, so you must also include the ScalaCheck JAR file on your classpath when you compile and run your tests.
which extends both <code>GeneratorDrivenPropertyChecks</code> and <a href="@latestScaladoc/#org.scalatest.prop.TableDrivenPropertyChecks"><code>TableDrivenPropertyChecks</code></a>. Generator-driven property checks uses <a href="https://www.scalacheck.org/">ScalaCheck</a>, so you must also include the ScalaCheck JAR file on your classpath when you compile and run your tests.
</p>

<p>
Expand Down