Page MenuHomePhabricator

headless browsertests: browser console output
Closed, DeclinedPublic

Description

For the headless (i.e. non-saucelabs) browsertests: Is there a way to assert the absence of certain classes of output in the browser console or a way to log the console output? This may be related to T118179: headless browsertests: assert absence of or log network errors. Currently it is hard to know what may have caused a failure that is not immediately reproducible. Example of classes of output that might be interesting is warnings or worse for Net, CSS, JS, Security, Logging tabs in the firefox. For window.console also the info and log level might interesting.

Event Timeline

JanZerebecki raised the priority of this task from to Needs Triage.
JanZerebecki updated the task description. (Show Details)

If there is no webriver solution (i.e. one that ask the browser with chrome level access) maybe use a solution that works inside the website, like mw.trackSubscribe( 'global.error', function ( topic, err ) {....

zeljkofilipin triaged this task as Medium priority.Nov 10 2015, 4:16 PM
zeljkofilipin set Security to None.
zeljkofilipin moved this task from Inbox to Ruby on the Browser-Tests-Infrastructure board.
JanZerebecki lowered the priority of this task from Medium to Low.Nov 10 2015, 4:33 PM
JanZerebecki moved this task from incoming to monitoring on the Wikidata board.Nov 10 2015, 5:13 PM
zeljkofilipin closed this task as Declined.Nov 2 2017, 5:38 PM
zeljkofilipin added a subscriber: zeljkofilipin.

Unlikely to ever be resolved because of T139740: Port Selenium tests from Ruby to Node.js.