I've been given the source code for an existing Java application (let's call it "WebApp") that needs to be tested . It's deployed into Glassfish as a WAR file. This is customer code so would like to avoid modifying the WebApp POM if I can help it.
So I'm creating a separate project (in Eclipse) to do the testing. The new project needs to call methods directly on various WebApp classes. I tried referencing the WAR file as a Maven Dependency but after doing this it doesn't show up in Maven Dependencies in Eclipse - see below:
<<< No WebApp war/jars here >>>
You have several options, in decreasing order of preference:
Deploy the war, fire HTTP requests at it, check the database separately. No access needed to the webapp's classes. This is the cleanest option and most maintainable.
Use Arquillian to deploy the application along with your tests and run them.
You would need to add
maven-war-plugin's config in the POM of the original war. Your Test project needs to depend on
[artifactid]-classes instead of
artifactid. Your tests run within Glassfish (Arquillian deals with starting up Glassfish and deploying the war).
Arquillian has a bit of learning curve.
Use something like Spring's HTTPInvoker to expose the classes you want to test to your test code. Your tests run in a separate JVM to Glassfish, and connect to the classes under test using HTTP. You still need to change the POM like in the in-container case. This might be tricky if your WAR isn't Spring-based, and is quite invasive to the original application. You may also run into problems with serialization.