|
From: Luke B. <lb...@gm...> - 2005-11-15 09:53:43
|
That's a really interesting problem Grant, thanks for the feedback! I have definitely struggled with the same issue extensively. Generally, whe= n I find a smell that's bothering me in my test code, I go start searching junit.org <http://junit.org> to see if some java person has had similar issues, as it turns out with this particular problem - fortunately - we're not alone! The first and most important thing that you can possibly do, is stop testin= g your server with your client. Your client and server should each be tested independently of the network and of each other. There are quite a few great articles on junit.org <http://junit.org>discussing this very topic for Java applications. Here are a few links I found: Writing Networked Unit Tests: http://www.javaworld.com/javaworld/jw-07-2002/jw-0719-networkunittest.html Mock Objects 1: http://www-128.ibm.com/developerworks/library/j-mocktest.html Mock Objects 2: http://www.onjava.com/pub/a/onjava/2004/02/11/mocks.html JUnit.org Articles Index: http://www.junit.org/news/article/index.htm I hope this helps! Thanks, Luke Bayes www.asunit.org <http://www.asunit.org> |