Commit 95d68e0
committed
[TE-4877] Fix broken test after Playwright upgrade
AMP LLM model told me this:
In Playwright, tests use fixtures like browserName, browser, context, and page. When you set a very short timeout (1ms), the test fails during fixture setup. The newer version of Playwright now times out during the "context" fixture setup (creating the browser context) rather than the "browserName" fixture setup. This is likely because newer Playwright optimizes browser launching to be faster or lazy-loads certain operations, so the timeout now hits later in the setup chain.
Playwright fixtures follow a hierarchical setup order:
browserName - Simple string constant (chromium/firefox/webkit)
browser - Worker-scoped; launches once per worker process (expensive operation)
context - Test-scoped; creates isolated browser context (like incognito mode) per test
page - Test-scoped; creates a page/tab within the context per test
When you set a 1ms timeout, the test fails during fixture setup. The newer Playwright version changed where the timeout triggers—from "browserName" to "context". This suggests the browser launch (browser fixture) now completes faster or is optimized differently, so the 1ms timeout now expires during the context creation step instead of earlier in the chain.1 parent 0b2f96b commit 95d68e0
1 file changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
120 | 120 | | |
121 | 121 | | |
122 | 122 | | |
123 | | - | |
| 123 | + | |
124 | 124 | | |
125 | 125 | | |
126 | | - | |
| 126 | + | |
127 | 127 | | |
128 | 128 | | |
129 | 129 | | |
| |||
132 | 132 | | |
133 | 133 | | |
134 | 134 | | |
135 | | - | |
| 135 | + | |
136 | 136 | | |
137 | 137 | | |
138 | | - | |
| 138 | + | |
139 | 139 | | |
140 | 140 | | |
141 | 141 | | |
| |||
0 commit comments