You can clone with
HTTPS or Subversion.
require have_link from the require farm
Adding have_link matcher.
Ignoring IntelliJ Idea files.
add rubyforge and homepage links to gemspec
bump to 1.0
pending spec re: failure messages when using inner expectations
expand the spec for nested expectations
support have_tag(".foo", :count => 0)
make the spec do what it said
spec to make sure arbitrary nested expectations keep working
make :matches? slightly less hideously large
support minimum/maximum in failure messages
include count details in failure messages
:matches? has grown big and ugly, but i want some assurance that
all of these messages are legible and make sense before i start
refactoring too heavily
spec failure messages a bit
Hack to duck-type CgiResponse to play nice with rspec_on_rails matchers
ignore pkg dir
spec and gem rake tasks
use hdoc.search() instead of overloaded '/'
support "response.should have_tag()"
demonstrate that this passes rspec LH ticket #316
more readme notes
helps to get the selector right
example using both inner text and options
pass the range spec
flesh out the README a bit
pending spec for :count => 1..4
support :count, :minimum, :maximum options
not really that lame.
only rescue ExpectationNotMetError
nested have_tag() is a logical AND
nested have_tag() calls
this is not as pretty as with_tag(), and can easily get confusing when you
start tossing should_not around, too. i just didn't feel like thinking
through how to get free-floating with_tag() calls working yet.
first pass at basic functionality
initial commit: README.