I wanted to run 18 test cases parallely so I created 18 suites with each test case. I put them into a test suite collection with execution property set as “Parallel”.
My test cases are configured in such a way that it will take screenshot if a failure happens. However, if a failure is happening, it is taking the screenshot of a different browser that is running in parallel for another test case.
I have previously run different suites at the same time but never faced this issue before.
Yes even I am facing this issue. In my case i have just 5 suites in test suite collection which are running in parallel and facing this issue.
Not sure if it is just taking the screenshot of the other browser or completely trying to execute test case on the browser which is launched by a different test case. (I doubt it)
If I remember correctly, I believe that the record feature works as a screen capture, which means that whichever browser window is in focus on the main display will get recorded. In fact, if you had the browser minimized, it would capture, say, your desktop instead.
Unless you have some kind of custom configuration I’m not aware of, it is absolutely a screen capture. This is for video capture, but I’d be surprised if a 1-frame screen capture was any different (maybe you can provide more proof of your issue?):
– Test1 will navigate to www.google.com
– Test2 will navigate to www.youtube.com
– These tests will both fail due to the assertion, after an ~15 second delay.
Observed behavior upon running TestSuiteCollection:
– Test1 fails, as expected, with the following screen capture: Test1.zip (827.9 KB)
– Test2 fails, as expected, with the following screen capture: Test2.zip (933.6 KB)
If that isn’t a screen-capture, I’m not sure what is…
As you can see, it’s simply recording whatever is happening on my main display. Now you could make the case that this is undesirable behavior, which I would agree with.
