NoSuchElementError should be suppressed for assert[.not].present() assertion in new Elem API.

[garg3133]

Description

When we do browser.element.find(selector).assert.present(), if the element is not found, we get the NoSuchElementError error, but in case of assert.present, this error should be suppressed since the failure of the assertion would anyway signify that the element is not present.

The same also goes for the .assert.not.present() assertion. In this case, if the element is not present, the assertion should normally pass without the NoSuchElementError.

(The test should pass with 0 errors unlike in the above screenshot.)

[Pikachu-345]

Hey @garg3133 I am a beginner at Open Source. So can I contribute to this issue, if yes. can you please specify what parts of the projects do I need to look at for fixing this issue.

Regards,
Thank you.

[garg3133]

Hey, the scoped-element.js file and the assert/element-assertions.js file are the two main files you should try to look at to solve this issue. Also, you can refer to the implementation of the isPresent command in the new Element API, which also automatically suppresses the NoSuchElementFound error as required in this issue: https://github.com/nightwatchjs/nightwatch/pull/4216/files

You might need to use the VSCode JS Debugger to understand how this part of the code works before solving this issue.

[Pikachu-345]

Okay, will be back soon with the solution.

[Dcoder10M]

Hey @garg3133, I noticed there hasn’t been any activity on the assigned issue in the last two weeks. If it’s no longer being worked on, I’d be happy to take it up and work on it.