Cross browser testing failing on browser already running message
As per the subject title I am getting the above error message trying to setup a cross browser test, however the browser and the related process is not running and when the test runs the log in page fo...
Ok it turns out that the test is picking up the instance id for the log in page rather than the name, I am currently trying to sort this but can anyone point me to an article detailing how to do this?