3

When i execute the test cases parallely, I get a lot of "The test has already finished errors." I am sure the following are not the cause as mentioned in Common error messages link here.

  1. driver.quit() is not the reason why the test is marked as finished, since it is not even executed when the above error came up.

  2. always managed to make sure that the no of concurrent VMs running are less than the total no of VM's available for the account.

  3. Internet connection is strong and stable.

Can you kindly help with this issue to determine what is wrong?

Shyam Visamsetty
  • 434
  • 1
  • 6
  • 16

2 Answers2

0

I solved this issue in 2014 with my NuGet package Saucery3. Project homepage is here and is open source.

The code you want is here and here.

In the first link look at the Cleanup() method that implements [Teardown].

In the second link is the NotifyStatus method.

Andrew Gray
  • 3,190
  • 2
  • 29
  • 55
0

If you're sure that parallelisation part on your side is coded correctly, it is most likely a timeouts issue. By default, in Saucelabs test session several timeouts are used. If any timeout is reached, session will be terminated on Saucelabs side. You can find more information here https://wiki.saucelabs.com/display/DOCS/Test+Configuration+Options#TestConfigurationOptions-Timeouts

Please keep in mind that Javascript command executed from WebDriver is NOT considered to be a command in Saucelabs.

Daria Yershova
  • 44
  • 2