In the last episode there was a test failure with a misleading error message. I will evaluate JMock and EasyMock to see whether they would produce better error messages than Mockito.
2012-02-22
2012-02-19
Let's Code Jumi #124: One Failing Test (Part 1)
Begin adding support for reporting test failures. Let's first focus on getting just the number of failed tests reported, and leave reporting the stack traces for later.
2012-02-16
Let's Code Jumi #123: Hunting Concurrency Bugs (Part 2)
Adding the rest of the JSR-305 annotations and doing some performance testing for the thread safety checker.
2012-02-12
Let's Code Jumi #122: Improved Stack Traces
Because of the way how Java shortens chained strack traces, the stack traces in last episode were a bit confusing to read, so let's improve that before continuing with more concurrency testing.
2012-02-01
Let's Code Jumi #121: Hunting Concurrency Bugs (Part 1)
Adding JSR-305 annotations (@NotThreadSafe etc.) and actually finding one concurrency bug, so our doubts were not unwarranted.
2012-01-29
Let's Code Jumi #120: Finishing Touches
Some refactoring to improve thread-safety checker's exception messages before starting to use it.
Subscribe to:
Posts (Atom)