My question is basically one of design. I am trying to test a server side object that is neither a Servlet, JSP, or EJB. It contains no Struts code. It just contains an algorithm for building an HTML menu. My first guess is that JUnit should be used. Would anyone agree with this?
It's not server-side code (= code that needs a server to run). It's code that happens to run within an app server. If it's plain Java, then test it as plain Java, using plain JUnit, exactly as you say.
Remember this, though: Cactus /is/ JUnit; Cactus merely runs it transparently in an app server for you.
Also, in the application I am testing Session IDs need to be passed between pages. Is there a best practice for storing this in my testing package for reuse among the different test cases?
I don't understand this. I hope someone else did. If not, then please explain it differently.
--
J. B. Rainsberger,
Diaspar Software Services
http://www.diasparsoftware.com :: +1 416 791-8603
Let's write software that people understand
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
