Fork me on GitHub
#test-check
<
2017-09-13
>
thedavidmeister10:09:04

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

thedavidmeister10:09:15

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

thedavidmeister10:09:43

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

gfredericks10:09:57

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

gfredericks10:09:33

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

gfredericks10:09:56

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

thedavidmeister10:09:02

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

thedavidmeister10:09:07

it just stops...

thedavidmeister10:09:15

and goes straight into the next test

gfredericks10:09:56

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

thedavidmeister10:09:43

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

thedavidmeister11:09:15

i might need a different approach