> Any clues as to what could be wrong?
It's either a bug or some other tests have side effects that only show
up when run together. Let me try to replicate it on one of my
codebases and get back to you.
Best,
Sidu Ponnappa.
http://c42.in
http://rubymonk.com
On 3 November 2011 04:11, Bram wrote:
http://blog.davidchelimsky.net/2011/11/06/rspec-280rc1-is-released/
See the blog post for more information, but highlights include:
1. tag overrides
Now you can set tag/filter defaults in .rspec:
--tag ~javascript
or in RSpec.configure (in spec_helper.rb):
RSpec.configure {|c| c.filter_ru
On Nov 6, 2011, at 4:45 PM, Alex Chaffee wrote:
> Double negatives are not unconfusing.
>
> Not unlike chaining mutable decorator objects.
>
> (I was tempted to say "non-immutable" but that would chain the jokes)
>
> btw with .once and .twice, why not .thrice? Lady or no.
module Thrice
def t
Double negatives are not unconfusing.
Not unlike chaining mutable decorator objects.
(I was tempted to say "non-immutable" but that would chain the jokes)
btw with .once and .twice, why not .thrice? Lady or no.
--
Alex Chaffee - a...@stinky.com
http://alexchaffee.com
http://twitter.com/alexch
On Nov 1, 2011, at 12:59 PM, David Hofer wrote:
> I recently saw a test passing when it should have failed, because the
> person who wrote it used should_not_receive instead of
> should_receive. Here is a simple example illustrating the behavior:
>
> class MyTest
> def foo
>puts "hey"
> en
Hello,
I'm trying to stub out a method with the any_instance method, this
works well if I run the spec individually however when I do a full run
it will call the actual method:
example "" do
Library::Class.any_instance.stub(:method).and_return true
Model.create
end
This will fire off the befo
I recently saw a test passing when it should have failed, because the
person who wrote it used should_not_receive instead of
should_receive. Here is a simple example illustrating the behavior:
class MyTest
def foo
puts "hey"
end
def bar
foo
end
end
describe MyTest do
it "passe
