Search
Recent Posts
- Automated testing software for your web app
- How to use Google App Engine Java with Maven
- OpenID, Google App Engine, and Yahoo
- trac plugin for Gliffy released
- In praise of scrumy
- Continuous Integration for QUnit tests
- TDD in Javascript with QUnit
- Consider having two backlogs
- Disprove that the site doesn’t work
- Collaboration vs Interruption
Tags
Archives
- April 2010
- January 2010
- November 2009
- January 2009
- May 2008
- February 2008
- November 2007
- October 2007
Syndication
Don’t make a mockery of testing
If you’ve worked on a Java team that valued test automation, you’ve probably been exposed to EasyMock or JMock.
While well intended, these tools imply that teams should focus their testing efforts on granular unit tests that provide maximum code coverage. Often these teams do this at the expense of integration tests. Since time is always finite, we suggest you spend the majority of your testing time on integration tests. Only after you’ve exhausted all integration testing possibilities should you be tempted to use mocks.
FTP passive mode and Java Sockets
Okay, my first blog entry. Be gentle…
I just spent most of the day diagnosing this problem with an FTP server and a Java application, and I thought maybe I could save someone the effort some time. (more…)
Replacing gcj on Fedora
Due to licensing issues, Linux distros can’t distribute Sun’s JDK. Instead they use gcj, which in my experience is utterly broken. I just provisioned a new Fedora 7 VPS server today, and as part of getting tomcat and ant installed I needed to replace gcj with Sun’s JDK. Here’s the steps:
(more…)
Unit testing Flex
This is part 3 of my exploration into Flex. In part 1 I wrote a simple weather forecast application. In part 2 I refactored the non-UI code into separate ActionScript classes. In this part I discuss unit testing those classes using FlexUnit. In short, FlexUnit allows you to run unit tests from the command line.