What error do you get?
On 12 дек. 2007, at 19:39, David Nolan wrote:
> Hello,
> Running RSpec without DRB works fine.
> However, "spec -X" runs without error but provides no output at all,
> even though the DRB spec_server seems to be fine.
> Has anyone got some suggestions as to why and how to
I first started to check things existence in the resulting page but
quickly decided to only check for permission-affected links, forms,
etc. Though if your applications are RESTful it would be good idea to
check http method form uses and hidden fields that Rails uses to
piggyback PUT and DE
When specing observers I usually put them into models directory under /
spec. Then, when specs are run observer class can't be found unless I
remove --load-by mtime from spec.opts.
My question is what's the Big Idea behind loading specs in that order
by default? Shouldn't default spec.opts co
Seems that the assertion itself is just obvious
lambda { ... }.should_not raise_error ...
But given the fact environment.rb is loaded well before examples are
run, is it worth the effort it may take to spec out Rails bootstrap process?
Sorry if I do not get your question.
Scott Taylor wrote:
>
RSpec itself is a nice example of pretty large open source project that
uses RSpec for testing ;)
It's a general problem in TDD/BDD worlds: what to test and how to keep
it maintainable. I'd recommend reading mockobjects.com.
Priit Tamboom wrote:
> Hi!
>
> Can anybody link to some ror based pro
+1 for those
On 19/08/07, David Chelimsky <[EMAIL PROTECTED]> wrote:
> I'm thinking about other ways to be explicit about this (besides the
> verbose ":behaviour_type => :view". What if we added methods like:
>
> describe_model
> describe_view
> describe_controller
> describe_helper
--
MK
__
