Scripted assertions in JDBC Requests - Issue
Hello, I have a test case with 8 steps - Data source, Groovy script, SOAP request, Delay, Groovy script, JDBC request1, JDBC Request2 and Data source loop. In each of the JDBC requests, I have a sc...
Forum Discussion
Iteration 1 : The assertion fails and the test step - JDBC_Request_HixGroupSetup_Initial is marked as failed. The logs after the failed assertion are skipped.
Iteration 2 : The assertion is successful. But still the test step JDBC_Request_HixGroupSetup_Initial is marked as failed. All the infos after the assertion logged. I am able to look up the results in the database too.
The generic behavior I observed is if a test step x fails in iteration n due to assertion failure, the same test step x fails in iteration n+1 even if the assertion is successful. the subsequent iterations are successful.
It seems like the test step result is cached and is returning the same result for the next iteration.
when I run the script assertion stand alone, it runs absolutely fine and all the infos are logged.
The 'expectedResult' is fed from the data source (Excel) and is always either "True" or "False".
I ran through the debugger and the response looks absolutely fine. I am getting the expected response from the SQL and the assertion passes. I can confirm that as the infos specified after the assertions are logged.
Iteration 2 : The assertion is successful. But still the test step JDBC_Request_HixGroupSetup_Initial is marked as failed. All the infos after the assertion logged. I am able to look up the results in the database too.
The generic behavior I observed is if a test step x fails in iteration n due to assertion failure, the same test step x fails in iteration n+1 even if the assertion is successful. the subsequent iterations are successful.
It seems like the test step result is cached and is returning the same result for the next iteration.
when I run the script assertion stand alone, it runs absolutely fine and all the infos are logged.
The 'expectedResult' is fed from the data source (Excel) and is always either "True" or "False".
I ran through the debugger and the response looks absolutely fine. I am getting the expected response from the SQL and the assertion passes. I can confirm that as the infos specified after the assertions are logged.
