Re: Tool to detect who broke a particular test

"[email protected] [junit]" <[email protected]> 08 Jun 2014 05:22:28 -0700
Newsgroups gmane.comp.java.junit.user
Message-ID <[email protected]>
I know bisect, and a per commit build should be the way to go.

I also know that this is more a cultural problem than a technical. We need a smart tool to teach the people not to commit not working code and that the single developer who broke a test is responsible to fix it. It is is much easier to let a tool detect the problematic commit instead of letting someone go thru each commit of the last day and after a few hours finally blame the one who caused the problem...