#within with a bad selector succeeds silently
Reported by Peter Jaros | December 10th, 2008 @ 06:01 PM | in 0.4
The code
within("#bogus") do |scope|
end
when there is no element with the id "bogus" does not raise an error. It also runs the block. The code
within("#bogus") do |scope|
scope.dom
end
fails with a cryptic NoMethodError from calling
nil.to_html.
Comments and changes to this ticket
-
gaffo January 6th, 2009 @ 11:26 PM
- Tag set to “bug”
- State changed from “new” to “open”
This has been verified on the http://github.com/gaffo/webrat_r... on branch lh_90
-
Bryan Helmkamp January 17th, 2009 @ 11:04 AM
- Milestone set to “0.4”
-
Bryan Helmkamp January 17th, 2009 @ 01:28 PM
- State changed from “open” to “resolved”
(from [3e3d8e3659333dfc15effb6fcfe093e501ca4d84]) Raise a Webrat::NotFoundError if the scope passed to #within doesn't exist [#90 state:resolved] http://github.com/brynary/webrat...
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Ruby Acceptance Testing for Web applications.
People watching this ticket
Bryan Helmkamp
Peter Jaros
Tags
Referenced by
-
84
When a scope isn't found, Webrat should raise a good error
Dupe of #90
-
90
#within with a bad selector succeeds silently
(from [3e3d8e3659333dfc15effb6fcfe093e501ca4d84]) Raise a...