schickling/chromeless

Access console.error output?

Open

#219 opened on Aug 11, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (13,240 stars) (606 forks)batch import
discussionfeaturehelp wanted

Description

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),

Contributor guide

Tech stack
typescriptjavascript
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
basic Node.jsfamiliarity with chromelessunderstanding of headless browser events
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
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.