I need a look on a definition given for rspec and cucumber earlier by a
member in rspec group. Where can I find it
Regards,
Diwakar
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Oops, forgot the gist:
http://gist.github.com/312383
Thanks,
Mike
On Feb 23, 9:19 pm, Mike Grafton wrote:
> Hey all,
>
> I've been using Rspec for a while now, but this is the first time I've run
> up against the following problem: how do you use Rspec to test code that
> uses Rspec?
>
> Basica
Hey all,
I've been using Rspec for a while now, but this is the first time I've run
up against the following problem: how do you use Rspec to test code that
uses Rspec?
Basically my code takes as input a representation of example groups, and it
should dynamically create those example groups and t
On Tue, Feb 23, 2010 at 4:43 PM, Pat Maddox wrote:
>
> there is also the set equality matcher, which checks that the contents of two
> collections are equal irrespective of order:
>
> voters.should =~ [bob, sally]
>
I can't believe I didn't know =~ could be used for comparing
collections regard
Pat, Thanks for the response.
On Feb 23, 1:43 pm, Pat Maddox wrote:
> I'm going to argue that your design is off, and then ignore the rest of your
> post :)
Fair enough :) The 'design' in my example was made up on the spot to
try and illustrate the kind of issues I've been coming up against
wit
This sounds relatively straightforward - I didn't know it was a
possibility to dump the errors out as things were running. Anyone have
sample code?
TIA,
-Robert
On Feb 23, 2:53 pm, Matt Wynne wrote:
> Why don't you fiddle with the formatters to output the failures into
> another file, and th
I'm going to argue that your design is off, and then ignore the rest of your
post :)
class Person < Struct.new(:name, :age)
VOTING_AGE = 18
def voter?
age >= VOTING_AGE
end
end
Now your tests become very simple:
Person.new('Jenny', 17).should_not be_voter
Person.new('Bob', 18).should
On 23 Feb 2010, at 19:11, rlw wrote:
and still get the output of accumulated errors?
My environment is awful, slow, and not modifiable. (Just don't go
there! At least I get to program in Ruby, which makes up for
everything else.) So when I see some errors in a 300 example test
file, it takes a
and still get the output of accumulated errors?
My environment is awful, slow, and not modifiable. (Just don't go
there! At least I get to program in Ruby, which makes up for
everything else.) So when I see some errors in a 300 example test
file, it takes a long time (many minutes) for the file to
On Tue, Feb 23, 2010 at 3:41 PM, Matt Wynne wrote:
>
> On 23 Feb 2010, at 17:30, Scott Taylor wrote:
>
>>
>> Has there been any development on shared helpers / it_should_behave_like
>> feature in rspec?
>>
>> I forget the reasons, but I remember a patch for something like this was
>> rejected:
>>
I just use a factory method.
describe 'Authorize.net CIM gateway', :shared => true do
describe 'saving a card' do
describe 'preconditions' do
it "should raise an error if the card is not saved" do
lambda {
gateway.save_credit_card(Factory.build(:credit_card, :user =>
Hi all,
I've tried to figure out whether rspec has any features to make it
easier to make assertions against the elements of a collection, but I
haven't had any luck finding anything so far. I thought I'd explain
the problem here, and propose a potential feature that might mitigate
it.
Let's say I
On 23 Feb 2010, at 17:30, Scott Taylor wrote:
Has there been any development on shared helpers /
it_should_behave_like feature in rspec?
I forget the reasons, but I remember a patch for something like this
was rejected:
it_should_behave_like "an_entry", :locals => { :entry =>
Entr
Has there been any development on shared helpers / it_should_behave_like
feature in rspec?
I forget the reasons, but I remember a patch for something like this was
rejected:
it_should_behave_like "an_entry", :locals => { :entry => Entry.new }
OR:
before do
@entry = Entry.new
On Tue, Feb 23, 2010 at 5:41 AM, Jon Seidel CMC wrote:
> Hi... I've been studying rspec and found some problems on the rspec.info
> site:
>
> 1. Bad link. On page http://rspec.info/rails/writing/views.html, the link to
> "Spec::Rails::Expectations" (http://rspec.info/rdoc-rails/index.html) gets a
Hi... I've been studying rspec and found some problems on the rspec.info site:
1. Bad link. On page http://rspec.info/rails/writing/views.html, the link to
"Spec::Rails::Expectations" (http://rspec.info/rdoc-rails/index.html) gets a
404 error.
2. Bad core team links. On the community page (http
16 matches
Mail list logo
