Ability to omit list of not-yet-implemented examples

slagyr / speclj

pronounced "speckle": a TDD/BDD framework for Clojure.

MIT License

458 stars 58 forks source link

Ability to omit list of not-yet-implemented examples #121

Open hlship opened 9 years ago

hlship commented 9 years ago

Another way to improve the signal-to-noise level would be an easy way to not list all the pending/not-implemented examples at the end of the report ... just show me the failures and the final summary.

Basically, I tend to care about the pendings when I run a full test suite over all my test cases, but it's just clutter (and more scroll back) when I'm in an iterative test-fix loop at the REPL.

thesoftwarephilosopher commented 9 years ago

Totally agree, this would be a handy option when practicing TDD and having a lot of pendings. @slagyr, would you be open to such a feature?

slagyr commented 9 years ago

Sure. Presumably this would be a command line option. I have no problem with that.

On Feb 13, 2015, at 4:15 PM, Steven Degutis notifications@github.com wrote:

Totally agree, this would be a handy option when practicing TDD and having a lot of pendings. @slagyr https://github.com/slagyr, would you be open to such a feature?

— Reply to this email directly or view it on GitHub https://github.com/slagyr/speclj/issues/121#issuecomment-74336706.

hlship commented 9 years ago

I kind of see this as an additional argument to run-specs, with a default I can easily set somewhere.

I run my tests two ways:

frequently, in IDE, one namespace at a time (using Cursive)
occasionally, from command prompt, using leiningen

In the latter case, I don't mind seeing the "pending" characteristics (though having an easy way to silence there would be good). In the former case, which happens literally every few minutes, I'd love to not have the "meat" of my console output scrolled out of view by the "pending" messages.

arlandism commented 9 years ago

Handled in #125. When 3.3.0 goes out, this should be good to go.