Skip to content

Conversation

@s-nel
Copy link

@s-nel s-nel commented Oct 8, 2025

It's not always possible to configure the ScalaCheck seed via -S <seed> argument. For example when using the JUnit runner via Gradle (see #2397). This PR allows us to specify a seed at the property or spec level to help reproducing property failures. This will be used by a subsequent PR in https://github.com/s-nel/scalatestplus-scalacheck that will use this parameter and fall back to the global seed in org.scalatest.prop.Seed, or a random seed if the global seed is absent.

Fixes: #2397

@cla-bot
Copy link

cla-bot bot commented Oct 8, 2025

Hi @s-nel, we require contributors to sign our Contributor License Agreement, and we don't have yours on file. In order for us to review and merge your code, please access https://www.artima.com/cla/choose-type to sign our Contributor License Agreement. Your effort is highly appreciated. Thank you.

@artimasites
Copy link

@cla-bot[bot] check

@cla-bot cla-bot bot added the cla-signed label Oct 8, 2025
@cla-bot
Copy link

cla-bot bot commented Oct 8, 2025

The cla-bot has been summoned, and re-checked this pull request!

@s-nel s-nel force-pushed the seed-parameter-support branch from 63221ca to 65c5a47 Compare October 8, 2025 23:02
@s-nel s-nel marked this pull request as ready for review October 8, 2025 23:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Setting seed via JUnitRunner

2 participants