search

nilswloka / lein-cucumber

A simple leiningen plugin for running clojure-based cucumber-jvm specifications.
The Unlicense
39 stars 26 forks source link

Better backtrace information? #16

Closed jeroenvandijk closed 12 years ago

jeroenvandijk commented 12 years ago

Hi Nils,

First off, thanks a lot for this work.

This is the first time I'm using Cucumber on the JVM, before this I've used it extensively with Ruby. I'm currently porting my Cucumber steps to Clojure from Ruby and I'm really missing some features, or I don't know how to activate them. Maybe this is a Cucumber JVM thing, but maybe you know how to activate them with lein-cucumber.

I'm running the following command:

 lein2 cucumber --glue features_steps

This is the output I got from a failing step:

..
FAIL in clojure.lang.PersistentList$EmptyList@1 (main_steps.clj:103)
expected: (= (-> (clojure.core/deref state) :response :status str) expected-status)
actual: (not (= "401" "201")).....

With this error I can see what step failed and how, but not in what scenario, I would love to know how to get some more info. And when I do:

tail -f target/test-reports/cucumber.out

I see duplicate lines and no mention of the above failure only of passing and pending steps.

Any ideas?

Cheers,

Jeroen

jeroenvandijk commented 12 years ago

Ah so after some more investigation I found a way to get more information:

lein2 cucumber --format pretty

I found this information by using help:

lein2 cucumber --help

This option, although maybe straightforward, is probably useful to add to the README.

I think the wrong formatting of the pretty output is due to Cucumber-JVM itself so I'll close this issue.

Thanks,

Jeroen