Forum Discussion

pembertonrw's avatar
pembertonrw
Contributor
12 years ago

Run soapUI Via Command Line or Maven on Continuous Build

I'm currently looking into automating the soapUI tests in a project written in Java and I am in two minds of whether the CI should us the Maven plug-in or run it via command line. I'm tempted to go down the Maven route which will mean I don't need to install soapUI onto the various servers and might make it easier for the dev's to run it locally. But I was wondering if anyone has come across reasons why using the Maven plug-in?

3 Replies

  • SiKing's avatar
    SiKing
    Community Expert
    12 years ago
    Personally I always chose Maven if I can, specifically for the reason you mentioned: it handles all dependencies for you. Keep in mind that if you get into any kind of advanced Groovy scripting you can use any jars out there.
    About the only drawback, and personally this is a very small drawback, is that SmartBear releases Maven later than the regular binaries. Although I hear they are working on that. >:D
  • redfish4ktc2's avatar
    redfish4ktc2
    Super Contributor
    12 years ago
    Hi
    I totally agree with SiKing; you don't need to install soapui nor configure your build to know where it is installed. Migration is easy, just modify the version of the plugin in your pom
    Note: this could be done with other build tools like gradle if plugin/scripts existed

    About the maven artifacts availability, they are now (starting from 4.6.1) available at the same time as the soapui distribution.
    For example, the 4.6.3 version has been released on 18-dec-2013, maven artifacts also (see http://www.soapui.org/repository/maven2 ... ar/soapui/)
  • pembertonrw's avatar
    pembertonrw
    Contributor
    12 years ago
    Thanks for the replies I took your advice and went down the Maven route, does seem a lot easier to setup than installing soapUI on the various build servers.