Teardown browser in watch mode.

[adunkman]

Summary

Fixes #269.

When jest is running with --watch, each test run creates a new browser — so we’ll want to teardown the browser to avoid memory leaks.

Test plan

I manually tested this — not sure how to write an automated test since it involves the setup and teardown process itself.

• I started the dev server by running PORT=4444 node server, since the dev server is not started in --watch mode (see In watch mode server doesn't start #229).
• In another terminal window, I ran yarn test --watch.
  • Observe that the browser is closed at the end of a test run.
  • I hit a to re-run all tests.
  • Observe a new browser is started, the tests are run, and it is closed.
  • Repeat forever!

[gregberge]

Thanks!

[Jiang-Xuan]

is ready to use?

[andreyctkn]

thanks @adunkman ! @neoziro Do you have any plan to publish it? because in 4.3.0 still contains the old one code https://github.com/smooth-code/jest-puppeteer/blob/0d72f09fa95173bf63999e05368bd4f312cde851/packages/jest-environment-puppeteer/src/global.js#L54-L65

[vcfvct]

Same here, Any timeline to publish this?
For now we have to modify the source code to get this behavior.

Thanks!