Hi there,I've now started trying to use loadUI and I've been trying to integrate it with my existing SoapUI project. I add a soapUI runner to a new loadUI project and select the required SoapUI test case. Yet when I use "Run Once" it completes with 1 failure listed. When I run the same testcase in SoapUI directly it runs without any hassle. Steps to re-create:1) I've created a new project in loadUI and added a soapUI runner to it. 2) I use Browse to navigate to the required soapUI project3) I select the desired testsuite and testcase via the dropdowns4) I've added a Table Log to the Results output of the soapUI runner5) I've added a Table Log to the Errors output of the soapUI runner6) I select "Run Once" on the soapUI runner7) The Completed and Failed counts on the soapUI Runner both increase by 18) I've captured the output at this point from the background DOS window of loadUI and attached it to this posting9) The Results and Errors Table Logs remain blankI suspect I've done some newbie loadUI / SoapUI integration mistake and hope this is easy / quick to solve. Many thanks in advance for the help...Kind regardsAdamNB:a) On the loadUI homescreen, I've previously selected Workspace -> Settings -> SoapUI and selected the batch file we use to launch SoapUITool Info:loadUI 1.0.1SoapUI 3.6.1

Hi Adam,judging from the log it seems your project needs the OdbcJdbc driver, please copy this jar (and any other external dependencies) into folder named "ext" under the loadUI folder.Also, the reason that you are not getting any entries in the TableLogs is that your test is not running (terminal connections only propagate messages when a test is running). Just start the test and you should get contents in the tablelogs when pressing the Run Once button. (You can temporarily disable any generators via their on-off switches)Hope this helps!regards,/Oleeviware.com

Hi there,I've tried finding an "ext" folder directly under "\loadUI-1.0.1", but found one under "\loadUI-1.0.1\jre\lib\ext" instead, is this the one you meant?We've tried updating the classpath defined in loadUItest.bat to read as:set CLASSPATH=.;C:\Adam\eviware\loadUI-1.0.1\jre\lib\ext\;lib/*;C:\Adam\eviware\;C:\Program Files\Java\;C:\Program Files\JavaFX\;I've also seen in my SoapUI code where I create the database connections I import the "groovy.sql.Sql" library.I've tried running the SoapUI testcase once from loadUI again but unfortunately still no joy...I see the following errors listed in the DOS command window:ERROR [SoapUI] An error occured [sun.jdbc.odbc.JdbcOdbcDriver], see error log for detailsjava.lang.ClassNotFoundException: sun.jdbc.odbc.JdbcOdbcDriverError [SoapUI] An error occured [Cannot invoke method getTestStepByName() on null], see error log for detailsjava.lang.NullPointerException: Cannot invoke method getTestStepByName() on null objectHave I missed something silly? I've not been able to find the OdbcJdbc driver directly, from what I could see on the net its included in the standard RT.jar that is part of the Java JDK. Help! (Thanks!)Kind regardsAdam

Hi Adam!Hm.. how exactly are you using the JDBC Driver? via a groovy script or a JDBC Connection?If the former, please try adding the following statement to your groovy code before using the driver:com.eviware.soapui.support.GroovyUtils.registerJdbcDriver( "sun.jdbc.odbc.JdbcOdbcDriver" )and if that doesn't help could share your project or give us enough details so we can try to reproduce?thanks in advance!regards,/Oleeviware.com

Hi there,Okay here goes...1) On my XP Professional SP2 2002 SP2 via Control Pannel -> Administrative Tools -> ODBC Data Source Administrator I've defined a User DSN entry for our Access Database using the Microsoft Access Driver (*.mdb, *.accdb)2) Within my SoapUI testcases I use Groovy Script steps when getting data from the external Access database3) At the start of each Groovy script I have import groovy.sql.Sql4) I then define a connection to the external database viadef sql = Sql.newInstance(context.expand('jdbc:odbc:<ODBC_Datasource_Name>), context.expand(' '), context.expand(' '), "sun.jdbc.odbc.JdbcOdbcDriver")5) I then create a results set viadef res = sql.firstRow("SELECT * FROM [<Access Database view name]....")NB: I use an Access Database view instead of directly accessing the underlying database table(s)That's pretty much it...I will also now try creating a little dummy project doing the above and attach it to the posting. Afraid I can't attach the actual work project due to various issues.Kind regardsAdam

Hi,I've been able to create a set of sanitized project files to help reproduce this issue which I've attached to this posting. They are a loadUI project, a SoapUI project, an Access database, and the logfile snapshot when trying to use the "Run Once" button in the loadUI project. You'll need to create an ODBC connection via Adminstrative Tools as described above.Hope this helps...Kind regardsAdam

"Run Once" in soapUI Runner fails to execute SoapUI testcase

16 Replies

Kathryn_O_Malle
Contributor
15 years ago
Hi Ole,

Did you mean me personally when you were asking for an upload of a full script to show the problem?
Just checking as I uploaded recently in this discussion a full SoapUI project, LoadUI project, access database, error log... With that one I encountered the same glitch even when all the SoapUI script was doing was connecting to the database and logging a single value via a loginfo command.

Kind regards
Adam
Kathryn_O_Malle
Contributor
15 years ago
And additionally I'm using the 1.0.1 release not the nightly build...

Again thanks...

Kind regards
Adam
SmartBear_Suppo
Alumni
15 years ago
Hello,

It is likely that this is related to one of the issues which has been fixed in the nightly build version of loadUI, please try downloading it from here. Make sure to either uninstall the old version first, or to install the new version into a different directory (do not "overwrite" the old version with the new one, it may cause problems). If you are still getting an error with the newest version, please attach an updated error log.

Regards,
Dain
eviware.com
Kathryn_O_Malle
Contributor
14 years ago
Hi,
After a break I'm able to update on what I've been able to achieve with this one. I've also attached a set of support files with error logs, etc to help out. I've determined the following points in trying to get LoadUI to run my SoapUI project.
1) The SoapUI testcase is happy to run in standalone mode without any modifications
2) When I try and use LoadUI to execute the SoapUI testcase using a nightly build version of LoadUI I still encounter an error (please see error log "24Jan2011_LoadUI_Error_Log PRE ext folder creation")
3) When I add an "ext" folder directly beneath the LoadUI home directory and place into it the rt.jar file I get a different error (please see error log "16Feb2011_LoadUI_Error_Log JDBC connection NOT registered")
4) Only when I also add in an additional line of code to my SoapUI testcase to register the ODBC connection will the test case run successfully

// ** Extra line of code here...
com.eviware.soapui.support.GroovyUtils.registerJdbcDriver("sun.jdbc.odbc.JdbcOdbcDriver")

From the above I think i have found the following integration issues (with the described workarounds):
a) The "/ext" folder is not automatically created during the LoadUI installation procedure
b) Any jar files required by the tools must be placed into the "ext" folder in (a)
c) As per the attached start up batch files, it does not appear that any supplied class path definitions are used right now (as the batch files used to start both LoadUI and SoapUI contain classpath definitions)
d) Each time an ODBC connection is used in a SoapUI groovy script step there must be an associated ODBC registration line of code (not required when running the SoapUI testcase in standalone mode)

Am I right in thinking that the above are "features" of the current LoadUI version? If yes do I need to cross-post them to the LoadUI bug forum for you?

Kind regards
Adam Hall
Support+Files+16Feb2011.zip30 KB
SmartBear_Suppo
Alumni
14 years ago
Hi!

thanks for your fantastic efforts!

Regarding these issues:

1) True, this will need to be fixed in our installer
2) This is true for jar files required by soapUI tests only
3) We'll have to look into this
4) Yes, due to how JDBC drivers are handled internally in Java there is unfortunately no easier way to get them working in loadUI also

I'll add issues 1-3 to our backlog.

regards!

/Ole
eviware.com
vasanthdharmara
14 years ago
Regarding the Hermes problem; Hermes (and thus JMS support) does unfortunately currently not work in loadUI, we hope to have that resolved in a future release.

kind regards,

/Ole
eviware.com

Any idea when we can look forward to the JMS support? Anything in the nightlies?

Forum Discussion

"Run Once" in soapUI Runner fails to execute SoapUI testcase

16 Replies

Recent Discussions

ReadyAPI "java.lang.OutOfMemoryError"

Nested Loops

Bug in LoadTest context.RunCount / TotalRunCount

Related Content

"Run TestCase" and use properties of target TestSuite

TestStep "Run TestCase" works different in 1.5.0 (Snapshot)

Allure report is generated only for the executed "Run TestCase" step