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.