Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

output of console.log is not being passed to the report #123

Open
AlexLevel opened this issue Jul 19, 2018 · 4 comments
Open

output of console.log is not being passed to the report #123

AlexLevel opened this issue Jul 19, 2018 · 4 comments

Comments

@AlexLevel
Copy link

AlexLevel commented Jul 19, 2018

hello,
don't know if that's intentional or not, but the output of console.log is not being captured in the html report, though time spent on it - does gets captured
i've described all here:
https://stackoverflow.com/questions/51414233/how-to-pass-console-log-value-to-protractor-jasmine2-screenshot-reporter

I can add all details here also.

@mlison
Copy link
Owner

mlison commented Jul 20, 2018

Good question. The output of browser's console doesn't get captured by the reporter itself, but to my understanding you can indeed access it via Protractor directly (browser.manage().logs()).
The next question is how to get it to the report - I can't think of a way from top of my hat, but metadata builder comes to mind, perhaps you can use it to store the output.

@AlexLevel
Copy link
Author

AlexLevel commented Jul 23, 2018

@mlison , thank you for your comment. would you happen to have a similar code for the reference?
can Extra configuration summary items (optional) be used? where can I find examples of its use?

@mlison
Copy link
Owner

mlison commented Jul 24, 2018

Not for this use-case, no, but there's a generic example on how to use metadata builder in the docs:
https://github.com/mlison/protractor-jasmine2-screenshot-reporter#metadata-builder-optional

@himawan-r
Copy link

i also wanted to be able to put console log in the report , leaving a comment here for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants