Forum Discussion

Scripps_Network's avatar
Scripps_Network
Occasional Contributor
13 years ago

[Reg] JDBC test step does not execute when changing the env

Hi Admin,
I have created a soap ui project in soap ui pro 4.5.1 and inside it i have around 20 test suites.
in each test suite i have jdbc test step to call the database and get the result of the query which i wrote in that jdbc test step.
in the project summary i have created JDBC connections for every environment - Dev, INT, QA, whichever i am using(double click the project, and go to environments tab, and then JDBC connections tab inside it)
so when i want to execute all the test suites in this project in Dev which is my default env, it works fine. But if i change the envs to INT or QA, JDBC test step is failing.
it is returning 0 rows. I have to manually execute this step instead.
Can you please resolve this issue?
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    Hi,

    thanks - this is a known issue that we just didn't manage to fix for 4.5.1 - we will notify here when it is fixed in the nightly.

    Sorry for your troubles..

    regards!

    /Ole
    SmartBear Software
  • Scripps_Network's avatar
    Scripps_Network
    Occasional Contributor
    13 years ago
    Hi,
    Thank you for working on this.
    We have verified the fix and it is working perfectly fine.
    But we want to point out one more issue related to maven SOAP UI pro plug-in 4.5.1
    We are facing the same problem with it.
    Can you please look into that?
  • erichmusick's avatar
    erichmusick
    New Contributor
    13 years ago
    Hi -

    Is there any sort of "known issues" list with the 4.5.1 Pro version of SoapUI? I ran into this issue as well and it took several hours of my time to realize what was happening and identify this forum post. It would be very helpful if there were somewhere I could go when I encounter an issue to determine if this is something that has been fixed in a more recent nightly.

    Thanks
  • erichmusick's avatar
    erichmusick
    New Contributor
    13 years ago
    I'm actually still seeing this issue with the latest nightly build.

    soapUI Pro 4.5.1.1-SNAPSHOT
    Build [internal], Build Date 2012/12/12 00:27
  • erichmusick's avatar
    erichmusick
    New Contributor
    13 years ago
    I added a Setup script to my project as a workaround; this seems to solve the problem. However, it certainly seems to be a defect in SoapUI.


    def env = project.getPropertyValue("EnvironmentVar")

    log.info "Environment param = " + project.getPropertyValue("EnvironmentVar")
    log.info "Pointing to environment = " + project.getActiveEnvironmentName()
    if (env != null && env != "") {
     project.setActiveEnvironment(env)
     log.info "Now Pointing to environment = " + project.getActiveEnvironmentName()
    }


    Here is my command line:

    call "C:\Program Files\SmartBear\soapUI-Pro-4.5.1.1-SNAPSHOT\bin\testrunner.bat" -I -a -A -j -ESystemTestB -r -f"C:\Jenkins\jobs\Tests_SYS\workspace\reports" -POutputDirectory=C:\Jenkins\jobs\SYS\workspace\reports -PEnvironmentVar=SystemTestB -tC:\Jenkins\customSettings\soapui-settings.xml "C:\Jenkins\customSettings\Integration15Tests"

    It should be sufficient to use only the first, but adding the second, in conjunction with the groovy script above seemed to solve my problem.