test-check

2017-09-13T10:54:04.000066Z

hey, is there something generated by clojure.test.check.generators/any that can break the output of the test runner?

2017-09-13T10:54:11.000279Z

i got this fail

2017-09-13T10:54:15.000281Z

FAIL in (??round-trip) (:)
expected: (= e (parse (string d)))
  actual: (not (= [["_Iq1WSpRhKoq+0M?1?!CV-I+GD-ul?s**R?!*!6arO*hmmz!" "6KnðåómÔ(OD{hl$g\tÉ\"²Å¹Þˆß’" "6

2017-09-13T10:54:43.000200Z

it's like the string somehow didn't finish or something

2017-09-13T10:55:57.000067Z

the string not finishing smells more like your output was truncated somehow

2017-09-13T10:56:33.000128Z

the worst thing about gen/any that could cause problems is that it can generate NaNs deep in the nested structure

2017-09-13T10:56:56.000033Z

which causes the whole thing to not equal itself, but maybe only under certain conditions

2017-09-13T10:57:12.000045Z

mmm

2017-09-13T10:58:02.000383Z

FAIL in (??round-trip) (:)expected: (= e (parse (string d))) actual: (not (= [["_Iq1WSpRhKoq+0M?1?!CV-I+GD-ul?s**R?!*!6arO*hmmz!" "6KnðåómÔ(OD{hl$g\tÉ\"²Å¹Þˆß’" "6Testing wheel.stylesheet.hoplon

2017-09-13T10:58:07.000208Z

it just stops...

2017-09-13T10:58:15.000006Z

and goes straight into the next test

2017-09-13T10:58:56.000211Z

you could bypass the test runner & printing by calling clojure.test.check/quick-check directly with your property and inspecting the return value

2017-09-13T10:59:43.000046Z

yeah, also i think what you said about NaN is going to derail me anyway

2017-09-13T11:00:15.000133Z

i might need a different approach