Vincent
"You're right is wasn't mentioned. My initial goal was to have for example a
single ServletTestCase class that could be used for both MO and IC. Thinking
about it, I have found 2 things... Now I am interested by your thoughts on
this."
I agree with Russell - if it requires base class specialization, then
perhaps it is best to dump the MO entirely and continue to focus Cactus on
in-container testing, so I shall await your response to him before
commenting further. One minor suggestion if you go ahead with MO is to name
the in-container base classes without the "IC" prefix. If you decide to back
out the MO later on, you do not have to explain why your standard base
classes are named "IC*".
"Yes, you are right about the 2 sets of classes (IC and MO tests)."
I am more in favor of dropping MO entirely. Maintaining two testing code
bases for a project is just too complicated and fraught with error.
"Yes, but it already exists. It's called Watchdog"
I drop all requests for a Cactus-Container module testing containers
themselves :).
Tom
