Forum Discussion

M_McDonald's avatar
M_McDonald
Super Contributor
16 years ago

[SOLVED]JDBC Request assertion failure not passed back to calling test case

I have a JDBC Request step in a test case (call it A) which gets called from another test case (call it B). When I run A the test case is failed if the step fails, but if I call A from B, B never gets the failure.

If I have another kind of request (say HTTP) in test case A, assertion failures for that step are reported correctly. See attached screen shot.

Please help!

I also notice that if I have script assertions with log statements in the JDBC request, they are not showing up in the script log tab when run from the outer (B) test case. The same kind of assertion from the HTTP request always gets executed.

Perhaps the assertions are not getting executed at all?

4 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hi!

    hmm.. I can't reproduce this.. do you have any errors in the error log?

    regards!

    /Ole
    eviware.com
  • M_McDonald's avatar
    M_McDonald
    Super Contributor
    16 years ago
    Yes:

    [tt:kweem1v2]java.lang.NullPointerException
    at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcRequest.getIcon(JdbcRequest.java:377)
    at com.eviware.soapui.impl.wsdl.teststeps.JdbcRequestTestStep.getIcon(JdbcRequestTestStep.java:462)
    at com.eviware.soapui.impl.wsdl.teststeps.JdbcRequestTestStep$PropertyChangeNotifier.(JdbcRequestTestStep.java:338)
    at com.eviware.soapui.impl.wsdl.teststeps.JdbcRequestTestStep.assertResponse(JdbcRequestTestStep.java:511)
    at com.eviware.soapui.impl.wsdl.teststeps.JdbcRequestTestStep.run(JdbcRequestTestStep.java:247)
    at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runTestStep(WsdlTestCaseRunner.java:194)
    at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.internalRun(WsdlTestCaseRunner.java:125)
    at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.internalRun(WsdlTestCaseRunner.java:39)
    at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:139)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)[/tt:kweem1v2]
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Thanks!

    I think this is fixed in the current nightly build, sorry for the inconvenience.

    regards!

    /Ole
    eviware.com