Fork me on GitHub
#test-check
<
2017-11-06
>
gfredericks14:11:29

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.

lucasbradstreet17:11:05

I think I’d like it.

gfredericks18:11:35

To be clear, it already does this.

gfredericks18:11:05

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

lucasbradstreet18:11:00

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.

mattly18:11:56

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

gfredericks19:11:03

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"}

gfredericks19:11:34

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

mattly21:11:55

interesting. Is defspec new?

gfredericks22:11:35

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

mattly23:11:27

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

gfredericks23:11:19

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