Playwright 超时机制深度解析TimeoutError 的触发、捕获与跨语言处理【免费下载链接】playwrightPlaywright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.项目地址: https://gitcode.com/GitHub_Trending/pl/playwright当 Playwright 的自动等待超出预算时抛出的正是TimeoutError。它是 Playwright 中所有因超时而终止的操作的统一异常信号——从locator.waitFor、各类点击/导航操作到BrowserType.launch启动浏览器失败都可能以它收尾。读懂这个异常类、理解底层deadline 竞争机制你就能在测试中精准区分超时与元素真的不存在并编写出确定性的失败诊断代码。类定义与继承关系TimeoutError自 v1.8 起提供继承自标准Error。其官方文档定义见 class-timeouterror.md一句话概括了它的语义TimeoutError is emitted whenever certain operations are terminated due to timeout, e.g.Locator.waitFororBrowserType.launch.在 JavaScript API 中你可以通过playwright.errors.TimeoutError访问该构造器并用instanceof做类型判断。TypeScript 声明中它也位于errors命名空间下见 types.d.tsclass TimeoutError extends Error { }多语言示例捕获超时四种官方 API 中捕获方式略有差异。JavaScript 用instanceof判断Python 直接except导出的异常类Java 捕获com.microsoft.playwright.TimeoutErrorC# 捕获的是 .NET 标准的TimeoutException。JavaScriptconst playwright require(playwright); (async () { const browser await playwright.chromium.launch(); const context await browser.newContext(); const page await context.newPage(); try { await page.locator(textFoo).click({ timeout: 100, // 覆盖该次操作的默认超时 }); } catch (error) { if (error instanceof playwright.errors.TimeoutError) console.log(Timeout!); } await browser.close(); })();Pythonasync APIimport asyncio from playwright.async_api import async_playwright, TimeoutError as PlaywrightTimeoutError, Playwright async def run(playwright: Playwright): browser await playwright.chromium.launch() page await browser.new_page() try: await page.locator(textExample).click(timeout100) except PlaywrightTimeoutError: print(Timeout!) await browser.close() async def main(): async with async_playwright() as playwright: await run(playwright) asyncio.run(main())Pythonsync APIfrom playwright.sync_api import sync_playwright, TimeoutError as PlaywrightTimeoutError with sync_playwright() as p: browser p.chromium.launch() page browser.new_page() try: page.locator(textExample).click(timeout100) except PlaywrightTimeoutError: print(Timeout!) browser.close()Javapackage org.example; import com.microsoft.playwright.*; public class TimeoutErrorExample { public static void main(String[] args) { try (Playwright playwright Playwright.create()) { Browser browser playwright.firefox().launch(); BrowserContext context browser.newContext(); Page page context.newPage(); try { page.locator(textExample).click(new Locator.ClickOptions().setTimeout(100)); } catch (TimeoutError e) { System.out.println(Timeout!); } } } }C#using Microsoft.Playwright; using var playwright await Playwright.CreateAsync(); await using var browser await playwright.Chromium.LaunchAsync(); var page await browser.NewPageAsync(); try { await page.ClickAsync(textExample, new() { Timeout 100 }); } catch (TimeoutException) { Console.WriteLine(Timeout!); }注意 Java 示例中 Java 类名与 JS 的playwright.errors.TimeoutError对应关系Java 里它就是导入com.microsoft.playwright.TimeoutError而 C# 映射到了 .NET 的System.TimeoutException因此catch (TimeoutException)即可无需额外导入 Playwright 专有类型。源码剖析TimeoutError 在客户端与服务端的实现Playwright 是驱动进程driver 浏览器进程的客户端/服务端架构TimeoutError在两侧各有一套类最终通过协议序列化传递到用户代码。客户端类客户端也就是你require(playwright)拿到的那套 API在 client/errors.ts 中定义了异常族export class PlaywrightError extends Error { log: string[] []; details?: any; // As declared in the protocol. } export class TimeoutError extends PlaywrightError { constructor(message: string) { super(message); this.name TimeoutError; } }可以看到TimeoutError不是裸的Error而是PlaywrightError的子类——这意味着它额外携带log操作日志数组Playwright 会把等待期间的 DOM 快照日志附加在错误上和details字段。同文件中还有TargetClosedError与AbortError分别对应目标已关闭与操作被中止它们与TimeoutError一起构成了 Playwright 的三大预期内失败类型。跨协议的反序列化为什么跨连接后仍是同一个类服务端抛出的异常并不会直接飞到客户端而是先被序列化。客户端的 parseError 负责把它还原export function parseError(error: SerializedError): PlaywrightError { // ... if (error.error.name TimeoutError) e new TimeoutError(error.error.message); else if (error.error.name TargetClosedError) e new TargetClosedError(error.error.message); else if (error.error.name AbortError) e new AbortError(error.error.message); // ... }关键点在于还原时按name字符串匹配。也就是说即使异常对象经历了 JSON 序列化message、stack、name 三要素见 serializeError只要name TimeoutError客户端就会 new 出真正的TimeoutError实例——这正是error instanceof playwright.errors.TimeoutError在远程驱动如connect模式场景下依然成立的原因。服务端类服务端的对应实现在 server/errors.tsclass CustomError extends Error { constructor(message: string, options?: ErrorOptions) { super(message, options); this.name this.constructor.name; } } export class TimeoutError extends CustomError {}CustomError构造器通过this.name this.constructor.name保证序列化后的name字段正确与客户端的按名匹配逻辑闭环。底层原理deadline 竞争与错误消息的生成超时在 Playwright 内部是如何被制造出来的答案分两层。第一层raceAgainstDeadline —— 与截止时间赛跑核心的计时工具在 isomorphic/timeoutRunner.tsexport async function raceAgainstDeadlineT(cb: () PromiseT, deadline: number): Promise{ result: T, timedOut: false } | { timedOut: true } { let timer: NodeJS.Timeout | undefined; return await Promise.race([ cb().then(result { return { result, timedOut: false }; }), new Promise{ timedOut: true }(resolve { if (!deadline) return; timer setTimeout(() resolve({ timedOut: true }), Math.max(0, deadline - monotonicTime())); }), ]).finally(() { clearTimeout(timer); }); }要点单调时钟剩余时间用Math.max(0, deadline - monotonicTime())计算monotonicTime来自 isomorphic/time.ts避免系统时间跳变导致的计时错乱deadline 0即禁用超时这与 API 文档中大量出现的 Pass0to disable timeout 约定一致。例如 BrowserType.connect 的 timeout 选项 明确说明默认0no timeout而connectOverCDP的 timeout 默认为3000030 秒同样允许传0禁用文件头部的注释特别强调此文件不使用builtins.setTimeout因为时钟模拟page.clock介入时内置定时器会被劫持底层计时必须走原始通道。同一文件中还有pollAgainstDeadlineL42-L62它按[100, 250, 500, 1000]毫秒的退避间隔循环轮询条件直到 deadline 耗尽返回{ timedOut: true }。这是waitFor类轮询式等待操作的基础。第二层进度系统把 timedOut 转成 TimeoutError服务端的进度progress系统消费上述结果并抛出带消息的异常。在 server/progress.ts 中L136const timeoutError new TimeoutError(\Timeout ${timeout}ms exceeded.);——这就是你在测试失败日志里看到的标准错误消息Timeout 30000ms exceeded. 的来源L168return error instanceof TimeoutError || !!(error as any)[kAbortErrorSymbol];——进度系统会把TimeoutError与主动中止视为同类可恢复错误来处理不污染浏览器日志。哪些操作会抛出 TimeoutError官方文档点名的两个代表是Locator.waitFor与BrowserType.launch实际覆盖面更广自动等待/操作类locator.click、locator.waitFor、page.goto的 load 等待等只要操作在timeout内未达成都会以Timeout {timeout}ms exceeded.收尾连接类BrowserType.launch浏览器进程在预算内未就绪、BrowserType.connectOverCDP默认 30 秒超时等覆盖策略单次操作可用timeout: 100这样的选项参数覆盖默认值上下文级/全局的默认超时由配置中的timeout等选项决定传0可禁用。实战要点小结用类型判断别用字符串匹配error instanceof playwright.errors.TimeoutErrorJS或各语言的等价catch类型是区分超时与选择器无匹配/目标已关闭TargetClosedError的可靠手段跨连接场景下该判断依然有效因为客户端按name字段精确还原了异常类型见 parseError读log字段定位根因客户端PlaywrightError携带的log: string[]会在等待过程中记录 DOM 状态快照是诊断为什么 100ms 内没等到 textFoo的第一手材料用0关闭超时对长任务操作大文件下载触发的大导航、慢环境下的connectOverCDP传timeout: 0可完全禁用计时这在 BrowserType API 文档 中有明确参数说明C# 注意映射差异.NET API 抛的是标准库的TimeoutException而非 Playwright 专有类catch时不要照搬其他语言的类型名。参考实现路径客户端异常、服务端异常、deadline 计时工具、进度系统、TimeoutError API 文档。【免费下载链接】playwrightPlaywright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.项目地址: https://gitcode.com/GitHub_Trending/pl/playwright创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
Playwright 超时机制深度解析TimeoutError 的触发、捕获与跨语言处理【免费下载链接】playwrightPlaywright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.项目地址: https://gitcode.com/GitHub_Trending/pl/playwright当 Playwright 的自动等待超出预算时抛出的正是TimeoutError。它是 Playwright 中所有因超时而终止的操作的统一异常信号——从locator.waitFor、各类点击/导航操作到BrowserType.launch启动浏览器失败都可能以它收尾。读懂这个异常类、理解底层deadline 竞争机制你就能在测试中精准区分超时与元素真的不存在并编写出确定性的失败诊断代码。类定义与继承关系TimeoutError自 v1.8 起提供继承自标准Error。其官方文档定义见 class-timeouterror.md一句话概括了它的语义TimeoutError is emitted whenever certain operations are terminated due to timeout, e.g.Locator.waitFororBrowserType.launch.在 JavaScript API 中你可以通过playwright.errors.TimeoutError访问该构造器并用instanceof做类型判断。TypeScript 声明中它也位于errors命名空间下见 types.d.tsclass TimeoutError extends Error { }多语言示例捕获超时四种官方 API 中捕获方式略有差异。JavaScript 用instanceof判断Python 直接except导出的异常类Java 捕获com.microsoft.playwright.TimeoutErrorC# 捕获的是 .NET 标准的TimeoutException。JavaScriptconst playwright require(playwright); (async () { const browser await playwright.chromium.launch(); const context await browser.newContext(); const page await context.newPage(); try { await page.locator(textFoo).click({ timeout: 100, // 覆盖该次操作的默认超时 }); } catch (error) { if (error instanceof playwright.errors.TimeoutError) console.log(Timeout!); } await browser.close(); })();Pythonasync APIimport asyncio from playwright.async_api import async_playwright, TimeoutError as PlaywrightTimeoutError, Playwright async def run(playwright: Playwright): browser await playwright.chromium.launch() page await browser.new_page() try: await page.locator(textExample).click(timeout100) except PlaywrightTimeoutError: print(Timeout!) await browser.close() async def main(): async with async_playwright() as playwright: await run(playwright) asyncio.run(main())Pythonsync APIfrom playwright.sync_api import sync_playwright, TimeoutError as PlaywrightTimeoutError with sync_playwright() as p: browser p.chromium.launch() page browser.new_page() try: page.locator(textExample).click(timeout100) except PlaywrightTimeoutError: print(Timeout!) browser.close()Javapackage org.example; import com.microsoft.playwright.*; public class TimeoutErrorExample { public static void main(String[] args) { try (Playwright playwright Playwright.create()) { Browser browser playwright.firefox().launch(); BrowserContext context browser.newContext(); Page page context.newPage(); try { page.locator(textExample).click(new Locator.ClickOptions().setTimeout(100)); } catch (TimeoutError e) { System.out.println(Timeout!); } } } }C#using Microsoft.Playwright; using var playwright await Playwright.CreateAsync(); await using var browser await playwright.Chromium.LaunchAsync(); var page await browser.NewPageAsync(); try { await page.ClickAsync(textExample, new() { Timeout 100 }); } catch (TimeoutException) { Console.WriteLine(Timeout!); }注意 Java 示例中 Java 类名与 JS 的playwright.errors.TimeoutError对应关系Java 里它就是导入com.microsoft.playwright.TimeoutError而 C# 映射到了 .NET 的System.TimeoutException因此catch (TimeoutException)即可无需额外导入 Playwright 专有类型。源码剖析TimeoutError 在客户端与服务端的实现Playwright 是驱动进程driver 浏览器进程的客户端/服务端架构TimeoutError在两侧各有一套类最终通过协议序列化传递到用户代码。客户端类客户端也就是你require(playwright)拿到的那套 API在 client/errors.ts 中定义了异常族export class PlaywrightError extends Error { log: string[] []; details?: any; // As declared in the protocol. } export class TimeoutError extends PlaywrightError { constructor(message: string) { super(message); this.name TimeoutError; } }可以看到TimeoutError不是裸的Error而是PlaywrightError的子类——这意味着它额外携带log操作日志数组Playwright 会把等待期间的 DOM 快照日志附加在错误上和details字段。同文件中还有TargetClosedError与AbortError分别对应目标已关闭与操作被中止它们与TimeoutError一起构成了 Playwright 的三大预期内失败类型。跨协议的反序列化为什么跨连接后仍是同一个类服务端抛出的异常并不会直接飞到客户端而是先被序列化。客户端的 parseError 负责把它还原export function parseError(error: SerializedError): PlaywrightError { // ... if (error.error.name TimeoutError) e new TimeoutError(error.error.message); else if (error.error.name TargetClosedError) e new TargetClosedError(error.error.message); else if (error.error.name AbortError) e new AbortError(error.error.message); // ... }关键点在于还原时按name字符串匹配。也就是说即使异常对象经历了 JSON 序列化message、stack、name 三要素见 serializeError只要name TimeoutError客户端就会 new 出真正的TimeoutError实例——这正是error instanceof playwright.errors.TimeoutError在远程驱动如connect模式场景下依然成立的原因。服务端类服务端的对应实现在 server/errors.tsclass CustomError extends Error { constructor(message: string, options?: ErrorOptions) { super(message, options); this.name this.constructor.name; } } export class TimeoutError extends CustomError {}CustomError构造器通过this.name this.constructor.name保证序列化后的name字段正确与客户端的按名匹配逻辑闭环。底层原理deadline 竞争与错误消息的生成超时在 Playwright 内部是如何被制造出来的答案分两层。第一层raceAgainstDeadline —— 与截止时间赛跑核心的计时工具在 isomorphic/timeoutRunner.tsexport async function raceAgainstDeadlineT(cb: () PromiseT, deadline: number): Promise{ result: T, timedOut: false } | { timedOut: true } { let timer: NodeJS.Timeout | undefined; return await Promise.race([ cb().then(result { return { result, timedOut: false }; }), new Promise{ timedOut: true }(resolve { if (!deadline) return; timer setTimeout(() resolve({ timedOut: true }), Math.max(0, deadline - monotonicTime())); }), ]).finally(() { clearTimeout(timer); }); }要点单调时钟剩余时间用Math.max(0, deadline - monotonicTime())计算monotonicTime来自 isomorphic/time.ts避免系统时间跳变导致的计时错乱deadline 0即禁用超时这与 API 文档中大量出现的 Pass0to disable timeout 约定一致。例如 BrowserType.connect 的 timeout 选项 明确说明默认0no timeout而connectOverCDP的 timeout 默认为3000030 秒同样允许传0禁用文件头部的注释特别强调此文件不使用builtins.setTimeout因为时钟模拟page.clock介入时内置定时器会被劫持底层计时必须走原始通道。同一文件中还有pollAgainstDeadlineL42-L62它按[100, 250, 500, 1000]毫秒的退避间隔循环轮询条件直到 deadline 耗尽返回{ timedOut: true }。这是waitFor类轮询式等待操作的基础。第二层进度系统把 timedOut 转成 TimeoutError服务端的进度progress系统消费上述结果并抛出带消息的异常。在 server/progress.ts 中L136const timeoutError new TimeoutError(\Timeout ${timeout}ms exceeded.);——这就是你在测试失败日志里看到的标准错误消息Timeout 30000ms exceeded. 的来源L168return error instanceof TimeoutError || !!(error as any)[kAbortErrorSymbol];——进度系统会把TimeoutError与主动中止视为同类可恢复错误来处理不污染浏览器日志。哪些操作会抛出 TimeoutError官方文档点名的两个代表是Locator.waitFor与BrowserType.launch实际覆盖面更广自动等待/操作类locator.click、locator.waitFor、page.goto的 load 等待等只要操作在timeout内未达成都会以Timeout {timeout}ms exceeded.收尾连接类BrowserType.launch浏览器进程在预算内未就绪、BrowserType.connectOverCDP默认 30 秒超时等覆盖策略单次操作可用timeout: 100这样的选项参数覆盖默认值上下文级/全局的默认超时由配置中的timeout等选项决定传0可禁用。实战要点小结用类型判断别用字符串匹配error instanceof playwright.errors.TimeoutErrorJS或各语言的等价catch类型是区分超时与选择器无匹配/目标已关闭TargetClosedError的可靠手段跨连接场景下该判断依然有效因为客户端按name字段精确还原了异常类型见 parseError读log字段定位根因客户端PlaywrightError携带的log: string[]会在等待过程中记录 DOM 状态快照是诊断为什么 100ms 内没等到 textFoo的第一手材料用0关闭超时对长任务操作大文件下载触发的大导航、慢环境下的connectOverCDP传timeout: 0可完全禁用计时这在 BrowserType API 文档 中有明确参数说明C# 注意映射差异.NET API 抛的是标准库的TimeoutException而非 Playwright 专有类catch时不要照搬其他语言的类型名。参考实现路径客户端异常、服务端异常、deadline 计时工具、进度系统、TimeoutError API 文档。【免费下载链接】playwrightPlaywright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.项目地址: https://gitcode.com/GitHub_Trending/pl/playwright创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
