search

nightwatchjs / nightwatch

Integrated end-to-end testing framework written in Node.js and using W3C Webdriver API. Developed at @browserstack
https://nightwatchjs.org
MIT License
11.8k stars 1.31k forks source link

Plugin reporting is very verbose #3390

Open AutomatedTester opened 2 years ago

AutomatedTester commented 2 years ago

Description of the bug/issue

In the latest versions of Nightwatch when an error is hit in the Axe plugin we get very verbose logging like image

but in 2.1 we had logging like image

I wonder if there is a way to make it less verbose, it looks like the actionable error messages are making the reporting of errors a lot bigger here than intended.

Steps to reproduce

  1. Go to '...'
  2. Click on '...'
  3. Scroll down to '...'
  4. See error

Sample test

No response

Command to run

No response

Verbose Output

No response

Nightwatch Configuration

No response

Nightwatch.js Version

2.3.5

Node Version

No response

Browser

No response

Operating System

No response

Additional Information

A workaround is that people can look at the HTML report to get a cleaner view but it would be good to see the output cleaner too

beatfactor commented 2 years ago

We need to remove the stack trace altogether here, it's totally unnecessary, even in the 2.1 version.

harshit-bs commented 2 years ago

@beatfactor Yes it would be a great idea but I think we should display stack-trace at least once to make users life easier. Thoughts?

beatfactor commented 2 years ago

The stack trace points to the axe internal commands and is not relevant to the actual error. It's basically noise.