test-check

2017-11-06T14:23:29.000351Z

How do folks feel about test.check printing success summaries? I'm processing a patch that makes this configurable, but didn't know whether it should stay on by default, since I don't know how many people like it.

lucasbradstreet 2017-11-06T17:56:05.000164Z

I think I’d like it.

2017-11-06T18:23:35.000211Z

To be clear, it already does this.

2017-11-06T18:30:05.000256Z

And currently it's not configurable I'm trying to decide between A) make it configurable, defaulting to on B) make it configurable, defaulting to off

lucasbradstreet 2017-11-06T18:34:00.000371Z

Oh, you mean printing the current summaries? Ah, I misread it. I think I prefer defaulting to on, especially since it’s the current behaviour.

mattly 2017-11-06T18:56:56.000016Z

@gfredericks can you provide an example of what you mean? I’m not entirely clear by “success sumaries”

2017-11-06T19:05:03.000492Z

This is a defspec thing in particular Right now when a defspec test runs, and passes, it prints something like:

{:result true, :num-tests 500, :seed 1509994998441, :test-var "the-name-of-my-test"}

2017-11-06T19:05:34.000175Z

you can compare this to the behavior of a regular clojure.test test, which prints nothing on success

mattly 2017-11-06T21:29:55.000392Z

interesting. Is defspec new?

2017-11-06T22:37:35.000326Z

no, defspec is the standard clojure.test integration that's been around for quite a while

mattly 2017-11-06T23:32:27.000340Z

ah, I guess I’ve only really ever used test.check in the context of test.chuck’s checking

2017-11-06T23:33:19.000049Z

Try to say "test.check in the context of test.chuck's checking" five times fast

mattly 2017-11-06T23:34:38.000036Z

😄