Comments on: Middleware integration testing with JUnit, Maven and VMware, part 3 (of 3) http://blog.xebia.com/2010/01/07/middleware-integration-testing-with-junit-maven-and-vmware-part-3/ Mon, 26 Jul 2010 20:40:47 +0200 http://wordpress.org/?v=2.8.4 hourly 1 By: Vincent Partington http://blog.xebia.com/2010/01/07/middleware-integration-testing-with-junit-maven-and-vmware-part-3/comment-page-1/#comment-93767 Vincent Partington Fri, 08 Jan 2010 10:05:09 +0000 http://blog.xebia.com/?p=3939#comment-93767 <strong>@Eru:</strong> Setting up the expected state is indeed not that hard, <em>by hand</em>. As for scripting that part: automating the middleware to be in a certain state is exactly the thing we are trying to test! So it's actually not <em>that</em> easy. Which is we set it once manually and then have the tests clean up after themselves (which is basically the automation you are seeking). And if that fails, we use revert the VMware image. The reason we use VMware to revert the configuration is because we it is a generic way to do this for all the different middleware systems we integrate with (WebSphere, WebLogic, JBoss, Apache for now, but soon ALSB, WebSphere MQ, WebSphere Portal, etc.) without having to figure out how to backup and restore their configurations. There is not so much effort involved actually. Setting up a VMware image is surprisingly easy. Another advantage here is that only one person on our team has to spend time setting up that image and the rest can just copy it! At XebiaLabs we are also very excited about the possibilities of using VMware to ease deployment as my colleague Robert van Loghem <a href="/2009/12/21/future-of-deployment-part-1-monuments-vs-cheap-housing/" rel="nofollow">has blogged about</a> recently. Ease of deployment is one of the big advantages of cloud computing. @Eru: Setting up the expected state is indeed not that hard, by hand. As for scripting that part: automating the middleware to be in a certain state is exactly the thing we are trying to test! So it’s actually not that easy. Which is we set it once manually and then have the tests clean up after themselves (which is basically the automation you are seeking). And if that fails, we use revert the VMware image.

The reason we use VMware to revert the configuration is because we it is a generic way to do this for all the different middleware systems we integrate with (WebSphere, WebLogic, JBoss, Apache for now, but soon ALSB, WebSphere MQ, WebSphere Portal, etc.) without having to figure out how to backup and restore their configurations.

There is not so much effort involved actually. Setting up a VMware image is surprisingly easy. Another advantage here is that only one person on our team has to spend time setting up that image and the rest can just copy it! At XebiaLabs we are also very excited about the possibilities of using VMware to ease deployment as my colleague Robert van Loghem has blogged about recently. Ease of deployment is one of the big advantages of cloud computing.

]]> By: Eru http://blog.xebia.com/2010/01/07/middleware-integration-testing-with-junit-maven-and-vmware-part-3/comment-page-1/#comment-93766 Eru Thu, 07 Jan 2010 20:40:36 +0000 http://blog.xebia.com/?p=3939#comment-93766 Read the blog, although a lot of things went over my head but still found it interesting. everything sounds perfectly fine but i am not sure about two things first thing is Defining the expected state for the target middleware. This is not very difficult as far as you know what you want in your configuration.... i accept it will be very difficult when it comes to performance tuning coz that takes a lot of time to try different combination and then analyzing the results from those combinations, but if we are clear about the configuration we want for our testing environment we can easily (not so easy) automate this using UNIX scripting. Second thing is why are we investing so much effort in VMWare, why are we not taking a backup of master configuration of our App Server and in case our test fails, then revert to original configuration. Read the blog, although a lot of things went over my head but still found it interesting. everything sounds perfectly fine but i am not sure about two things

first thing is Defining the expected state for the target middleware.
This is not very difficult as far as you know what you want in your configuration…. i accept it will be very difficult when it comes to performance tuning coz that takes a lot of time to try different combination and then analyzing the results from those combinations, but if we are clear about the configuration we want for our testing environment we can easily (not so easy) automate this using UNIX scripting.

Second thing is why are we investing so much effort in VMWare, why are we not taking a backup of master configuration of our App Server and in case our test fails, then revert to original configuration.

]]>