com.microsoft.jdbc.SQLServer driver and Test Runner
I am actually using SoapUI Pro 4.5
We have many JDBC steps in our project that validate values in a SQL Server database.
When we run the suite from within the SoapUI client by going to the test case and clicking the "Run this TestCase" button, the test runs fine.
When we right click on the testcase and select "Launch TestRunner" and run the test, the test fails with the following error:
java.lang.ClassNotFoundException: com.microsoft.jdbc.SQLServerDriver
I have already tried/verified the following suggestions I have found on the forums.
1. The sqljdbc.jar file is in the bin/ext folder
2. We have a groovy script that loads the driver with com.eviware.soapui.support.GroovyUtils.registerJdbcDriver("com.microsoft.sqlserver.jdbc.SQLServerDriver")
Please help me figure out why the test case runs fine from within the SoapUI client, but not via the command line tool. Thanks.
We have many JDBC steps in our project that validate values in a SQL Server database.
When we run the suite from within the SoapUI client by going to the test case and clicking the "Run this TestCase" button, the test runs fine.
When we right click on the testcase and select "Launch TestRunner" and run the test, the test fails with the following error:
java.lang.ClassNotFoundException: com.microsoft.jdbc.SQLServerDriver
I have already tried/verified the following suggestions I have found on the forums.
1. The sqljdbc.jar file is in the bin/ext folder
2. We have a groovy script that loads the driver with com.eviware.soapui.support.GroovyUtils.registerJdbcDriver("com.microsoft.sqlserver.jdbc.SQLServerDriver")
Please help me figure out why the test case runs fine from within the SoapUI client, but not via the command line tool. Thanks.
. I have followed all the steps, but I keep getting the error that the driver is not found or the ClassNotFoundException occurs. I really want to get this working, my test script depends on SQL updates to the DB as the test steps execute. So far my trial of this software is not going well with respect to hooking up to the db...hopefully an easy fix/mistake on my end, but it looks like others are running into the same issue with the SQLServerDriver.