Sorry it took a couple of days for me to approve this through the spam
filter. I didn't see any notification from Google groups.
I'm surprised ScalaCheck would generate the same parameters multiple
times. That's a question for the scalacheck group, which I've CC'd.
What you'll have to do in the meantime is just count. This means you
can't let ScalaCheck do things in parallel, but I believe the default
is not in parallel. I showed an example in my previous email of using
a count variable. That should work.
Bill
On Wed, Sep 14, 2011 at 4:56 AM, Andreas Sewe
<se...@st.informatik.tu-darmstadt.de> wrote:
> Hi Bill again,
>
>>> forAll { (a: String, b: String) =>
>>> test("Parameterized test with fixture (" + a + ", " + b + ")") { fixture =>
>>> ...
>>> }
>>> }
>>>
>>> Here I put a and b into the test name. Only question there is what the
>>> heck is ScalaCheck going to generate for those strings.
>>
>> Don't worry about that. I was just using Strings to keep the examples
>> simple.
>
> there's unfortunately still a problem with the above solution. :-(
>
> The same combination of a and b may be generated multiple times
> (unlikely for two Strings, but much more likely for other data types) if
> I use something like arbitrary[String] or Gen.posInt. Is there any way
> to convince ScalaCheck not to check the same parameters twice (which
> would also save some time during testing)?
>
> Best wishes,
>
> Andreas
>
> --
> You received this message because you are subscribed to the Google
> Groups "scalatest-users" group.
> To post to this group, send email to scalate...@googlegroups.com
> To unsubscribe from this group, send email to
> scalatest-use...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/scalatest-users?hl=en
> ScalaTest itself, and documentation, is available here:
> http://www.artima.com/scalatest
>
--
Bill Venners
Artima, Inc.
http://www.artima.com