I read the xUnit test patterns.
http://martinfowler.com/books.html
There is the expression "Churchill KO" in Martin Fowler, like this ...
If you go to junit.org, you will see a quote from me: "never in the field of software development so much so many so few lines of code." JUnit was criticized as secondary, something that any reasonable programmer could offer on the weekend. It’s true, but it’s completely lacking in meaning. The reason JUnit is important and deserves Churchill's knockout is that the presence of this tiny tool was necessary for a fundamental shift for many programmers. Offset when testing has moved to the front and center of the programming. People have advocated this before, but JUnit has done it more than anything.
I did not look for “Churchill knockout”. Could you help me understand what this means? Thanks in advance.
source
share