[Feature Request] Keep browser loaded between tests about test-runner HOT 4 OPEN

AFAIK the maxWorkers determines how many pages get created. these pages get reused throughout the lifetime of the test run, unless there is a failing test. at that point, the page gets reset. How many workers are you using?

from test-runner.

Github runners have two cores, so two I guess two workers.

these pages get reused throughout the lifetime of the test run

Are you sure about that? I see output like this, which makes me think that each story needs to load a new page

page loaded in 782ms.
PASS browser: chromium src/components/patterns/snippet/Snippet.stories.tsx
page loaded in 798ms.
PASS browser: chromium src/components/atoms/forms/textarea/Textarea.stories.tsx
page loaded in 788ms.
PASS browser: chromium src/components/atoms/buttons/inline-button/InlineButton.stories.tsx
page loaded in 787ms.
PASS browser: chromium src/components/patterns/page-header/PageHeader.stories.tsx
page loaded in 768ms.
PASS browser: chromium src/components/atoms/forms/label/Label.stories.tsx

from test-runner.

Hmm can confirm that it opens a new browser for each story file. @yannbf this sounds like a bug to me. WDYT?

from test-runner.

I think this might just be the way that the jest runner for playwright works. I believe a new page is loaded each time using https://playwright.dev/docs/api/class-page#page-goto. I've opened playwright-community/jest-playwright#791 asking if perhaps there's a way to avoid that full page load each time.

from test-runner.