I'm currently updating our Jenkins scripts for Behat 3 compatibility. Once thing that I wasn't anticipating is that the output from Behat has changed substantially. Previously, we parsed the various output files to pull out useful information and email developers about failures.
It looks like the code that does this will need to be re-written, and probably simplified, so I wanted to ask what others do in terms of notifying people about failed tests.
As we run tests every night rather than after each commit, we can't just email the person who last committed a change. Our previous strategy was to determine who last edited each feature file that failed and email them details of the failures from that feature. We did this by using the name of the junit XML file which corresponded to the failing feature file, although this correspondence no longer exists in Behat 3.
Any pointers on a smart way of notifying people about failures would be appreciated, especially if there's something like a Jenkins plugin to do so, rather than having to do parsing of outputs via a script!
Thanks Rajesh, that's clever! Once we've stabilised our codebase following out 3.1 merge, I'll look at whether it would be feasible to implement this.