You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed sometimes in tests (particularly when rewriting the error_handler to not die, not sure how that's the "magic" to it) that on failure to find_element you'll see the aforementioned error.
When looking at the code, it doesn't look like we're verifying the args are strings before doing regexp on them, so it shouldn't be too surprising we see this occasionally. The subroutine probably just needs to replace with blank string if the argument we're doing substitution with is undef.
The text was updated successfully, but these errors were encountered:
It just wasn't setting sane defaults before running regex replace.
This commit additionally adds test coverage for the modified
subroutine, hopefully in the correct place.
I also added a block to properly include the libdir when running
the affected test via prove (so that you don't have to use -Ilib
or something like that) whenever we're not running the test via
'dzil test' or anything else where we've plopped the libs and
tests in a temporary '.build' directory.
troglodyne
added a commit
to troglodyne/Selenium-Remote-Driver
that referenced
this issue
Aug 10, 2017
It just wasn't setting sane defaults before running regex replace.
This commit additionally adds test coverage for the modified
subroutine, hopefully in the correct place.
I also added a block to properly include the libdir when running
the affected test via prove (so that you don't have to use -Ilib
or something like that) whenever we're not running the test via
'dzil test' or anything else where we've plopped the libs and
tests in a temporary '.build' directory.
Made PR #332 to address this and up test cover for the affected subroutine.
Also did some things to the test to make my life easier when prototyping the test update. If you don't like em, feel free to holler and I'll pare it down to just the added assertions.
troglodyne
added a commit
to troglodyne/Selenium-Remote-Driver
that referenced
this issue
Oct 31, 2017
I've noticed sometimes in tests (particularly when rewriting the error_handler to not die, not sure how that's the "magic" to it) that on failure to find_element you'll see the aforementioned error.
When looking at the code, it doesn't look like we're verifying the args are strings before doing regexp on them, so it shouldn't be too surprising we see this occasionally. The subroutine probably just needs to replace with blank string if the argument we're doing substitution with is undef.
The text was updated successfully, but these errors were encountered: