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
When pry-byebug is added to this project's gem file and binding.pry is used within a feature test (RSpec or Cucumber with Capybara) the web thread/process waits on the binding.pry even if that breakpoint is located in the test file. When pry-byebug is removed, the web thread/process is not blocked and the user may click around around if they are using a non-headless browser (Selenium w/ Firefox in this case).
Steps to Reproduce
Clone this repo.
bundle
rake db:create
rspec spec/features/users/sign_in_spec.rb:11
When the break point is reached, attempt to click a link to a new page.
Expected Result
The server is able to handle the request and renders the page.
Actual Result
The server hangs waiting on the binding.pry call.
Continue on from the breakpoint.
Remove gem 'pry-byebug' from the gem file.
rspec spec/features/users/sign_in_spec.rb:11
When the break point is reached, attempt to click a link to a new page.
Actual Result
The server does not wait on the binding.pry call.
Is this intended behavior? Maybe this is related to #69?
The text was updated successfully, but these errors were encountered:
Repo that reproduces issue
Summary
When pry-byebug is added to this project's gem file and
binding.pry
is used within a feature test (RSpec or Cucumber with Capybara) the web thread/process waits on thebinding.pry
even if that breakpoint is located in the test file. When pry-byebug is removed, the web thread/process is not blocked and the user may click around around if they are using a non-headless browser (Selenium w/ Firefox in this case).Steps to Reproduce
bundle
rake db:create
rspec spec/features/users/sign_in_spec.rb:11
Expected Result
The server is able to handle the request and renders the page.
Actual Result
The server hangs waiting on the binding.pry call.
gem 'pry-byebug'
from the gem file.rspec spec/features/users/sign_in_spec.rb:11
Actual Result
The server does not wait on the binding.pry call.
Is this intended behavior? Maybe this is related to #69?
The text was updated successfully, but these errors were encountered: