gartha1
commented
5 years ago This shows what happens if I use 'next' rather than 'step'.
It doesn't stop at each put statement. (which is what I want to do).
So either way, step or next, it doesn't work or doesn't do what I'd like.
Apples-MBP:aa apple$ ls -l
total 24
-rw-r--r-- 1 apple staff 17 29 Dec 03:52 Gemfile
-rw-r--r-- 1 apple staff 287 29 Dec 03:53 Gemfile.lock
-rw-r--r-- 1 apple staff 490 29 Dec 03:53 pbb_selenium_thing.rb
Apples-MBP:aa apple$ cat Gemfile
gem 'pry-byebug'
Apples-MBP:aa apple$ cat pbb_selenium_thing.rb
# https://stackoverflow.com/questions/53962313/in-ruby-i-cant-get-byebug-to-work-with-selenium?noredirect=1#comment94763217_53962313
require 'selenium-webdriver'
require 'pry'
require 'pry-byebug'
binding.pry
driver = Selenium::WebDriver.for:chrome
driver.navigate.to "http://google.com"
puts driver.find_element(:tag_name, 'input');
puts driver.find_element(:name, 'q');
driver.find_element(:name, 'q').send_keys("asdf");
#sleep 20
Apples-MBP:aa apple$ ruby pbb_selenium_thing.rb
WARN: Unresolved specs during Gem::Specification.reset:
ffi (>= 1.0.11, ~> 1.0)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
From: /Users/apple/rubyselenium1/aa/pbb_selenium_thing.rb @ line 9 :
4: require 'pry'
5: require 'pry-byebug'
6:
7: binding.pry
8:
=> 9: driver = Selenium::WebDriver.for:chrome
10:
11: driver.navigate.to "http://google.com"
12:
13: puts driver.find_element(:tag_name, 'input');
14: puts driver.find_element(:name, 'q');
[1] pry(main)> next
#<Selenium::WebDriver::Element:0x00007fb4a7bff8e8>
#<Selenium::WebDriver::Element:0x00007fb4a7b0c3c8>
Apples-MBP:aa apple$
manik1235
When I try using pry-byebug, I find I am unable to step through my code.
It goes into some internal code not written by me, and then gives an error about deadlock.
For anybody unfamiliar with Selenium, it is a library that lets a person programmatically control a web browser. I am using Mac osx. I had to do
$gem install selenium-webdriver(which I guess you know). And I had to install a chrome web driver which I did with$brew tap homebrew/caskand$brew cask install chrome driver. Selenium is running fine for me.The program below demonstrates an issue I'm having with pry-byebug.