test-check

Hukka 2018-07-06T12:29:09.000302Z

strgen helpfully mentions test.chuck for more comprehensive regex support. But is there then any reason to not use test.chuck always?

2018-07-06T12:48:01.000368Z

test.chuck isn't an alternative to test.check, it's a pile of miscellaneous utilities to go with it

2018-07-06T12:48:25.000309Z

so it's fine to have it around if you want, but if you're not using any of its parts then it's not providing any value

Hukka 2018-07-06T12:48:26.000354Z

Sure. I'm mostly looking for helpers to generate the input

Hukka 2018-07-06T12:49:07.000224Z

strgen is purely for making strings based on regexes, but mentions that test.chuck has more comprehensive support. I was just wondering is there ever any reason to use that, instead of test.chuck

2018-07-06T12:50:35.000124Z

oh I'm sorry

2018-07-06T12:50:40.000395Z

I missed the part about strgen

2018-07-06T12:51:41.000011Z

it looks like strgen targets portability?

2018-07-06T12:51:50.000117Z

i.e., it probably works in cljs

2018-07-06T12:52:09.000300Z

there's a half-pull-request in test.chuck for adding cljs support, but it needs some more work

Hukka 2018-07-06T12:54:11.000155Z

I see, thanks! Good to know – though for now I'm just speccing the backend code, there's plenty of fiddly data munging on the frontend too

Hukka 2018-07-06T15:14:41.000422Z

Not sure if this belongs here, as it's really a spec problem... but if running (stest/check) without any arguments gives an exception when check can't create any input that passes the input predicates, is there any way to know which specced function is causing problems?

2018-07-06T22:45:08.000161Z

lot more likely to be answered in the spec room I'd wager

2018-07-06T22:45:17.000040Z

they have over ten times more people