Ahh. Well in this case, I did need the full seed to repro for whatever
reason, then I easily found my small bug. Thanks for the help!
On Wed, Feb 5, 2020 at 3:59 PM Dawid Weiss wrote:
>
>
> The second part of the seed is derived from the first (and iteration number,
> test name etc) so typically
The second part of the seed is derived from the first (and iteration
number, test name etc) so typically the first would be sufficient.
D.
On Wed, Feb 5, 2020, 19:59 Michael Sokolov wrote:
> ah thanks I never did understand the split seed before. I'm still a
> little confused because I had prev
ah thanks I never did understand the split seed before. I'm still a
little confused because I had previously thought that to reproduce a
test failure I would define tests.seed= to be the first part of the
seed (like it says in the repro line), but if I would still get a
different seed applied to ca
In case I was not clear: in case of most tests the tests.iters _is_ the
right way to repeat the same test with different seeds. The only difference
is when you would like to randomize static stuff - then tests.iters would
still apply only to tests, not the static test context ( which would remain
t
Short because I am on a phone only. The first part of the seed.is the
"static" part that applies to static context - constructors, beforeclass
etc. The second part would apply to methods. Test.iters is a.property
recognized by the runner (so it works from the ide etc.) - if your random
failure is a
Hi, I've been using gradlew a lot last few days, and first I want to
give a huge thanks to those who did the work to make this possible.
I'm not naming names since I probably don't know everyone who chipped
in, but this is really great. I'm especially loving the `gradlew
tasks` and the excellent do
