I ran into the same problem. I solved this by dropping bind.pry in the test and stopping the selenium browser. When checking, I noticed that the js console generated errors: Selenium could not find the .js file.
The root of the problem was an outdated rails test application preloaded with spring. I installed the gem (points-in-rails), but still continued to run my tests using spring rspec, which did not have the proper directory to search for the js file.
restarting spring fixed the problem.
source share