Hi Shane,
(I'll continue with the top-posting, but I think it should be discouraged.)
As David just mentioned to me in the response to a related question, you
might want to check out
@controller.expects_render
which is now available in rspec trunk. While the response.body.should
be_empty k
Hello,
Are there are any best pracitces for integration-testing is rspec?
What about tutorials ?
I found only http://wincent.com/knowledge-base/
Using_Watir_with_RSpec_and_Rails
Chears
Hussein
___
rspec-users mailing list
rspec-users@rubyforge.or
Could we have at least a warning that mentions that parameters passed to
:render expectations are going to be thrown away and mention an
alternative way of spec-ing this behaviour?
>>> In trunk, when you call should_receive(:render) you will get an error
>>> saying you should use the
I was, for the first time, spec'ing a class that redefined ==. And my
spec was incorrect, so == was returning false.
The result was something like:
class C
def ==(other)
false
end
end
.. C.new.should == other...
expected other, got # (using ==)
But wait! Why on earth is == return
On 8/2/07, Hussein Morsy <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Are there are any best pracitces for integration-testing is rspec?
> What about tutorials ?
>
> I found only http://wincent.com/knowledge-base/
> Using_Watir_with_RSpec_and_Rails
We're working on getting the rbehave story runner merg
>
> We're working on getting the rbehave story runner merged into rspec
> and able to integrate w/ rails, but that's probably a couple of months
> away from reality.
>
nice to hear :-)
> Right now I just use rails integration testing and spec/ui to drive
> in-browser tests with Selenium or Wat
On 8/2/07, Hussein Morsy <[EMAIL PROTECTED]> wrote:
> >
> > We're working on getting the rbehave story runner merged into rspec
> > and able to integrate w/ rails, but that's probably a couple of months
> > away from reality.
> >
>
> nice to hear :-)
>
>
>
>
> > Right now I just use rails integrati
On 8/2/07, Jay Levitt <[EMAIL PROTECTED]> wrote:
> I was, for the first time, spec'ing a class that redefined ==. And my
> spec was incorrect, so == was returning false.
>
> The result was something like:
>
> class C
>def ==(other)
> false
>end
> end
>
> .. C.new.should == other...
>
>
> We're working on getting the rbehave story runner merged into rspec
> and able to integrate w/ rails, but that's probably a couple of months
> away from reality.
nice to hear :-)
> Right now I just use rails integration testing and spec/ui to drive
> in-browser tests with Selenium or Watir.
David Chelimsky wrote:
> On 8/2/07, Jay Levitt <[EMAIL PROTECTED]> wrote:
>> I was, for the first time, spec'ing a class that redefined ==. And my
>> spec was incorrect, so == was returning false.
>>
>> The result was something like:
>>
>> class C
>>def ==(other)
>> false
>>end
>> end
[Rails plugin 1.0.5]
Hi,
I am looking for some guidance.
When working on a partial which looks like this
I have some examples which should fail - I think - but do not:
it ' should fail' do
response.should have_tag( 'div.bug', :content => 'There is no
content!' )
end
On 8/2/07, sinclair bain <[EMAIL PROTECTED]> wrote:
> [Rails plugin 1.0.5]
>
>
> Hi,
> I am looking for some guidance.
> When working on a partial which looks like this
>
>
>
> I have some examples which should fail - I think - but do not:
>
> it ' should fail' do
>response.s
On 8/2/07, sinclair bain <[EMAIL PROTECTED]> wrote:
> [Rails plugin 1.0.5]
>
>
> Hi,
> I am looking for some guidance.
> When working on a partial which looks like this
>
>
>
> I have some examples which should fail - I think - but do not:
>
> it ' should fail' do
>response.s
13 matches
Mail list logo
