error thrown for non-existing element

[chaim-aharonson-applitools]

Also added support for non-js-languages, not sure how to verify it works there as well

[tourdedave]

I'm not too familiar with the emitting code these days. But at a glance it looks good. For the other languages, it probably makes to tag one or more developers from the other SDK team for them to review. That, or Artem from the QA team.

[chaim-aharonson-applitools]

I'm not too familiar with the emitting code these days. But at a glance it looks good. For the other languages, it probably makes to tag one or more developers from the other SDK team for them to review. That, or Artem from the QA team.

@amitzur , following @tourdedave comment, should I add the test to overrides.js (for other frameworks) and by that will avoid tests failures and signal the other SDK team that it needs to be checked? in case I shouldn't add to overrides.js - should I mention Artem here?

[amitzur]

See one inline comment. I believe that even with my suggestion, the emitters for non-JS will have work to do to make this work. So skip it in overrides and tag Artem for help.

[amitzur]

I believe you could do:

error => assert.equal(error.message, 'Element not found!')

And avoid the need to add hasErrorMessage.