> -----Original Message----- > From: Nicholas Lesiecki [mailto:[EMAIL PROTECTED] > Sent: 02 November 2003 17:14 > To: Cactus Developers List > Subject: Re: Serializing test case classes > > (Sorry I'm late in jumping onto this thread) > > This seems like a good idea because it will finally eliminate the > counterintuitive behavior of the test state not persisting from the client > to the server. However, will the test be reserialized and sent back to the > client to be finished? It seems like the process should be symmetrical... >
In JUnit, the test result is not hold in the test case instance. The test result is already "serialized". We are serializing in XML and I'd like to keep that feature as it's quite useful and allows to run cactus tests from a browser (even applying a stylesheet on the client side). Independently of this we could send back the test case instance to the client but it becomes really complex to implement (it will require one addition HTTP request). > > It might be good to keep the > > current behaviour as a fallback if the test case is not serializable. > > I'm -1 for having two modes. I doubt many users are taking advantage of > the > non-Cactus suite method of running tests, and requiring them to make the > tests serializable seems like a small burden. I'm not sure I agree. I think I'd prefer to find a solution to support existing ServletTestSuite tests. One solution is to continue to support the existing mechanism, possibly deprecate it if we think the new one is better( but that's to be proved first). -Vincent [snip] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
