Getting more familar with J2EE, JBoss and MyEclipse I want to add more capabilities to my pocket of skills. Doing JUnit tests and test-driven programming for ages (: I want to test my EJB and Servlets/JSP classes. I was cross reading the internet and stuck on Cactus. It seams to be exactly what I am looking for (since it seams to integrate nicely within JUnit).
Does anyone has any hints how to set it up best?
While doing some serious investigation the following issues rasied:
I1: For non-J2EE testing I am using an additional source-folder within the same project (called src-test). The package structure is the same like the src folder. Therefore testing on package-level is easy and the test code is still seperated. I would like to do J2EE testing the same way. So the question is:
Q1: Is it practicable to use an additional src folder containing the tests?
I2: For unit testing I am about to use a second JBoss 3.2 server context (called test) and a database called test too. Therefore I run into the constraints of the deployment manager. (only deploy on one server of same kind). I think I can live with it. I only need to deploy on the default server two or three times a day I guess. Maybe I ll write a script… (simply copying the ear from one server to the other) And once a day I would like to run some functional tests without the deployed test methods. I think I can handle that, too.
Q2: Any other strategies preferable? Currently I am doing a database port, while working alone (just doing something usefull while balancing on the lerning curve) but soon I’ll get some mates 😉
Q3: What are common ways to test J2EE using MyEclipse environment?
Thanks,
Martin