Emitters

[Brian Marick]

Midje allows for plugging in alternate "emitters (of failures)". It seems the alternates, most particularly the junit one, are broken in the current version. This is embarrassing.

However, I'm not the one to fix this. We use Midje in our Clojure apps, but we just use the plain emitter and have our continuous integration server check for a non-zero exit status. More to the point, we're not a Java shop, so I have no understanding of what people want from JUnit-style failures.

If someone took this on, it would be swell.

Alternately, I'm inclined to deprecate alternate output styles and hide the documentation about how to create them.
https://github.com/marick/Midje/wiki/Customizing-reporting

Thoughts?

--------
Latest book: /Functional Programming for the Object-Oriented Programmer/
https://leanpub.com/fp-oo

[Eric Arthen]

On Sunday, May 18, 2014 7:18:50 PM UTC-4, Brian Marick wrote:

> Midje allows for plugging in alternate "emitters (of failures)". It seems the alternates, most particularly the junit one, are broken in the current version. This is embarrassing. 

That is a shame, as I'm on a new clojure project I was thinking of trying to use the junit emitter, but had not yet tried it.

> However, I'm not the one to fix this. We use Midje in our Clojure apps, but we just use the plain emitter and have our continuous integration server check for a non-zero exit status.

> More to the point, we're not a Java shop, so I have no understanding of what people want from JUnit-style failures. 
 

The reason I want it is for good integration with my continuous integration system, so it can tell me more than "success"/"fail" across a whole set of tests with out my having to look into the log files for each separate test run. Also it can give counts of the number of tests, and let me drill in and see the history of individual tests. For example, if a specific fact failed today, is this this first time it has ever failed, or has it failed a number of times in the past few weeks. What was the first check in that caused that failure. 

When I first started using Clojure the fact that Midje did not support junit output was almost enough to prevent me from using it. (Until I compared Midje to the other options.)

We use JetBrain's TeamCity CI system, other systems have similar features built on the JUnit style output, such as opensource Jenkins & Hudson.

This is the kind of feature that is not important everyday and when tests are all being successful, but can be a godsend in larger projects when things get messy or when you want a quick sense of the kind of test coverage a module has since you can see the name of each fact in each test.

So it is certainly worth noting the the documentation that this is current broken and pointing to the issue with details. (https://github.com/marick/Midje/issues/263 )

I'd like to say I'd take a look at it, although it may not be that realistic. I'll see if I can get to it.

Eric

 

[Chris Blom]

Please keep the documentation about customizing reporting, I use it sometimes to make variations of the default emitter for

purposes like timing facts to find slow tests or to collect failures in project with lots of tests

[Brian Marick]

I've put a link to [[Customizing Reporting]] in the Reference section of
the wiki.

> --
> You received this message because you are subscribed to the Google
> Groups "Midje" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to midje+un...@googlegroups.com
> <mailto:midje+un...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.