I am sorry to hear you're running into this problem. A test with that many data iterations is very likely to encounter memory issues deep into execution causing the beahvior you're describing. To overcome this, please try using our ReuseAppWindow
feature available in the Test Properties
. This defines the number of iterations to reuse the browser window for a single test.
By default, zero keeps the same application open during the entire data driven test causing high memory consumption. Increasing that number can help to improve memory and performance. If you change it to 50, for example, the browser will close and reopen after each fiftieth iteration, which will reset the memory consumption of the browser.
If you continue to have difficulty, please send us the Application Log
. Ensure you enable logging first (clear out existing log, then run the problematic test) and send us the log within a .zip file.