This seems to happen to me no matter what project I’m on. I try to implement a simple (or not so simple) feature and end up exposing at least one bug that’s been hiding around for quite some time. As an illustration, I was adding a feature to Frame2 today to allow some parameters to [...]
read on »All posts filed in “testing”
Approaching the Finish Line
Frame2 is almost ready to be released as a new version. I may still make some changes, but it’s definitely in Release Candidate stage now. There are only a few things that I may add before testing the heck out of it: Upgrade unit tests to JUnit 4. There are a lot of tests, especially [...]
read on »A Consistent API is a Very Good Thing
I’ve been mucking around in the codebase, cleaning up pieces of the API that annoy me. Some bright person thought that it was a good idea to have a method that returns an Iterator to access a collection. I’ve been cleaning up all of these methods, changing them so that they return an actual collection [...]
read on »FindBugs Is Even Cooler Than I Thought
I’ve mentioned before that I’m using FindBugs to help make sure that the Frame2 code is up to snuff. The Eclipse compiler can catch a lot of things, bug FindBugs has some neat tricks up its sleeve to find things that Eclipse can’t. FindBugs uses static analysis of the code to search for patterns that [...]
read on »Unit Testing Web Applications is a Pain
I’ve finally reached the point where I hurdled my JAXB related validation issues, so another round of full unit testing is called for. Frame2 has two levels of testing: Unit tests that can be run outside of a servlet container. These include simple tests on discreet sections of the framework, and some tests written using [...]
read on »
