Forum Discussion
sanjeevkumar7
15 years agoOccasional Contributor
Hi Henrik
That's great. I never thought that way. I still had to store the response in the database. So I chose the 2nd method.
Added two columns - run_id and version. run_id increments for each run.
I send the same request for two different versions, capture the required response, use a stored procedure to compare the rows of two versions with the same run_id and write the result to another table.
May be all of the above could have been done with groovy, but thought of using sql to do the heavy lifting.
Is there a way to read the results table (which will contain the failed cases ) and populate in the report?
Your tip helped me move forward with this. Thanks.
-Sanjeev
Can't you send requests to both versions in two subsequent TestSteps and comparing them on the fly?
That's great. I never thought that way. I still had to store the response in the database. So I chose the 2nd method.
Added two columns - run_id and version. run_id increments for each run.
I send the same request for two different versions, capture the required response, use a stored procedure to compare the rows of two versions with the same run_id and write the result to another table.
May be all of the above could have been done with groovy, but thought of using sql to do the heavy lifting.
Is there a way to read the results table (which will contain the failed cases ) and populate in the report?
Your tip helped me move forward with this. Thanks.
-Sanjeev