schickling/chromeless

Access console.error output?

Open

#219 创建于 2017年8月11日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)TypeScript (13,240 star) (606 fork)batch import
discussionfeaturehelp wanted

描述

Is it possible to use chromeless to monitor the console output and see if there are any error messages in the console? The use case for this would be a smoke test of the application hitting every page looking for console errors (and resource errors?) as part of our CI release.

I believe casper.js has this via their events API (remote.message),

贡献者指南

技术栈
typescriptjavascript
领域
testing
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
basic Node.jsfamiliarity with chromelessunderstanding of headless browser events
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
50
研究方向
Investigate how chromeless currently exposes page events (e.g., see the existing source code for event handling). Look into Puppeteer's 'console' event to capture console messages. Implement a method like `onConsole` or modify the existing API to allow users to listen for console.error output. Consider adding an example in the documentation. Ensure the implementation fits the current architecture and does not break existing functionality.