cmd/go: don't cache tests that use testing/quick.Check and friends #26276
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env
)?What did you do?
https://play.golang.org/p/e6SHcVstHOW
What did you expect to see?
What did you see instead?
My assumption here is that the people who use
testing/quick
want the tests to run as often as possible to maximise the potential of finding a bug. Caching the first successful result thus seems counterproductive. I know that the official way to disable caching for tests is-count 1
, but it seems silly to provide a randomised testing package and than have it be almost useless by default.If the consensus is that the people who use
testing/quick
should just also use-count 1
, then I think it would be nice to reflect that in the package documentation.The text was updated successfully, but these errors were encountered: