Forum Discussion

EMC_Support's avatar
EMC_Support
Contributor
13 years ago

List of dependencies to integrate soapUI 4.5.0 as JUnit test

Hi,

I listed in my BuildConfig.groovy dependencies entry the following:

test 'eviware:soapui:4.5.0-SNAPSHOT'
test 'eviware:soapui-xmlbeans:4.5.0-SNAPSHOT'
test 'eviware:wsdl-xmlbeans:1.1'
test 'eviware:wadl-xmlbeans:1.1'
test 'eviware:soap-xmlbeans:1.2'
test 'eviware:ext-xmlbeans:1.2'
test 'eviware:j2ee-xmlbeans:1.3'
test 'eviware:policy-xmlbeans:1.5'
test 'org.apache.commons:commons-cli:1.0'

However I get the following error:
Compilation error compiling [integration] tests: java.lang.NoClassDefFoundError: com/eviware/soapui/config/InvalidSecurityScanConfig

Do you have a list of the dependencies needed to integrate soapUI 4.5.0 as a JUnit testcase, purely from maven artifacts ?
  • Hello,

    It should be in soapui-xmlbeans.jar. I'm not sure if your configuration is correct ( Grails ? ).

    robert
    /Smartbear
  • It needed explicit import on the grails test.

    I'm still having problems at runtime now, with soapUI not being able to find org.apache.xml.serialize.XMLSerializer even though xercesImpl-2.9.0 is on the dependency list. And no, explicit import on the grails test did not work :/

    When are you going to have a maven plugin that supports multiple projects per run of maven ?
    I am going to all this trouble just because of this bug of yours!
  • Hello,

    I'm sorry for troubles you have. Can you just point Grails to soapui lib folder :


    repositories {
    flatDir name:'soapUILibs', dirs:'/path/to/soapui/lib'
    }


    All I can say about maven plugin is that it is taken in consideration. I understand your frustration and I'm sorry.

    robert
    /Smartbear
  • I gave up this approach. It did not work at all.

    I am now using soapUI directly from Maven using the failsafe plugin to run the JUnit wrapped runners (so that I can run multiple projects...), against a cargo deployed container with the grails app.

    Not pretty but doable.