These are chat archives for etorreborre/specs2

4th
May 2018
Marko Dimjašević
@mdimjasevic
May 04 2018 06:43
@etorreborre , that's great to hear! I'll give it a try right away.
Marko Dimjašević
@mdimjasevic
May 04 2018 06:57
Is this the right way to reproduce a failing spec from within sbt with a particular seed?
testOnly <spec-name> -- scalacheck.seed "95jIaKL8oJGC7q3Hc0sNVG_2xtI6XLR8-IpzspUoCMH="
Eric Torreborre
@etorreborre
May 04 2018 07:42
Without the quotes should work
Marko Dimjašević
@mdimjasevic
May 04 2018 07:52
thanks!
Marko Dimjašević
@mdimjasevic
May 04 2018 13:29
@etorreborre : I'm still trying to fix that specification that used to work with 3.8.6, but doesn't work with 4.2.0. It relied on fragments being eagerly evaluated, which isn't the case any more with 4.2.0. How do I go about it? There are global variables that have to be initialized at some point, which isn't happening in the right order any more.
Can I somehow change def setupTest: Fragments = ??? to a SpecStructure that will make it automagically work?
Eric Torreborre
@etorreborre
May 04 2018 14:03
Can you "force" the evaluation of fragments before including them in the spec
?
Marko Dimjašević
@mdimjasevic
May 04 2018 14:17
I figured it out. There was a fragment and I just turned its input arguments into lazy ones and that got it working.
Eric Torreborre
@etorreborre
May 04 2018 20:57
good to know :-)