Dmitry Gozman

We recommend everyone to have a separate `tests/tsconfig.json` file that will be test-specific. If you put your tests under `tests/` directory, Playwright will automatically pick it up. ``` src/ source.ts...

We recommend a separate `tests/tsconfig.json` file in the tests directory that will be automatically picked up by Playwright. [See documentation](https://playwright.dev/docs/test-typescript#tsconfigjson)

@Camo30 We were not satisfied with the API, so decided to remove for now. We'll probably bring them back in one of the future release. Let me reopen the issue.

I can repro, and only in Firefox.

See also #18332 for a more specific issue covering `toHaveAccessibleName` and `toHaveAccessibleDescription`.

@heku Indeed, [this place](https://source.chromium.org/chromium/chromium/src/+/main:headless/lib/renderer/headless_print_render_frame_helper_delegate.cc;l=25-28;drc=adfe4659ed3661a61722948054c8f0ab427effcf;bpv=0;bpt=1) suggests that we always generate tagged pdfs.

See https://bugs.chromium.org/p/chromium/issues/detail?id=1309963 for upstream Chromium issue.

@Mosorathia If you are launching the persistent context, you can set up the user data dir to your liking by using the browser with that user data dir first. `localStorage`...

A workaround to set cookies for the persistent context: ```ts // Get cookies from some other context, for example the one you were authenticating in. const cookies = await someOtherContext.cookies();...

@piotrgajow There is no such tool yet. You can manually go over failed screenshots in the html report, but that's it right now. We were thinking along these lines, so...