know /why/. I don't see
an easy way to include these sorts of messages in RSpec, which seems likely
to cause me to waste time on test failures. Am I missing something? How
are experienced RSpec users resolving this?
Thanks,
- Geoffrey
--
Geoffrey Wiseman
a validation rule changed and the validation failed), which aren't
as easy to message.
Still, i'm willing to give this approach a shot and see if this bothers me
increasingly less.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users
rails_rspec.rb in
lib/autotest. We were considering separating our acceptance tests from the
rest.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
for setup; the syntax would
look a little weird what with it_should_behave_like, but it's still a
thought.
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
:in
`alias_method'
from
/work/workspace/ng/vendor/plugins/rspec_on_rails/lib/spec/matchers/have.rb:4
from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require'
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users
of the spec, sometimes; when we're doing walkthroughs with the
customer representative, it's useful for him to be able to see the source as
well as the descriptions.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
a written tutorial or screencast
that walks this whole gamut in order if someone ever has time to do one.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
into the effort of creating a patch, but at the moment, I don't even
know why my route generation's failing.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
live with the
current approach as well, looks odd, but it's not a serious problem for me.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
I go
a-digging?
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
in a module
using include myself, got the same message above, but for a different
method. Not sure if 'include' was having the desired effect for me
(although I found another path by doing the include in helper.rb instead
of inside the Scenario, which solved the problem for me.
- Geoffrey
--
Geoffrey
and with_tag seem to work
fine on XML for me, so ... if upgrading is an option, might be worth a shot.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
so much what you
use. It's far more important for the committers to pick the tool that works
for them.)
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
13 matches
Mail list logo