playwright-mcp/tests
Max Schmitt 062cdd0704
fix: sticky launch errors (#324)
This fixes an issue that there were sticky launch errors. When the
[following code
path](a15f0f301b/src/context.ts (L307-L339))
was throwing, the Error was stored in the Promise and not cleared
afterwards, this meant:

- If a browser was not there and the user tried to install it via
`browser_install` it was never working since the error was sticky.
- If other errors like CDP is not available yet etc. error appear a
re-connect would not work - the MCP server would require a restart.

Test plan: Since we don't have any `browser_install` tests I added a CDP
test for now to cover this bug.
2025-05-02 15:32:37 +02:00
..
testserver chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
capabilities.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
cdp.spec.ts fix: sticky launch errors (#324) 2025-05-02 15:32:37 +02:00
console.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
core.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
device.spec.ts test: use TestOptions type in config (#326) 2025-05-02 13:50:03 +02:00
dialogs.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
files.spec.ts chore: save downloads to outputDir (#310) 2025-05-02 10:57:31 +02:00
fixtures.ts fix: sticky launch errors (#324) 2025-05-02 15:32:37 +02:00
headed.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
iframes.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
launch.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
network.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
pdf.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
screenshot.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
sse.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00
tabs.spec.ts fix: sticky launch errors (#324) 2025-05-02 15:32:37 +02:00
webdriver.spec.ts chore: migrate to ESM (#303) 2025-04-30 23:06:56 +02:00