8000 Browser console output should be logged to log/development.log · Issue #581 · jejacks0n/teaspoon · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Browser console output should be logged to log/development.log  #581
Open
@thebravoman

Description

@thebravoman

Running specs from browser. Console log in browser contains things like

Uncaught Extension 'lc' registered to listen for non existing event: 'ac'!
2scenarios_spec.self-aab74e4a9e58cea940c59c886d2b129405e994265bcef3120b9d937e78387840.js?body=1?body=1:54 Uncaught (in promise) undefined
checkEvent @ scenarios_spec.self-aab74e4a9e58cea940c59c886d2b129405e994265bcef3120b9d937e78387840.js?body=1?body=1:54
setTimeout (async)
checkEvent @ scenarios_spec.self-aab74e4a9e58cea940c59c886d2b129405e994265bcef3120b9d937e78387840.js?body=1?body=1:62
setTimeout (async)
checkEvent @ scenarios_spec.self-aab74e4a9e58cea940c59c886d2b129405e994265bcef3120b9d937e78387840.js?body=1?body=1:62

These are errors that my tests output as error in the console, because of some promises.

What I can not find and I think should be added to the documentation is how to get this error logged to log/development.log when I am starting teaspoon from cli

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0