Skip to main content

Blog Archive for mriem during December 2011

In the previous article we have worked out how to run the integration tests against Glassfish, but what about other versions of Glassfish or even other servers? Well, the infrastructure groundwork has been laid for that. Before we are going to reap the fruits we are going to explain the difference between downloading, installing and configuring your server within Cargo. The main reason...
In the previous article we added the Glassfish application server into the mix for testing. This looks all nice,but one might wonder how this would work in a parent project (POM) and child projects setup. Well it is fairly easy to accomplish. We will move all the bits first over to the new parent POM we are going to use. See below for what theparent POM will look like. <?xml version=&...
In the previous article we described a setup for integration testing. It did not explain how to do automatic deployment to an application server. Since we want to make it convenient to do integration tests we are now going to add Glassfish into the mix. Note that in the previous article we put the integration testing into a separate profile. We are now going to put it back into the normal build...
If you want to do integration testing using HtmlUnit and Maven the following sets you up for easy testing. 1. Create a Maven web application project 2. Add index.jsp page (or whatever flavor of framework you want to use). 3. Add HtmlUnit dependency 4. Write integration test for the index.jsp page 5. Add the profile to support running of the integration tests separate from the main build cycle...