Description of the bug/issue
The errors coming from the new Element API do not pinpoint the exact location where the command that led to the error was used in the test case.
This is in contrast with the old API which used to show the exact location of command usage in the error stack.
For e.g., if we use await browser.findElement('.invalid_selector');, we'd get the following error (the line where the findElement command is used is clearly highlighted):
On the other hand, when using the new Element API (await browser.element.find('.invalid_selector');), we get the following error (the highlight does not show where the command was actually used):
Steps to reproduce
Run await browser.element.find('.invalid_selector'); in any test.
Nightwatch.js Version
latest
Description of the bug/issue
The errors coming from the new Element API do not pinpoint the exact location where the command that led to the error was used in the test case.
This is in contrast with the old API which used to show the exact location of command usage in the error stack.
For e.g., if we use
await browser.findElement('.invalid_selector');, we'd get the following error (the line where thefindElementcommand is used is clearly highlighted):On the other hand, when using the new Element API (
await browser.element.find('.invalid_selector');), we get the following error (the highlight does not show where the command was actually used):Steps to reproduce
Run
await browser.element.find('.invalid_selector');in any test.Nightwatch.js Version
latest