Testability Explorer: Using Byte-Code Analysis to Engineer Lasting Social Changes in an Organization’s Software Development Process. (Or How to Get Developers to Write Testable Code) Presented at 2008 OOPSLA by Miško Hevery a Best Practices Coach @ Google Abstract Testability Explorer is an open-source tool that identifies hard-to-test Java code. Testability Explorer provides a repeatable [...]

by Miško Hevery | 19 August 2008 | republished from alphaITjournal So you’ve figured out a better way of doing things, but how do you get everyone to change the way they work and start writing code in this better way? This is something I face daily in my line of work as a best [...]

A good definition of unit tests is a test which 1) runs fast <5ms and 2) when it fails you can determine what is wrong without resorting to a debugger. This implies that a unit-tests must execute very limited amount of code so that the failures are well isolated. The ability to be able to [...]

In theory I know what Aspect-Oriented-Programing (AOP) is. In practice I have never used AOP! (AspectJ, AspectWerkz nor any other AOP framework). Nevertheless I am going to go out on a limb and make a bold statement. AspectJ is way better then AspectWerkz! I would love to hear about any anecdotal evidence which can support [...]

Last year I noticed that I could refactor a piece of code and make it better without actually knowing what the code does. This made me realize that the goodness of the code is independent of its function. I also realized that when I was looking at code to refactor I went thought a mental [...]