Performance multiple JDBC requests
When I run multiple small JDBC requests as separate teststeps, say 30 in a row to retrieve 1 record each in 30 different tables, I see the following strange behaviour: Running 1 teststep manually sho...
Forum Discussion
Sorry, but the assertions are taking 1 or 2 milliseconds, not 230 milliseconds.
Is the overhead maybe in setting up and tearing down the JDBC connection for every teststep?
Is there a way to set up the connection in the set-up script and tearing it down afterwards, instead of setting it up for every JDBC request?
It would be great if there was a way to maintainthe JDBC connection at testcase level and then specifying at teststep level that the testcase connection should be used.
I have a lot of tests comparing 2 databases by looping through them and comparing them with scripts.
Is the overhead maybe in setting up and tearing down the JDBC connection for every teststep?
Is there a way to set up the connection in the set-up script and tearing it down afterwards, instead of setting it up for every JDBC request?
It would be great if there was a way to maintainthe JDBC connection at testcase level and then specifying at teststep level that the testcase connection should be used.
I have a lot of tests comparing 2 databases by looping through them and comparing them with scripts.