ngauthier capybara-slow_finder_errors issues

ngauthier / capybara-slow_finder_errors

MIT License

212 stars 19 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

New release?

#19 amy-hs closed 1 year ago
2
Use monotonic clock and catch expectation errors

#18 john-h-k closed 1 year ago
0
Ruby 3.x compatibility

#17 kivikakk closed 2 years ago
1
Add other suggestions as well for capybara fixes

#16 zoras opened 6 years ago
0
What's the point of 0.1.5

#15 pelletencate closed 6 years ago
1
Add support to capybara v3

#14 kevinhq closed 6 years ago
1
Add support for Capybara versions greater than 2.5

#13 devinrm closed 6 years ago
0
Capybara 3.0 support?

#12 erikaxel opened 6 years ago
3
[Regression] SlowFinderError not raised on version 0.1.4

#11 epidemian opened 7 years ago
0
Keep original exception and backtrace

#10 clemens closed 8 years ago
1
fix deprecation warning

#9 beanieboi closed 8 years ago
1
SlowFinder errors obscure failing assertion error messages

#8 zmoazeni closed 5 years ago
10
Handle zero wait time passed to a waiting finder

#7 jonleighton closed 9 years ago
4
Be more lenient about args to be more compatible with capybara versions

#6 carols10cents closed 9 years ago
4
Add a descriptive message to the raised error

#5 jjulian closed 9 years ago
1
Capybara dependency should be stricter?

#4 mikecmpbll closed 9 years ago
5
Raise current exception if it’s not a timeout

#3 pacoguzman closed 9 years ago
4
I'm getting a NoMethodError when the content is not in the page

#2 pacoguzman closed 9 years ago
2
Note that capybara/rspec's matchers already use the negated assertion in readme

#1 cgunther closed 9 years ago
3