Thx for your reply.
Now look from mine perspective (and I see on some users site as well).
Scenarios are tested against 800 bind sets.
They include various combinations with huge difference of LIO and this is the main problem-some scenarios runs fast for one group of bind set while on other group they are bad. I know this is data problem, but explain you the real case.
They are split in test execution because all should be tested in specific time. This is important because some indexes they use are under heavy pressure in that tim3 so “best query” plan may be inefficient in particular moment of execution, because other processing in the database.
So when I resume, I have to open best scenario test case until that moment, export data in Excel and summarize the time of best solution and then put that number in terminate dialog. This is tedious work.
So please, if you do not want to change termination part, at least put next columns in result grid :
- total elapsed time (for all bind set) for each scenario that was already run
- total LIO (for all bind set) for each scenario that was already run
- start and end time for each scenario that was already run (when test starts and when ends)
This would be also a solution. I hope i have clear up mine case.