Caching issues - Environment Testings
We have a composite project with different environments (testing, staging) set up, and the default is testing environment. The two environments have different end points and JDBC connections (differe...
Forum Discussion
Hi,
Thanks for the reply.
I could replicate the issue in SoapUI GUI while running between environments.
If I open the Data Source step in any failed case, I notice the Connection is set to NONE (instead of testing/staging JDBC connection).
I added a test step to log the connectionString after the DataSource step. The connectionString is updated properly while running between environments.
It seems the JDBC connection is NOT reset (close the connectoin to testing db and open a new connection to staging db) while switching to a new environment.
In addition, is there any workaround for the JDBC connection issue you mentioned below?
I tried to put a Groovy script at the Event handler as described in the following post, but it does not work.
http://forum.loadui.org/viewtopic.php?f ... hilit=1210
Thanks again for your help.
Thanks for the reply.
I could replicate the issue in SoapUI GUI while running between environments.
If I open the Data Source step in any failed case, I notice the Connection is set to NONE (instead of testing/staging JDBC connection).
I added a test step to log the connectionString after the DataSource step. The connectionString is updated properly while running between environments.
It seems the JDBC connection is NOT reset (close the connectoin to testing db and open a new connection to staging db) while switching to a new environment.
In addition, is there any workaround for the JDBC connection issue you mentioned below?
I tried to put a Groovy script at the Event handler as described in the following post, but it does not work.
http://forum.loadui.org/viewtopic.php?f ... hilit=1210
Thanks again for your help.