Reverse use of GIT bisect

Here is an interesting post on how to make reverse use of GIT bisect to find fix-introducing commits instead of fault-introducing commits. (The link is broken, but the original post can be found at What it boils down to is this:

Since git bisect was designed to find regressions, we need to flip the meanings of “bad” and “good” in order to use it to find a fix.

It seems to me that using this would be helpful for anyone wanting to use the regression test selection (RTS) method we introduced a few years back.

Check my publications page for more details.

Update 2014-01-01: this reverse use of GIT bisect has recently been covered on stackoverflow.

One-liner test cases

There are many kinds of testing. Detailled scripted manual test cases are quite popular but an article at might be an eye-opener if that is your favourite kind of test case. According to the article, these test cases are a waste of time and effort and demeaning to the…

Continue reading

Do I have a healthy test suite?

Source: Owned by the authorWith TDD etc we are all assuming that we have a healthy test suite. Now some researchers from the Netherlands and Belgium have published a way to actaully measure this. Their idea is to plot on one axis the percentage of the total code base that…

Continue reading