jest-playwright | Running tests using Jest & Playwright | Testing library

I would recommend Playwright Test, because

• it works without other external dependencies
• has support for TypeScript out of the box
• has multi-project support with different browser configurations
• Supports trace-viewer, video, and screenshot creation out of the box via the config.
• Applies context per test best practice to have them isolated and self contained

For more references see here: https://playwright.dev/docs/test-intro

I've managed to find solution in this GitHub issue: https://github.com/kulshekhar/ts-jest/issues/1107#issuecomment-559759395

In short, by default ts-jest transform is invoked later than it should, so doesn't have a chance to process all the files. The tsconfig-paths can help with that:

1. Install above package with yarn add --dev tsconfig-paths
2. In global-setup file add require('tsconfig-paths/register'); at the very beginning of the file.

All the absolute imports should work.

There are deliberate specialized cases you may want to use page.close() in a custom fixture/config but I'm wouldn't say that's the case for you based on what you're trying to do. By default, the browser/context will close automatically after each test, and will therefore also close the page being tested. You can see the default teardown here.

Removing your afterEach method should resolve the issue. :)

Other notable features:

• Checkout Playwright-Test to see how custom config/fixtures can help you make consistent test environments, (ie. if you wanted some environments to take screenshots only-on-failure but not others.
• Playwright also supports page object models -- a feature that makes your tests much more readable and maintainable. I also have an example here that you can reference for Page Object Models with the new version of Playwright, if this helps.

The node:latest does not have the appropriate system dependencies to run the browsers. You can use the Playwright docker image.