Hi Gabriele, Cactus is about *unit testing* *server side* components. It doesn't address client side unit tests nor functional end 2 end tests.
Thus I confirm Cactus is not adequate for your need. Why don't you simply use JUnit + mock objects/stubs? Thanks -Vincent Wanna see JUnit in Action? (http://manning.com/massol) > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Gabriele Carcassi > Sent: 13 March 2004 19:20 > To: [EMAIL PROTECTED] > Subject: Testing client server communication > > Hi all, > > I don't seem to find a clever way to use cactus to test the client/server > communication of my application. I wonder if any of you can provide with > an > insight, or can confirm that cactus is not sufficient. > > I have two classes, Client and Server. The first has a set of > Client.fireXxx, and the other has a corresponding set of Server.onXxx. > Calling Client.fireXxx will trigger an http client to connect to a > servlet, > which then calls the Server.onXxx methods. > > I want to test the communication: in the setUp pop up the client and a > mock > server, and have a testXxx call the Client.fireXxx and test whether the > mock > server received onXxx. > > How would you do it? > > Thanks, > Gabriele > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
