andrewmcdonagh wrote:
On Nov 26, 4:25 pm, Arne Vajh?j <a...@vajhoej.dk> wrote:
andrewmcdonagh wrote:
Having been asked how to unit test a servlet without using a container,
so much lately, I thought an example here might help - certainly should
help if the search engines pick it up.It should be noted that this code does not implement the full
functionality of the container context, which imposes some restrictions
on what the servlet can do.
If it is in any way possible, then I will find a Tomcat on the
dev box and Cactus a better test, because it has the full
container environment.
That's right - and its purposely that way, as its a its a unit test -
its testing the helloworld class I wrote - just the current behaviour
within my servlet - not how the container works.
The (preferably) automated integration and system tests do that job,I am not talking about testing the container.
But this way of unit testing assume certain things
about the implementation in the servlet.
If the implementation is changed (like caching
in session or application), then you need to
modify the unit test to supply more of the
container environment.
If you use a container and Cactus, then the unit test
can focus on the interface.
test rarely needs changing. Sometimes they may need extra test case