Support multiple Actors.

[perrygoy]

While i was writing a test that has two Actors attempt to get on a call together, i noticed only one of the Actors was successfully tearing down and taking screenshots. The second Actor would get an error from Playwright, saying that the Playwright instance was already closed.

Well of course it was, that first Actor would do self.playwright.close() when their BrowseTheWebSynchronously ability was forgotten!

This PR takes out that call. Now that i'm more familiar with how Playwright works, keeping the Playwright instance active makes a lot more sense, especially in the context of the pytest fixtures Playwright provides in their plugin.

[MarcelWilson]

I'm concerned about parity with screenpy_selenium. As a tester, I would expect BrowseTheWeb.forget to behave similar to BrowseTheWebSynchronously.forget.

I guess my question is; is playwright.close() on par with selenium driver.quit()?

In addition to this, if BrowseTheWebSynchronously.using_chromium() calls playwright.start() I would expect forget to call playwright.close(). At the same time I would also expect that if the caller already did the initial playwright initialization, then forget shouldn't bother shutting it down.

Does this need to be a bit more intelligent about determining what should happen during forget?

• If BrowseTheWebSynchronously calls start(), forget should call close()
• If BrowseTheWebSynchronously does not call start(), forget should NOT call close()

[perrygoy]

I guess my question is; is playwright.close() on par with selenium driver.quit()?

Shortly, no. playwright.close() is similar to shutting down the SeleniumServer, while browser.close is the Playwright version of driver.quit. I don't know if that parallel is 100% perfect, but if you shut down playwright that closes all the browsers and browser contexts it spawned, so all other active Actors will no longer be able to perform ScreenPy: Playwright Actions.