From mark at mwilden.com  Sun Mar  1 01:19:00 2009
From: mark at mwilden.com (Mark Wilden)
Date: Sat, 28 Feb 2009 22:19:00 -0800
Subject: [rspec-users] cucumber ambiguous match
In-Reply-To: <49A9EAE4.3060704@benmabey.com>
References: <c715e640902281259w36702fdapa9847becc05d491f@mail.gmail.com>
	<49A9EAE4.3060704@benmabey.com>
Message-ID: <3c30da400902282219i427a421akd7f81a6ab22ba5fb@mail.gmail.com>

On Sat, Feb 28, 2009 at 5:54 PM, Ben Mabey <ben at benmabey.com> wrote:
> Joe Van Dyk wrote:
>> ? ? ?Ambiguous match of "a volunteer 'Joe' from 'Cincinnati'":
>>
>> ? ? ?features/step_definitions/user_steps.rb:1:in `/^a volunteer '(.*)'$/'
>> ? ? ?features/step_definitions/user_steps.rb:5:in `/^a volunteer
>> '(.*)' from '(.*)'$/'
>
> Try making your captures non-greedy (with ?).

Greedy or non-greedy, both regexps still match.

To distinguish between them, you (basically) need to replace '.*' with '[^']*' .

///ark

From matt at mattwynne.net  Sun Mar  1 08:27:31 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Sun, 1 Mar 2009 13:27:31 +0000
Subject: [rspec-users] Rspecing an enumerator from outside-in woes
In-Reply-To: <20090228212917.GA19515@devielle>
References: <20090228212917.GA19515@devielle>
Message-ID: <18FD4D43-0429-4977-A01D-E651D9E0CA2F@mattwynne.net>


On 28 Feb 2009, at 21:29, Shot (Piotr Szotkowski) wrote:

> I?m trying to spec a system from outside-in as an excercise in  
> ?emergent
> design? ? and so far I love it; it made me think about the design for
> two days before I even wrote the first spec? :)

Great :)

> My most-outside class seems to be a prime candidate for an #each  
> method.
> The attached (stripped) spec carrying two of the approaches I came up
> with passes, and raises the following quesitions ? any answer would be
> most appreciated!
>
> 1. A philosophical/kosherness question: In the finished system
> Decomposer#each will yield Decomposition objects, but as I?m specing
> from outside-in, the Decomposition class is not yet created. In the
> attached example I?m using an Array as a poor man?s Decomposition
> replacement. Is this a sane approach, or should I rather create
> a skeletal Decomposition#initialize instead?

I think you should try to write the specs so they won't have to change  
when you build the real implementation. That doesn't mean creating an  
actual Decomposition class just yet, but it does mean that you should  
return something that looks enough like one for the tests to still be  
valid when you swap one in.

> 2. The first spec shows my initial approach, with a variable polling  
> the
> stuff yielded by #each and then validating its contents, but it seems
> clumsy?

I think what you're finding clumsy here is the mocking setup. You  
don't always have to use mock objects as your 'test doubles' and often  
it's much easier (and leaves behind more flexible tests) if you use  
stubs rather than mocks.

In this case, although it's possible to create a test double for the  
Generators using RSpec's mocking framework, it's pretty awkward and  
hard to read. I would be tempted to write my own test double instead.  
Applying outside-in to the behaviour I want from the test double, I'd  
write this:
http://gist.github.com/72327

I'll leave it to you to code the #each method on the FakeGenerator,  
but hopefully you get the idea.

Notice that I just used an Array as the fake for @uv_gen - I might  
have missed something but I think that would provide an adequate  
double for the behaviour you had specified for the mock.

> 3. ?so I came up with the second, Decomposer.new.to_enum approach,  
> which
> simply validates the enumrator?s #next objects. Unfortunately, this  
> does
> not seem to trigger #should_receive(:each) on the *_gen mocks and made
> me #stub!(:each) on them instead. Is this because I?m using RSpec  
> 1.1.12
> with Ruby 1.9.1, or am I missing something on how message expectations
> work with lazy iterators (and, thus, #should_receive fail properly)?

I think you're getting too far into specifying the implementation  
here. I like the #each approach better.

Hope that helps.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From walketim at gmail.com  Sun Mar  1 11:50:37 2009
From: walketim at gmail.com (Tim Walker)
Date: Sun, 1 Mar 2009 09:50:37 -0700
Subject: [rspec-users] [cucumber] Cucumber and Chronic
Message-ID: <1ebf5a4d0903010850l54c7ee19i58dbbc48150a9339@mail.gmail.com>

This may have been discussed before but just wanted to pass along a
killer one-two punch that we stumbled upon as an excellent and natural
extension to our domain language around the expression and testing of
complex time based constructs.

Please consider:

Cucumber allows you to specify behavior in natural language.

Chronic is a natural language date/time parser written in pure Ruby.
(http://chronic.rubyforge.org/)

Example of a cucumber test:

Scenario: Test control operations
Given that I have have a control operation named ?set clock date time?
to ?Monday Jan 1, 2009 10:00?
When the control named ?set clock date time? runs
Then the clock should be ?10:00?

Now, this works fine, if you?re only testing that you can set the
clock to "Monday Jan 1, 2009 10:00". It gets more complex quickly when
you try to do much more than this. Adding chronic to the mix allows us
to define and use more complex time concepts in plain language. This
allows for the parsing of sentence fragments such as ?next month? and
?next Tuesday? and combine them in to complex structures such as ?next
Tuesday at 9:00? in a way that our tests continue to run as time
marches on.

For example:
>> sentence = "next tuesday at 3:00 pm"
=> "next tuesday at 3:00 pm"
>> time = Chronic.parse(sentence)
=> Tue Mar 03 15:00:00 -0700 2009

Now, the scenario can use this easily express clearly ?when? the
control operation runs in more complex and useful expressions, for
example:

Scenario: Test control operations
Given that I have have a control operation named ?set clock date time?
to "next tuesday at 3:00 pm"
When the control named ?set clock date time? runs
Then the clock should be ?next tuesday at 3:00 pm"

Scenario: Test spy sweeping schedules
Given that I have have a control operation named ?clean spies?  that
is scheduled to run ?next Monday at 8:00 AM"
And the customer has excluded ?weekdays? from allowing the control
operation ?clean spies? to run
When the control named ?set clock time? runs
Then it should log a message and quit

From phlip2005 at gmail.com  Sun Mar  1 12:29:15 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 01 Mar 2009 09:29:15 -0800
Subject: [rspec-users] how to get started with cucumber and assert{ 2.0 }
Message-ID: <goegle$l4g$1@ger.gmane.org>

[Warning: The following is not a question]

Cucumberists:

One of the irons in my fires is learning a little Cuke. So I try an experiment:

Feature: join
   In order to get premium content
   As an unregistered member
   I want to enter signup information for a new account

   Scenario: Proper signup
     Given newb is not in the user database
     And I go to /join

Okay, now that provides the standard Given suggestion, and I convert it to this:

   Given /^(.*) is not in the user database$/ do |newb|
     Subscription.find_by_username(newb).should_not be_nil
    end

Notice the "_not be_nil". I want to see a failure; otherwise if I see a success 
it might not be for the correct reason.

The failure looks like this:
   Scenario: Proper signup                   # features/join.feature:6
     Given newb is not in the user database  # .../webrat_steps.rb:101
       expected nil? to return false, got true (Spec::Expectations::Expect...)
       ./features/step_definitions/webrat_steps.rb:102:
                               in `Given /^(.*) is not in the user database$/'
       features/join.feature:7:in `Given newb is not in the user database' 
 

     And I go to /join          # features/step_definitions/webrat_steps.rb:6 
 


Now that reflects quite a bit, but the actual .should_not only reflected 
"expected nil? to return false, got true"

So let's upgrade to assert{ 2.0 }...

   Given /^(.*) is not in the user database$/ do |newb|
     assert{ Subscription.find_by_username(newb) != nil }
   end

Not to brag (too much), but the difference is like night and day:

     Given newb is not in the user database  # 
features/step_definitions/webrat_steps.rb:101
      assert{ (not(Subscription.find_by_username(newb) == nil)) }       --> false

                          newb                 --> "newb"
           Subscription.find_by_username(newb) --> nil. (AssertionFailedError)

       ./features/step_definitions/webrat_steps.rb:103:
                               in `Given /^(.*) is not in the user database$/'
       features/join.feature:7:in `Given newb is not in the user database'

Don't get me wrong - assert{ 2.0 } is for high-density tests of low-level code. 
Not for customer-facing verbiage.

So why can't every Cucumber do-end block use RubyReflector directly? Primarily 
because (with current technology), the reflector re-evaluates everything more 
than twice at fault time, and if you put your money-line inside a do-end block 
and it fails, the second re-evaluations might change their value and cause a 
confusing output!

Ruby1.9, with its built-in Ripper, will probably make this reflection easier...

-- 
   Phlip
   http://www.zeroplayer.com/


From shot at hot.pl  Sun Mar  1 12:30:06 2009
From: shot at hot.pl (Shot (Piotr Szotkowski))
Date: Sun, 1 Mar 2009 18:30:06 +0100
Subject: [rspec-users] Rspecing an enumerator from outside-in woes
In-Reply-To: <18FD4D43-0429-4977-A01D-E651D9E0CA2F@mattwynne.net>
References: <20090228212917.GA19515@devielle>
	<18FD4D43-0429-4977-A01D-E651D9E0CA2F@mattwynne.net>
Message-ID: <20090301173006.GD7432@devielle>

Thanks a lot, Matt, for your reply! It?s seriously most enlightening.

Matt Wynne:

> On 28 Feb 2009, at 21:29, Shot (Piotr Szotkowski) wrote:

>> 1. A philosophical/kosherness question: In the finished system
>> Decomposer#each will yield Decomposition objects, but as I?m specing
>> from outside-in, the Decomposition class is not yet created. In the
>> attached example I?m using an Array as a poor man?s Decomposition
>> replacement. Is this a sane approach, or should I rather create
>> a skeletal Decomposition#initialize instead?

> I think you should try to write the specs so they won't have to change 
> when you build the real implementation. That doesn't mean creating an 
> actual Decomposition class just yet, but it does mean that you should 
> return something that looks enough like one for the tests to still be 
> valid when you swap one in.

Hmm, interesting ? so an outside-in implementation should side-step 
using future classes? constructors, and the implementation code should 
actually change when the relevant classes appear?

I ended up creating a skeletal Decomposition class, but then had to 
add Decomposition#==(other) ? which, in turn, made me add attribute 
accessors ? just to be able to test against Decomposition objects in 
RSpec. 

Decomposition#== will be useful in the future, but currently it exists 
solely so I can use RSpec?s ?.should == Decomposition.new(?), which 
seems wrong. Hmm, another thing to ponder upon ? every time a new RSpec 
paradigm shows me something new, some other, unrelated spec begins to 
raise suspicions? :)

> I think what you're finding clumsy here is the mocking setup. You 
> don't always have to use mock objects as your 'test doubles' and often 
> it's much easier (and leaves behind more flexible tests) if you use 
> stubs rather than mocks.

Thanks a ton for the Array-based generators ? I haven?t thought of that; 
they are most interesting. I can?t use your example verbatim, as in my 
real code Decomposer.new takes class names and only then instantiates 
the relevant generators?, but it surely opened my eyes on stubbing 
objects with general-purpose classes rather than mocking them. I?ll 
see how I can use them to clean-up the specs. :)

? http://github.com/Chastell/art-decomp/commit/f9f8d3b2a3e431290d0656f7244b64f5376fab8f

>> 3. ?so I came up with the second, Decomposer.new.to_enum approach, 
>> which simply validates the enumrator?s #next objects. Unfortunately, 
>> this does not seem to trigger #should_receive(:each) on the *_gen 
>> mocks and made me #stub!(:each) on them instead. Is this because
>> I?m using RSpec 1.1.12 with Ruby 1.9.1, or am I missing something
>> on how message expectations work with lazy iterators (and, thus, 
>> #should_receive fail properly)?

> I think you're getting too far into specifying the
> implementation here. I like the #each approach better.

I think I agree ? but the real question was why don?t the (lazy) 
enumerator?s #next calls satisfy the mocks? #should_receive()s ? 
am I missing something fundamental, or is this simply an RSpec 1.1.12 
incompatibility with Ruby 1.9.1?

For reference, my original attachment: http://gist.github.com/72399 ? 
if you replace the #stub!()s in the second spec with #should_receive()s, 
the spec breaks with (allegedly) unsatisfied expectations.

? Shot
-- 
uo???n??suo? ??pun
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090301/b8481eb4/attachment.bin>

From matt at mattwynne.net  Sun Mar  1 13:53:38 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Sun, 1 Mar 2009 18:53:38 +0000
Subject: [rspec-users] Rspecing an enumerator from outside-in woes
In-Reply-To: <20090301173006.GD7432@devielle>
References: <20090228212917.GA19515@devielle>
	<18FD4D43-0429-4977-A01D-E651D9E0CA2F@mattwynne.net>
	<20090301173006.GD7432@devielle>
Message-ID: <D9A94771-2CB0-41F7-9B7A-D755D2DDCD84@mattwynne.net>


On 1 Mar 2009, at 17:30, Shot (Piotr Szotkowski) wrote:

> Thanks a lot, Matt, for your reply! It?s seriously most enlightening.
>
> Matt Wynne:
>
>> On 28 Feb 2009, at 21:29, Shot (Piotr Szotkowski) wrote:
>
>>> 1. A philosophical/kosherness question: In the finished system
>>> Decomposer#each will yield Decomposition objects, but as I?m specing
>>> from outside-in, the Decomposition class is not yet created. In the
>>> attached example I?m using an Array as a poor man?s Decomposition
>>> replacement. Is this a sane approach, or should I rather create
>>> a skeletal Decomposition#initialize instead?
>
>> I think you should try to write the specs so they won't have to  
>> change
>> when you build the real implementation. That doesn't mean creating an
>> actual Decomposition class just yet, but it does mean that you should
>> return something that looks enough like one for the tests to still be
>> valid when you swap one in.
>
> Hmm, interesting ? so an outside-in implementation should side-step
> using future classes? constructors, and the implementation code should
> actually change when the relevant classes appear?

I wouldn't suggest you did anything that meant you had to change the  
implementation later when you replace the fake with a real object.  
Assuming you wanted to keep your focus on the Decomposer class, but  
you knew that the concept of a Decomposition was a firm one in your  
design, you could define an empty Decomposition class, then stub the  
constructor to return a test double of some sort:

     class Decomposition
     end

     ...

     Decomposition.stub!(:new).and_return mock('Decomposition', :foo  
=> 'bar')


> I ended up creating a skeletal Decomposition class, but then had to
> add Decomposition#==(other) ? which, in turn, made me add attribute
> accessors ? just to be able to test against Decomposition objects in
> RSpec.
>
> Decomposition#== will be useful in the future, but currently it exists
> solely so I can use RSpec?s ?.should == Decomposition.new(?), which
> seems wrong. Hmm, another thing to ponder upon ? every time a new  
> RSpec
> paradigm shows me something new, some other, unrelated spec begins to
> raise suspicions? :)

I'm less fussy these days about adding a bit of code to make something  
testable - I think of it a bit like adding screws to let you take an  
appliance like a CD player apart, rather than sealing it all up with  
glue. Having said that, if you have to work hard to do this, there  
might be a smell in your design. You could consider the Decomposition  
with all those nasty getters all over it to be something you only use  
in your tests - a TestableDecomposition. One technique for creating a  
test double is to subclass the object you want to fake, and add extra  
behaviour in the subclass that make the object more testable, without  
adding its behaviour. Exposing some state in the form of getters, or  
adding #== might be an example of this.

Ideally though, you really want to avoid testing state and instead  
think about testing the interactions between objects. If the  
relationship between the Decomposer and the Decomposition is for one  
to create instances of the other, then I would be quite satisfied  
writing mock expectations on the Decomposition's constructor, like this:

      Decomposition.should_receive(:new).with [1,2]

>> I think what you're finding clumsy here is the mocking setup. You
>> don't always have to use mock objects as your 'test doubles' and  
>> often
>> it's much easier (and leaves behind more flexible tests) if you use
>> stubs rather than mocks.
>
> Thanks a ton for the Array-based generators ? I haven?t thought of  
> that;
> they are most interesting. I can?t use your example verbatim, as in my
> real code Decomposer.new takes class names and only then instantiates
> the relevant generators?, but it surely opened my eyes on stubbing
> objects with general-purpose classes rather than mocking them. I?ll
> see how I can use them to clean-up the specs. :)
>
> ? http://github.com/Chastell/art-decomp/commit/f9f8d3b2a3e431290d0656f7244b64f5376fab8f
>
>>> 3. ?so I came up with the second, Decomposer.new.to_enum approach,
>>> which simply validates the enumrator?s #next objects. Unfortunately,
>>> this does not seem to trigger #should_receive(:each) on the *_gen
>>> mocks and made me #stub!(:each) on them instead. Is this because
>>> I?m using RSpec 1.1.12 with Ruby 1.9.1, or am I missing something
>>> on how message expectations work with lazy iterators (and, thus,
>>> #should_receive fail properly)?
>
>> I think you're getting too far into specifying the
>> implementation here. I like the #each approach better.
>
> I think I agree ? but the real question was why don?t the (lazy)
> enumerator?s #next calls satisfy the mocks? #should_receive()s ?
> am I missing something fundamental, or is this simply an RSpec 1.1.12
> incompatibility with Ruby 1.9.1?
>
> For reference, my original attachment: http://gist.github.com/72399 ?
> if you replace the #stub!()s in the second spec with  
> #should_receive()s,
> the spec breaks with (allegedly) unsatisfied expectations.

Sorry, not sure about that one - I've not tried playing with these  
lazy enumerators - is this a Ruby 1.9 thing

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From mark at mwilden.com  Sun Mar  1 14:07:18 2009
From: mark at mwilden.com (Mark Wilden)
Date: Sun, 1 Mar 2009 11:07:18 -0800
Subject: [rspec-users] [cucumber] Cucumber and Chronic
In-Reply-To: <1ebf5a4d0903010850l54c7ee19i58dbbc48150a9339@mail.gmail.com>
References: <1ebf5a4d0903010850l54c7ee19i58dbbc48150a9339@mail.gmail.com>
Message-ID: <3c30da400903011107n7057e73fy89b2913085d222c0@mail.gmail.com>

On Sun, Mar 1, 2009 at 8:50 AM, Tim Walker <walketim at gmail.com> wrote:
>
> Now, this works fine, if you?re only testing that you can set the
> clock to "Monday Jan 1, 2009 10:00". It gets more complex quickly when
> you try to do much more than this. Adding chronic to the mix allows us
> to define and use more complex time concepts in plain language. This
> allows for the parsing of sentence fragments such as ?next month? and
> ?next Tuesday? and combine them in to complex structures such as ?next
> Tuesday at 9:00? in a way that our tests continue to run as time
> marches on.
>
> For example:
>>> sentence = "next tuesday at 3:00 pm"
> => "next tuesday at 3:00 pm"
>>> time = Chronic.parse(sentence)
> => Tue Mar 03 15:00:00 -0700 2009

Just be careful when when basing durations from "now" that daylight
savings time doesn't affect anything.

///ark

From lists at ruby-forum.com  Sun Mar  1 14:18:23 2009
From: lists at ruby-forum.com (Jeff Bowen)
Date: Sun, 1 Mar 2009 20:18:23 +0100
Subject: [rspec-users] starting a program from ruby on windows
Message-ID: <024cc34d2b0cfab954fe115ffae16d42@ruby-forum.com>

I simply want to start another program from this GUI and let the GUI
continue doing its own thing.  The other program will run independent of
the GUI and should stay running if the GUI is closed.

require 'fox16'
include Fox

class ClipMainWindow < FXMainWindow
  def initialize(anApp)
    # Initialize base class first
    super(anApp, "TEST", :opts => DECOR_ALL, :width => 500, :height =>
300)

    # The CCTV button
    button = FXButton.new(self, 'Connect To CCTV', :opts =>
BUTTON_NORMAL|LAYOUT_LEFT|LAYOUT_FILL_X)
    Dir.chdir("\\program files\\VBrick\\StreamPlayerPlus\\")
    button.connect(SEL_COMMAND){`StreamPlayerPlus.exe`}
    #button.connect(SEL_COMMAND) {Thread.new{(`StreamPlayerPlus.exe`)}}
    #button.connect(SEL_COMMAND) { exec("\\program
files\\VBrick\\StreamPlayerPlus\\StreamPlayerPlus.exe") }

  end

  def create
    super
    show(PLACEMENT_SCREEN)
  end
end

if __FILE__ == $0
  FXApp.new("TEST", "FXRuby") do |theApp|
    ClipMainWindow.new(theApp)
    theApp.create
    theApp.run
  end
end
-- 
Posted via http://www.ruby-forum.com/.

From andy at elaptics.co.uk  Sun Mar  1 16:05:08 2009
From: andy at elaptics.co.uk (Andrew Henson)
Date: Sun, 1 Mar 2009 21:05:08 +0000
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>
	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>
	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
Message-ID: <B3D1839B-B502-42BD-B835-D17E86B51A8F@elaptics.co.uk>


On 28 Feb 2009, at 22:26, Chris Flipse wrote:
>
> Yes!  This is what I was trying (poorly) to get at.
>
> Responsibility issues might be a large part of why it got factored  
> this way to begin with.  The global is bad.  Really bad, which is  
> why I'm trying to figure out something that works better.  But I  
> believe it was put in place so that a model can be responsible for  
> it's own authorization.  Some of the models are used and updated  
> from several different controllers, so any authorization logic  
> external to the model would have had to be repeated in several  
> different locations.
>
> The concern with that might be an over-enthusiastic embrace of DRY.   
> However some of the authorization stuff is Really Really Important,  
> so embedding the authorization logic in the model itself was seen as  
> a way to ensure it's not forgotten about.
>
> Half of my problem right now is that I'm not even sure what layer to  
> put model specific authentication!  If it's in the controller layer,  
> it's repeated logic in every controller that touches the model in  
> question.  If it's in the model, the logic is centralized, but now  
> your model needs not only to know about Users in general, it needs a  
> specific user.  You have less chance of someone doing Something They  
> Shouldn't due to a forgotten check in a controller, but the test  
> setup seems to suffer for it.
>
> One way or the other, the global User.current is going away --  
> soon.  It's just a question of what to replace it with, and where.

I was only skim-reading this topic so I may be misunderstanding what  
you're after but I think that maybe what you're looking for is  
something like http://github.com/stffn/declarative_authorization/tree/master 
, a Rails plugin that allows you to specify the authorisation in a  
single place for both controllers and at the model level. I've just  
started using it for a project and so far it seems a good fit, though  
I'm trying to keep the whole app as restful resources which makes  
things a little easier.

It also has a few test helper methods which make it really easy to use  
with Cucumber and RSpec.

Andy

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090301/cf7d2668/attachment.html>

From yi2004 at gmail.com  Sun Mar  1 08:38:12 2009
From: yi2004 at gmail.com (ty)
Date: Sun, 1 Mar 2009 05:38:12 -0800 (PST)
Subject: [rspec-users] Is there a way to generate spec for existing
	controllers?
Message-ID: <75cf4ca0-0e93-4b38-abda-e052dc4feac2@k19g2000prh.googlegroups.com>

Hi list,

We just start using RSpec and rspec_on_rails for a existing Rails
project.
After run script/generate rspec. It only generate the structure
folders.
We've got quite a few controllers and models. I wonder is it a way to
auto-generate specs for them.

Many thanks

ty

From dchelimsky at gmail.com  Sun Mar  1 18:18:22 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 1 Mar 2009 17:18:22 -0600
Subject: [rspec-users] How do you mock a local variable ?
In-Reply-To: <1f285f53-7c17-443f-a928-cd7f6a6d770b@j8g2000yql.googlegroups.com>
References: <1f285f53-7c17-443f-a928-cd7f6a6d770b@j8g2000yql.googlegroups.com>
Message-ID: <57c63afe0903011518se9c9c0ardbc01a5b0ca6f7d5@mail.gmail.com>

Sorry all - this was sitting waiting for moderation, but it's already
been addressed.

Cheers,
David

On Thu, Feb 26, 2009 at 2:43 PM, MathLef <mlefrancois19 at gmail.com> wrote:
> Hi,
>
> I need some help to spec' a function I am developping. Note that the
> function is still not complete, cause I am trying to spec' it while
> working on it, as it should be ! Basically, this is what my function
> should look like :
>
> private
> def obtain_criterias(hash_params)
> ?crits = {}
> ?hash_params.each {
> ? |key, val|
> ? ?crits[key.to_sym] = StringUtils.sanitize(val).upcase if not (key
> == "controller" || key == "action")
> ?}
> ?return crits
> end
>
> ?- hash_params is a hash table of some parameters received by a
> controller
> ?- StringUtils.sanitize removes all kind of accents from the string
> passed in parameters
> ?- it is encapsulated in a controller
>
> The problem is with the local variable "crits" on which I can not seem
> to have any kind of control in my rspec. Now, I am wandering, is this
> (still) a good way to code from a spec point of view ?! Can you give
> me ideas on ways to spec this ?
>
> Many thanks in advance !
> Mathieu
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From mark at mwilden.com  Sun Mar  1 18:30:45 2009
From: mark at mwilden.com (Mark Wilden)
Date: Sun, 1 Mar 2009 15:30:45 -0800
Subject: [rspec-users] [cucumber] Cucumber and Chronic
In-Reply-To: <3c30da400903011107n7057e73fy89b2913085d222c0@mail.gmail.com>
References: <1ebf5a4d0903010850l54c7ee19i58dbbc48150a9339@mail.gmail.com>
	<3c30da400903011107n7057e73fy89b2913085d222c0@mail.gmail.com>
Message-ID: <3c30da400903011530vbf3b9b8v3ace26553e29a078@mail.gmail.com>

On Sun, Mar 1, 2009 at 11:07 AM, Mark Wilden <mark at mwilden.com> wrote:
>
> Just be careful when when basing durations from "now" that daylight
> savings time doesn't affect anything.

Along the same lines, don't write tests that assume 1.month.ago was <
29 days ago, or specs could start failing in March (as just happened
with us). :)

///ark

From dchelimsky at gmail.com  Sun Mar  1 18:51:06 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 1 Mar 2009 17:51:06 -0600
Subject: [rspec-users] Is there a way to generate spec for existing
	controllers?
In-Reply-To: <75cf4ca0-0e93-4b38-abda-e052dc4feac2@k19g2000prh.googlegroups.com>
References: <75cf4ca0-0e93-4b38-abda-e052dc4feac2@k19g2000prh.googlegroups.com>
Message-ID: <57c63afe0903011551k77426d7fy560ba9d36736976f@mail.gmail.com>

On Sun, Mar 1, 2009 at 7:38 AM, ty <yi2004 at gmail.com> wrote:
> Hi list,
>
> We just start using RSpec and rspec_on_rails for a existing Rails
> project.
> After run script/generate rspec. It only generate the structure
> folders.
> We've got quite a few controllers and models. I wonder is it a way to
> auto-generate specs for them.

Nope. Sorry.

>
> Many thanks
>
> ty
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From joevandyk at gmail.com  Sun Mar  1 20:04:44 2009
From: joevandyk at gmail.com (Joe Van Dyk)
Date: Sun, 1 Mar 2009 17:04:44 -0800
Subject: [rspec-users] testing multiple sessions in cucumber/webrat
In-Reply-To: <9e50e5690902281717v7a072f78k998321c48cb87ece@mail.gmail.com>
References: <c715e640902281204wbfc9f39p43c7d3a7159d5389@mail.gmail.com>
	<9e50e5690902281717v7a072f78k998321c48cb87ece@mail.gmail.com>
Message-ID: <c715e640903011704v35f22768l67b7edaff043f97e@mail.gmail.com>

So you're saying no?  :D

On Sat, Feb 28, 2009 at 5:17 PM, BJ Clark <bj at aboutus.org> wrote:
> Joe,
> I would test this in 2 steps.
> I'd first test that whatever state change (or whatever happens when you User
> A clicks the link) takes place.
> Then in another test, I'd check that, given a certain state (or again,
> whatever is supposed to happen), then User B sees whatever.
> HTH,
> BJ Clark
>
> On Sat, Feb 28, 2009 at 12:04 PM, Joe Van Dyk <joe at pinkpucker.net> wrote:
>>
>> Is it possible to have a scenario where you are testing the
>> interaction between two different session?
>>
>> i.e.
>>
>> Given User A clicks this link
>> Then User B should see this
>>
>> It used to be possible, but don't know if it still is.
>>
>> Joe
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From lists at ruby-forum.com  Sun Mar  1 21:17:30 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 2 Mar 2009 03:17:30 +0100
Subject: [rspec-users] Cucumber for large projects
In-Reply-To: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
References: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
Message-ID: <05103fc0825a21747e3e71ce0cd53c93@ruby-forum.com>

Tom ten Thij wrote:
> We will be using Cucumber for a fairly large project. Are there any
> areas that cucumber is lacking when there are many scenarios?
> 
> I believe the best candidate for showing our client the scenario
> results is the html output. It strikes me that that becomes fairly
> cumbersome to check with many scenarios. Methinks some javascript code
> to hide all passing scenarios / features would be useful. Is there any
> work being done on this?
> 
> In which areas could we help cucumber accommodate for large projects?
> 
> Tom.

Try the progress formatter.

$ cucumber -f progress -r features features
-- 
Posted via http://www.ruby-forum.com/.

From zach.dennis at gmail.com  Sun Mar  1 21:14:17 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Sun, 1 Mar 2009 21:14:17 -0500
Subject: [rspec-users] testing multiple sessions in cucumber/webrat
In-Reply-To: <c715e640903011704v35f22768l67b7edaff043f97e@mail.gmail.com>
References: <c715e640902281204wbfc9f39p43c7d3a7159d5389@mail.gmail.com>
	<9e50e5690902281717v7a072f78k998321c48cb87ece@mail.gmail.com>
	<c715e640903011704v35f22768l67b7edaff043f97e@mail.gmail.com>
Message-ID: <85d99afe0903011814u434e5062rf3e4bca06a3bef9@mail.gmail.com>

On Sun, Mar 1, 2009 at 8:04 PM, Joe Van Dyk <joevandyk at gmail.com> wrote:
> So you're saying no? ?:D

It is possible, you simply have to logout from UserA and log in as
UserB. Also, although it's not exposed with webrat IIRC it is possible
to have selenium run to separate browsers at the same time. You could
theoretically have UserA and UserB logged in concurrently doing their
thing,

Zach



>
> On Sat, Feb 28, 2009 at 5:17 PM, BJ Clark <bj at aboutus.org> wrote:
>> Joe,
>> I would test this in 2 steps.
>> I'd first test that whatever state change (or whatever happens when you User
>> A clicks the link) takes place.
>> Then in another test, I'd check that, given a certain state (or again,
>> whatever is supposed to happen), then User B sees whatever.
>> HTH,
>> BJ Clark
>>
>> On Sat, Feb 28, 2009 at 12:04 PM, Joe Van Dyk <joe at pinkpucker.net> wrote:
>>>
>>> Is it possible to have a scenario where you are testing the
>>> interaction between two different session?
>>>
>>> i.e.
>>>
>>> Given User A clicks this link
>>> Then User B should see this
>>>
>>> It used to be possible, but don't know if it still is.
>>>
>>> Joe
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From phlip2005 at gmail.com  Sun Mar  1 22:08:23 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 01 Mar 2009 19:08:23 -0800
Subject: [rspec-users] Is there a way to generate spec for existing
	controllers?
In-Reply-To: <57c63afe0903011551k77426d7fy560ba9d36736976f@mail.gmail.com>
References: <75cf4ca0-0e93-4b38-abda-e052dc4feac2@k19g2000prh.googlegroups.com>
	<57c63afe0903011551k77426d7fy560ba9d36736976f@mail.gmail.com>
Message-ID: <gofij9$clh$1@ger.gmane.org>

David Chelimsky wrote:

> ty wrote:

>> We just start using RSpec and rspec_on_rails for a existing Rails
>> project.

No unit tests, right?

>> After run script/generate rspec. It only generate the structure
>> folders.
>> We've got quite a few controllers and models. I wonder is it a way to
>> auto-generate specs for them.
> 
> Nope. Sorry.

Ask your goal-donor what feature they'd like to see in a spec.

That is the point of specs - writing verbiage that a "product manager" or 
"business analyst" can review.

-- 
   Phlip


From ben at benmabey.com  Sun Mar  1 22:46:39 2009
From: ben at benmabey.com (Ben Mabey)
Date: Sun, 01 Mar 2009 20:46:39 -0700
Subject: [rspec-users] testing multiple sessions in cucumber/webrat
In-Reply-To: <c715e640902281204wbfc9f39p43c7d3a7159d5389@mail.gmail.com>
References: <c715e640902281204wbfc9f39p43c7d3a7159d5389@mail.gmail.com>
Message-ID: <49AB569F.6080800@benmabey.com>

Joe Van Dyk wrote:
> Is it possible to have a scenario where you are testing the
> interaction between two different session?
>
> i.e.
>
> Given User A clicks this link
> Then User B should see this
>
> It used to be possible, but don't know if it still is.
>
> Joe
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>   

Have you tried creating a new webrat session?  I haven't looked into it 
myself, but like you said it was possible.  Not much has changed with 
the underling rails integration session so I imagine that if you just 
created a new webrat session and used that for user B then you should be 
fine.  (So, you will have to store this second session as an instance 
var in the other session.. kinda odd but I would try it.)  I would be 
interested to hear if this works, so please report back.  BTW, you might 
get some better answers on the webrat mailing list.

-Ben

From sfeley at gmail.com  Mon Mar  2 00:07:31 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Mon, 2 Mar 2009 00:07:31 -0500
Subject: [rspec-users] [cucumber] Cucumber and Chronic
In-Reply-To: <3c30da400903011530vbf3b9b8v3ace26553e29a078@mail.gmail.com>
References: <1ebf5a4d0903010850l54c7ee19i58dbbc48150a9339@mail.gmail.com>
	<3c30da400903011107n7057e73fy89b2913085d222c0@mail.gmail.com>
	<3c30da400903011530vbf3b9b8v3ace26553e29a078@mail.gmail.com>
Message-ID: <1fb4df0903012107q6d65aaf6w255fb01233064f95@mail.gmail.com>

On Sun, Mar 1, 2009 at 6:30 PM, Mark Wilden <mark at mwilden.com> wrote:
> On Sun, Mar 1, 2009 at 11:07 AM, Mark Wilden <mark at mwilden.com> wrote:
>>
>> Just be careful when when basing durations from "now" that daylight
>> savings time doesn't affect anything.
>
> Along the same lines, don't write tests that assume 1.month.ago was <
> 29 days ago, or specs could start failing in March (as just happened
> with us). :)

You wouldn't happen to be on the Microsoft Zune development team,
would you?  >8->

For date testing, I've just discovered and successfully used Notahat's
"time_travel" plugin:
http://github.com/notahat/time_travel/

It's essentially a scoped override for Time.now, so that any code you
pass it executes as if the current time is frozen at whatever you tell
it.  This makes repeatable testing much, much simpler.  This is the
same guy who developed Machinist (my preferred fixture/factory tool)
and not_a_mock, which I used for a little while before I abandoned
mocking.  >8->  So...yeah.  He does good stuff.


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From lists at ruby-forum.com  Mon Mar  2 05:08:30 2009
From: lists at ruby-forum.com (Juanma Cervera)
Date: Mon, 2 Mar 2009 11:08:30 +0100
Subject: [rspec-users] Changes in specs for routes in rspec 1.1.99.x
Message-ID: <4b8a6a1f20a84f53853d62c062603af2@ruby-forum.com>

Trying the next release of rspec, I have had to make changes in the
existing specs for routing.
I have written an script with sed that makes this automatically (two
files)


spec/upgrade.sed
================
/route_for/s/id => 1/id => "1"/g
/route_for.*create/s/== \(["'].*["']\)/== {:path => \1, :method =>
:post}/
/route_for.*update/s/== \(["'].*["']\)/== {:path => \1, :method =>
:put}/
/route_for.*destroy/s/== \(["'].*["']\)/== {:path => \1, :method =>
:delete}/


and
spec/upgrade
============
for f in `find controllers -name "*routing*rb" -type f`; do sed -i -f
upgrade.sed $f; done


You shoud make this file executable and run it

I hope this helps somebody.
Juanma
-- 
Posted via http://www.ruby-forum.com/.

From joe at josephwilk.net  Mon Mar  2 05:31:20 2009
From: joe at josephwilk.net (Joseph Wilk)
Date: Mon, 02 Mar 2009 10:31:20 +0000
Subject: [rspec-users] [cucumber] noob Q deleteing from a list.
In-Reply-To: <7b0154b4-105b-4398-9b43-175c64ba95e5@17g2000vbf.googlegroups.com>
References: <a03a8676-679c-4974-84dd-3bea8e38e1fe@r34g2000vbp.googlegroups.com>	<8d961d900902260759u7905a806h231f75aa580a9fc7@mail.gmail.com>
	<3c30da400902261053k65065af1y95453d6c02dc7504@mail.gmail.com>
	<49A6E8C7.5000909@benmabey.com>
	<7b0154b4-105b-4398-9b43-175c64ba95e5@17g2000vbf.googlegroups.com>
Message-ID: <49ABB578.5050709@josephwilk.net>

John Ivanoff wrote:
> Thanks for all the help. With the
> puts response.body
> I was able so see what was going on. I know that I am now deleting the
> third frooble!!!!
>
> Now when
> Then I should see the following froobles:
> I get this error
> ----------------------------------
> Then I should see the following froobles:  # features/step_definitions/
> frooble_steps.rb:12
>       expected: ["description 1"],
>            got: "description 1" (using ==)
>       Diff:
>       @@ -1,2 +1,2 @@
>       -["description 1"]
>       +"description 1" (Spec::Expectations::ExpectationNotMetError)
>       ./features/step_definitions/frooble_steps.rb:18:in `Then /^I
> should see the following froobles:$/'
>       /Library/Ruby/Gems/1.8/gems/webrat-0.4.0/lib/webrat/core/
> matchers/have_xpath.rb:50:in `call'
>       /Library/Ruby/Gems/1.8/gems/webrat-0.4.0/lib/webrat/core/
> matchers/have_xpath.rb:50:in `matches_nokogiri?'
>       /Library/Ruby/Gems/1.8/gems/webrat-0.4.0/lib/webrat/core/
> matchers/have_xpath.rb:15:in `matches?'
>       ./features/step_definitions/frooble_steps.rb:17:in `Then /^I
> should see the following froobles:$/'
>       (eval):3:in `each_with_index'
>       ./features/step_definitions/frooble_steps.rb:16:in `each'
>       ./features/step_definitions/frooble_steps.rb:16:in
> `each_with_index'
>       ./features/step_definitions/frooble_steps.rb:16:in `Then /^I
> should see the following froobles:$/'
>       features/list.feature:15:in `Then I should see the following
> froobles:'
> ----------------------------------
>
> Again any help will be appreciated.
>   
You are expecting a list  in your test but you are getting back a string.
> John
>
> On Feb 26, 1:08 pm, Ben Mabey <b... at benmabey.com> wrote:
>   
>> Mark Wilden wrote:
>>     
>>> On Thu, Feb 26, 2009 at 7:59 AM, aslak hellesoy
>>> <aslak.helle... at gmail.com> wrote:
>>>       
>>>> puts response.body
>>>>         
>>> Another debugging technique we use is
>>>       
>>> When /^I view the response$/ do
>>>   Tempfile.open("response") do |file|
>>>     file.print response.body
>>>     `open "file://#{file.path}"`
>>>     sleep 2
>>>   end
>>> end
>>>       
>>> ///ark
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-us... at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>       
>> If you are using webrat and you want to see the HTML repsonse you can
>> use: save_and_open_page
>>
>> -Ben
>> _______________________________________________
>> rspec-users mailing list
>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
>>     
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
>   


-- 
Joseph Wilk
http://blog.josephwilk.net


From aidy.lewis at googlemail.com  Mon Mar  2 08:53:38 2009
From: aidy.lewis at googlemail.com (aidy lewis)
Date: Mon, 2 Mar 2009 13:53:38 +0000
Subject: [rspec-users] Cucumber for large projects
In-Reply-To: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
References: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
Message-ID: <7ac2300c0903020553l77e4c8e4ub2dd6563b5382863@mail.gmail.com>

Hi Tom,

We have written an extension that counts your tests and provides a
link(s) to the failure backtrace in the Cucumber HTML.

There seem to be issues when Cucumber writes to the HTML over around
800 steps, so we are waiting for version 0.2.

Aidy

On 26/02/2009, Tom ten Thij <mail at tomtenthij.nl> wrote:
> We will be using Cucumber for a fairly large project. Are there any
>  areas that cucumber is lacking when there are many scenarios?
>
>  I believe the best candidate for showing our client the scenario
>  results is the html output. It strikes me that that becomes fairly
>  cumbersome to check with many scenarios. Methinks some javascript code
>  to hide all passing scenarios / features would be useful. Is there any
>  work being done on this?
>
>  In which areas could we help cucumber accommodate for large projects?
>
>  Tom.
>  _______________________________________________
>  rspec-users mailing list
>  rspec-users at rubyforge.org
>  http://rubyforge.org/mailman/listinfo/rspec-users
>

From zuperinfinite at gmail.com  Mon Mar  2 09:15:33 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Mon, 2 Mar 2009 15:15:33 +0100
Subject: [rspec-users] testing multiple sessions in cucumber/webrat
In-Reply-To: <c715e640902281204wbfc9f39p43c7d3a7159d5389@mail.gmail.com>
References: <c715e640902281204wbfc9f39p43c7d3a7159d5389@mail.gmail.com>
Message-ID: <2B9D31AD-A815-4BB0-9882-72B8197CACE6@gmail.com>


On 28-feb-2009, at 21:04, Joe Van Dyk wrote:

> Is it possible to have a scenario where you are testing the
> interaction between two different session?

If you mean something along these lines:

User A uploads a picture,
User B logs in to see the picture uploaded by User A

that is possible.

I use this construct a lot to test-drive some revisions code I came  
up with. Something like:

Given I am logged in
And     there is an article
And    the title of the article has been modified twice
When I  compare the revisions
Then  I should see the difference in title

GIven "the title of the article has been modified twice" do
   Given "I am logged in as an editor"

   2.times do |i|
     visit edit_article_path(@article)
     fill_in "Title", :with => "Title #{i}"
     click_button "Save"
   end

   Given "I am logged in as a writer"
end

cheers,
bartz

From zuperinfinite at gmail.com  Mon Mar  2 09:18:55 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Mon, 2 Mar 2009 15:18:55 +0100
Subject: [rspec-users] Is there a way to generate spec for existing
	controllers?
In-Reply-To: <gofij9$clh$1@ger.gmane.org>
References: <75cf4ca0-0e93-4b38-abda-e052dc4feac2@k19g2000prh.googlegroups.com>
	<57c63afe0903011551k77426d7fy560ba9d36736976f@mail.gmail.com>
	<gofij9$clh$1@ger.gmane.org>
Message-ID: <779347D0-C4BA-432F-865D-3220B3FBDEF9@gmail.com>


On 2-mrt-2009, at 4:08, Phlip wrote:

> David Chelimsky wrote:
>
>> ty wrote:
>
>>> We just start using RSpec and rspec_on_rails for a existing Rails
>>> project.
>
> No unit tests, right?
>
>>> After run script/generate rspec. It only generate the structure
>>> folders.
>>> We've got quite a few controllers and models. I wonder is it a  
>>> way to
>>> auto-generate specs for them.
>> Nope. Sorry.
>
> Ask your goal-donor what feature they'd like to see in a spec.
>
> That is the point of specs - writing verbiage that a "product  
> manager" or "business analyst" can review.

I fully agree.
For views though, there is http://github.com/hashrocket/view_specify/ 
tree/master
Haven't tried it, and never will :).

cheers,
bartz


From zuperinfinite at gmail.com  Mon Mar  2 09:20:55 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Mon, 2 Mar 2009 15:20:55 +0100
Subject: [rspec-users] be_valid (validates_format_of ..., :on => :create)
In-Reply-To: <38f994ca-7da0-43cc-a013-34e51a5cca7e@j8g2000yql.googlegroups.com>
References: <38f994ca-7da0-43cc-a013-34e51a5cca7e@j8g2000yql.googlegroups.com>
Message-ID: <6F193A20-D635-44D0-BB30-11F8341D12AA@gmail.com>


On 28-feb-2009, at 11:45, MAwiniarski wrote:

> Greetings,
>
> How to write Example which will check if model's variable's
> format is valid using :on => :create, like this:
>
> class User < ActiveRecord::Base
> ...
>  validates_format_of       :email, :with => /.../, :on => :create
> ...
>
> Using following code is not right:
> it "should ..." do
>    @user = users(:example_user)
>    @user.email = 'invalid_email_format'
>    @user.save
>    @user.should_not be_valid
> end

Try:

it "should ..." do
    user = User.new # create a NEW user, instead of loading an  
already saved user from a fixtures file
    user.email = 'invalid_email_format'
    user.should_not be_valid
    user.should have(1).errors_on(:email)
end

cheers,
bartz

From apremdas at gmail.com  Mon Mar  2 09:56:48 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Mon, 2 Mar 2009 14:56:48 +0000
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>
	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>
	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
Message-ID: <88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>

Personally I think this should be in the model layer. As you've pointed it
you get alot of repetition if its in the controller layer. But putting
business logic in the controller layer goes against the fundamentals of MVC,
and is a bit of a Rails anti-pattern (fat controller).

So given that the rules should be in the model then the question is which
part of the model should have this responsibility and how do you call it.
Three choices come to mind here

1) Place the rule inside User
2) Place the rule inside the affected model
3) Create a new model(s) to encapsulate this functionality. It might be
helpful to think of this as a service which models can use

1) Pollutes User with additional responsibility, but you can live with this
so long as things remain very simple

2) Isn't DRY if the rules apply to many different models

3) Is more complex

It sounds like you have 1) and should consider moving to 3). However you
might get some change out of improving 1) first if you can, by using
standard refactorings

Have you considered creating a spike and doing a bit of BDD on the spike.
i.e write the stories you want to write, implement simple code for them and
try and work out the interactions you need from there. Even if you don't use
the spike code in your application this might help you get a better set of
features for this piece of functionality, (not tainted by the implementation
of the existing code. These features then can be applied to your legacy
project and perhaps other projects as well.

HTH

Andrew


2009/2/28 Chris Flipse <cflipse at gmail.com>

>
>
> On Sat, Feb 28, 2009 at 3:42 PM, Ben Mabey <ben at benmabey.com> wrote:
>
>> Chris Flipse wrote:
>>
>>> I've actually been okay with it at the unit testing / rspec level -- I've
>>> had it stubbed as you describe for a while.
>>>
>>> The pain point came in as I was trying to setup data for Cucumber ...
>>> Which, listening to my tests, tells me that the current structure is bad.  I
>>> was more curious to see how others are handling that sort of situation.
>>>
>>
>> If you are seeing state from one scenario bleed over to the next I would
>> suggest something like this in your env.rb:
>>
>> After do
>> User.reset_current
>> end
>>
>
> Yep got that.  The tests are actually *working*, it's just that the setup
> has gotten painful.
>
>
>>
>>> I want to get *away* from the global variable, I'm just not entirely sure
>>> what the target should be.  There doesn't seem to be a whole lot of talk
>>> about actual implementation specifics around model level authorization.
>>>
>>
>> I generally have a current_user method defined of my controller to return
>> the logged in user.
>
>
> Same.  Authentication was originally generated using acts_as_authenticated,
> so the standard conventions at the controller level are in place.
>
>
>> Assuming that your app is only using User.current in your controllers you
>> could try to move towards something like that... If you have models
>> accessing User.current then it truly is being used as a global. :/
>
>
> It truly is being used as a global.
>
>
>> The user will then have some permissions methods that may take other
>> objects or symbols.  The method will simply return a boolean telling if the
>> user is authorized or not.  That logic usually is based on the role(s) of
>> that user or relationship with the passed in object.  Having this logic in
>> the user could be viewed as a responsibility issue- should the user really
>> be responsible for telling if it is authorized for everything?  In general I
>> do this for most simple cases.  Only when it starts to get complex do I move
>> it out into a Manager-like object.
>>
>
> Yes!  This is what I was trying (poorly) to get at.
>
> Responsibility issues might be a large part of why it got factored this way
> to begin with.  The global is bad.  Really bad, which is why I'm trying to
> figure out something that works better.  But I believe it was put in place
> so that a model can be responsible for it's own authorization.  Some of the
> models are used and updated from several different controllers, so any
> authorization logic external to the model would have had to be repeated in
> several different locations.
>
> The concern with that might be an over-enthusiastic embrace of DRY.
> However some of the authorization stuff is Really Really Important, so
> embedding the authorization logic in the model itself was seen as a way to
> ensure it's not forgotten about.
>
> Half of my problem right now is that I'm not even sure what *layer* to put
> model specific authentication!  If it's in the controller layer, it's
> repeated logic in every controller that touches the model in question.  If
> it's in the model, the logic is centralized, but now your model needs not
> only to know about Users in general, it needs a specific user.  You have
> less chance of someone doing Something They Shouldn't due to a forgotten
> check in a controller, but the test setup seems to suffer for it.
>
> One way or the other, the global User.current is going away -- soon.  It's
> just a question of what to replace it with, and where.
>
> --
> // anything worth taking seriously is worth making fun of
> // http://blog.devcaffeine.com/
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090302/42e3f032/attachment.html>

From lists at ruby-forum.com  Mon Mar  2 10:07:23 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 2 Mar 2009 16:07:23 +0100
Subject: [rspec-users] Feature Size-Scope-Scale
Message-ID: <1ef2dc9f45c1e3ec88431704451454c3@ruby-forum.com>

The more I work with BDD the more I realize how different this is from
my previous experience.  I now consider that part of the difficulty I
have lies in establishing the proper scale for the features that I
propose.  My question lies in that vein.  What size should a feature be?

I have read a great deal about scaling features in terms of hours of
work.  However, at my present level of inefficiency, that will probably
result in features that are too small just as I now believe that the
features I have now are too large.  Besides which, I seem to grasp
examples better than metrics when conceptualizing such things.

Returning to my client case.  Given that the system must permit
administering clients then does one have a single feature called "System
has clients..." and bundle all the activity related thereto in its
scenarios.  Or, as I begin to suspect, should one have separate features
like "Add a new client"; "Deactivate an existing client"; Reactivate an
inactive client"; "Report all active clients; ... and so forth.
-- 
Posted via http://www.ruby-forum.com/.

From zuperinfinite at gmail.com  Mon Mar  2 10:19:38 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Mon, 2 Mar 2009 16:19:38 +0100
Subject: [rspec-users] Feature Size-Scope-Scale
In-Reply-To: <1ef2dc9f45c1e3ec88431704451454c3@ruby-forum.com>
References: <1ef2dc9f45c1e3ec88431704451454c3@ruby-forum.com>
Message-ID: <493E4FB9-598B-4B80-B29D-6587308F2123@gmail.com>


On 2-mrt-2009, at 16:07, James Byrne wrote:

> The more I work with BDD the more I realize how different this is from
> my previous experience.  I now consider that part of the difficulty I
> have lies in establishing the proper scale for the features that I
> propose.  My question lies in that vein.  What size should a  
> feature be?

It should be big enough to describe the functionality.

Imagine a weblog system, with which a user can post articles.
My typical approach would be 4 features, Creating/Editing/Destroying  
and Viewing a post.
Imagine I have validates_presence for the title and contents of an  
article.

The Creating feature would have 3 scenarios:
- Creating an article
- Creating an article without a title
- Creating an article without the contents

Updating, 4 scenarios:
- Updating the title
- Updating the contents
- Removing the title (eg, a blank title)
- Removing the contents

Destroying and Viewing would be just 1 scenario.

I am rather curious what other list members use though..

cheers,
bartz

From lists at ruby-forum.com  Mon Mar  2 10:31:43 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 2 Mar 2009 16:31:43 +0100
Subject: [rspec-users] Cucumber Feature Scenario critique
In-Reply-To: <88fd8ddc0902250829v4cd73892qaf74892d046ab18c@mail.gmail.com>
References: <5f0f67d14c7eee172dc6db9a14be3ded@ruby-forum.com>
	<88fd8ddc0902230757j4c4b3465m4ba5699923ebf19a@mail.gmail.com>
	<1fb4df0902230944x31bb96d2pd45a286037e68c8e@mail.gmail.com>
	<6c8eb20a0eed0ed9845666e7c8e86a5c@ruby-forum.com>
	<88fd8ddc0902231655y1188ecf2ub48d0d4fc0ab6546@mail.gmail.com>
	<a58ea302d3105adccbb5e3de7f90338a@ruby-forum.com>
	<88fd8ddc0902250829v4cd73892qaf74892d046ab18c@mail.gmail.com>
Message-ID: <4548f1ed0b5abb573f7b0bc1c55e647d@ruby-forum.com>

Andrew Premdas wrote:
> James,

> 
> I'd question whether you need to give a monkey's about 'entity'. Whilst 
> it maybe an essential concept in the overall legal framework that doesn't 
> mean it has to be in YOUR world. If your software is about recording services
> provided to some client and related payments. You can simplify - you can
> just choose not to model all that legal stuff. If you model everything
> you'll

I have been mulling this over these past few days.  I now think that 
what is wrong, besides having as yet only vague ideas of how this is all 
meant to work, is that I am injecting too many implementation details 
into the features and scenarios.  Whether or not a client is a 
stand-alone design element or is dependent upon a superior element of 
abstraction is really quite beside the point insofar as the presentation 
of the system to the user is concerned.  I now believe that I should 
just be writing down whatever it is that a client has to be in order to 
satisfy the business requirements. If we need a higher level of 
abstraction to capture other attributes then that should remain 
invisible to the users.

Of course, realizing this issue and actually dealing with it are two 
different things.  I will probably experience a great deal of difficulty 
arriving at a balance between expression and implementation.
-- 
Posted via http://www.ruby-forum.com/.

From dchelimsky at gmail.com  Mon Mar  2 10:50:07 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 2 Mar 2009 09:50:07 -0600
Subject: [rspec-users] be_valid (validates_format_of ..., :on => :create)
In-Reply-To: <6F193A20-D635-44D0-BB30-11F8341D12AA@gmail.com>
References: <38f994ca-7da0-43cc-a013-34e51a5cca7e@j8g2000yql.googlegroups.com>
	<6F193A20-D635-44D0-BB30-11F8341D12AA@gmail.com>
Message-ID: <57c63afe0903020750g5936966cg85cf715a5d8c980a@mail.gmail.com>

On Mon, Mar 2, 2009 at 8:20 AM, Bart Zonneveld <zuperinfinite at gmail.com> wrote:
>
> On 28-feb-2009, at 11:45, MAwiniarski wrote:
>
>> Greetings,
>>
>> How to write Example which will check if model's variable's
>> format is valid using :on => :create, like this:
>>
>> class User < ActiveRecord::Base
>> ...
>> ?validates_format_of ? ? ? :email, :with => /.../, :on => :create
>> ...
>>
>> Using following code is not right:
>> it "should ..." do
>> ? @user = users(:example_user)
>> ? @user.email = 'invalid_email_format'
>> ? @user.save
>> ? @user.should_not be_valid
>> end
>
> Try:
>
> it "should ..." do
> ? user = User.new # create a NEW user, instead of loading an already saved
> user from a fixtures file
> ? user.email = 'invalid_email_format'
> ? user.should_not be_valid
> ? user.should have(1).errors_on(:email)
> end

+1

I might combine the first two lines:

  user = User.create(:email => "invalid_email_format")

That reads more clearly to me because the invalid email format is
assigned on create, not after. It would have an extra call to valid?
but I think it's worth it for the clarity of intent in this case.

Otherwise, this is the right idea, IMO.

Cheers,
David

>
> cheers,
> bartz
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From zuperinfinite at gmail.com  Mon Mar  2 11:23:08 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Mon, 2 Mar 2009 17:23:08 +0100
Subject: [rspec-users] be_valid (validates_format_of ..., :on => :create)
In-Reply-To: <57c63afe0903020750g5936966cg85cf715a5d8c980a@mail.gmail.com>
References: <38f994ca-7da0-43cc-a013-34e51a5cca7e@j8g2000yql.googlegroups.com>
	<6F193A20-D635-44D0-BB30-11F8341D12AA@gmail.com>
	<57c63afe0903020750g5936966cg85cf715a5d8c980a@mail.gmail.com>
Message-ID: <937E5EFE-C47A-433F-AD35-A76889F35434@gmail.com>


On 2-mrt-2009, at 16:50, David Chelimsky wrote:

> On Mon, Mar 2, 2009 at 8:20 AM, Bart Zonneveld  
> <zuperinfinite at gmail.com> wrote:
>>
>> On 28-feb-2009, at 11:45, MAwiniarski wrote:
>>
>>> Greetings,
>>>
>>> How to write Example which will check if model's variable's
>>> format is valid using :on => :create, like this:
>>>
>>> class User < ActiveRecord::Base
>>> ...
>>>  validates_format_of       :email, :with => /.../, :on => :create
>>> ...
>>>
>>> Using following code is not right:
>>> it "should ..." do
>>>   @user = users(:example_user)
>>>   @user.email = 'invalid_email_format'
>>>   @user.save
>>>   @user.should_not be_valid
>>> end
>>
>> Try:
>>
>> it "should ..." do
>>   user = User.new # create a NEW user, instead of loading an  
>> already saved
>> user from a fixtures file
>>   user.email = 'invalid_email_format'
>>   user.should_not be_valid
>>   user.should have(1).errors_on(:email)
>> end
>
> +1
>
> I might combine the first two lines:
>
>   user = User.create(:email => "invalid_email_format")
>
> That reads more clearly to me because the invalid email format is
> assigned on create, not after. It would have an extra call to valid?
> but I think it's worth it for the clarity of intent in this case.

Although I agree with the reasoning you display here, I'd *never*  
validate any attribute just on create.
I'm pretty sure a user can update his email address somewhere in the  
site, but then his email address wouldn't be validated anymore.

On a second note, I noticed rspec default generated model specs now  
use Model.create!(@valid_attributes) as their default "all is valid"  
test. What's the advantage of this approach? I just write  
@model.attributes = @valid_attributes; @model.should be_valid, to  
prevent these specs to actually hit the db, and therefore speed up my  
specs a bit.

thanks,
bartz


From dchelimsky at gmail.com  Mon Mar  2 11:38:46 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 2 Mar 2009 10:38:46 -0600
Subject: [rspec-users] be_valid (validates_format_of ..., :on => :create)
In-Reply-To: <937E5EFE-C47A-433F-AD35-A76889F35434@gmail.com>
References: <38f994ca-7da0-43cc-a013-34e51a5cca7e@j8g2000yql.googlegroups.com>
	<6F193A20-D635-44D0-BB30-11F8341D12AA@gmail.com>
	<57c63afe0903020750g5936966cg85cf715a5d8c980a@mail.gmail.com>
	<937E5EFE-C47A-433F-AD35-A76889F35434@gmail.com>
Message-ID: <57c63afe0903020838g4013ac5u91637f525f046158@mail.gmail.com>

On Mon, Mar 2, 2009 at 10:23 AM, Bart Zonneveld <zuperinfinite at gmail.com> wrote:
>
> On 2-mrt-2009, at 16:50, David Chelimsky wrote:
>
>> On Mon, Mar 2, 2009 at 8:20 AM, Bart Zonneveld <zuperinfinite at gmail.com>
>> wrote:
>>>
>>> On 28-feb-2009, at 11:45, MAwiniarski wrote:
>>>
>>>> Greetings,
>>>>
>>>> How to write Example which will check if model's variable's
>>>> format is valid using :on => :create, like this:
>>>>
>>>> class User < ActiveRecord::Base
>>>> ...
>>>> ?validates_format_of ? ? ? :email, :with => /.../, :on => :create
>>>> ...
>>>>
>>>> Using following code is not right:
>>>> it "should ..." do
>>>> ?@user = users(:example_user)
>>>> ?@user.email = 'invalid_email_format'
>>>> ?@user.save
>>>> ?@user.should_not be_valid
>>>> end
>>>
>>> Try:
>>>
>>> it "should ..." do
>>> ?user = User.new # create a NEW user, instead of loading an already saved
>>> user from a fixtures file
>>> ?user.email = 'invalid_email_format'
>>> ?user.should_not be_valid
>>> ?user.should have(1).errors_on(:email)
>>> end
>>
>> +1
>>
>> I might combine the first two lines:
>>
>> ?user = User.create(:email => "invalid_email_format")
>>
>> That reads more clearly to me because the invalid email format is
>> assigned on create, not after. It would have an extra call to valid?
>> but I think it's worth it for the clarity of intent in this case.
>
> Although I agree with the reasoning you display here, I'd *never* validate
> any attribute just on create.
> I'm pretty sure a user can update his email address somewhere in the site,
> but then his email address wouldn't be validated anymore.

FWIW, the OP's code says :on => :create. I also happened to see
http://mawiniarski.wordpress.com/2009/02/28/rspec-validation-on-create/,
which reinforced for me that this is about validating on create, not
general validation.

> On a second note, I noticed rspec default generated model specs now use
> Model.create!(@valid_attributes) as their default "all is valid" test.
> What's the advantage of this approach? I just write @model.attributes =
> @valid_attributes; @model.should be_valid, to prevent these specs to
> actually hit the db, and therefore speed up my specs a bit.

Good point. Wanna submit a patch? http://rspec.lighthouseapp.com

Cheers,
David

>
> thanks,
> bartz
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From sfeley at gmail.com  Mon Mar  2 11:54:23 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Mon, 2 Mar 2009 11:54:23 -0500
Subject: [rspec-users] Feature Size-Scope-Scale
In-Reply-To: <1ef2dc9f45c1e3ec88431704451454c3@ruby-forum.com>
References: <1ef2dc9f45c1e3ec88431704451454c3@ruby-forum.com>
Message-ID: <1fb4df0903020854v71571570r222dc816f762012@mail.gmail.com>

On Mon, Mar 2, 2009 at 10:07 AM, James Byrne <lists at ruby-forum.com> wrote:
>
> I have read a great deal about scaling features in terms of hours of
> work. ?However, at my present level of inefficiency, that will probably
> result in features that are too small just as I now believe that the
> features I have now are too large. ?Besides which, I seem to grasp
> examples better than metrics when conceptualizing such things.


Real features for a real project I'm working on:

Feature: View Episodes
  As a listener
  I want to see a list of episodes
  So that I can experience the joy of consuming them

Feature: Create Episode
  As a podcaster
  I want to add an episode
  So that I don't die like Emily Dickinson

Feature: Edit Episode
  As a podcaster
  I want to edit an existing episode
  So that my listeners can catch my mistakes for me

Feature: Add MP3 Enclosure
  As a podcaster
  I want to link to an MP3 file
  So that people don't confuse me for a blogger

...That's my basic feature size.  An atomic unit of work,  and
generally one that comprises a single Web interaction.  I'll usually
put down 2-3 scenarios when I make the feature file (critical success
path, and at least one exception case) and then add more if/when I
think of them.

These mostly fall out to a few hours of work each, but that seems to
be a natural consequence of thinking at an atomic level and not a
deliberate goal I'd planned for.  If one of them took days, well, it'd
take days.


> [ . . . ] ?Or, as I begin to suspect, should one have separate features
> like "Add a new client"; "Deactivate an existing client"; Reactivate an
> inactive client"; "Report all active clients; ... and so forth.

Here would be my suggestion:

* Start by doing it the way you think makes the most sense.
* If it feels good and seems to result in better code done faster,
keep doing it that way.
* If it hurts, or slows you down without a quality increase, either
try changing the way you're doing it, or stop doing it entirely.
* Whenever you next run across something that you think might be a
good improvement in your working methods, repeat steps 1-3.

Penultimately it's about people and product.  But people build the
product, so ultimately it's about people.  You need to figure out what
works for you and your task at hand.  Others can offer advice or
experiences but they can't give you the right answers.


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From mark at mwilden.com  Mon Mar  2 12:07:45 2009
From: mark at mwilden.com (Mark Wilden)
Date: Mon, 2 Mar 2009 09:07:45 -0800
Subject: [rspec-users] Cucumber Feature Scenario critique
In-Reply-To: <4548f1ed0b5abb573f7b0bc1c55e647d@ruby-forum.com>
References: <5f0f67d14c7eee172dc6db9a14be3ded@ruby-forum.com>
	<88fd8ddc0902230757j4c4b3465m4ba5699923ebf19a@mail.gmail.com>
	<1fb4df0902230944x31bb96d2pd45a286037e68c8e@mail.gmail.com>
	<6c8eb20a0eed0ed9845666e7c8e86a5c@ruby-forum.com>
	<88fd8ddc0902231655y1188ecf2ub48d0d4fc0ab6546@mail.gmail.com>
	<a58ea302d3105adccbb5e3de7f90338a@ruby-forum.com>
	<88fd8ddc0902250829v4cd73892qaf74892d046ab18c@mail.gmail.com>
	<4548f1ed0b5abb573f7b0bc1c55e647d@ruby-forum.com>
Message-ID: <3c30da400903020907t2433a4cq785366924cbe1284@mail.gmail.com>

On Mon, Mar 2, 2009 at 7:31 AM, James Byrne <lists at ruby-forum.com> wrote:

>?Whether or not a client is a
> stand-alone design element or is dependent upon a superior element of
> abstraction is really quite beside the point insofar as the presentation
> of the system to the user is concerned.

I like to focus on that key word, "presentation," meaning what a user
sees on a screen or a piece of paper. The only truly important part of
a system is its physical output. Everything else is subservient to
that end.

Define an output ("customer balance on web page"). Define how to make
that happen, via a story/feature. Repeat.

///ark

From mark at mwilden.com  Mon Mar  2 12:12:14 2009
From: mark at mwilden.com (Mark Wilden)
Date: Mon, 2 Mar 2009 09:12:14 -0800
Subject: [rspec-users] be_valid (validates_format_of ..., :on => :create)
In-Reply-To: <937E5EFE-C47A-433F-AD35-A76889F35434@gmail.com>
References: <38f994ca-7da0-43cc-a013-34e51a5cca7e@j8g2000yql.googlegroups.com>
	<6F193A20-D635-44D0-BB30-11F8341D12AA@gmail.com>
	<57c63afe0903020750g5936966cg85cf715a5d8c980a@mail.gmail.com>
	<937E5EFE-C47A-433F-AD35-A76889F35434@gmail.com>
Message-ID: <3c30da400903020912x1eeb7c6cmd4e0ce8d5d4b8dd0@mail.gmail.com>

On Mon, Mar 2, 2009 at 8:23 AM, Bart Zonneveld <zuperinfinite at gmail.com> wrote:
>
> On a second note, I noticed rspec default generated model specs now use
> Model.create!(@valid_attributes) as their default "all is valid" test.
> What's the advantage of this approach? I just write @model.attributes =
> @valid_attributes; @model.should be_valid, to prevent these specs to
> actually hit the db, and therefore speed up my specs a bit.

Wouldn't it be better to go through the complete create! cycle, to
make sure callbacks and database constraints (if any) are exercised?

///ark

From mark at mwilden.com  Mon Mar  2 12:19:26 2009
From: mark at mwilden.com (Mark Wilden)
Date: Mon, 2 Mar 2009 09:19:26 -0800
Subject: [rspec-users] [cucumber] Cucumber and Chronic
In-Reply-To: <1fb4df0903012107q6d65aaf6w255fb01233064f95@mail.gmail.com>
References: <1ebf5a4d0903010850l54c7ee19i58dbbc48150a9339@mail.gmail.com>
	<3c30da400903011107n7057e73fy89b2913085d222c0@mail.gmail.com>
	<3c30da400903011530vbf3b9b8v3ace26553e29a078@mail.gmail.com>
	<1fb4df0903012107q6d65aaf6w255fb01233064f95@mail.gmail.com>
Message-ID: <3c30da400903020919t65e344cdg148a91cd44d00b2a@mail.gmail.com>

On Sun, Mar 1, 2009 at 9:07 PM, Stephen Eley <sfeley at gmail.com> wrote:
>
> For date testing, I've just discovered and successfully used Notahat's
> "time_travel" plugin:
> http://github.com/notahat/time_travel/

We have just been stubbing Time.now, but I'll think about time_travel.
One advantage would be not having to "manually" reset RSpec mocks
after each Cucumber scenario is run in After.

///ark

From lists at ruby-forum.com  Mon Mar  2 13:39:11 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 2 Mar 2009 19:39:11 +0100
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>
	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>
	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
Message-ID: <675261bfd8ca95790d348539630b1398@ruby-forum.com>

Andrew Premdas wrote:

> So given that the rules should be in the model then the question is 
> which part of the model should have this responsibility and how do
> you call  it.
> Three choices come to mind here
> 
> 1) Place the rule inside User
> 2) Place the rule inside the affected model
> 3) Create a new model(s) to encapsulate this functionality. It might be
> helpful to think of this as a service which models can use
> 
> 1) Pollutes User with additional responsibility, but you can live with 
> this so long as things remain very simple
> 

I am not sure that this is really "pollution".  One of the things that 
was pointed out to me on the Ruby list when I first began transitioning 
to OO was the mantra "ask" don't "tell".  It seems to me that in an OO 
authorization scheme one might properly ask the user instance (model) 
whether or not they are permitted to do "something" (controller) rather 
than have the "something" test to see if that user is permitted.

-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Mon Mar  2 13:48:19 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 2 Mar 2009 19:48:19 +0100
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <675261bfd8ca95790d348539630b1398@ruby-forum.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>
	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>
	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
Message-ID: <94fccb07c80c388f81351eda71aa47fd@ruby-forum.com>

James Byrne wrote:

> 
> I am not sure that this is really "pollution".  One of the things that 
> was pointed out to me on the Ruby list when I first began transitioning 
> to OO was the mantra "ask" don't "tell".  It seems to me that in an OO 
> authorization scheme one might properly ask the user instance (model) 
> whether or not they are permitted to do "something" (controller) rather 
> than have the "something" test to see if that user is permitted.

Unless I have misunderstood your intent and by your third choice you are 
referring to an external role based model while your first choice refers 
to putting the actual rules inside the user model.  In which case I 
agree with you.

My comments refer to the idea that the user model makes the calls to the 
role model and returns whether or not they were authorized to the 
request.
-- 
Posted via http://www.ruby-forum.com/.

From mark at mwilden.com  Mon Mar  2 14:10:28 2009
From: mark at mwilden.com (Mark Wilden)
Date: Mon, 2 Mar 2009 11:10:28 -0800
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <675261bfd8ca95790d348539630b1398@ruby-forum.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>
	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>
	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
Message-ID: <3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>

On Mon, Mar 2, 2009 at 10:39 AM, James Byrne <lists at ruby-forum.com> wrote:
>
> I am not sure that this is really "pollution". ?One of the things that
> was pointed out to me on the Ruby list when I first began transitioning
> to OO was the mantra "ask" don't "tell".

Actually, it's the other way around.

http://www.pragprog.com/articles/tell-dont-ask

///ark

From lists at ruby-forum.com  Mon Mar  2 14:23:41 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 2 Mar 2009 20:23:41 +0100
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>
	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>
	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
Message-ID: <068ba0be3d6da3cedfa70f9a2a0a4e99@ruby-forum.com>

Mark Wilden wrote:
>
> 
> Actually, it's the other way around.
> 
> http://www.pragprog.com/articles/tell-dont-ask

Sigh...


-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Mon Mar  2 14:37:34 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 2 Mar 2009 20:37:34 +0100
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>
	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>
	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
Message-ID: <e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>

Mark Wilden wrote:

> 
> Actually, it's the other way around.
> 
> http://www.pragprog.com/articles/tell-dont-ask
> 

I have read this article and it leaves me rather more confused than not. 
I gather that I am missing something fundamental.  Consider that when I 
write x.to_s I am telling the object what to give back.  But then what 
am I doing when I write x.exists? or x.is_a?(y) or 
sam.authorized?(controller_or_model, action)?

Is this a semantic confusion on my part?  Should I consider that what I 
do with x.exists? is tell the object to answer a question?

-- 
Posted via http://www.ruby-forum.com/.

From phlip2005 at gmail.com  Mon Mar  2 14:57:38 2009
From: phlip2005 at gmail.com (Phlip)
Date: Mon, 02 Mar 2009 11:57:38 -0800
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>	<49A9A1C0.9050904@benmabey.com>	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>	<675261bfd8ca95790d348539630b1398@ruby-forum.com>	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
Message-ID: <gohdnj$irq$1@ger.gmane.org>

James Byrne wrote:

> Is this a semantic confusion on my part?  Should I consider that what I 
> do with x.exists? is tell the object to answer a question?

Consider...

   if x.exists?
     x.important_method()
   else
     # nothing!
   end

Now lets upgrade the variable x. Sometimes it points to a thing that exists, and 
sometimes it points to a stub object whose only job is to return 'false' from 
exists?, and do nothing inside important_method():

   if x.exists?
     x.important_method()
   else
     x.important_method()
   end

Now you can take out the if!

   x.important_method()

We are no longer asking x if it exists. We are telling it what to do, and 
letting it decide how to do it. That is the heart of OO programming.

(There is still an 'if', somewhere - the one that populates x. But - hopefully - 
it's only in one place.)

-- 
   Phlip
   http://www.zeroplayer.com/


From r_j_h_box-sf at yahoo.com  Mon Mar  2 15:22:44 2009
From: r_j_h_box-sf at yahoo.com (r_j_h_box-sf at yahoo.com)
Date: Mon, 2 Mar 2009 12:22:44 -0800 (PST)
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>
	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>
	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
Message-ID: <387919.43677.qm@web31802.mail.mud.yahoo.com>






----- Original Message ----
> From: James Byrne <lists at ruby-forum.com>

> Mark Wilden wrote:
> > Actually, it's the other way around.
> > 
> > http://www.pragprog.com/articles/tell-dont-ask
>
> I have read this article and it leaves me rather more confused than not. 

That's the danger of oversimplification.  Another way to phrase it is, don't rely on objects for things they know.  Rely on them for things they know how to do.

Now it boils down to who's responsible.  The door's lock is responsible for reading the key, and the bolt is responsible for unlocking the door.   The door is only responsible for letting me in, along with some cold air.  The key is a role here, the lock is the controller, and the bolt... okay, the analogy breaks down again.  But consider zones of responibility.

> sam.authorized?(controller_or_model, action)?

I'll suggest that it's the controllers who are responsible for telling what role or other requirements need to be satisfied to get their services, and that it's the job of the user object (maybe by delegating to some role class or objects) to provide the information as to whether those requirements are met.  

I smell something when I think about individual models specifying their requirements.  Front-gate access through the controller actions smells more correct to me.  

If your actions can't be boiled down that atomically, I ask the question, "is there something else wrong?".

Randy

From lists at ruby-forum.com  Mon Mar  2 15:59:04 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 2 Mar 2009 21:59:04 +0100
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <387919.43677.qm@web31802.mail.mud.yahoo.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>
	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>
	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
Message-ID: <2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>

unknown wrote:

> 
>> sam.authorized?(controller_or_model, action)?
> 
> I'll suggest that it's the controllers who are responsible for telling 
> what role or other requirements need to be satisfied to get their 
> services, and that it's the job of the user object (maybe by delegating 
> to some role class or objects) to provide the information as to whether 
> those requirements are met.
> 


That is what I thought that I was doing.  The Controller sends the 
message to the User Instance telling it to answer the question: are you 
authorized to perform "controller + action"?; or role, or whatever the 
controller sends as the criteria to be met.  It seems to me necessary 
that the User model receive the context of the authorization call.  Now 
the actual check on whether user x is authorized to perform the create 
method of the PaymentReceivedController is done in the #authorized? 
method of User.

Is this what should be done or is there a different way?

-- 
Posted via http://www.ruby-forum.com/.

From zach.dennis at gmail.com  Mon Mar  2 16:50:59 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Mon, 2 Mar 2009 16:50:59 -0500
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
Message-ID: <85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>

On Mon, Mar 2, 2009 at 3:59 PM, James Byrne <lists at ruby-forum.com> wrote:
> unknown wrote:
>
>>
>>> sam.authorized?(controller_or_model, action)?
>>
>> I'll suggest that it's the controllers who are responsible for telling
>> what role or other requirements need to be satisfied to get their
>> services, and that it's the job of the user object (maybe by delegating
>> to some role class or objects) to provide the information as to whether
>> those requirements are met.
>>
>
>
> That is what I thought that I was doing. ?The Controller sends the
> message to the User Instance telling it to answer the question: are you
> authorized to perform "controller + action"?; or role, or whatever the
> controller sends as the criteria to be met. ?It seems to me necessary
> that the User model receive the context of the authorization call. ?Now
> the actual check on whether user x is authorized to perform the create
> method of the PaymentReceivedController is done in the #authorized?
> method of User.
>
> Is this what should be done or is there a different way?

Today, my pair and I hit a scenario which I think maybe a good example
to clarify.

Let's say that you have an "admin" and "associate" role. Each role can
access invoices in the system, but each role can access different
subsets of invoices.

In our controller, we could have something like:

def index
   if user.has_role?("admin")
      Invoice.all
   elsif user.has_role?("associate")
      Invoice.by_area(current_user.area)
   else
     raise AccessDenied
   end
end

We ended up not doing this because the lines "Invoice.all" and
"Invoice.by_area" is behaviour which is tied specifically to a certain
role in the system. We don't want behaviour for these roles to be
scattered throughout controller actions. We want it in one single
location.

So we create a FiscalAdmin role object and a FiscalAssociate role
object. As these roles become filled out we leave the role-specific
behaviour in one location, creating a well-defined cohesive class for
each role.

For me it's a little win, that results in big ways. :)


-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From zach.dennis at gmail.com  Mon Mar  2 17:16:33 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Mon, 2 Mar 2009 17:16:33 -0500
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
Message-ID: <85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>

On Mon, Mar 2, 2009 at 4:50 PM, Zach Dennis <zach.dennis at gmail.com> wrote:
> On Mon, Mar 2, 2009 at 3:59 PM, James Byrne <lists at ruby-forum.com> wrote:
>> unknown wrote:
>>
>>>
>>>> sam.authorized?(controller_or_model, action)?
>>>
>>> I'll suggest that it's the controllers who are responsible for telling
>>> what role or other requirements need to be satisfied to get their
>>> services, and that it's the job of the user object (maybe by delegating
>>> to some role class or objects) to provide the information as to whether
>>> those requirements are met.
>>>
>>
>>
>> That is what I thought that I was doing. ?The Controller sends the
>> message to the User Instance telling it to answer the question: are you
>> authorized to perform "controller + action"?; or role, or whatever the
>> controller sends as the criteria to be met. ?It seems to me necessary
>> that the User model receive the context of the authorization call. ?Now
>> the actual check on whether user x is authorized to perform the create
>> method of the PaymentReceivedController is done in the #authorized?
>> method of User.
>>
>> Is this what should be done or is there a different way?
>
> Today, my pair and I hit a scenario which I think maybe a good example
> to clarify.
>
> Let's say that you have an "admin" and "associate" role. Each role can
> access invoices in the system, but each role can access different
> subsets of invoices.
>
> In our controller, we could have something like:
>
> def index
> ? if user.has_role?("admin")
> ? ? ?Invoice.all
> ? elsif user.has_role?("associate")
> ? ? ?Invoice.by_area(current_user.area)
> ? else
> ? ? raise AccessDenied
> ? end
> end
>
> We ended up not doing this because the lines "Invoice.all" and
> "Invoice.by_area" is behaviour which is tied specifically to a certain
> role in the system. We don't want behaviour for these roles to be
> scattered throughout controller actions. We want it in one single
> location.
>
> So we create a FiscalAdmin role object and a FiscalAssociate role
> object. As these roles become filled out we leave the role-specific
> behaviour in one location, creating a well-defined cohesive class for
> each role.
>
> For me it's a little win, that results in big ways. :)
>

Forgot to mention what we did do. We ended up with the following...

def index
  if user.has_role?("admin")
    user.in_role("admin").invoices
  elsif user.has_role?("associate")
    user.in_role("associate").invoices
  else
    raise AccessDenied
  end
end

To us, the change here is subtle, but important. The controller is
allowed to ask for invoices from each role, but is not allowed to know
how find the invoices, that's the behaviour of the role.

> --
> - Show quoted text -
> Zach Dennis
> http://www.continuousthinking.com
> http://www.mutuallyhuman.com
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From matt at mattwynne.net  Mon Mar  2 18:17:22 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Mon, 2 Mar 2009 23:17:22 +0000
Subject: [rspec-users] Cucumber for large projects
In-Reply-To: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
References: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
Message-ID: <2287172B-8A6F-4567-9F83-28990DF5506A@mattwynne.net>


On 26 Feb 2009, at 15:33, Tom ten Thij wrote:

> We will be using Cucumber for a fairly large project. Are there any
> areas that cucumber is lacking when there are many scenarios?
>
> I believe the best candidate for showing our client the scenario
> results is the html output. It strikes me that that becomes fairly
> cumbersome to check with many scenarios. Methinks some javascript code
> to hide all passing scenarios / features would be useful. Is there any
> work being done on this?
>
> In which areas could we help cucumber accommodate for large projects?
>
> Tom.

Hi Tom,

At Songkick.com, we currently have 635 scenarios in our Cucumber  
tests, and while we've had a few issues, the ROI has definitely been  
worth it.

At the moment, IMO, the tools for feeding back the features to non- 
technical people are pretty immature. My colleague Dan Lucraft wrote a  
tool which produces a nicely-formatted PDF document from your features  
folder[1] which is great, but won't work with the new version (0.2) of  
Cucumber when it's released as the API against which such formatters  
are written has undergone some significant changes for the new version.

Once this stuff stabilises into the 0.2 release I expect more effort  
will be put into such tools, as the changes Aslak has made will make  
it much easier to write them. Check out the brave vision for the new  
HTML formatter:
http://rspec.lighthouseapp.com/projects/16211/tickets/178-design-the-html-markup-for-cucumber-02

Other than that, you'll be likely to hit some issues just to do with  
managing the large number of specifications, but to be honest this has  
surprised me by being much easier than expected. The amount of code  
you actually write in the step definitions is minimal, especially if  
you're using Rails and something like factory_girl, so with a bit of  
regular re-factoring it's really easy to stay on top of it. We made a  
call early on to split our features folder into sub-folders named  
after the type of user, which has worked well for us:

e.g.

   features/visitor/view_homepage.feature
   features/user/change_password.feature
   features/admin/list_users.feature

That's helped us to keep things tidy, but there are obviously other  
ways to slice things up too. Are you planning to test the browser too  
(with selenium / watir / etc) or just from the HTTP requests down?  
Assuming you're building a web app of course... :)

[1]http://www.daniellucraft.com/blog/2009/01/features_report/

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From shot at hot.pl  Mon Mar  2 18:32:26 2009
From: shot at hot.pl (Shot (Piotr Szotkowski))
Date: Tue, 3 Mar 2009 00:32:26 +0100
Subject: [rspec-users] Rspecing an enumerator from outside-in woes
In-Reply-To: <D9A94771-2CB0-41F7-9B7A-D755D2DDCD84@mattwynne.net>
References: <20090228212917.GA19515@devielle>
	<18FD4D43-0429-4977-A01D-E651D9E0CA2F@mattwynne.net>
	<20090301173006.GD7432@devielle>
	<D9A94771-2CB0-41F7-9B7A-D755D2DDCD84@mattwynne.net>
Message-ID: <20090302233226.GE30550@devielle>

Once again ? thanks a ton for your response! I wish ?The RSpec Book? 
answered my use cases; I bought it hoping I?ll learn all this stuff from 
it, but it seems the most interesting chapters are not written yet. :)

Matt Wynne:

> Assuming you wanted to keep your focus on the Decomposer class, but 
> you knew that the concept of a Decomposition was a firm one in your 
> design, you could define an empty Decomposition class, then stub the 
> constructor to return a test double of some sort:

>     class Decomposition
>     end

>     ...

>     Decomposition.stub!(:new).and_return mock('Decomposition', :foo => 'bar')

Ah, a very good point. :) The idea of subclassing something to make
it testable is also interesting; I?d rather try hard to come up
with a better spec and/or design, but it?s good to remember there?s 
a solution to keep all the code added solely for testability in one 
place.

> Ideally though, you really want to avoid testing state and instead 
> think about testing the interactions between objects. If the 
> relationship between the Decomposer and the Decomposition is for
> one to create instances of the other, then I would be quite satisfied 
> writing mock expectations on the Decomposition's constructor, like 
> this:

>      Decomposition.should_receive(:new).with [1,2]

And this is exactly where you hit the nail on the head. :) I think
my main problem at this stage of ?getting RSpec? is the (shrinking, 
but still existing) inability to blur the border between the RSpec world 
and the world of the code under test. I happily started to use mocks and 
stubs, but I keep forgetting that they can be applied to the stuff from 
the ?other? world; I hope I?ll keep that in mind from now on.

FWIW, your example on replacing 
?.should_receive(:each).and_yield(?).and_yield(?).?
with a fake generator struck a very nice chord with
me, and I managed to side-step the problem that all
three of my generator types expect a varying number
of params to their #each calls:
http://github.com/Chastell/art-decomp/commit/9979e3b687a33fd75e6394b6297e2200b052b354

> On 1 Mar 2009, at 17:30, Shot (Piotr Szotkowski) wrote:

>> I think I agree ? but the real question was why don?t the (lazy)
>> enumerator?s #next calls satisfy the mocks? #should_receive()s ?
>> am I missing something fundamental, or is this simply an RSpec 1.1.12
>> incompatibility with Ruby 1.9.1?

> Sorry, not sure about that one - I've not tried playing
> with these lazy enumerators - is this a Ruby 1.9 thing

Yes and no ? some/all of the Enumerator stuff was backported to 1.8 and 
is included in Ruby 1.8.7. Basically, if you have an #each method on 
your class, you can create an Enumerator? for its objects and then do 
very nice things, like having a free #with_index traversal or fetching 
the elements one-by-one with #next. The latter is useful for classes 
generating/representing infinite sequences and in cases (like my case 
of interdependent generators) when the cost of generating subsequent 
elements is rather high and it would be wasteful to generate all of them 
upfront.

? http://ruby-doc.org/core-1.9/classes/Enumerable/Enumerator.html

? Shot
-- 
uo???n??suo? ??pun
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090303/5b5e72e2/attachment.bin>

From zach.dennis at gmail.com  Mon Mar  2 18:36:30 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Mon, 2 Mar 2009 18:36:30 -0500
Subject: [rspec-users] Is there a way to generate spec for existing
	controllers?
In-Reply-To: <gofij9$clh$1@ger.gmane.org>
References: <75cf4ca0-0e93-4b38-abda-e052dc4feac2@k19g2000prh.googlegroups.com>
	<57c63afe0903011551k77426d7fy560ba9d36736976f@mail.gmail.com>
	<gofij9$clh$1@ger.gmane.org>
Message-ID: <85d99afe0903021536n2992c2a2tbd680c145097ba3@mail.gmail.com>

On Sun, Mar 1, 2009 at 10:08 PM, Phlip <phlip2005 at gmail.com> wrote:
> David Chelimsky wrote:
>
>> ty wrote:
>
>>> We just start using RSpec and rspec_on_rails for a existing Rails
>>> project.
>
> No unit tests, right?
>
>>> After run script/generate rspec. It only generate the structure
>>> folders.
>>> We've got quite a few controllers and models. I wonder is it a way to
>>> auto-generate specs for them.
>>
>> Nope. Sorry.
>
> Ask your goal-donor what feature they'd like to see in a spec.
>
> That is the point of specs - writing verbiage that a "product manager" or
> "business analyst" can review.

I think you're referring to business specs, and I think ty is asking
about developer specs. You probably meant to refer him to writing
features, no?


-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From matt at mattwynne.net  Mon Mar  2 18:44:28 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Mon, 2 Mar 2009 23:44:28 +0000
Subject: [rspec-users] Rspecing an enumerator from outside-in woes
In-Reply-To: <20090302233226.GE30550@devielle>
References: <20090228212917.GA19515@devielle>
	<18FD4D43-0429-4977-A01D-E651D9E0CA2F@mattwynne.net>
	<20090301173006.GD7432@devielle>
	<D9A94771-2CB0-41F7-9B7A-D755D2DDCD84@mattwynne.net>
	<20090302233226.GE30550@devielle>
Message-ID: <7A291EC8-8C1B-4ED6-90BF-33418716AE42@mattwynne.net>


On 2 Mar 2009, at 23:32, Shot (Piotr Szotkowski) wrote:

> Once again ? thanks a ton for your response! I wish ?The RSpec Book?
> answered my use cases; I bought it hoping I?ll learn all this stuff  
> from
> it, but it seems the most interesting chapters are not written yet. :)
>
> Matt Wynne:
>
>> Assuming you wanted to keep your focus on the Decomposer class, but
>> you knew that the concept of a Decomposition was a firm one in your
>> design, you could define an empty Decomposition class, then stub the
>> constructor to return a test double of some sort:
>
>>    class Decomposition
>>    end
>
>>    ...
>
>>    Decomposition.stub!(:new).and_return mock('Decomposition', :foo  
>> => 'bar')
>
> Ah, a very good point. :) The idea of subclassing something to make
> it testable is also interesting; I?d rather try hard to come up
> with a better spec and/or design, but it?s good to remember there?s
> a solution to keep all the code added solely for testability in one
> place.

The idea comes from this book:
http://www.amazon.co.uk/xUnit-Test-Patterns-Refactoring-Signature

There are lots of other good ideas in that book. Some of them are only  
necessary because of the awkward things statically-typed languages  
force you to do, but many of them are equally applicable to and useful  
in Ruby.

>> Ideally though, you really want to avoid testing state and instead
>> think about testing the interactions between objects. If the
>> relationship between the Decomposer and the Decomposition is for
>> one to create instances of the other, then I would be quite satisfied
>> writing mock expectations on the Decomposition's constructor, like
>> this:
>
>>     Decomposition.should_receive(:new).with [1,2]
>
> And this is exactly where you hit the nail on the head. :) I think
> my main problem at this stage of ?getting RSpec? is the (shrinking,
> but still existing) inability to blur the border between the RSpec  
> world
> and the world of the code under test. I happily started to use mocks  
> and
> stubs, but I keep forgetting that they can be applied to the stuff  
> from
> the ?other? world; I hope I?ll keep that in mind from now on.
>
> FWIW, your example on replacing
> ?.should_receive(:each).and_yield(?).and_yield(?).?
> with a fake generator struck a very nice chord with
> me, and I managed to side-step the problem that all
> three of my generator types expect a varying number
> of params to their #each calls:
> http://github.com/Chastell/art-decomp/commit/9979e3b687a33fd75e6394b6297e2200b052b354

Glad it helped :)

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From walketim at gmail.com  Mon Mar  2 20:55:53 2009
From: walketim at gmail.com (Tim Walker)
Date: Mon, 2 Mar 2009 18:55:53 -0700
Subject: [rspec-users] [cucumber] Cucumber and Chronic
In-Reply-To: <3c30da400903011530vbf3b9b8v3ace26553e29a078@mail.gmail.com>
References: <1ebf5a4d0903010850l54c7ee19i58dbbc48150a9339@mail.gmail.com>
	<3c30da400903011107n7057e73fy89b2913085d222c0@mail.gmail.com>
	<3c30da400903011530vbf3b9b8v3ace26553e29a078@mail.gmail.com>
Message-ID: <1ebf5a4d0903021755u7920e3c4r8233e54da04fd151@mail.gmail.com>

Absolutely. I'd respectfully suggest that this is more a requirement
of the way the step definition or test fixture that implements the
feature needs to behave than the intent of describing time based logic
in a natural language such that product owners, ba's etc. can write
them (i.e. Cucumber, FitNesse, etc). That Chronic takes into
consideration the things you mention (time zone, DST, Leap Years,
etc), is simply an imperative of it. Anyway, I think it fits
hand-in-glve with Cucumber and BDD in general. Just for the record, I
have no vested interest in Chronic and really don't know who even
authored it, but I can say it's looking pretty awesome in our own
Cucumber tests.

Thanks,

Tim

On Sun, Mar 1, 2009 at 4:30 PM, Mark Wilden <mark at mwilden.com> wrote:
> On Sun, Mar 1, 2009 at 11:07 AM, Mark Wilden <mark at mwilden.com> wrote:
>>
>> Just be careful when when basing durations from "now" that daylight
>> savings time doesn't affect anything.
>
> Along the same lines, don't write tests that assume 1.month.ago was <
> 29 days ago, or specs could start failing in March (as just happened
> with us). :)
>
> ///ark
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From sfeley at gmail.com  Mon Mar  2 23:35:51 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Mon, 2 Mar 2009 23:35:51 -0500
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
	<85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
Message-ID: <1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>

On Mon, Mar 2, 2009 at 5:16 PM, Zach Dennis <zach.dennis at gmail.com> wrote:
>
> Forgot to mention what we did do. We ended up with the following...
>
> def index
> ?if user.has_role?("admin")
> ? ?user.in_role("admin").invoices
> ?elsif user.has_role?("associate")
> ? ?user.in_role("associate").invoices
> ?else
> ? ?raise AccessDenied
> ?end
> end

That seems sort of backwards to me.  These aren't the user's invoices,
right?  They're just invoices which the user happens to be allowed to
see?  Chaining it this way makes it look like the invoices *belong* to
the role, and seems put the user up front instead of the invoices.
You also have conditional branching with hardcoded values, making the
controller brittle, and some redundancy with the controller asking the
model for a value and then passing the value right back to the model.

Can a model have more than one role?  If it can, you have a problem
here because the 'if' will only ever *act* on one role.  If it can't,
life gets simple:

[controller]
def index
  @invoices = Invoice.by_role(user)
rescue AccessDenied
  flash[:warning] = "Nope.  Sorry.  Nice try."
  redirect_to :back
end

[Invoice model]
def by_role(user)
  case user.role
  when "admin"
    [whatever]
  when "associate"
    [whatever]
  else
    raise AccessDenied
  end
end

...That could probably still be made more elegant.  I'm not a huge fan
of case statements, and I have in my head some idea that you could
have named scopes for each role and use "send" to pick the right
scope.  But that could be overdesigning it, and in any case I don't
really know what each role has to return in your business case.

The important takeaway here is that the Invoice is responsible for
figuring out what to return, based on user data passed to it at
runtime; the User doesn't have to have special logic to know how to
query every other model in the system.


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From sfeley at gmail.com  Tue Mar  3 00:01:03 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Tue, 3 Mar 2009 00:01:03 -0500
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>
	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>
	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
Message-ID: <1fb4df0903022101o2aeb09d8t7fc232406262300e@mail.gmail.com>

On Sat, Feb 28, 2009 at 5:26 PM, Chris Flipse <cflipse at gmail.com> wrote:
>
> Half of my problem right now is that I'm not even sure what layer to put
> model specific authentication!? If it's in the controller layer, it's
> repeated logic in every controller that touches the model in question.? If
> it's in the model, the logic is centralized, but now your model needs not
> only to know about Users in general, it needs a specific user.

My two cents:

1.) I feel authorization belongs in two places: models and views.
Models need to know what they're allowed to do.  Authorization becomes
a scope on reads and a validation on updates.  Views (specifically
helper methods) need to know whether they're allowed to show that
"Edit" button, etc.  That's not critical path, that's navigation,
maybe one step up from cosmetics.  I don't see a reason why
controllers need to know as long as they can handle nils coming back
from the models.

2.) In both cases, you need to know who the current user is, and
that's fine.  Figuring it out is the job of *authentication*, not
authorization.  Your authentication stack just needs to give you a
hook where you can ask it for the user, and your authorization stack
should handle it sensibly if the answer is 'nil.'  The
restful_authentication plugin implements current_user as a global
Application method, but that's not the only way to do it.

3.) Consider separating the authorization stuff from the core business
logic of your app, and implementing it as a module on the authorizable
classes instead.  Then if your basic authz behavior changes, you
(ideally) only have to change it in one place.  And it doesn't mess up
the readability of your main behavior.

...And because everyone else is doing it, here are my design notes on
my own overcomplicated authorization system (which, caveat, has yet to
be built, but I wrote this all down anyway to get it out of my head):

http://extraneous.org/past/2009/2/6/mother_do_you_think_theyll_drop_the_bomb/

I know it looks rather overdone, and it's perfectly possible that it
is, but my requirements were sincere:

* it needs to handle both users and groups, and
* I wanted it to be hierarchical, such that privileges on parent pages
trickle down to their children.

Between those two constraints, I couldn't off the top of my head think
of anything more elegant.



-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From zach.dennis at gmail.com  Tue Mar  3 00:15:39 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Tue, 3 Mar 2009 00:15:39 -0500
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
	<85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
	<1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>
Message-ID: <85d99afe0903022115k1230ad72m6a0a66f29779b668@mail.gmail.com>

On Mon, Mar 2, 2009 at 11:35 PM, Stephen Eley <sfeley at gmail.com> wrote:
> On Mon, Mar 2, 2009 at 5:16 PM, Zach Dennis <zach.dennis at gmail.com> wrote:
>>
>> Forgot to mention what we did do. We ended up with the following...
>>
>> def index
>>  if user.has_role?("admin")
>>    user.in_role("admin").invoices
>>  elsif user.has_role?("associate")
>>    user.in_role("associate").invoices
>>  else
>>    raise AccessDenied
>>  end
>> end
>
> That seems sort of backwards to me.  These aren't the user's invoices,
> right?  They're just invoices which the user happens to be allowed to
> see?  Chaining it this way makes it look like the invoices *belong* to
> the role, and seems put the user up front instead of the invoices.

I agree, it could be better.

> You also have conditional branching with hardcoded values, making the
> controller brittle, and some redundancy with the controller asking the
> model for a value and then passing the value right back to the model.

I would like to push down the conditional logic to a lower part of the
app and there probably is a way that I haven't found yet with the
technique I'm using. Right now I'm exploring some trade-offs. Put more
emphasis on the responsibility of a role or on the responsibility of
the model? I've been down the model route, and would like to see where
the role route takes me. :)


>
> Can a model have more than one role?  If it can, you have a problem
> here because the 'if' will only ever *act* on one role.  If it can't,
> life gets simple:
>
> [controller]
> def index
>  @invoices = Invoice.by_role(user)
> rescue AccessDenied
>  flash[:warning] = "Nope.  Sorry.  Nice try."
>  redirect_to :back
> end
>
> [Invoice model]
> def by_role(user)
>  case user.role
>  when "admin"
>    [whatever]
>  when "associate"
>    [whatever]
>  else
>    raise AccessDenied
>  end
> end
>
> ...That could probably still be made more elegant.  I'm not a huge fan
> of case statements, and I have in my head some idea that you could
> have named scopes for each role and use "send" to pick the right
> scope.  But that could be overdesigning it, and in any case I don't
> really know what each role has to return in your business case.

I've been down this path many times. It has worked well when the
privilege/role set was limited and fairly simple, but seems to leave
models convoluted for anything else. That's what sparked me to explore
concretely identifying the Role in my app, and allowing it to make
decisions that are unique to it, rather than sprinkling them
throughout the models.

>
> The important takeaway here is that the Invoice is responsible for
> figuring out what to return, based on user data passed to it at
> runtime; the User doesn't have to have special logic to know how to
> query every other model in the system.

To clarify, the User doesn't know how-to query anything. All it knows
is if it can fulfill a Role. If it can it returns the appropriate role
object. Each role is responsible for knowing what it can access, but
it doesn't do the nitty gritty work. It calls methods on other models.
For the Invoice example, the associate role calls
Invoice.by_area(user.area), whereas the Admin role calls Invoice.all
in each of their respective #invoices methods.

Some of what has piqued my interest in exploring apps that place more
emphasis on Roles and Privileges is that it it's difficult to
understand what it means to be an admin when what it means to be able
to to be an "admin" or  "supervisor" or a "team supervisor" or an
"employee" is sprinkled throughout the app. So far I have enjoyed
having the responsibility of an admin in one spot, even though that
Admin object doesn't deal with the details. It just knows how-to make
a decision and then it tells another object to do it. It's kind of
like inserting a thin-layer of roles and privileges between the
application layer and the domain layer. I'd say these sit on the top
end of the domain layer.

As you pointed out earlier, the API for #in_role could use a little love.

-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From mark at mwilden.com  Tue Mar  3 01:04:04 2009
From: mark at mwilden.com (Mark Wilden)
Date: Mon, 2 Mar 2009 22:04:04 -0800
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
	<85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
	<1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>
Message-ID: <3c30da400903022204j143825b2x992b633236b99fa0@mail.gmail.com>

On Mon, Mar 2, 2009 at 8:35 PM, Stephen Eley <sfeley at gmail.com> wrote:

> ?@invoices = Invoice.by_role(user)

It doesn't seem right to me that invoices know about users and roles.
I think of invoices are being closer to the metal -- closer to the
essence of the application -- than petty concerns like authorization.

I would try something like

 user.role.invoices

where Role is a model that does the traffic-cop work of deciding what
invoices are available to it.

///ark

From sfeley at gmail.com  Tue Mar  3 01:34:21 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Tue, 3 Mar 2009 01:34:21 -0500
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <3c30da400903022204j143825b2x992b633236b99fa0@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
	<85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
	<1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>
	<3c30da400903022204j143825b2x992b633236b99fa0@mail.gmail.com>
Message-ID: <1fb4df0903022234g61542536jdae9a4745d5c49d2@mail.gmail.com>

On Tue, Mar 3, 2009 at 1:04 AM, Mark Wilden <mark at mwilden.com> wrote:
> On Mon, Mar 2, 2009 at 8:35 PM, Stephen Eley <sfeley at gmail.com> wrote:
>
>> ?@invoices = Invoice.by_role(user)
>
> It doesn't seem right to me that invoices know about users and roles.
>
> I would try something like
> ?user.role.invoices

Heh.  Which is what Zach said he wanted to do, and it isn't wrong.
But it doesn't seem right to *me* that roles know about invoices.
>8->  As I see it, if you go that path you end up having to inform
roles about every *other* model, and consolidating all your business
logic in one class.  At which point you're risking drifting away from
object-oriented programming and heading back to big procedures and
spaghetti code.

But that's a kneejerk response, and it needn't be that bad.  It really
comes down to taste.  To-mae-to, to-mah-to.  Sooner or later it's all
ones and zeros.


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From mark at mwilden.com  Tue Mar  3 02:21:37 2009
From: mark at mwilden.com (Mark Wilden)
Date: Mon, 2 Mar 2009 23:21:37 -0800
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <1fb4df0903022234g61542536jdae9a4745d5c49d2@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
	<85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
	<1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>
	<3c30da400903022204j143825b2x992b633236b99fa0@mail.gmail.com>
	<1fb4df0903022234g61542536jdae9a4745d5c49d2@mail.gmail.com>
Message-ID: <3c30da400903022321k4d9da5b6g28ac25dc0b3944c@mail.gmail.com>

On Mon, Mar 2, 2009 at 10:34 PM, Stephen Eley <sfeley at gmail.com> wrote:
> On Tue, Mar 3, 2009 at 1:04 AM, Mark Wilden <mark at mwilden.com> wrote:

>> ?user.role.invoices
>
> Heh. ?Which is what Zach said he wanted to do, and it isn't wrong.

Actually, I thought Zach was talking about a method on User called in_role.

> But it doesn't seem right to *me* that roles know about invoices.

Roles know about access to invoices. That's what their purpose is - to
let people do some things and not let them do others.

>>8-> ?As I see it, if you go that path you end up having to inform
> roles about every *other* model, and consolidating all your business
> logic in one class.

You do consolidate all your _access_ logic in one class, just as you
might consolidate all your sales tax knowledge in another class. That
way you have one source of responsibility for that behavior.
Otherwise, if you added, changed or deleted a role, you'd have to
change every model.

This is basically the Mediator pattern. Pluses and minuses, to be sure.

///ark

From f.mischa at gmail.com  Tue Mar  3 04:08:54 2009
From: f.mischa at gmail.com (Mischa Fierer)
Date: Tue, 3 Mar 2009 03:08:54 -0600
Subject: [rspec-users] Cucumber for large projects
In-Reply-To: <2287172B-8A6F-4567-9F83-28990DF5506A@mattwynne.net>
References: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
	<2287172B-8A6F-4567-9F83-28990DF5506A@mattwynne.net>
Message-ID: <ae16b71e0903030108t2d78813cmda5ce642f9cdbe3c@mail.gmail.com>

Speed will possibly become a big issue once you get above 1-2k steps or so.
Testjour was written to solve this:
http://github.com/brynary/testjour/tree/master

While I haven't been able to use it myself, since I work mostly from home,
it apparently radically reduces the time it takes to run features.

The only other tip I have for using cucumber in big projects is to make sure
that you stay on top of small changes to code that don't break features, but
over time end up changing what is happening to the point that, while the
test passes, it is no longer testing what you think it is testing. So, like
Matt said, it's a good idea to keep on top of things.  However, this is a
minor issue and not cucumber specific.

Best,

M

On Mon, Mar 2, 2009 at 5:17 PM, Matt Wynne <matt at mattwynne.net> wrote:

>
> On 26 Feb 2009, at 15:33, Tom ten Thij wrote:
>
>  We will be using Cucumber for a fairly large project. Are there any
>> areas that cucumber is lacking when there are many scenarios?
>>
>> I believe the best candidate for showing our client the scenario
>> results is the html output. It strikes me that that becomes fairly
>> cumbersome to check with many scenarios. Methinks some javascript code
>> to hide all passing scenarios / features would be useful. Is there any
>> work being done on this?
>>
>> In which areas could we help cucumber accommodate for large projects?
>>
>> Tom.
>>
>
> Hi Tom,
>
> At Songkick.com, we currently have 635 scenarios in our Cucumber tests, and
> while we've had a few issues, the ROI has definitely been worth it.
>
> At the moment, IMO, the tools for feeding back the features to
> non-technical people are pretty immature. My colleague Dan Lucraft wrote a
> tool which produces a nicely-formatted PDF document from your features
> folder[1] which is great, but won't work with the new version (0.2) of
> Cucumber when it's released as the API against which such formatters are
> written has undergone some significant changes for the new version.
>
> Once this stuff stabilises into the 0.2 release I expect more effort will
> be put into such tools, as the changes Aslak has made will make it much
> easier to write them. Check out the brave vision for the new HTML formatter:
>
> http://rspec.lighthouseapp.com/projects/16211/tickets/178-design-the-html-markup-for-cucumber-02
>
> Other than that, you'll be likely to hit some issues just to do with
> managing the large number of specifications, but to be honest this has
> surprised me by being much easier than expected. The amount of code you
> actually write in the step definitions is minimal, especially if you're
> using Rails and something like factory_girl, so with a bit of regular
> re-factoring it's really easy to stay on top of it. We made a call early on
> to split our features folder into sub-folders named after the type of user,
> which has worked well for us:
>
> e.g.
>
>  features/visitor/view_homepage.feature
>  features/user/change_password.feature
>  features/admin/list_users.feature
>
> That's helped us to keep things tidy, but there are obviously other ways to
> slice things up too. Are you planning to test the browser too (with selenium
> / watir / etc) or just from the HTTP requests down? Assuming you're building
> a web app of course... :)
>
> [1]http://www.daniellucraft.com/blog/2009/01/features_report/
>
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090303/921acf86/attachment-0001.html>

From zuperinfinite at gmail.com  Tue Mar  3 04:15:37 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Tue, 3 Mar 2009 10:15:37 +0100
Subject: [rspec-users] be_valid (validates_format_of ..., :on => :create)
In-Reply-To: <3c30da400903020912x1eeb7c6cmd4e0ce8d5d4b8dd0@mail.gmail.com>
References: <38f994ca-7da0-43cc-a013-34e51a5cca7e@j8g2000yql.googlegroups.com>
	<6F193A20-D635-44D0-BB30-11F8341D12AA@gmail.com>
	<57c63afe0903020750g5936966cg85cf715a5d8c980a@mail.gmail.com>
	<937E5EFE-C47A-433F-AD35-A76889F35434@gmail.com>
	<3c30da400903020912x1eeb7c6cmd4e0ce8d5d4b8dd0@mail.gmail.com>
Message-ID: <66B073D3-4980-4566-878F-BF67B883651B@gmail.com>


On 2-mrt-2009, at 18:12, Mark Wilden wrote:

> On Mon, Mar 2, 2009 at 8:23 AM, Bart Zonneveld  
> <zuperinfinite at gmail.com> wrote:
>>
>> On a second note, I noticed rspec default generated model specs  
>> now use
>> Model.create!(@valid_attributes) as their default "all is valid"  
>> test.
>> What's the advantage of this approach? I just write  
>> @model.attributes =
>> @valid_attributes; @model.should be_valid, to prevent these specs to
>> actually hit the db, and therefore speed up my specs a bit.
>
> Wouldn't it be better to go through the complete create! cycle, to
> make sure callbacks and database constraints (if any) are exercised?

Could be, but imagine I have 5 validations on my model. Only the  
first will throw an error on create!.
And since my validations are in Dutch, I specifically test each  
validation to see whether it returns the correct error message.

I use the following structure:

class Article
   validates_presence_of :title
end

describe Article
   before(:each) do
     @article = Article.new
     @valid_attributes = { :title => "Title" }
   end

   it "should not be valid without a title" do
     @article.attributes = @valid_attributes.except :title
     @article.should_not be_valid
   end

   it "should be valid with all valid attributes" do
     @article.attributes = @valid_attributes
     @article.should be_valid
   end
end


From aidy.lewis at googlemail.com  Tue Mar  3 05:06:00 2009
From: aidy.lewis at googlemail.com (aidy lewis)
Date: Tue, 3 Mar 2009 10:06:00 +0000
Subject: [rspec-users] Cucumber for large projects
In-Reply-To: <2287172B-8A6F-4567-9F83-28990DF5506A@mattwynne.net>
References: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
	<2287172B-8A6F-4567-9F83-28990DF5506A@mattwynne.net>
Message-ID: <7ac2300c0903030206g45f58270m31fc6e5ae736796c@mail.gmail.com>

Hi Matt/Dan

2009/3/2 Matt Wynne <matt at mattwynne.net>:

> At the moment, IMO, the tools for feeding back the features to non-technical
> people are pretty immature. My colleague Dan Lucraft wrote a tool which
> produces a nicely-formatted PDF document from your features folder[1] which
> is great, but won't work with the new version (0.2) of Cucumber when it's
> released as the API against which such formatters are written has undergone
> some significant changes for the new version.
>

> [1]http://www.daniellucraft.com/blog/2009/01/features_report/

To me the user\customer should be involved in the creation of the
stories and the acceptance criteria and by producing a pdf later in
the cycle for those stakeholders to read and understand may be argued
as something that is not Story-Driven-Development and more like
comprehendible automated tests.


Aidy

From gcirne at gmail.com  Tue Mar  3 08:17:06 2009
From: gcirne at gmail.com (Guilherme Machado Cirne)
Date: Tue, 3 Mar 2009 10:17:06 -0300
Subject: [rspec-users] Cucumber and selenium grid
In-Reply-To: <49A8918C.6010306@gmail.com>
References: <21a1366d0902271335k51fb95d6n92e265bfcbcb3e0b@mail.gmail.com>
	<49A8918C.6010306@gmail.com>
Message-ID: <21a1366d0903030517o79539416w3f851f2f302ada89@mail.gmail.com>

Ok.

How about the html report generation when running features in parallel? I
don't suppose there would be a single merged html report, correct?

Thanks,

-- 
Guilherme Machado Cirne
gcirne at gmail.com


On Fri, Feb 27, 2009 at 10:21 PM, Mike Gaffney <mr.gaffo at gmail.com> wrote:

> You can configure webrat to use selenium grid. Running tests in parallel
> would take having seperate test tasks or breaking them down somehow. Also
> the tests need to be touching atomic data or they will interfere.
>
> Guilherme Machado Cirne wrote:
>
>> Hi,
>>
>> Does anybody know how to integrate cucumber features with selenium grid?
>> Actually, what is needed is to run cucumber features in parallel so that
>> using selenium grid helps cut down on the total time it takes to run a test
>> suite.
>>
>> Thanks,
>>
>> --
>> Guilherme Machado Cirne
>> gcirne at gmail.com <mailto:gcirne at gmail.com>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
> --
> -Mike Gaffney (http://rdocul.us)
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090303/492f440e/attachment.html>

From matt at mattwynne.net  Tue Mar  3 08:49:54 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Tue, 3 Mar 2009 13:49:54 +0000
Subject: [rspec-users] Cucumber for large projects
In-Reply-To: <7ac2300c0903030206g45f58270m31fc6e5ae736796c@mail.gmail.com>
References: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
	<2287172B-8A6F-4567-9F83-28990DF5506A@mattwynne.net>
	<7ac2300c0903030206g45f58270m31fc6e5ae736796c@mail.gmail.com>
Message-ID: <A00F0A8A-0DD3-4B4A-BC84-620D822D1397@mattwynne.net>


On 3 Mar 2009, at 10:06, aidy lewis wrote:

> Hi Matt/Dan
>
> 2009/3/2 Matt Wynne <matt at mattwynne.net>:
>
>> At the moment, IMO, the tools for feeding back the features to non- 
>> technical
>> people are pretty immature. My colleague Dan Lucraft wrote a tool  
>> which
>> produces a nicely-formatted PDF document from your features  
>> folder[1] which
>> is great, but won't work with the new version (0.2) of Cucumber  
>> when it's
>> released as the API against which such formatters are written has  
>> undergone
>> some significant changes for the new version.
>>
>
>> [1]http://www.daniellucraft.com/blog/2009/01/features_report/
>
> To me the user\customer should be involved in the creation of the
> stories and the acceptance criteria and by producing a pdf later in
> the cycle for those stakeholders to read and understand may be argued
> as something that is not Story-Driven-Development and more like
> comprehendible automated tests.

Should I expect a visit from the Extreme Programing Police Aidy? ;)

I take your point, and I always try to pair with stakeholders when  
creating new features. I think it's also important though that when  
stakeholders are considering adding new features or changing existing  
ones that the current set of Running Tested Features is as visible as  
possible to them. This is one of the advantages of something like  
Fitnesse, where each feature is only a URL away.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From jkleindl at gmail.com  Mon Mar  2 17:13:13 2009
From: jkleindl at gmail.com (Jeremy Kleindl)
Date: Mon, 2 Mar 2009 14:13:13 -0800 (PST)
Subject: [rspec-users] Changes in specs for routes in rspec 1.1.99.x
In-Reply-To: <4b8a6a1f20a84f53853d62c062603af2@ruby-forum.com>
References: <4b8a6a1f20a84f53853d62c062603af2@ruby-forum.com>
Message-ID: <9609f340-c246-4083-8d79-785e47c2efaf@k29g2000prf.googlegroups.com>

Thank you for posting this.
Is this a script to replace/add arguments to the route_for methods in
my current controller routing specs?
Will the changes this script affects fix the errors I get when running
specs like " route_for(_whatever_)should == '/foo/1' " on :update
and :destroy actions generating a :show route?

I've tried adding a :method argument and passing :put and :delete - no
go on these assuring the correct routes so far. I'm off to read the
rspec source to figure out WTF changed...

On Mar 2, 4:08 am, Juanma Cervera <li... at ruby-forum.com> wrote:
> Trying the next release of rspec, I have had to make changes in the
> existing specs for routing.
> I have written an script with sed that makes this automatically (two
> files)
>
> spec/upgrade.sed
> ================
> /route_for/s/id => 1/id => "1"/g
> /route_for.*create/s/== \(["'].*["']\)/== {:path => \1, :method =>
> :post}/
> /route_for.*update/s/== \(["'].*["']\)/== {:path => \1, :method =>
> :put}/
> /route_for.*destroy/s/== \(["'].*["']\)/== {:path => \1, :method =>
> :delete}/
>
> and
> spec/upgrade
> ============
> for f in `find controllers -name "*routing*rb" -type f`; do sed -i -f
> upgrade.sed $f; done
>
> You shoud make this file executable and run it
>
> I hope this helps somebody.
> Juanma
> --
> Posted viahttp://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From jkleindl at gmail.com  Mon Mar  2 17:22:37 2009
From: jkleindl at gmail.com (Jeremy Kleindl)
Date: Mon, 2 Mar 2009 14:22:37 -0800 (PST)
Subject: [rspec-users] Changes in specs for routes in rspec 1.1.99.x
In-Reply-To: <4b8a6a1f20a84f53853d62c062603af2@ruby-forum.com>
References: <4b8a6a1f20a84f53853d62c062603af2@ruby-forum.com>
Message-ID: <08590a9e-5604-4201-a349-03e83d386468@b38g2000prf.googlegroups.com>

GAh! easy one - I was adding the method argument to the 'route_for()'
instead of the 'should ==' hash it compares the generated output with.
And now I see how the script you made takes the single string argument
from the old style and drops it into a hash that includes the restful
method name.
Thank you for providing the clue I needed to get the correct syntax.

On Mar 2, 4:08 am, Juanma Cervera <li... at ruby-forum.com> wrote:
> Trying the next release of rspec, I have had to make changes in the
> existing specs for routing.
> I have written an script with sed that makes this automatically (two
> files)
>
> spec/upgrade.sed
> ================
> /route_for/s/id => 1/id => "1"/g
> /route_for.*create/s/== \(["'].*["']\)/== {:path => \1, :method =>
> :post}/
> /route_for.*update/s/== \(["'].*["']\)/== {:path => \1, :method =>
> :put}/
> /route_for.*destroy/s/== \(["'].*["']\)/== {:path => \1, :method =>
> :delete}/
>
> and
> spec/upgrade
> ============
> for f in `find controllers -name "*routing*rb" -type f`; do sed -i -f
> upgrade.sed $f; done
>
> You shoud make this file executable and run it
>
> I hope this helps somebody.
> Juanma
> --
> Posted viahttp://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From lists at ruby-forum.com  Tue Mar  3 10:08:38 2009
From: lists at ruby-forum.com (James Byrne)
Date: Tue, 3 Mar 2009 16:08:38 +0100
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <3c30da400903022321k4d9da5b6g28ac25dc0b3944c@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<57c63afe0902281038w6a5d9dbas5d6179abfdfa1d5b@mail.gmail.com>
	<e3e91d130902281051y1c20e21fw19649de8f0de13e2@mail.gmail.com>
	<57c63afe0902281116n1a75f5f4n300519b942e8cd19@mail.gmail.com>
	<e3e91d130902281154l619f8e4ala5e7262c039b23e2@mail.gmail.com>
	<49A9A1C0.9050904@benmabey.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
	<85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
	<1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>
	<3c30da400903022204j143825b2x992b633236b99fa0@mail.gmail.com>
	<1fb4df0903022234g61542536jdae9a4745d5c49d2@mail.gmail.com>
	<3c30da400903022321k4d9da5b6g28ac25dc0b3944c@mail.gmail.com>
Message-ID: <aeda51e07f4feac99ec06e43af3691ac@ruby-forum.com>

Mark Wilden wrote:

> 
> You do consolidate all your _access_ logic in one class, just as you
> might consolidate all your sales tax knowledge in another class. That
> way you have one source of responsibility for that behavior.
> Otherwise, if you added, changed or deleted a role, you'd have to
> change every model.
> 
> This is basically the Mediator pattern. Pluses and minuses, to be sure.
> 

This is not where I am spending my time at the moment, but it is an area 
that i am going to confront sooner than later.  So, I am interested in 
this subject.

If I understand aright, it is agreed that authorization is best 
determined by the user model, either as a full-blown authorization 
method wholly contained in the User class or as a call to a subordinate 
Authorization class which does the heavy lifting and then returns the 
result to the User class.  The controllers (and perhaps models) that 
require authorization simply call the equivalent to an "authorized?" 
method on the current_user passing the context, whether this be a named 
role or a control/action pair or a model/attribute pair.  The 
User.authorized? method simply replies whether this current_user belongs 
to the named role or otherwise has the privilege of performing the 
desired action.

If there is an Authorization class then this is where the work is done 
(lookups on models or tables as the case may be).

Does this capture the essence?

The question that I have is: If one implements an authorization system 
as a model or models then would this best be implemented in the user as 
an association rather than as a separate Authorization class?
-- 
Posted via http://www.ruby-forum.com/.

From apremdas at gmail.com  Tue Mar  3 11:07:30 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Tue, 3 Mar 2009 16:07:30 +0000
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<e3e91d130902281426n1724ab2emb78554c71bd63ae6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
	<85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
Message-ID: <88fd8ddc0903030807k4539a94duf28fd4b4e285e53@mail.gmail.com>

I think this discussion has gone backwards a bit. Here is what I think the
index method in the invoices controller should be like

def index
  begin
   invoice.get_collection
  rescue
    # decide what to do if we can't get collection
  end
end

Now clearly this needs some work to get it to work ...

1) What is 'invoice'

Rails by default ties 'invoice' to a class in app/model. Usually this
ActiveRecord model class, but it doesn't have to be. We can always put
another layer inbetween (e.g. Presenter) if it makes our code simpler

2) Authentication parameters

Clearly these need to be passed through to get_collection. This can be done
by parameters or by making the authentication available in a wider context.

3) Exceptions

We need an exception hierarchy. NotAuthorised, NotFound etc.

All the controller should do is get the collection and deal with exceptions
if the collection is not available. (n.b. the collection being empty is not
exceptional.)

Rails historically has corrupted (compromised, polluted ...) MVC by allowing
concerns of how we get the collection to be included in the controller.
RESTful design has highlighted the problems with this and now we end up with
this situation where things like authentication and authorisation don't
really have an obvious place.

These things - authentication, authorisation and the exception handling (for
the resource) - are services which all resources need access to. They need
to be seperated and applied in a cross-cutting manner. Perhaps we could do
things more elegantly with an Aspect Orientated solution.

Andrew



2009/3/2 Zach Dennis <zach.dennis at gmail.com>

>
> Forgot to mention what we did do. We ended up with the following...
>
> def index
>  if user.has_role?("admin")
>     user.in_role("admin").invoices
>   elsif user.has_role?("associate")
>     user.in_role("associate").invoices
>   else
>    raise AccessDenied
>  end
> end
>
> To us, the change here is subtle, but important. The controller is
> allowed to ask for invoices from each role, but is not allowed to know
> how find the invoices, that's the behaviour of the role.
>
> > --
> > - Show quoted text -
> > Zach Dennis
> > http://www.continuousthinking.com
> > http://www.mutuallyhuman.com
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090303/0b3407c2/attachment-0001.html>

From zach.dennis at gmail.com  Tue Mar  3 12:06:32 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Tue, 3 Mar 2009 12:06:32 -0500
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <88fd8ddc0903030807k4539a94duf28fd4b4e285e53@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
	<85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
	<88fd8ddc0903030807k4539a94duf28fd4b4e285e53@mail.gmail.com>
Message-ID: <85d99afe0903030906t44484148l847857fca5d55463@mail.gmail.com>

On Tue, Mar 3, 2009 at 11:07 AM, Andrew Premdas <apremdas at gmail.com> wrote:
> I think this discussion has gone backwards a bit. Here is what I think the
> index method in the invoices controller should be like
>
> def index
> ? begin
> ?? invoice.get_collection
> ? rescue
> ??? # decide what to do if we can't get collection
> ? end
> end
>
> Now clearly this needs some work to get it to work ...
>
> 1) What is 'invoice'
>
> Rails by default ties 'invoice' to a class in app/model. Usually this
> ActiveRecord model class, but it doesn't have to be. We can always put
> another layer inbetween (e.g. Presenter) if it makes our code simpler

Presenters are for presentation logic, not for authorization concerns.

>
> 2) Authentication parameters
>
> Clearly these need to be passed through to get_collection. This can be done
> by parameters or by making the authentication available in a wider context.

Authentication isn't the issue here, authorization is.

>
> 3) Exceptions
>
> We need an exception hierarchy. NotAuthorised, NotFound etc.
>
> All the controller should do is get the collection and deal with exceptions
> if the collection is not available. (n.b. the collection being empty is not
> exceptional.)
>
> Rails historically has corrupted (compromised, polluted ...) MVC by allowing
> concerns of how we get the collection to be included in the controller.
> RESTful design has highlighted the problems with this and now we end up with
> this situation where things like authentication and authorisation don't
> really have an obvious place.

It is up to the controllers to know how-to ask for something, it
should not know how the internals of that request work. For a
controller to know what role can access a particular resource is
completely aligned with a layered architecture, keeping application
concerns in the right layer, and domain logic in another layer.

>
> These things - authentication, authorisation and the exception handling (for
> the resource) - are services which all resources need access to. They need
> to be seperated and applied in a cross-cutting manner. Perhaps we could do
> things more elegantly with an Aspect Orientated solution.
>

Is some cases yes, but I fail to see where it benefits or adds more
value then concretely identifying a role that has particular behavior.

>
> 2009/3/2 Zach Dennis <zach.dennis at gmail.com>
>>
>> Forgot to mention what we did do. We ended up with the following...
>>
>> def index
>> ?if user.has_role?("admin")
>> ? ?user.in_role("admin").invoices
>> ?elsif user.has_role?("associate")
>> ? ?user.in_role("associate").invoices
>> ?else
>> ? ?raise AccessDenied
>> ?end
>> end
>>
>> To us, the change here is subtle, but important. The controller is
>> allowed to ask for invoices from each role, but is not allowed to know
>> how find the invoices, that's the behaviour of the role.
>>
>> > --
>> > - Show quoted text -
>> > Zach Dennis
>> > http://www.continuousthinking.com
>> > http://www.mutuallyhuman.com
>> >
>>
>>
>
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From pat.maddox at gmail.com  Tue Mar  3 12:32:33 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Tue, 3 Mar 2009 09:32:33 -0800
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<88fd8ddc0903020656y54888d44gb3928cc555302bcf@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
	<85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
	<1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>
Message-ID: <2c7e61990903030932q353018f4v8323b4ed99366db0@mail.gmail.com>

On Mon, Mar 2, 2009 at 8:35 PM, Stephen Eley <sfeley at gmail.com> wrote:
> On Mon, Mar 2, 2009 at 5:16 PM, Zach Dennis <zach.dennis at gmail.com> wrote:
>>
>> Forgot to mention what we did do. We ended up with the following...
>>
>> def index
>> ?if user.has_role?("admin")
>> ? ?user.in_role("admin").invoices
>> ?elsif user.has_role?("associate")
>> ? ?user.in_role("associate").invoices
>> ?else
>> ? ?raise AccessDenied
>> ?end
>> end
>
> That seems sort of backwards to me. ?These aren't the user's invoices,
> right? ?They're just invoices which the user happens to be allowed to
> see? ?Chaining it this way makes it look like the invoices *belong* to
> the role, and seems put the user up front instead of the invoices.
> You also have conditional branching with hardcoded values, making the
> controller brittle, and some redundancy with the controller asking the
> model for a value and then passing the value right back to the model.

Agreed.  I have a similar example in a blog post:
http://www.patmaddox.com/blog/2008/7/23/when-duplication-in-tests-informs-design

Pat

From zach.dennis at gmail.com  Tue Mar  3 13:06:12 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Tue, 3 Mar 2009 13:06:12 -0500
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <2c7e61990903030932q353018f4v8323b4ed99366db0@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<675261bfd8ca95790d348539630b1398@ruby-forum.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
	<85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
	<1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>
	<2c7e61990903030932q353018f4v8323b4ed99366db0@mail.gmail.com>
Message-ID: <85d99afe0903031006v34236d8du5ae5b2f18da89be9@mail.gmail.com>

On Tue, Mar 3, 2009 at 12:32 PM, Pat Maddox <pat.maddox at gmail.com> wrote:
> On Mon, Mar 2, 2009 at 8:35 PM, Stephen Eley <sfeley at gmail.com> wrote:
>> On Mon, Mar 2, 2009 at 5:16 PM, Zach Dennis <zach.dennis at gmail.com> wrote:
>>>
>>> Forgot to mention what we did do. We ended up with the following...
>>>
>>> def index
>>> ?if user.has_role?("admin")
>>> ? ?user.in_role("admin").invoices
>>> ?elsif user.has_role?("associate")
>>> ? ?user.in_role("associate").invoices
>>> ?else
>>> ? ?raise AccessDenied
>>> ?end
>>> end
>>
>> That seems sort of backwards to me. ?These aren't the user's invoices,
>> right? ?They're just invoices which the user happens to be allowed to
>> see? ?Chaining it this way makes it look like the invoices *belong* to
>> the role, and seems put the user up front instead of the invoices.
>> You also have conditional branching with hardcoded values, making the
>> controller brittle, and some redundancy with the controller asking the
>> model for a value and then passing the value right back to the model.
>
> Agreed. ?I have a similar example in a blog post:
> http://www.patmaddox.com/blog/2008/7/23/when-duplication-in-tests-informs-design

I agree I'm taking a step back to try to make two steps forward. The
heart of the exploration is more than the conditional in the action
(which simply states which roles are allowed to access that action, I
just made it explicit rather than using a #restrict_to call). To me
this discussion is about where the behaviour for a role should go and
how-to access that behaviour.

The flip side of this is that models end up with redundant conditional
branches to do x for RoleA or y for RoleB (for every model thats
affected by a Role). I would like to collapse these conditional
branches and attempt a more polymorphic approach by extracting a class
representative of each role, and simply calling the method in
question. e.g:

  FiscalAssociate.new(user).invoices
  FiscalAdmin.new(user).invoices

Rather than the following approach. Keep in mind that roles hardly
ever are limited to one model. Consider having the case statement in
20 models. Where's the redundancy now?

   Invoice.by_role(<role_name>)

   def by_role(role
       case role
       when "associate"
        ....
       when "admin"
        ...
   end


-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From apremdas at gmail.com  Tue Mar  3 14:50:42 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Tue, 3 Mar 2009 19:50:42 +0000
Subject: [rspec-users] [rails] An authorization question
In-Reply-To: <85d99afe0903031006v34236d8du5ae5b2f18da89be9@mail.gmail.com>
References: <e3e91d130902280952n553bebb7qfdd62e5046de88d6@mail.gmail.com>
	<3c30da400903021110t52991e46y16a0f644a4992baf@mail.gmail.com>
	<e620ae7dbbb728cee54fa569d4884e9d@ruby-forum.com>
	<387919.43677.qm@web31802.mail.mud.yahoo.com>
	<2ce629d2f33b1a587b46ee90413d0e77@ruby-forum.com>
	<85d99afe0903021350p1e79dd9cw66cf43b7f1d1184b@mail.gmail.com>
	<85d99afe0903021416k6d9dc768q2676db5107146065@mail.gmail.com>
	<1fb4df0903022035u2aadd8ek201f3f3faaeb5c88@mail.gmail.com>
	<2c7e61990903030932q353018f4v8323b4ed99366db0@mail.gmail.com>
	<85d99afe0903031006v34236d8du5ae5b2f18da89be9@mail.gmail.com>
Message-ID: <88fd8ddc0903031150l4cc4acc8nc81393e8ac319a48@mail.gmail.com>

Zach

By saying that models need the following case statement

  def by_role(role
   case role
     when "associate"
       ....
     when "admin"
       ...
  end

your implying that the model is represented in a different way depending on
the role. So in your case of invoices the associate's view is different from
the administrators. If this is the case then you have identified two
distinct resources!

Currently you are representing these two resources with one url e.g.
/invoices

However if you think of these as seperate resources then you have two url's

/admin_invoices /associatie_invoices

Other url schems come fo mind /admin/invoices /invoices/admin etc.

Point is that you can implement these seperate resources in the standard
rails way and remove any need for case statements

class AdminInvoicesController
  before_filter must_be_admin

  def index
    Invoices.find # specify admin criteria here
  end
end

class AssociateInvoices
  before_filter must_be_associate

  def index
    Invoices.find # specify associate criteria here
  end
end

Andrew

2009/3/3 Zach Dennis <zach.dennis at gmail.com>

> On Tue, Mar 3, 2009 at 12:32 PM, Pat Maddox <pat.maddox at gmail.com> wrote:
> > On Mon, Mar 2, 2009 at 8:35 PM, Stephen Eley <sfeley at gmail.com> wrote:
> >> On Mon, Mar 2, 2009 at 5:16 PM, Zach Dennis <zach.dennis at gmail.com>
> wrote:
> >>>
> >>> Forgot to mention what we did do. We ended up with the following...
> >>>
> >>> def index
> >>>  if user.has_role?("admin")
> >>>    user.in_role("admin").invoices
> >>>  elsif user.has_role?("associate")
> >>>    user.in_role("associate").invoices
> >>>  else
> >>>    raise AccessDenied
> >>>  end
> >>> end
> >>
> >> That seems sort of backwards to me.  These aren't the user's invoices,
> >> right?  They're just invoices which the user happens to be allowed to
> >> see?  Chaining it this way makes it look like the invoices *belong* to
> >> the role, and seems put the user up front instead of the invoices.
> >> You also have conditional branching with hardcoded values, making the
> >> controller brittle, and some redundancy with the controller asking the
> >> model for a value and then passing the value right back to the model.
> >
> > Agreed.  I have a similar example in a blog post:
> >
> http://www.patmaddox.com/blog/2008/7/23/when-duplication-in-tests-informs-design
>
> I agree I'm taking a step back to try to make two steps forward. The
> heart of the exploration is more than the conditional in the action
> (which simply states which roles are allowed to access that action, I
> just made it explicit rather than using a #restrict_to call). To me
> this discussion is about where the behaviour for a role should go and
> how-to access that behaviour.
>
> The flip side of this is that models end up with redundant conditional
> branches to do x for RoleA or y for RoleB (for every model thats
> affected by a Role). I would like to collapse these conditional
> branches and attempt a more polymorphic approach by extracting a class
> representative of each role, and simply calling the method in
> question. e.g:
>
>  FiscalAssociate.new(user).invoices
>  FiscalAdmin.new(user).invoices
>
> Rather than the following approach. Keep in mind that roles hardly
> ever are limited to one model. Consider having the case statement in
> 20 models. Where's the redundancy now?
>
>   Invoice.by_role(<role_name>)
>
>   def by_role(role
>       case role
>       when "associate"
>        ....
>       when "admin"
>        ...
>   end
>
>
> --
> Zach Dennis
> http://www.continuousthinking.com
> http://www.mutuallyhuman.com
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090303/fc7ebcaf/attachment.html>

From rdm at cfcl.com  Tue Mar  3 14:43:32 2009
From: rdm at cfcl.com (Rich Morin)
Date: Tue, 3 Mar 2009 11:43:32 -0800
Subject: [rspec-users] Gherkin syntax notes (WIP)
Message-ID: <p06230906c5d3386f6f5c@[192.168.1.205]>

I made a start on some Gherkin syntax notes:

  http://wiki.github.com/aslakhellesoy/cucumber/gherkin

Please look them over, fix errors, and/or send me a note
about things I've missed or gotten wrong...

-r
-- 
http://www.cfcl.com/rdm            Rich Morin
http://www.cfcl.com/rdm/resume     rdm at cfcl.com
http://www.cfcl.com/rdm/weblog     +1 650-873-7841

Technical editing and writing, programming, and web development

From pat.maddox at gmail.com  Tue Mar  3 19:41:11 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Tue, 3 Mar 2009 16:41:11 -0800
Subject: [rspec-users] Cucumber for large projects
In-Reply-To: <7ac2300c0903030206g45f58270m31fc6e5ae736796c@mail.gmail.com>
References: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
	<2287172B-8A6F-4567-9F83-28990DF5506A@mattwynne.net>
	<7ac2300c0903030206g45f58270m31fc6e5ae736796c@mail.gmail.com>
Message-ID: <2c7e61990903031641v5873a6dfqe344b7a0ae2fa494@mail.gmail.com>

On Tue, Mar 3, 2009 at 2:06 AM, aidy lewis <aidy.lewis at googlemail.com> wrote:
> Hi Matt/Dan
>
> 2009/3/2 Matt Wynne <matt at mattwynne.net>:
>
>> At the moment, IMO, the tools for feeding back the features to non-technical
>> people are pretty immature. My colleague Dan Lucraft wrote a tool which
>> produces a nicely-formatted PDF document from your features folder[1] which
>> is great, but won't work with the new version (0.2) of Cucumber when it's
>> released as the API against which such formatters are written has undergone
>> some significant changes for the new version.
>>
>
>> [1]http://www.daniellucraft.com/blog/2009/01/features_report/
>
> To me the user\customer should be involved in the creation of the
> stories and the acceptance criteria and by producing a pdf later in
> the cycle for those stakeholders to read and understand may be argued
> as something that is not Story-Driven-Development and more like
> comprehendible automated tests.

Not quite.  Some customers don't want to sit down next to you as you
write the stories.  In that situation, we'll talk about features, I
take notes, then I write up the features and ship them via email or
wiki.  They're still involved in the creation of stories and
acceptance criteria, they're just not present when those criteria get
entered into cucumber features.

Pat

From rdm at cfcl.com  Tue Mar  3 20:51:33 2009
From: rdm at cfcl.com (Rich Morin)
Date: Tue, 3 Mar 2009 17:51:33 -0800
Subject: [rspec-users] Cucumber for large projects
In-Reply-To: <2c7e61990903031641v5873a6dfqe344b7a0ae2fa494@mail.gmail.com>
References: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
	<2287172B-8A6F-4567-9F83-28990DF5506A@mattwynne.net>
	<7ac2300c0903030206g45f58270m31fc6e5ae736796c@mail.gmail.com>
	<2c7e61990903031641v5873a6dfqe344b7a0ae2fa494@mail.gmail.com>
Message-ID: <p0623090dc5d38d084396@[192.168.1.205]>

At 16:41 -0800 3/3/09, Pat Maddox wrote:
> Not quite.  Some customers don't want to sit down next to you as you
> write the stories.  In that situation, we'll talk about features, I
> take notes, then I write up the features and ship them via email or
> wiki.  They're still involved in the creation of stories and
> acceptance criteria, they're just not present when those criteria get
> entered into cucumber features.

In the Ontiki project, I am acting as my own initial customer and the
primary customers (for at least a while) will be Ruby programmers.  So,
I'm playing with the use of a pre-processor which allows use of eRuby
(for selection, repetition, and variable substitution), line folding,
etc.  This DRYs out my editable files (fe/*.fe), while generating
readable and Gherkin-compliant feature (*.feature) files.

This would not work well for a highly interactive situation, but it
might work in a situation like the one you describe.  It may also give
us some useful feedback about useful extensions for Gherkin.

-r
-- 
http://www.cfcl.com/rdm            Rich Morin
http://www.cfcl.com/rdm/resume     rdm at cfcl.com
http://www.cfcl.com/rdm/weblog     +1 650-873-7841

Technical editing and writing, programming, and web development

From rem.gagnon at gmail.com  Tue Mar  3 21:21:34 2009
From: rem.gagnon at gmail.com (Remi Gagnon)
Date: Tue, 3 Mar 2009 21:21:34 -0500
Subject: [rspec-users] Cucumber for large projects
In-Reply-To: <p0623090dc5d38d084396@192.168.1.205>
References: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
	<2287172B-8A6F-4567-9F83-28990DF5506A@mattwynne.net>
	<7ac2300c0903030206g45f58270m31fc6e5ae736796c@mail.gmail.com>
	<2c7e61990903031641v5873a6dfqe344b7a0ae2fa494@mail.gmail.com>
	<p0623090dc5d38d084396@192.168.1.205>
Message-ID: <aecbd5a50903031821w354f9732jcc635b321229eb1@mail.gmail.com>

Let me share my experience.

On my side we do produce 3 documents before starting with rspec.

1- A web designer creates a design for a screen in conjunction with the
marketing team and the analyst assigned to the this feature.  The marketing
dep, acts as the customer.

2-The analyst produce a "word" document containing the stories and scenarios
attached to this screen.  This work is done again in conjunction with the
web designer cause she is also an ergonomist and the Marketing dep.  The
analyst has to have the approval of these stories-scenarios before he can
share this info to the ruby programmers.

3- The analyst produce also a little spreadsheet defining all labels, fields
and any specifities of the screen to eleminates any "second guess" of the
ruby dev.

As soon the ruby dep got those docs they start creating specs for this.  For
now we are not using cucumber yet.  It is already a huge challenge for me to
convience legacy programmers to learn ruby, rails OOP in the BDD way.  In
short term I plan to experience it.

For now we are not having any tool to transfer stories-scenarios from our
word doc to rspec file.  If any of you have something for that, let me know.

R?mi Gagnon

On Tue, Mar 3, 2009 at 8:51 PM, Rich Morin <rdm at cfcl.com> wrote:

> At 16:41 -0800 3/3/09, Pat Maddox wrote:
> > Not quite.  Some customers don't want to sit down next to you as you
> > write the stories.  In that situation, we'll talk about features, I
> > take notes, then I write up the features and ship them via email or
> > wiki.  They're still involved in the creation of stories and
> > acceptance criteria, they're just not present when those criteria get
> > entered into cucumber features.
>
> In the Ontiki project, I am acting as my own initial customer and the
> primary customers (for at least a while) will be Ruby programmers.  So,
> I'm playing with the use of a pre-processor which allows use of eRuby
> (for selection, repetition, and variable substitution), line folding,
> etc.  This DRYs out my editable files (fe/*.fe), while generating
> readable and Gherkin-compliant feature (*.feature) files.
>
> This would not work well for a highly interactive situation, but it
> might work in a situation like the one you describe.  It may also give
> us some useful feedback about useful extensions for Gherkin.
>
> -r
> --
> http://www.cfcl.com/rdm            Rich Morin
> http://www.cfcl.com/rdm/resume     rdm at cfcl.com
> http://www.cfcl.com/rdm/weblog     +1 650-873-7841
>
> Technical editing and writing, programming, and web development
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090303/e8cf2454/attachment.html>

From apremdas at gmail.com  Tue Mar  3 23:30:23 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Wed, 4 Mar 2009 04:30:23 +0000
Subject: [rspec-users] Sinitra and Cucumber
In-Reply-To: <FB7BBF64-6E3E-41E1-AF7E-A9AB604EF5C7@gmail.com>
References: <88fd8ddc0902152239v1c96d9a0o4c3b607f9dbaf529@mail.gmail.com>
	<620c6d021a378669605b46bce1c93dd6@ruby-forum.com>
	<8d961d900902260450i344cddbey8d0381b104ba1731@mail.gmail.com>
	<ccbf3a87ef9bcf83fb5e82a54ed64b26@ruby-forum.com>
	<FB7BBF64-6E3E-41E1-AF7E-A9AB604EF5C7@gmail.com>
Message-ID: <88fd8ddc0903032030n54779266k14492d81399efa27@mail.gmail.com>

With Cuc and Rails I'd be able to debug step definitions by putting
'debugger' in the relevant step definition. With Sinatra configured as above
this doesn't work. Any tips on making this work and/or explaining whats
different/

Cheers

Andrew

2009/2/27 Aslak Helles?y <aslak.hellesoy at gmail.com>

>
>
>  Aslak Helles?y wrote:
>>
>>> Rob Holland updated the wiki yesterday:
>>> http://wiki.github.com/aslakhellesoy/cucumber/sinatra
>>> (He reports that the $0 trick described in the blog doesn't work with
>>> the latest Sinatra).
>>> Rob also has an example in his fork, which I have yet to merge into my
>>> repo:
>>>
>>> http://github.com/robholland/cucumber/commit/0e12d8100ca8541af014abe6a480c53a90b6aebd
>>>
>>>
> This is now in my master too.
>
> Aslak
>
>
>  Aslak
>>>
>>
>> Thanks, I've updated my blog to reflect.
>>
>> --
>> Posted via http://www.ruby-forum.com/.
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090304/4fa7c849/attachment.html>

From apremdas at gmail.com  Tue Mar  3 23:39:30 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Wed, 4 Mar 2009 04:39:30 +0000
Subject: [rspec-users] Sinitra 0.9.1 Webrat 0.4.2 Cuc problem
Message-ID: <88fd8ddc0903032039t4dad780ay628ca56bc57953c4@mail.gmail.com>

Have created sample sinatra cucumber app as suggested on wiki. Tried both
env.rb configurations from there and aslaks git repo. With this combination
of gems I get the following error doing basic cuc tests

 When I visit '/foo'                                       #
features/step_definitions/general.rb:1
      PATH_INFO must start with / (Rack::Lint::LintError)
      /Library/Ruby/Gems/1.8/gems/rack-0.9.1/lib/rack/lint.rb:16:in `assert'
      /Library/Ruby/Gems/1.8/gems/rack-0.9.1/lib/rack/lint.rb:178:in
`check_env'
      /Library/Ruby/Gems/1.8/gems/rack-0.9.1/lib/rack/lint.rb:39:in `_call'
      /Library/Ruby/Gems/1.8/gems/rack-0.9.1/lib/rack/lint.rb:33:in `call'
      /Library/Ruby/Gems/1.8/gems/rack-0.9.1/lib/rack/mock.rb:70:in
`request'
      /Library/Ruby/Gems/1.8/gems/sinatra-0.9.1/lib/sinatra/test.rb:41:in
`make_request'
      /Library/Ruby/Gems/1.8/gems/sinatra-0.9.1/lib/sinatra/test.rb:44:in
`orig_get'
      /Library/Ruby/Gems/1.8/gems/webrat-0.4.2/lib/webrat/sinatra.rb:26:in
`__send__'
      /Library/Ruby/Gems/1.8/gems/webrat-0.4.2/lib/webrat/sinatra.rb:26:in
`get'

/Library/Ruby/Gems/1.8/gems/webrat-0.4.2/lib/webrat/core/session.rb:104:in
`send'

/Library/Ruby/Gems/1.8/gems/webrat-0.4.2/lib/webrat/core/session.rb:104:in
`request_page'

/Library/Ruby/Gems/1.8/gems/webrat-0.4.2/lib/webrat/core/session.rb:205:in
`visit'
      ./features/step_definitions/general.rb:3:in `When /^I visit (.*)$/'
      features/basic.feature:17:in `When I visit '/foo''


Afraid I can't expand on this as I can't getting debugging working with cuc
and sinatra.

All best

Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090304/7351c907/attachment.html>

From sfeley at gmail.com  Tue Mar  3 23:44:02 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Tue, 3 Mar 2009 23:44:02 -0500
Subject: [rspec-users] Cucumber for large projects
In-Reply-To: <7ac2300c0903030206g45f58270m31fc6e5ae736796c@mail.gmail.com>
References: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
	<2287172B-8A6F-4567-9F83-28990DF5506A@mattwynne.net>
	<7ac2300c0903030206g45f58270m31fc6e5ae736796c@mail.gmail.com>
Message-ID: <1fb4df0903032044y4d976c01m9f758851dc31b0a4@mail.gmail.com>

On Tue, Mar 3, 2009 at 5:06 AM, aidy lewis <aidy.lewis at googlemail.com> wrote:
>
> To me the user\customer should be involved in the creation of the
> stories and the acceptance criteria and by producing a pdf later in
> the cycle for those stakeholders to read and understand may be argued
> as something that is not Story-Driven-Development and more like
> comprehendible automated tests.

There's more than one way to skin a ca...a cucumber.  In my
organization, people are definitely invested in what I intend to
build, and we do discuss requirements.  But if I tried to tell them,
"All right, I need all of us to sit down and write scenarios in a
particular text file format for all of our critical path success and
failure cases," I would just get blank stares.  They wouldn't Get It.
And I don't see it as a necessary part of my job to drag everyone else
into this culture, if I can just document my best understanding and
then show them the results for feedback.


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From lists at ruby-forum.com  Wed Mar  4 00:35:19 2009
From: lists at ruby-forum.com (Sebastian W.)
Date: Wed, 4 Mar 2009 06:35:19 +0100
Subject: [rspec-users] Testing my scripts?
Message-ID: <5e257dbc314d72c9770f6aea3e14170d@ruby-forum.com>

Hello RSpec mailing list,
I have a question which I'm sure someone here has a "duh!" answer to. :P

A lot of the Ruby programming I do is around installing servers and
automating various tasks. The pattern I use goes as follows, I'm sure
you'll see where the gap is.

Write a failing test. Write enough Ruby code to make it pass. Continue
until I have a class (or set of classes) that solve my problem. So far,
so good.

I then need to put this code into a script so I can run it as part of
everyday automation. My approach so far has been to take green-light
code and plug it into the script so that when the script gets run, it
takes the arguments to the scripts and passes it to my tested code. The
script runs and does what its supposed to do; all is well.

Now -- there's a bug in my code somewhere, or I need to add something to
the code I've written to improve it. No problem initially. First, run
all tests. Green light, good. Write a failing test. Write enough Ruby
code to make it pass. Happy, happy.

Problem: the code in my script is not fixed! Running my spec suite does
not catch the fact that there's client code in my script using bad code.

So, my question is: how can I make sure that when I run my spec suite
that all the code in my scripts gets tested as well? I thought about
adding  "--test" option to all my scripts, but that seems, well...just
not the right way to do it.

Anyone have any words of wisdom they'd like to share? Have I walked into
an antipattern here?

Thanks much!
Sebastian
-- 
Posted via http://www.ruby-forum.com/.

From patnakajima at gmail.com  Wed Mar  4 00:54:28 2009
From: patnakajima at gmail.com (Pat Nakajima)
Date: Wed, 4 Mar 2009 00:54:28 -0500
Subject: [rspec-users] Sinitra 0.9.1 Webrat 0.4.2 Cuc problem
In-Reply-To: <88fd8ddc0903032039t4dad780ay628ca56bc57953c4@mail.gmail.com>
References: <88fd8ddc0903032039t4dad780ay628ca56bc57953c4@mail.gmail.com>
Message-ID: <97ae2db00903032154i1b27180cp544563f1eff4c3@mail.gmail.com>

For what it's worth, here's how I had to hack Webrat to get my Sinatra 0.9.1
app working properly: http://gist.github.com/73735.

On Tue, Mar 3, 2009 at 11:39 PM, Andrew Premdas <apremdas at gmail.com> wrote:

> Have created sample sinatra cucumber app as suggested on wiki. Tried both
> env.rb configurations from there and aslaks git repo. With this combination
> of gems I get the following error doing basic cuc tests
>
>  When I visit '/foo'                                       #
> features/step_definitions/general.rb:1
>       PATH_INFO must start with / (Rack::Lint::LintError)
>       /Library/Ruby/Gems/1.8/gems/rack-0.9.1/lib/rack/lint.rb:16:in
> `assert'
>       /Library/Ruby/Gems/1.8/gems/rack-0.9.1/lib/rack/lint.rb:178:in
> `check_env'
>       /Library/Ruby/Gems/1.8/gems/rack-0.9.1/lib/rack/lint.rb:39:in `_call'
>       /Library/Ruby/Gems/1.8/gems/rack-0.9.1/lib/rack/lint.rb:33:in `call'
>       /Library/Ruby/Gems/1.8/gems/rack-0.9.1/lib/rack/mock.rb:70:in
> `request'
>       /Library/Ruby/Gems/1.8/gems/sinatra-0.9.1/lib/sinatra/test.rb:41:in
> `make_request'
>       /Library/Ruby/Gems/1.8/gems/sinatra-0.9.1/lib/sinatra/test.rb:44:in
> `orig_get'
>       /Library/Ruby/Gems/1.8/gems/webrat-0.4.2/lib/webrat/sinatra.rb:26:in
> `__send__'
>       /Library/Ruby/Gems/1.8/gems/webrat-0.4.2/lib/webrat/sinatra.rb:26:in
> `get'
>
> /Library/Ruby/Gems/1.8/gems/webrat-0.4.2/lib/webrat/core/session.rb:104:in
> `send'
>
> /Library/Ruby/Gems/1.8/gems/webrat-0.4.2/lib/webrat/core/session.rb:104:in
> `request_page'
>
> /Library/Ruby/Gems/1.8/gems/webrat-0.4.2/lib/webrat/core/session.rb:205:in
> `visit'
>       ./features/step_definitions/general.rb:3:in `When /^I visit (.*)$/'
>       features/basic.feature:17:in `When I visit '/foo''
>
>
> Afraid I can't expand on this as I can't getting debugging working with cuc
> and sinatra.
>
> All best
>
> Andrew
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090304/a3c942d0/attachment.html>

From rdm at cfcl.com  Wed Mar  4 00:50:13 2009
From: rdm at cfcl.com (Rich Morin)
Date: Tue, 3 Mar 2009 21:50:13 -0800
Subject: [rspec-users] Cucumber for large projects
In-Reply-To: <aecbd5a50903031821w354f9732jcc635b321229eb1@mail.gmail.com>
References: <c19f1c910902260733x25f78f04n67236827c28e3fb9@mail.gmail.com>
	<2287172B-8A6F-4567-9F83-28990DF5506A@mattwynne.net>
	<7ac2300c0903030206g45f58270m31fc6e5ae736796c@mail.gmail.com>
	<2c7e61990903031641v5873a6dfqe344b7a0ae2fa494@mail.gmail.com>
	<p0623090dc5d38d084396@192.168.1.205>
	<aecbd5a50903031821w354f9732jcc635b321229eb1@mail.gmail.com>
Message-ID: <p06230912c5d3c622a5be@[192.168.1.205]>

At 21:21 -0500 3/3/09, Remi Gagnon wrote:
>
> For now we are not having any tool to transfer
> stories-scenarios from our word doc to rspec file.
> If any of you have something for that, let me know.

I don't have any software to offer, but I can offer a
suggestion regarding process.  If the "word" document
is a Microsoft Word document, and the format is stable
and well-defined, you may be able to have Word export
a document in an intermediate format (eg, HTML, XML)
that can be parsed and used as input by a mechanized
process.

-r
-- 
http://www.cfcl.com/rdm            Rich Morin
http://www.cfcl.com/rdm/resume     rdm at cfcl.com
http://www.cfcl.com/rdm/weblog     +1 650-873-7841

Technical editing and writing, programming, and web development

From rob.holland at gmail.com  Wed Mar  4 04:33:28 2009
From: rob.holland at gmail.com (Rob Holland)
Date: Wed, 4 Mar 2009 09:33:28 +0000
Subject: [rspec-users] Sinitra and Cucumber
In-Reply-To: <88fd8ddc0903032030n54779266k14492d81399efa27@mail.gmail.com>
References: <88fd8ddc0902152239v1c96d9a0o4c3b607f9dbaf529@mail.gmail.com>
	<620c6d021a378669605b46bce1c93dd6@ruby-forum.com>
	<8d961d900902260450i344cddbey8d0381b104ba1731@mail.gmail.com>
	<ccbf3a87ef9bcf83fb5e82a54ed64b26@ruby-forum.com>
	<FB7BBF64-6E3E-41E1-AF7E-A9AB604EF5C7@gmail.com>
	<88fd8ddc0903032030n54779266k14492d81399efa27@mail.gmail.com>
Message-ID: <6ea3a1b80903040133y127b1688j96a477325dd73e4c@mail.gmail.com>

On Wed, Mar 4, 2009 at 4:30 AM, Andrew Premdas <apremdas at gmail.com> wrote:
> With Cuc and Rails I'd be able to debug step definitions by putting
> 'debugger' in the relevant step definition. With Sinatra configured as above
> this doesn't work. Any tips on making this work and/or explaining whats
> different/

Just use: require 'ruby-debug/debugger' where you'd normally use debugger.

The difference is sinatra doesn't load ruby-debug itself.

From rob.holland at gmail.com  Wed Mar  4 04:43:13 2009
From: rob.holland at gmail.com (Rob Holland)
Date: Wed, 4 Mar 2009 09:43:13 +0000
Subject: [rspec-users] Sinitra 0.9.1 Webrat 0.4.2 Cuc problem
In-Reply-To: <97ae2db00903032154i1b27180cp544563f1eff4c3@mail.gmail.com>
References: <88fd8ddc0903032039t4dad780ay628ca56bc57953c4@mail.gmail.com>
	<97ae2db00903032154i1b27180cp544563f1eff4c3@mail.gmail.com>
Message-ID: <6ea3a1b80903040143v47d4f4fco562baff873b728b4@mail.gmail.com>

My application (the one on which the wiki example is based) still runs
just fine on 0.9.1, so I don't think it's related to the version
change.

I think the hacks Pat used are solely to do with getting selenium mode happy.

From thibaut.barrere at gmail.com  Wed Mar  4 05:35:38 2009
From: thibaut.barrere at gmail.com (=?ISO-8859-1?Q?Thibaut_Barr=E8re?=)
Date: Wed, 4 Mar 2009 11:35:38 +0100
Subject: [rspec-users] Cucumber - Performance
In-Reply-To: <22FA105F-8A20-4CDB-B4EA-22C1BF506397@mattwynne.net>
References: <BLU140-W415A871C905CDD8E824F4EABDF0@phx.gbl>
	<8d961d900901070346k4e452dcfva2edd0123e2ef7c0@mail.gmail.com>
	<22FA105F-8A20-4CDB-B4EA-22C1BF506397@mattwynne.net>
Message-ID: <4a68b8cf0903040235w512cb632odd4a7861be9183c9@mail.gmail.com>

> My guess is that it's the initial start-up that's slow. This is a great
> reason to use something like autotest, which will keep the process loaded
> up. I wonder how that hell you could make that work with C# code though!
> Watch the DLLs?!

coming late on this one - if this is useful to someone, you can quite
easily watch the dll's using the built-in FileSystemWatcher
(http://msdn.microsoft.com/en-us/library/system.io.filesystemwatcher.aspx).

cheers,

-- Thibaut

>
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From u.alberton at gmail.com  Wed Mar  4 05:54:51 2009
From: u.alberton at gmail.com (Bira)
Date: Wed, 4 Mar 2009 07:54:51 -0300
Subject: [rspec-users] Writing specs for AMQP clients.
Message-ID: <d391a7990903040254x3690f6f0o6aa38deb1fe260ff@mail.gmail.com>

Hello!

I've been lurking in the list a while, and now I would like to ask you
a somewhat "noobish" question... This is the first time I've run
across this particular problem, so I'm not sure what to do. I'm sure
this is so common that's in a textbook somewhere, but what is the best
way to write specs for code that calls out to an external server?

I've just started working on a project that will use AMQP messaging
(and the "amqp" gem), and most of the code I've written so far is all
about talking to a messaging server. The only alternatives I saw for
writing specs were starting said server, and mocking/stubbing out all
the code that would talk to it. I went witht he second one, but I feel
it's a fragile approach that won't actually allow me to find bugs,
since everything is mocked out. What is the best way to do this?

-- 
Bira
http://compexplicita.wordpress.com
http://compexplicita.tumblr.com

From tastapod at gmail.com  Wed Mar  4 06:25:24 2009
From: tastapod at gmail.com (Dan North)
Date: Wed, 4 Mar 2009 11:25:24 +0000
Subject: [rspec-users] [cucumber] Cucumber and CI
In-Reply-To: <8d961d900902240510s46f945f9ofb08a003395a139d@mail.gmail.com>
References: <ee6f48c00902221147h2327b886ye2df76bb985d93be@mail.gmail.com>
	<8d961d900902221336x7822dc36p43ea7c29bca44430@mail.gmail.com>
	<ee6f48c00902221609o49ed4e09pa4dff9a7b4e81ad3@mail.gmail.com>
	<824F1590-C31C-44D9-B283-C7C0550F0D84@mattwynne.net>
	<6ea3a1b80902240130u3d8bcb8dyf46a2945165a776c@mail.gmail.com>
	<8d961d900902240510s46f945f9ofb08a003395a139d@mail.gmail.com>
Message-ID: <d559d8430903040325r4bfe2297p32c60cfa5ab9370c@mail.gmail.com>

2009/2/24 aslak hellesoy <aslak.hellesoy at gmail.com>

> On Tue, Feb 24, 2009 at 10:30 AM, Rob Holland <rob.holland at gmail.com>
> wrote:
> > On Tue, Feb 24, 2009 at 9:17 AM, Matt Wynne <matt at mattwynne.net> wrote:
> >
> >> You can even use git commit --amend to commit on red (e.g at the end of
> the
> >> day) and then change that commit later.
> >
> > While I think commit --amend is very useful, I'm not sure why you'd
> > bother to commit at the end of the day, knowing full well you were
> > going to amend it first thing tomorrow morning.
> >
>
> Because the longer you wait, the more your code will diverge from your
> teammates'. If you don't commit often you rob them of the opportunity
> to reduce merge hell.


This is the money line for me.

There's a lovely CI pattern I've seen in the centralised SCM world (with
Java, but that's less important) that I'm surprised hasn't been mentioned.
Before I describe it I'd like to take this back to first principles.

The point of *continuous* integration is to keep each individual integration
small and avoid less frequent *big* integrations, because that's where the
pain happens. Syncing up once per story or feature, which could easily be
several days work, strikes me as a retrograde step. The fact that DSCMs like
git or hg allow you to do this doesn't make it a good thing. There are many
fantastic reasons to use DSCM - modelling IBM Rational ClearCase "best
practice" usage patterns shouldn't be one of them.

Anyhoo, it seems to me the problem we are discussing is the coupling between
checking in an unfinished scenario and failing the build. The solution I've
seen - scaling to projects with tens of developers and thousands of
scenarios - is to separate in-progress features from finished ones, and
build everything.

If an in-progress scenario fails then the build carries on. If a completed
scenario fails it causes the build to fail. There is a nice corollary to
this whereby you fail the build if an in-progress scenario accidentally *
passes*. This is because you usually want a human to find out why. In
cuke-land you would do this at a feature level rather than a scenario level
since the convention is to have one feature (with multiple scenarios) per
file.

Marking a feature as done can be as simple as moving it between two
directories (called in-progress and done), renaming the feature (from
openid_login.in-progress to openid_login.feature) or having an
:in_progresstag on a feature until it's done.

In Java-land I prefer the first model because I can point the same junit
task at either the in-progress or done directories and just change the
failOnError flag.

In any case, I would strongly encourage changing the build so you can
integrate continuously - i.e. git push as frequently as you normally would -
knowing the build will remain clean as long as you mark your unfinished work
as in-progress. Lightweight, cheap branches are great for local spikes,
exploration of unfamiliar code and any number of other incidental
activities, but I'm deeply sceptical that they should form part of your core
workflow.

No doubt once this becomes the norm and Rational are laughing up their
sleeves I'll live to regret saying that :)


Aslak


Cheers,
Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090304/f7cb6a43/attachment-0001.html>

From dchelimsky at gmail.com  Wed Mar  4 08:02:56 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 4 Mar 2009 07:02:56 -0600
Subject: [rspec-users] Writing specs for AMQP clients.
In-Reply-To: <d391a7990903040254x3690f6f0o6aa38deb1fe260ff@mail.gmail.com>
References: <d391a7990903040254x3690f6f0o6aa38deb1fe260ff@mail.gmail.com>
Message-ID: <57c63afe0903040502u66f98051y55d7cfa8f9169c58@mail.gmail.com>

On Wed, Mar 4, 2009 at 4:54 AM, Bira <u.alberton at gmail.com> wrote:
> Hello!
>
> I've been lurking in the list a while, and now I would like to ask you
> a somewhat "noobish" question... This is the first time I've run
> across this particular problem, so I'm not sure what to do. I'm sure
> this is so common that's in a textbook somewhere, but what is the best
> way to write specs for code that calls out to an external server?
>
> I've just started working on a project that will use AMQP messaging
> (and the "amqp" gem), and most of the code I've written so far is all
> about talking to a messaging server. The only alternatives I saw for
> writing specs were starting said server, and mocking/stubbing out all
> the code that would talk to it. I went witht he second one, but I feel
> it's a fragile approach that won't actually allow me to find bugs,
> since everything is mocked out. What is the best way to do this?

I'm not familiar w/ amqp in particular, but one "good" approach is to
use mock objects to evolve a protocol for this service in the language
of your app, and then write an adapter for amqp with a few system
level tests in place to verify happy paths.

This approach does a few good things.

* Keeps you focused on the business domain while writing the business
objects, because you're not sidetracked by the details of messaging.
* Keeps the suite of specs running fast
* Makes it easy to choose a different messaging API later, because all
of the code that depends directly on that API lives in the adapter.

HTH,
David



>
> --
> Bira
> http://compexplicita.wordpress.com
> http://compexplicita.tumblr.com
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Wed Mar  4 08:08:51 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 4 Mar 2009 07:08:51 -0600
Subject: [rspec-users] Testing my scripts?
In-Reply-To: <5e257dbc314d72c9770f6aea3e14170d@ruby-forum.com>
References: <5e257dbc314d72c9770f6aea3e14170d@ruby-forum.com>
Message-ID: <57c63afe0903040508v111afd16g8762f8415316d835@mail.gmail.com>

On Tue, Mar 3, 2009 at 11:35 PM, Sebastian W. <lists at ruby-forum.com> wrote:
> Hello RSpec mailing list,
> I have a question which I'm sure someone here has a "duh!" answer to. :P
>
> A lot of the Ruby programming I do is around installing servers and
> automating various tasks. The pattern I use goes as follows, I'm sure
> you'll see where the gap is.
>
> Write a failing test. Write enough Ruby code to make it pass. Continue
> until I have a class (or set of classes) that solve my problem. So far,
> so good.
>
> I then need to put this code into a script so I can run it as part of
> everyday automation. My approach so far has been to take green-light
> code and plug it into the script so that when the script gets run, it
> takes the arguments to the scripts and passes it to my tested code. The
> script runs and does what its supposed to do; all is well.
>
> Now -- there's a bug in my code somewhere, or I need to add something to
> the code I've written to improve it. No problem initially. First, run
> all tests. Green light, good. Write a failing test. Write enough Ruby
> code to make it pass. Happy, happy.
>
> Problem: the code in my script is not fixed! Running my spec suite does
> not catch the fact that there's client code in my script using bad code.
>
> So, my question is: how can I make sure that when I run my spec suite
> that all the code in my scripts gets tested as well? I thought about
> adding ?"--test" option to all my scripts, but that seems, well...just
> not the right way to do it.
>
> Anyone have any words of wisdom they'd like to share? Have I walked into
> an antipattern here?

BDD means (among other things) driving development from the
outside-in. It sounds like you're working in the opposite direction
here.

The approach we'd take with RSpec and Cucumber, would be to write
Cucumber features with scenarios that drive the scripts, and then work
your way down to RSpec code examples that drive the smaller bits.

In case this is new to you, the Cucumber scenarios will fail until you
get all of the RSpec code examples to pass. If you get to the point
where all of the scenarios are passing, but you feel like you want to
drive out more code in the underlying objects, take a step back and
think of a new failing scenario you can add to the Cucumber features
first.

This approach should help you refine the work you're doing on the
objects, as well as build confidence that deploying the scripts will
work.

HTH,
David

>
> Thanks much!
> Sebastian
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From patnakajima at gmail.com  Wed Mar  4 08:47:21 2009
From: patnakajima at gmail.com (Pat Nakajima)
Date: Wed, 4 Mar 2009 08:47:21 -0500
Subject: [rspec-users] Sinitra 0.9.1 Webrat 0.4.2 Cuc problem
In-Reply-To: <6ea3a1b80903040143v47d4f4fco562baff873b728b4@mail.gmail.com>
References: <88fd8ddc0903032039t4dad780ay628ca56bc57953c4@mail.gmail.com>
	<97ae2db00903032154i1b27180cp544563f1eff4c3@mail.gmail.com>
	<6ea3a1b80903040143v47d4f4fco562baff873b728b4@mail.gmail.com>
Message-ID: <7A967D15-A777-4314-A5F2-46BC3331F1E8@gmail.com>

Rob,

Is your Sinatra app using the "classic" style? If so, I think it would  
work without need for modification. If your app is a class that  
inherits from Sinatra::Base, you're likely to see issues unless you  
take the steps in the Gist.

Pat

On Mar 4, 2009, at 4:43 AM, Rob Holland <rob.holland at gmail.com> wrote:

> My application (the one on which the wiki example is based) still runs
> just fine on 0.9.1, so I don't think it's related to the version
> change.
>
> I think the hacks Pat used are solely to do with getting selenium  
> mode happy.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

From apremdas at gmail.com  Wed Mar  4 09:22:51 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Wed, 4 Mar 2009 14:22:51 +0000
Subject: [rspec-users] Sinitra 0.9.1 Webrat 0.4.2 Cuc problem
In-Reply-To: <6ea3a1b80903040143v47d4f4fco562baff873b728b4@mail.gmail.com>
References: <88fd8ddc0903032039t4dad780ay628ca56bc57953c4@mail.gmail.com>
	<97ae2db00903032154i1b27180cp544563f1eff4c3@mail.gmail.com>
	<6ea3a1b80903040143v47d4f4fco562baff873b728b4@mail.gmail.com>
Message-ID: <88fd8ddc0903040622g6f68c4deu7400cdbabdd7989c@mail.gmail.com>

The app runs fine, its the cucumber tests that don't. If you can point me to
your app I'll give it go here.

I'm using classic style (just started with Sinatra)

2009/3/4 Rob Holland <rob.holland at gmail.com>

> My application (the one on which the wiki example is based) still runs
> just fine on 0.9.1, so I don't think it's related to the version
> change.
>
> I think the hacks Pat used are solely to do with getting selenium mode
> happy.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090304/8ac13db2/attachment.html>

From apremdas at gmail.com  Wed Mar  4 09:25:07 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Wed, 4 Mar 2009 14:25:07 +0000
Subject: [rspec-users] Sinitra and Cucumber
In-Reply-To: <6ea3a1b80903040133y127b1688j96a477325dd73e4c@mail.gmail.com>
References: <88fd8ddc0902152239v1c96d9a0o4c3b607f9dbaf529@mail.gmail.com>
	<620c6d021a378669605b46bce1c93dd6@ruby-forum.com>
	<8d961d900902260450i344cddbey8d0381b104ba1731@mail.gmail.com>
	<ccbf3a87ef9bcf83fb5e82a54ed64b26@ruby-forum.com>
	<FB7BBF64-6E3E-41E1-AF7E-A9AB604EF5C7@gmail.com>
	<88fd8ddc0903032030n54779266k14492d81399efa27@mail.gmail.com>
	<6ea3a1b80903040133y127b1688j96a477325dd73e4c@mail.gmail.com>
Message-ID: <88fd8ddc0903040625n41563f44m485edd744edcc035@mail.gmail.com>

Thanks alot - works a treat :)

2009/3/4 Rob Holland <rob.holland at gmail.com>

> On Wed, Mar 4, 2009 at 4:30 AM, Andrew Premdas <apremdas at gmail.com> wrote:
> > With Cuc and Rails I'd be able to debug step definitions by putting
> > 'debugger' in the relevant step definition. With Sinatra configured as
> above
> > this doesn't work. Any tips on making this work and/or explaining whats
> > different/
>
> Just use: require 'ruby-debug/debugger' where you'd normally use debugger.
>
> The difference is sinatra doesn't load ruby-debug itself.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090304/5f42fbb9/attachment.html>

From apremdas at gmail.com  Wed Mar  4 09:39:10 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Wed, 4 Mar 2009 14:39:10 +0000
Subject: [rspec-users] Sinitra 0.9.1 Webrat 0.4.2 Cuc problem
In-Reply-To: <88fd8ddc0903040622g6f68c4deu7400cdbabdd7989c@mail.gmail.com>
References: <88fd8ddc0903032039t4dad780ay628ca56bc57953c4@mail.gmail.com>
	<97ae2db00903032154i1b27180cp544563f1eff4c3@mail.gmail.com>
	<6ea3a1b80903040143v47d4f4fco562baff873b728b4@mail.gmail.com>
	<88fd8ddc0903040622g6f68c4deu7400cdbabdd7989c@mail.gmail.com>
Message-ID: <88fd8ddc0903040639p6ce8e218h687f7b185a904543@mail.gmail.com>

Apologies - false alarm - problem was with my step-definition

all best

Andrew


2009/3/4 Andrew Premdas <apremdas at gmail.com>

> The app runs fine, its the cucumber tests that don't. If you can point me
> to your app I'll give it go here.
>
> I'm using classic style (just started with Sinatra)
>
> 2009/3/4 Rob Holland <rob.holland at gmail.com>
>
> My application (the one on which the wiki example is based) still runs
>> just fine on 0.9.1, so I don't think it's related to the version
>> change.
>>
>> I think the hacks Pat used are solely to do with getting selenium mode
>> happy.
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090304/02406ad0/attachment.html>

From ben at benmabey.com  Wed Mar  4 11:27:20 2009
From: ben at benmabey.com (Ben Mabey)
Date: Wed, 04 Mar 2009 09:27:20 -0700
Subject: [rspec-users] Writing specs for AMQP clients.
In-Reply-To: <57c63afe0903040502u66f98051y55d7cfa8f9169c58@mail.gmail.com>
References: <d391a7990903040254x3690f6f0o6aa38deb1fe260ff@mail.gmail.com>
	<57c63afe0903040502u66f98051y55d7cfa8f9169c58@mail.gmail.com>
Message-ID: <49AEABE8.8090602@benmabey.com>

David Chelimsky wrote:
> On Wed, Mar 4, 2009 at 4:54 AM, Bira <u.alberton at gmail.com> wrote:
>   
>> Hello!
>>
>> I've been lurking in the list a while, and now I would like to ask you
>> a somewhat "noobish" question... This is the first time I've run
>> across this particular problem, so I'm not sure what to do. I'm sure
>> this is so common that's in a textbook somewhere, but what is the best
>> way to write specs for code that calls out to an external server?
>>
>> I've just started working on a project that will use AMQP messaging
>> (and the "amqp" gem), and most of the code I've written so far is all
>> about talking to a messaging server. The only alternatives I saw for
>> writing specs were starting said server, and mocking/stubbing out all
>> the code that would talk to it. I went witht he second one, but I feel
>> it's a fragile approach that won't actually allow me to find bugs,
>> since everything is mocked out. What is the best way to do this?
>>     
>
> I'm not familiar w/ amqp in particular, but one "good" approach is to
> use mock objects to evolve a protocol for this service in the language
> of your app, and then write an adapter for amqp with a few system
> level tests in place to verify happy paths.
>
> This approach does a few good things.
>
> * Keeps you focused on the business domain while writing the business
> objects, because you're not sidetracked by the details of messaging.
> * Keeps the suite of specs running fast
> * Makes it easy to choose a different messaging API later, because all
> of the code that depends directly on that API lives in the adapter.
>
> HTH,
> David
>
>
>   

Bria,
In the past, I have done exactly as David has suggested.  I have my 
cucumber features use the actual messaging system to verify that 
everything is hooked up and is working correctly.  I then use a 
combination of null and fake adapters in my specs to keep them fast and 
focused on testing the object's responsibility.  Doing this required 
that an adapter layer be introduced.  The nice thing about this, as 
David also points out, is that you can then easily swap out another 
messaging system by simply writing a new adapter.

I have actually open soured my efforts (and my coworker's, Chris 
Wyckoff) so you can use, or at least get ideas from, the library here:

https://github.com/bmabey/rosetta_queue/tree

You can use currently use the library with messaging systems that speak 
AMQP or stomp.

Additionally, I have blogged about how we used Cucumber and this library 
to integrate our distributed systems:

http://www.benmabey.com/2009/02/17/using-cucumber-to-integrate-distributed-systems-and-test-messaging/

HTH,
Ben



From nick at ekenosen.net  Wed Mar  4 12:04:54 2009
From: nick at ekenosen.net (nicholas a. evans)
Date: Wed, 4 Mar 2009 12:04:54 -0500
Subject: [rspec-users] [cucumber] Cucumber and CI
In-Reply-To: <d559d8430903040325r4bfe2297p32c60cfa5ab9370c@mail.gmail.com>
References: <ee6f48c00902221147h2327b886ye2df76bb985d93be@mail.gmail.com>
	<8d961d900902221336x7822dc36p43ea7c29bca44430@mail.gmail.com>
	<ee6f48c00902221609o49ed4e09pa4dff9a7b4e81ad3@mail.gmail.com>
	<824F1590-C31C-44D9-B283-C7C0550F0D84@mattwynne.net>
	<6ea3a1b80902240130u3d8bcb8dyf46a2945165a776c@mail.gmail.com>
	<8d961d900902240510s46f945f9ofb08a003395a139d@mail.gmail.com>
	<d559d8430903040325r4bfe2297p32c60cfa5ab9370c@mail.gmail.com>
Message-ID: <276ff9870903040904v71f15635rb3f07c1c2508d871@mail.gmail.com>

On Wed, Mar 4, 2009 at 6:25 AM, Dan North <tastapod at gmail.com> wrote:
> Marking a feature as done can be as simple as moving it between two
> directories (called in-progress and done), renaming the feature (from
> openid_login.in-progress to openid_login.feature) or having an :in_progress
> tag on a feature until it's done.

I started out with using an in-process directory, but now I prefer to
use a pending step:

Given ...
And ...
And the rest of this scenario is pending: see ticket number #1234, in
progress (2009.03.04)
When I ...
And ...
Then ...

That way, the build won't break even if some of the steps have already
been implemented (e.g. for other scenarios), and I can organize my
scenarios according to their final destination (dir and feature file),
without needing to worry as much about current status.  But I do need
to make sure I insert the appropriate "pending" steps prior to "svn
commit" / "bzr push",

-- 
Nick

From matt at mattwynne.net  Wed Mar  4 12:09:39 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Wed, 4 Mar 2009 17:09:39 +0000
Subject: [rspec-users] [cucumber] Cucumber and CI
In-Reply-To: <d559d8430903040325r4bfe2297p32c60cfa5ab9370c@mail.gmail.com>
References: <ee6f48c00902221147h2327b886ye2df76bb985d93be@mail.gmail.com>
	<8d961d900902221336x7822dc36p43ea7c29bca44430@mail.gmail.com>
	<ee6f48c00902221609o49ed4e09pa4dff9a7b4e81ad3@mail.gmail.com>
	<824F1590-C31C-44D9-B283-C7C0550F0D84@mattwynne.net>
	<6ea3a1b80902240130u3d8bcb8dyf46a2945165a776c@mail.gmail.com>
	<8d961d900902240510s46f945f9ofb08a003395a139d@mail.gmail.com>
	<d559d8430903040325r4bfe2297p32c60cfa5ab9370c@mail.gmail.com>
Message-ID: <E3E1B95E-A42F-40EF-887E-85AD63BE2502@mattwynne.net>


On 4 Mar 2009, at 11:25, Dan North wrote:

> 2009/2/24 aslak hellesoy <aslak.hellesoy at gmail.com>
> On Tue, Feb 24, 2009 at 10:30 AM, Rob Holland  
> <rob.holland at gmail.com> wrote:
> > On Tue, Feb 24, 2009 at 9:17 AM, Matt Wynne <matt at mattwynne.net>  
> wrote:
> >
> >> You can even use git commit --amend to commit on red (e.g at the  
> end of the
> >> day) and then change that commit later.
> >
> > While I think commit --amend is very useful, I'm not sure why you'd
> > bother to commit at the end of the day, knowing full well you were
> > going to amend it first thing tomorrow morning.
> >
>
> Because the longer you wait, the more your code will diverge from your
> teammates'. If you don't commit often you rob them of the opportunity
> to reduce merge hell.
>
> This is the money line for me.
>
> There's a lovely CI pattern I've seen in the centralised SCM world  
> (with Java, but that's less important) that I'm surprised hasn't  
> been mentioned. Before I describe it I'd like to take this back to  
> first principles.
>
> The point of continuous integration is to keep each individual  
> integration small and avoid less frequent big integrations, because  
> that's where the pain happens. Syncing up once per story or feature,  
> which could easily be several days work, strikes me as a retrograde  
> step. The fact that DSCMs like git or hg allow you to do this  
> doesn't make it a good thing. There are many fantastic reasons to  
> use DSCM - modelling IBM Rational ClearCase "best practice" usage  
> patterns shouldn't be one of them.
>
> Anyhoo, it seems to me the problem we are discussing is the coupling  
> between checking in an unfinished scenario and failing the build.  
> The solution I've seen - scaling to projects with tens of developers  
> and thousands of scenarios - is to separate in-progress features  
> from finished ones, and build everything.
>
> If an in-progress scenario fails then the build carries on. If a  
> completed scenario fails it causes the build to fail. There is a  
> nice corollary to this whereby you fail the build if an in-progress  
> scenario accidentally passes. This is because you usually want a  
> human to find out why. In cuke-land you would do this at a feature  
> level rather than a scenario level since the convention is to have  
> one feature (with multiple scenarios) per file.
>
> Marking a feature as done can be as simple as moving it between two  
> directories (called in-progress and done), renaming the feature  
> (from openid_login.in-progress to openid_login.feature) or having  
> an :in_progress tag on a feature until it's done.
>
> In Java-land I prefer the first model because I can point the same  
> junit task at either the in-progress or done directories and just  
> change the failOnError flag.

Thanks for your thoughts, Dan. Cucumber 0.2 tags are ideal for this  
sort of filtering. I'm going to look at adding a 'two tier' feature  
run to our build.


Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From lists at ruby-forum.com  Wed Mar  4 12:16:29 2009
From: lists at ruby-forum.com (James Byrne)
Date: Wed, 4 Mar 2009 18:16:29 +0100
Subject: [rspec-users] OT: AR Default Values
Message-ID: <6ec7f496f43a7c6085465ef3c738d329@ruby-forum.com>

This is sort of off topic but it arose from a cucumber test failure and
I am unsure how to address the underlying issue.

I spent yesterday tracking down an obscure error that was exposed by a
new cucumber test.  It turned out to be an improper default value
assignment made in a controller which in turn proved dependent upon
recent changes (Rails 2.2) made in how AR handles timezones.  It also
turned out that the same error was made in another controller handling
that same model.

This led me to consider that the place to handle AR default values
really should be somewhere else and the logical places are either in the
model or in the DBMS schema.  The problem with the latter is that Rails
migrations provide no accommodation for dynamic defaults like the
current time, other than by recourse to explicit SQL.  In any case, a
DBMS provided default value is not going to be available to a view until
after the new row is INSERTed and subsequently SELECTEed, which is too
late to be of any use in the presentation of a "new"/"create" resource
pair.

Thus, I considered it best to handle this requirement in the model.
There is a vast amount of information on this subject but it appears, to
me, inconsistent and the issue unresolved.  The obvious answer is to
override the initializer method.  However, there are several warnings
that basically say that for AR this is NOT A GOOD IDEA!  There are a few
references that indicate AR may not actually call #new in every case.
There is also the matter of interpretation of what new actually means to
an ORM.  A new model instance is not always the same thing as a new DBMS
"row".

There are references to using the :after_initialize callback.  However,
after_initialize is called on every row instantiation whereas a default
value only applies on a new DBMS instance.  This is an old topic for the
rails core team:

 http://groups.google.com/group/rubyonrails-core/browse_thread/thread/b509a2fe2b62ac5

So, after confusing myself thoroughly, I have to ask: How do people here
handle dynamic default values?  Do leave these instructions in the
controllers or is there an accepted technique for moving this code into
the model?  If there is then what is it? I ran across this in my
research:

http://m.onkey.org/2007/7/24/how-to-set-default-values-in-your-model

But this is not what one would describe as self documenting code.
-- 
Posted via http://www.ruby-forum.com/.

From hayafirst at gmail.com  Wed Mar  4 12:31:28 2009
From: hayafirst at gmail.com (Yi)
Date: Wed, 4 Mar 2009 11:31:28 -0600
Subject: [rspec-users] [cucumber] Cucumber and CI
In-Reply-To: <d559d8430903040325r4bfe2297p32c60cfa5ab9370c@mail.gmail.com>
References: <ee6f48c00902221147h2327b886ye2df76bb985d93be@mail.gmail.com>
	<8d961d900902221336x7822dc36p43ea7c29bca44430@mail.gmail.com>
	<ee6f48c00902221609o49ed4e09pa4dff9a7b4e81ad3@mail.gmail.com>
	<824F1590-C31C-44D9-B283-C7C0550F0D84@mattwynne.net>
	<6ea3a1b80902240130u3d8bcb8dyf46a2945165a776c@mail.gmail.com>
	<8d961d900902240510s46f945f9ofb08a003395a139d@mail.gmail.com>
	<d559d8430903040325r4bfe2297p32c60cfa5ab9370c@mail.gmail.com>
Message-ID: <ee6f48c00903040931y3ad5b366xccd3c133eea2ccac@mail.gmail.com>

Great writing. Thanks

On Wed, Mar 4, 2009 at 5:25 AM, Dan North <tastapod at gmail.com> wrote:

> 2009/2/24 aslak hellesoy <aslak.hellesoy at gmail.com>
>
>> On Tue, Feb 24, 2009 at 10:30 AM, Rob Holland <rob.holland at gmail.com>
>> wrote:
>> > On Tue, Feb 24, 2009 at 9:17 AM, Matt Wynne <matt at mattwynne.net> wrote:
>> >
>> >> You can even use git commit --amend to commit on red (e.g at the end of
>> the
>> >> day) and then change that commit later.
>> >
>> > While I think commit --amend is very useful, I'm not sure why you'd
>> > bother to commit at the end of the day, knowing full well you were
>> > going to amend it first thing tomorrow morning.
>> >
>>
>> Because the longer you wait, the more your code will diverge from your
>> teammates'. If you don't commit often you rob them of the opportunity
>> to reduce merge hell.
>
>
> This is the money line for me.
>
> There's a lovely CI pattern I've seen in the centralised SCM world (with
> Java, but that's less important) that I'm surprised hasn't been mentioned.
> Before I describe it I'd like to take this back to first principles.
>
> The point of *continuous* integration is to keep each individual
> integration small and avoid less frequent *big* integrations, because
> that's where the pain happens. Syncing up once per story or feature, which
> could easily be several days work, strikes me as a retrograde step. The fact
> that DSCMs like git or hg allow you to do this doesn't make it a good thing.
> There are many fantastic reasons to use DSCM - modelling IBM Rational
> ClearCase "best practice" usage patterns shouldn't be one of them.
>
> Anyhoo, it seems to me the problem we are discussing is the coupling
> between checking in an unfinished scenario and failing the build. The
> solution I've seen - scaling to projects with tens of developers and
> thousands of scenarios - is to separate in-progress features from finished
> ones, and build everything.
>
> If an in-progress scenario fails then the build carries on. If a completed
> scenario fails it causes the build to fail. There is a nice corollary to
> this whereby you fail the build if an in-progress scenario accidentally *
> passes*. This is because you usually want a human to find out why. In
> cuke-land you would do this at a feature level rather than a scenario level
> since the convention is to have one feature (with multiple scenarios) per
> file.
>
> Marking a feature as done can be as simple as moving it between two
> directories (called in-progress and done), renaming the feature (from
> openid_login.in-progress to openid_login.feature) or having an
> :in_progress tag on a feature until it's done.
>
> In Java-land I prefer the first model because I can point the same junit
> task at either the in-progress or done directories and just change the
> failOnError flag.
>
> In any case, I would strongly encourage changing the build so you can
> integrate continuously - i.e. git push as frequently as you normally would -
> knowing the build will remain clean as long as you mark your unfinished work
> as in-progress. Lightweight, cheap branches are great for local spikes,
> exploration of unfamiliar code and any number of other incidental
> activities, but I'm deeply sceptical that they should form part of your core
> workflow.
>
> No doubt once this becomes the norm and Rational are laughing up their
> sleeves I'll live to regret saying that :)
>
>
> Aslak
>
>
> Cheers,
> Dan
>
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090304/6f759721/attachment.html>

From u.alberton at gmail.com  Wed Mar  4 12:37:16 2009
From: u.alberton at gmail.com (Bira)
Date: Wed, 4 Mar 2009 14:37:16 -0300
Subject: [rspec-users] Writing specs for AMQP clients.
In-Reply-To: <49AEABE8.8090602@benmabey.com>
References: <d391a7990903040254x3690f6f0o6aa38deb1fe260ff@mail.gmail.com>
	<57c63afe0903040502u66f98051y55d7cfa8f9169c58@mail.gmail.com>
	<49AEABE8.8090602@benmabey.com>
Message-ID: <d391a7990903040937sa31069em9886f8e3a6ad692d@mail.gmail.com>

David and Ben,

Thank you very much for your advice :).

-- 
Bira
http://compexplicita.wordpress.com
http://compexplicita.tumblr.com

From lists at ruby-forum.com  Wed Mar  4 12:46:23 2009
From: lists at ruby-forum.com (Sebastian W.)
Date: Wed, 4 Mar 2009 18:46:23 +0100
Subject: [rspec-users] Testing my scripts?
In-Reply-To: <57c63afe0903040508v111afd16g8762f8415316d835@mail.gmail.com>
References: <5e257dbc314d72c9770f6aea3e14170d@ruby-forum.com>
	<57c63afe0903040508v111afd16g8762f8415316d835@mail.gmail.com>
Message-ID: <09fb36729014dc7fb191fb6e4b39b449@ruby-forum.com>

Hi David,
I think I see what you're saying, but I admit I'm still a bit confused. 
Maybe I'm missing something here, but I can't think of how I would drive 
the scripts (even through Cucumber) without actually invoking them, thus 
kicking off processes that I don't want.

Real code to illustrate my thought process:

#test.rb
class Test
  def test
    true
  end
end

#test_spec.rb
describe Test
  it "should test"
    Test.new.test.should be(true)
  end
end

#my_script_using_test.rb
require 'test'

Test.new.test


Even if I invoke my "script" through Cucumber, it's still going to fire, 
no? I think perhaps I am just missing the point altogether. :)

Thank you,
Sebastian
-- 
Posted via http://www.ruby-forum.com/.

From scott at railsnewbie.com  Wed Mar  4 14:13:41 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Wed, 4 Mar 2009 14:13:41 -0500
Subject: [rspec-users] OT: AR Default Values
In-Reply-To: <6ec7f496f43a7c6085465ef3c738d329@ruby-forum.com>
References: <6ec7f496f43a7c6085465ef3c738d329@ruby-forum.com>
Message-ID: <32093C1D-CCFE-4F2B-B6D3-0869069FCFFD@railsnewbie.com>


On Mar 4, 2009, at 12:16 PM, James Byrne wrote:

> This is sort of off topic but it arose from a cucumber test failure  
> and
> I am unsure how to address the underlying issue.
>
> I spent yesterday tracking down an obscure error that was exposed by a
> new cucumber test.  It turned out to be an improper default value
> assignment made in a controller which in turn proved dependent upon
> recent changes (Rails 2.2) made in how AR handles timezones.  It also
> turned out that the same error was made in another controller handling
> that same model.
>
> This led me to consider that the place to handle AR default values
> really should be somewhere else and the logical places are either in  
> the
> model or in the DBMS schema.  The problem with the latter is that  
> Rails
> migrations provide no accommodation for dynamic defaults like the
> current time, other than by recourse to explicit SQL.  In any case, a
> DBMS provided default value is not going to be available to a view  
> until
> after the new row is INSERTed and subsequently SELECTEed, which is too
> late to be of any use in the presentation of a "new"/"create" resource
> pair.
>
> Thus, I considered it best to handle this requirement in the model.
> There is a vast amount of information on this subject but it  
> appears, to
> me, inconsistent and the issue unresolved.  The obvious answer is to
> override the initializer method.  However, there are several warnings
> that basically say that for AR this is NOT A GOOD IDEA!  There are a  
> few
> references that indicate AR may not actually call #new in every case.
> There is also the matter of interpretation of what new actually  
> means to
> an ORM.  A new model instance is not always the same thing as a new  
> DBMS
> "row".
>
> There are references to using the :after_initialize callback.   
> However,
> after_initialize is called on every row instantiation whereas a  
> default
> value only applies on a new DBMS instance.  This is an old topic for  
> the
> rails core team:
>
> http://groups.google.com/group/rubyonrails-core/browse_thread/thread/b509a2fe2b62ac5
>
> So, after confusing myself thoroughly, I have to ask: How do people  
> here
> handle dynamic default values?  Do leave these instructions in the
> controllers or is there an accepted technique for moving this code  
> into
> the model?  If there is then what is it? I ran across this in my
> research:
>
> http://m.onkey.org/2007/7/24/how-to-set-default-values-in-your-model
>
> But this is not what one would describe as self documenting code.

You could try this plugin:

http://github.com/aussiegeek/active_record_defaults/tree/master

Scott

>
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From lists at ruby-forum.com  Wed Mar  4 14:58:50 2009
From: lists at ruby-forum.com (James Byrne)
Date: Wed, 4 Mar 2009 20:58:50 +0100
Subject: [rspec-users] OT: AR Default Values
In-Reply-To: <32093C1D-CCFE-4F2B-B6D3-0869069FCFFD@railsnewbie.com>
References: <6ec7f496f43a7c6085465ef3c738d329@ruby-forum.com>
	<32093C1D-CCFE-4F2B-B6D3-0869069FCFFD@railsnewbie.com>
Message-ID: <36c7a89533c59fc78edb2fd5f07d43fc@ruby-forum.com>

Scott Taylor wrote:

> You could try this plugin:
> 
> http://github.com/aussiegeek/active_record_defaults/tree/master
> 
> Scott

Thanks, I will try this out.
-- 
Posted via http://www.ruby-forum.com/.

From apsmith at aps.org  Wed Mar  4 14:57:19 2009
From: apsmith at aps.org (Arthur Smith)
Date: Wed, 04 Mar 2009 14:57:19 -0500
Subject: [rspec-users] ArgumentError mystery with jruby/rspec-1.1.11
In-Reply-To: <4DD7A591-4B03-4407-911F-512D5FCB1293@aps.org>
References: <4DD7A591-4B03-4407-911F-512D5FCB1293@aps.org>
Message-ID: <49AEDD1F.6020600@aps.org>

We've seen this behavior again, this time with rspec-1.1.12 and jruby 
1.2.0RC1; the common factors seem to be:

(1) jruby
(2) rspec 1.1.11 or 1.1.12
(3) naming a java class with the string 'context' or 'Context' in its name.

In this case the bit of ruby causing trouble was:

       SecurityContextHolder = 
Java::org.acegisecurity.context.SecurityContextHolder

And running 'jruby script/spec -b ...' gave:

ArgumentError in 'ManuscriptPublishedController check_unauthorized 
should respond with unauthorized for create if user does not have privilege'
ArgumentError
[...]/jruby-1.2.0RC1/lib/ruby/gems/1.8/gems/rspec-1.1.12/lib/spec/example/example_group_factory.rb:54:in 
`create_example_group'
[...]/jruby-1.2.0RC1/lib/ruby/gems/1.8/gems/rspec-1.1.12/lib/spec/dsl/main.rb:25:in 
`describe'
[...]

Replacing the above SecurityContextHolder definition with an import:

         import 'org.acegisecurity.context.SecurityContextHolder'

fixed the errors. Any explanations out there?

       Arthur Smith

Lenny Marks wrote:
> I just got bitten by a strange issue with rspec-1.1.11 and jruby 
> 1.1.3-1.1.6RC1. I'd love to know what the problem was if anyone has 
> any ideas. It's almost as if, rspec didn't like something about this 
> particular class since substituting others worked fine. It does work 
> with Rspec edge so I guess its not too important. Hopefully if anyone 
> else runs into this they'll hit upon this.
>
> -lenny
>
> # reproduce.rb
>
> require './spring.jar'
>
> describe "test with spring" do
>
>    it "should not raise ArgumentError" do
>       
> Java::org.springframework.context.support.ClassPathXmlApplicationContext 
> # line 7
>    end
>
> end
>
> > jruby-1.1.3/bin/jruby -v -S spec -v
> jruby 1.1.3 (ruby 1.8.6 patchlevel 114) (2008-12-08 rev 6586) 
> [x86_64-java]
> rspec 1.1.11
>
>
> >  jruby-1.1.3/bin/jruby -S spec -fs -b reproduce.rb
>
> test with spring
> - should not raise ArgumentError (ERROR - 1)
>
> 1)
> ArgumentError in 'test with spring should not raise ArgumentError'
> ArgumentError
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/extensions/main.rb:23:in 
> `describe'
> /home/jis/compsvc/lenny/tmp/x/./reproduce.rb:7:
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/example_methods.rb:81:in 
> `instance_eval'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/example_methods.rb:81:in 
> `eval_block'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/example_methods.rb:15:in 
> `execute'
> /Users/Shared/eds_test/share/jruby-1.1.3/lib/ruby/1.8/timeout.rb:48:in 
> `timeout'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/example_methods.rb:12:in 
> `execute'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/example_group_methods.rb:245:in 
> `execute_examples'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/example_group_methods.rb:244:in 
> `each'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/example_group_methods.rb:244:in 
> `execute_examples'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/example_group_methods.rb:141:in 
> `run'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/runner/example_group_runner.rb:22:in 
> `run'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/runner/example_group_runner.rb:21:in 
> `each'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/runner/example_group_runner.rb:21:in 
> `run'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/runner/options.rb:115:in 
> `run_examples'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/runner/command_line.rb:10:in 
> `run'
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/bin/spec:4:
> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/bin/spec:19:in `load'
> /Users/Shared/eds_test/share/jruby-1.1.3/bin/spec:19:
>
>
> /jruby-1.1.3/bin/jruby -v rspec/bin/spec  -v
> jruby 1.1.3 (ruby 1.8.6 patchlevel 114) (2008-12-08 rev 6586) 
> [x86_64-java]
> rspec 1.1.11.1
>
> > jruby-1.1.3/bin/jruby rspec/bin/spec -fs reproduce.rb
>
> test with spring
> - should not raise ArgumentError
>
> Finished in 0.329 seconds
>
> 1 example, 0 failures
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
>


From pezlists at gmail.com  Wed Mar  4 23:38:08 2009
From: pezlists at gmail.com (Perryn Fowler)
Date: Thu, 5 Mar 2009 15:38:08 +1100
Subject: [rspec-users] Can I construct the controller myself in a controller
	spec?
Message-ID: <1c319b810903042038g19ee5248m4de5e644fce7e9a1@mail.gmail.com>

Hi

I am experimenting with Constructor based dependency injection for
rails controllers.

So I have something like this

class LoginSessionsController < ApplicationController

  def initialize(authenticator =  TheRealAuthenticator)
    @authenticator = authenticator
  end

 ....
end


The plan was to override the authenticator used when testing with something like

describe LoginSessionsController.new(MyMockAuthenticator) do
   ......
end

but rspec seems to insist on constructing the controller itself

Is there a way to do this I am missing?

From dchelimsky at gmail.com  Thu Mar  5 01:02:39 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 5 Mar 2009 00:02:39 -0600
Subject: [rspec-users] Can I construct the controller myself in a
	controller spec?
In-Reply-To: <1c319b810903042038g19ee5248m4de5e644fce7e9a1@mail.gmail.com>
References: <1c319b810903042038g19ee5248m4de5e644fce7e9a1@mail.gmail.com>
Message-ID: <57c63afe0903042202r4cb79dc1h9697cb67889f216d@mail.gmail.com>

On Wed, Mar 4, 2009 at 10:38 PM, Perryn Fowler <pezlists at gmail.com> wrote:
> Hi
>
> I am experimenting with Constructor based dependency injection for
> rails controllers.
>
> So I have something like this
>
> class LoginSessionsController < ApplicationController
>
> ?def initialize(authenticator = ?TheRealAuthenticator)
> ? ?@authenticator = authenticator
> ?end
>
> ?....
> end
>
>
> The plan was to override the authenticator used when testing with something like
>
> describe LoginSessionsController.new(MyMockAuthenticator) do
> ? ......
> end
>
> but rspec seems to insist on constructing the controller itself

No, Rails insists upon constructing the controller itself. rspec-rails
just wraps rails' testing framework. I'd much rather be constructing
the objects myself.

As for DI, there is a wealth of discussion about DI in Ruby in various
user lists - general consensus is don't do it. I concur. You don't
need it. You might be particularly interested in
http://rubyconf2008.confreaks.com/recovering-from-enterprise.html, in
which Jamis Buck, who authored a DI library for Ruby named needle,
explains why that was unnecessary.

But even if you disagree, you're kinda stuck here because Rails wants
to construct the controllers for us.

HTH,
David

>
> Is there a way to do this I am missing?
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From pat.maddox at gmail.com  Thu Mar  5 01:47:00 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Wed, 4 Mar 2009 22:47:00 -0800
Subject: [rspec-users] Can I construct the controller myself in a
	controller spec?
In-Reply-To: <1c319b810903042038g19ee5248m4de5e644fce7e9a1@mail.gmail.com>
References: <1c319b810903042038g19ee5248m4de5e644fce7e9a1@mail.gmail.com>
Message-ID: <2c7e61990903042247j5bf67c2cra53c2b1f6529adcb@mail.gmail.com>

On Wed, Mar 4, 2009 at 8:38 PM, Perryn Fowler <pezlists at gmail.com> wrote:
> Hi
>
> I am experimenting with Constructor based dependency injection for
> rails controllers.
>
> So I have something like this
>
> class LoginSessionsController < ApplicationController
>
> ?def initialize(authenticator = ?TheRealAuthenticator)
> ? ?@authenticator = authenticator
> ?end
>
> ?....
> end
>
>
> The plan was to override the authenticator used when testing with something like
>
> describe LoginSessionsController.new(MyMockAuthenticator) do
> ? ......
> end
>
> but rspec seems to insist on constructing the controller itself
>
> Is there a way to do this I am missing?
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

It'd be badass, but, basically, no.  Instantiating a controller in
Rails takes a lot of work - request/response objects, routes, and the
code that does so is a big mess.

You could use factory methods, and then stub that method in your examples:

class LoginSessionsController < ApplicationController
  def authenticator
    TheRealAuthenticator
  end
end

describe LoginSessionsController do
  before(:each) do
    controller.stub!(:authenticator).and_return MockAuthenticator
  end
end

Pat

From matt at mattwynne.net  Thu Mar  5 04:31:42 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Thu, 5 Mar 2009 09:31:42 +0000
Subject: [rspec-users] Can I construct the controller myself in a
	controller spec?
In-Reply-To: <57c63afe0903042202r4cb79dc1h9697cb67889f216d@mail.gmail.com>
References: <1c319b810903042038g19ee5248m4de5e644fce7e9a1@mail.gmail.com>
	<57c63afe0903042202r4cb79dc1h9697cb67889f216d@mail.gmail.com>
Message-ID: <011E39CE-1EF6-4E7E-A215-0995FC1A28A8@mattwynne.net>


On 5 Mar 2009, at 06:02, David Chelimsky wrote:

> On Wed, Mar 4, 2009 at 10:38 PM, Perryn Fowler <pezlists at gmail.com>  
> wrote:
>> Hi
>>
>> I am experimenting with Constructor based dependency injection for
>> rails controllers.
>>
>> So I have something like this
>>
>> class LoginSessionsController < ApplicationController
>>
>>  def initialize(authenticator =  TheRealAuthenticator)
>>    @authenticator = authenticator
>>  end
>>
>>  ....
>> end
>>
>>
>> The plan was to override the authenticator used when testing with  
>> something like
>>
>> describe LoginSessionsController.new(MyMockAuthenticator) do
>>   ......
>> end
>>
>> but rspec seems to insist on constructing the controller itself
>
> No, Rails insists upon constructing the controller itself. rspec-rails
> just wraps rails' testing framework. I'd much rather be constructing
> the objects myself.
>
> As for DI, there is a wealth of discussion about DI in Ruby in various
> user lists - general consensus is don't do it. I concur. You don't
> need it. You might be particularly interested in
> http://rubyconf2008.confreaks.com/recovering-from-enterprise.html, in
> which Jamis Buck, who authored a DI library for Ruby named needle,
> explains why that was unnecessary.

That sounds a little bit like throwing the baby out with the bathwater  
though - you still need to be able to do some kind of DI if you're  
doing TDD, so that you can swap in a fake dependency, no? DI doesn't  
have to mean you use some fancy framework.

As Pat said, this is hard when the object you want to test (in this  
case, a Rails ActionController) is so damn awkward to instantiate in a  
test.

One approach would be to change the references to @authenticator in  
your controller to call a local #authenticator method, then override  
this with a TestController subclass and use that subclass instead in  
your test.

David, how would you suggest the OP injects his MockAuthenticator?  
stub out Authenticator.new? I guess that's what I mostly do.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From lists at ruby-forum.com  Thu Mar  5 09:21:11 2009
From: lists at ruby-forum.com (John Small)
Date: Thu, 5 Mar 2009 15:21:11 +0100
Subject: [rspec-users] where does cucumber.yml live?
Message-ID: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>

Where do I put cucumber.yml? I can't find anything mentioned in the
documentation.

Thanks

John Small
-- 
Posted via http://www.ruby-forum.com/.

From dchelimsky at gmail.com  Thu Mar  5 09:26:01 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 5 Mar 2009 08:26:01 -0600
Subject: [rspec-users] Can I construct the controller myself in a
	controller spec?
In-Reply-To: <011E39CE-1EF6-4E7E-A215-0995FC1A28A8@mattwynne.net>
References: <1c319b810903042038g19ee5248m4de5e644fce7e9a1@mail.gmail.com>
	<57c63afe0903042202r4cb79dc1h9697cb67889f216d@mail.gmail.com>
	<011E39CE-1EF6-4E7E-A215-0995FC1A28A8@mattwynne.net>
Message-ID: <57c63afe0903050626w1e9c4401k5d004729b7092fec@mail.gmail.com>

On Thu, Mar 5, 2009 at 3:31 AM, Matt Wynne <matt at mattwynne.net> wrote:
>
> On 5 Mar 2009, at 06:02, David Chelimsky wrote:
>
>> On Wed, Mar 4, 2009 at 10:38 PM, Perryn Fowler <pezlists at gmail.com> wrote:
>>>
>>> Hi
>>>
>>> I am experimenting with Constructor based dependency injection for
>>> rails controllers.
>>>
>>> So I have something like this
>>>
>>> class LoginSessionsController < ApplicationController
>>>
>>> ?def initialize(authenticator = ?TheRealAuthenticator)
>>> ? @authenticator = authenticator
>>> ?end
>>>
>>> ?....
>>> end
>>>
>>>
>>> The plan was to override the authenticator used when testing with
>>> something like
>>>
>>> describe LoginSessionsController.new(MyMockAuthenticator) do
>>> ?......
>>> end
>>>
>>> but rspec seems to insist on constructing the controller itself
>>
>> No, Rails insists upon constructing the controller itself. rspec-rails
>> just wraps rails' testing framework. I'd much rather be constructing
>> the objects myself.
>>
>> As for DI, there is a wealth of discussion about DI in Ruby in various
>> user lists - general consensus is don't do it. I concur. You don't
>> need it. You might be particularly interested in
>> http://rubyconf2008.confreaks.com/recovering-from-enterprise.html, in
>> which Jamis Buck, who authored a DI library for Ruby named needle,
>> explains why that was unnecessary.
>
> That sounds a little bit like throwing the baby out with the bathwater
> though - you still need to be able to do some kind of DI if you're doing
> TDD, so that you can swap in a fake dependency, no? DI doesn't have to mean
> you use some fancy framework.

Agreed. I think I reacted to the term DI, about which J.B. Rainsberger
once commented "Oh, you mean parameters." I totally agree that we need
strategies for introducing doubles.

>
> As Pat said, this is hard when the object you want to test (in this case, a
> Rails ActionController) is so damn awkward to instantiate in a test.
>
> One approach would be to change the references to @authenticator in your
> controller to call a local #authenticator method, then override this with a
> TestController subclass and use that subclass instead in your test.
>
> David, how would you suggest the OP injects his MockAuthenticator? stub out
> Authenticator.new? I guess that's what I mostly do.

That's what I usually do as well. If you think of it, in this case
Authenticator is the factory, and you're providing a stub factory with
this approach - something that would require more elaborate measures
in other languages.

Maybe we should make this easier by providing some facility in the
mock framework to express the following in one statement:

@authenticator = stub('authenticator')
Authenticator.stub!(:new).and_return(@authenticator)

Sure, you could make that a one liner:

Authenticator.stub!(:new).and_return(@authenticator = stub('authenticator')

But I mean something like:

@authenticator = Authenticator.stub!

I don't think *that* is the answer - but something that concise would be nice.

Thoughts?

David


>
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Thu Mar  5 09:45:12 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 5 Mar 2009 08:45:12 -0600
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
Message-ID: <57c63afe0903050645n7d4a580bo2606baef85e6429f@mail.gmail.com>

On Thu, Mar 5, 2009 at 8:21 AM, John Small <lists at ruby-forum.com> wrote:
> Where do I put cucumber.yml? I can't find anything mentioned in the
> documentation.

In the project root (or wherever you're typing commands from).

Cheers,
David

>
> Thanks
>
> John Small
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From ben at benmabey.com  Thu Mar  5 10:24:27 2009
From: ben at benmabey.com (Ben Mabey)
Date: Thu, 05 Mar 2009 08:24:27 -0700
Subject: [rspec-users] Can I construct the controller myself in
 a	controller spec?
In-Reply-To: <57c63afe0903050626w1e9c4401k5d004729b7092fec@mail.gmail.com>
References: <1c319b810903042038g19ee5248m4de5e644fce7e9a1@mail.gmail.com>	<57c63afe0903042202r4cb79dc1h9697cb67889f216d@mail.gmail.com>	<011E39CE-1EF6-4E7E-A215-0995FC1A28A8@mattwynne.net>
	<57c63afe0903050626w1e9c4401k5d004729b7092fec@mail.gmail.com>
Message-ID: <49AFEEAB.5020602@benmabey.com>

David Chelimsky wrote:
> On Thu, Mar 5, 2009 at 3:31 AM, Matt Wynne <matt at mattwynne.net> wrote:
>   
>> On 5 Mar 2009, at 06:02, David Chelimsky wrote:
>>
>>     
>>> On Wed, Mar 4, 2009 at 10:38 PM, Perryn Fowler <pezlists at gmail.com> wrote:
>>>       
>>>> Hi
>>>>
>>>> I am experimenting with Constructor based dependency injection for
>>>> rails controllers.
>>>>
>>>> So I have something like this
>>>>
>>>> class LoginSessionsController < ApplicationController
>>>>
>>>>  def initialize(authenticator =  TheRealAuthenticator)
>>>>   @authenticator = authenticator
>>>>  end
>>>>
>>>>  ....
>>>> end
>>>>
>>>>
>>>> The plan was to override the authenticator used when testing with
>>>> something like
>>>>
>>>> describe LoginSessionsController.new(MyMockAuthenticator) do
>>>>  ......
>>>> end
>>>>
>>>> but rspec seems to insist on constructing the controller itself
>>>>         
>>> No, Rails insists upon constructing the controller itself. rspec-rails
>>> just wraps rails' testing framework. I'd much rather be constructing
>>> the objects myself.
>>>
>>> As for DI, there is a wealth of discussion about DI in Ruby in various
>>> user lists - general consensus is don't do it. I concur. You don't
>>> need it. You might be particularly interested in
>>> http://rubyconf2008.confreaks.com/recovering-from-enterprise.html, in
>>> which Jamis Buck, who authored a DI library for Ruby named needle,
>>> explains why that was unnecessary.
>>>       
>> That sounds a little bit like throwing the baby out with the bathwater
>> though - you still need to be able to do some kind of DI if you're doing
>> TDD, so that you can swap in a fake dependency, no? DI doesn't have to mean
>> you use some fancy framework.
>>     
>
> Agreed. I think I reacted to the term DI, about which J.B. Rainsberger
> once commented "Oh, you mean parameters." I totally agree that we need
> strategies for introducing doubles.
>
>   
>> As Pat said, this is hard when the object you want to test (in this case, a
>> Rails ActionController) is so damn awkward to instantiate in a test.
>>
>> One approach would be to change the references to @authenticator in your
>> controller to call a local #authenticator method, then override this with a
>> TestController subclass and use that subclass instead in your test.
>>
>> David, how would you suggest the OP injects his MockAuthenticator? stub out
>> Authenticator.new? I guess that's what I mostly do.
>>     
>
> That's what I usually do as well. If you think of it, in this case
> Authenticator is the factory, and you're providing a stub factory with
> this approach - something that would require more elaborate measures
> in other languages.
>
> Maybe we should make this easier by providing some facility in the
> mock framework to express the following in one statement:
>
> @authenticator = stub('authenticator')
> Authenticator.stub!(:new).and_return(@authenticator)
>
> Sure, you could make that a one liner:
>
> Authenticator.stub!(:new).and_return(@authenticator = stub('authenticator')
>
> But I mean something like:
>
> @authenticator = Authenticator.stub!
>
> I don't think *that* is the answer - but something that concise would be nice.
>
> Thoughts?
>
> David
>
>   
I like the conciseness, but it isn't very clear what it is doing IMO.  
Perhaps something a little more intention-revealing like:

@authenticator = Authenticator.stub_new!

-Ben


From lists at ruby-forum.com  Thu Mar  5 10:43:35 2009
From: lists at ruby-forum.com (John Small)
Date: Thu, 5 Mar 2009 16:43:35 +0100
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <57c63afe0903050645n7d4a580bo2606baef85e6429f@mail.gmail.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
	<57c63afe0903050645n7d4a580bo2606baef85e6429f@mail.gmail.com>
Message-ID: <c98dd5bee32f2a1b18dd64d72cd74210@ruby-forum.com>

David Chelimsky wrote:
> On Thu, Mar 5, 2009 at 8:21 AM, John Small <lists at ruby-forum.com> wrote:
>> Where do I put cucumber.yml? I can't find anything mentioned in the
>> documentation.
> 
> In the project root (or wherever you're typing commands from).
> 
> Cheers,
> David

Ok, I tried config and features to no avail, I guess that's the only 
option left

Is this documented anywhere, or are people expected to just know it?

Ta

John Small
-- 
Posted via http://www.ruby-forum.com/.

From aslak.hellesoy at gmail.com  Thu Mar  5 11:37:47 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Thu, 5 Mar 2009 17:37:47 +0100
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
Message-ID: <8d961d900903050837h2941770cp1fe1c871e8a8105e@mail.gmail.com>

On Thu, Mar 5, 2009 at 3:21 PM, John Small <lists at ruby-forum.com> wrote:
> Where do I put cucumber.yml? I can't find anything mentioned in the
> documentation.
>

Here it is: http://wiki.github.com/aslakhellesoy/cucumber/running-features

Aslak

> Thanks
>
> John Small
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)

From aslak.hellesoy at gmail.com  Thu Mar  5 11:55:28 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Thu, 5 Mar 2009 17:55:28 +0100
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <c98dd5bee32f2a1b18dd64d72cd74210@ruby-forum.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
	<57c63afe0903050645n7d4a580bo2606baef85e6429f@mail.gmail.com>
	<c98dd5bee32f2a1b18dd64d72cd74210@ruby-forum.com>
Message-ID: <8d961d900903050855h28dab74bof0f1d0d0d3cade33@mail.gmail.com>

On Thu, Mar 5, 2009 at 4:43 PM, John Small <lists at ruby-forum.com> wrote:
> David Chelimsky wrote:
>> On Thu, Mar 5, 2009 at 8:21 AM, John Small <lists at ruby-forum.com> wrote:
>>> Where do I put cucumber.yml? I can't find anything mentioned in the
>>> documentation.
>>
>> In the project root (or wherever you're typing commands from).
>>
>> Cheers,
>> David
>
> Ok, I tried config and features to no avail, I guess that's the only
> option left
>
> Is this documented anywhere, or are people expected to just know it?
>

You didn't read the mail I sent 20 minutes ago?

http://wiki.github.com/aslakhellesoy/cucumber/running-features

Aslak

> Ta
>
> John Small
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)

From nick at deadorange.com  Thu Mar  5 11:58:05 2009
From: nick at deadorange.com (Nick Hoffman)
Date: Thu, 5 Mar 2009 11:58:05 -0500
Subject: [rspec-users] OT: AR Default Values
In-Reply-To: <36c7a89533c59fc78edb2fd5f07d43fc@ruby-forum.com>
References: <6ec7f496f43a7c6085465ef3c738d329@ruby-forum.com>
	<32093C1D-CCFE-4F2B-B6D3-0869069FCFFD@railsnewbie.com>
	<36c7a89533c59fc78edb2fd5f07d43fc@ruby-forum.com>
Message-ID: <16827fa20903050858u5ddec343l8de2e08a2c210a21@mail.gmail.com>

On Wed, Mar 4, 2009 at 2:58 PM, James Byrne <lists at ruby-forum.com> wrote:
> Scott Taylor wrote:
>
>> You could try this plugin:
>>
>> http://github.com/aussiegeek/active_record_defaults/tree/master
>>
>> Scott
>
> Thanks, I will try this out.

Hi James. Just a quick message to let you know that I've used
active_record_defaults in the past, and it's been very helpful. Good
luck.
-Nick

From r_j_h_box-sf at yahoo.com  Thu Mar  5 12:12:36 2009
From: r_j_h_box-sf at yahoo.com (r_j_h_box-sf at yahoo.com)
Date: Thu, 5 Mar 2009 09:12:36 -0800 (PST)
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <c98dd5bee32f2a1b18dd64d72cd74210@ruby-forum.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
	<57c63afe0903050645n7d4a580bo2606baef85e6429f@mail.gmail.com>
	<c98dd5bee32f2a1b18dd64d72cd74210@ruby-forum.com>
Message-ID: <32974.97429.qm@web31805.mail.mud.yahoo.com>






----- Original Message ----
> From: John Small <lists at ruby-forum.com>
[David:]
> > In the project root (or wherever you're typing commands from).

> Is this documented anywhere, or are people expected to just know it?

I added the information to the wiki in one or two places, having been bitten by the same expectation you had, and having read through the code that seeks out that file.  

I think it should look in places named in the options, plus the config/ directory, personally.  The config directory is where I'd want to put it, but not every project in the world is a rails project, so I add a grain of salt to that impulse.

Randy

From aslak.hellesoy at gmail.com  Thu Mar  5 12:17:52 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Thu, 5 Mar 2009 18:17:52 +0100
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <32974.97429.qm@web31805.mail.mud.yahoo.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
	<57c63afe0903050645n7d4a580bo2606baef85e6429f@mail.gmail.com>
	<c98dd5bee32f2a1b18dd64d72cd74210@ruby-forum.com>
	<32974.97429.qm@web31805.mail.mud.yahoo.com>
Message-ID: <8d961d900903050917o7f4a48bfi3ebdceb78040b344@mail.gmail.com>

On Thu, Mar 5, 2009 at 6:12 PM,  <r_j_h_box-sf at yahoo.com> wrote:
>
>
>
>
>
> ----- Original Message ----
>> From: John Small <lists at ruby-forum.com>
> [David:]
>> > In the project root (or wherever you're typing commands from).
>
>> Is this documented anywhere, or are people expected to just know it?
>
> I added the information to the wiki in one or two places, having been bitten by the same expectation you had, and having read through the code that seeks out that file.
>
> I think it should look in places named in the options, plus the config/ directory, personally. ?The config directory is where I'd want to put it, but not every project in the world is a rails project, so I add a grain of salt to that impulse.
>

Randy, John: You really don't read my responses, do you? Or is there
some gmail lag issue going on here?

Aslak

> Randy
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)

From anja-email1 at web.de  Thu Mar  5 11:49:47 2009
From: anja-email1 at web.de (Andrea Jahn)
Date: Thu, 05 Mar 2009 17:49:47 +0100
Subject: [rspec-users] errors in controller specs when running by rake
Message-ID: <1285036318@web.de>



 

Hi,

I'm working on Windows Vista and I've installed the plugins rspec and rspec-rails V1.1.12.
If I run the controller specs directly by ruby, they are all ok:

-----------------------------------
C:\InstantRails-2.0-win\rails_apps\myapplication>ruby spec/controllers/planning/pl_plann
ings/pl_plannings_controller_new_spec.rb
...

Finished in 0.587 seconds

3 examples, 0 failures
-----------------------------------
C:\InstantRails-2.0-win\rails_apps\myapplication>ruby -I"C:/InstantRails-2.0-win/rails_a
pps/myapplication/vendor/plugins/rspec/lib" "C:/InstantRails-2.0-win/rails_apps/myapplication/ve
ndor/plugins/rspec/bin/spec" "spec/controllers/planning/pl_plannings/pl_planning
s_controller_new_spec.rb" --options "C:/InstantRails-2.0-win/rails_apps/myapplication/sp
ec/spec.opts"
...

Finished in 0.158 seconds

3 examples, 0 failures
-------------------------------------------

But when I run "rake spec", I get a lot of errors (and an exception from rake):

(in C:/InstantRails-2.0-win/rails_apps/myapplication)
** Invoke spec (first_time)
** Invoke db:test:prepare (first_time)
** Invoke db:abort_if_pending_migrations (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:abort_if_pending_migrations
** Execute db:test:prepare
** Invoke db:test:load (first_time)
** Invoke db:test:purge (first_time)
** Invoke environment 
** Execute db:test:purge
** Execute db:test:load
** Invoke db:schema:load (first_time)
** Invoke environment 
** Execute db:schema:load
** Execute spec
.............................F..FFF........FFF...............FFF..FFFFF....

1)
'Planning::PlPlanningsController GET new should render the new template' FAILED
expected "new", got "planning/pl_plannings/index"
./spec/controllers/planning/pl_plannings/pl_plannings_controller_new_spec.rb:35:

2)
'Planning::PlPlanningsController GET show should render the show template' FAILED
expected "show", got "planning/pl_plannings/index"
./spec/controllers/planning/pl_plannings/pl_plannings_controller_show_spec.rb:47:

3)
Spec::Mocks::MockExpectationError in 'Planning::PlPlanningsController GET show should call the find method of the PlPlanning class'
<PlPlanning(id: integer, title: string, created_at: datetime, updated_at: datetime) (class)> expected :find with (nil) but received it with (:all)
./spec/controllers/planning/pl_plannings/pl_plannings_controller_show_spec.rb:41:

4)
'Planning::PlPlanningsController GET show should assign a pl_planning' FAILED
expected instance_of?(PlPlanning(id: integer, title: string, created_at: datetime, updated_at: datetime)) to return true, got false
./spec/controllers/planning/pl_plannings/pl_plannings_controller_show_spec.rb:36:

5)
'Planning::PlPlanningsController GET edit should render the edit template' FAILED
expected "edit", got "planning/pl_plannings/index"
./spec/controllers/planning/pl_plannings/pl_plannings_controller_edit_spec.rb:47:

6)
Spec::Mocks::MockExpectationError in 'Planning::PlPlanningsController GET edit should call the find method of the PlPlanning class'
<PlPlanning(id: integer, title: string, created_at: datetime, updated_at: datetime) (class)> expected :find with (nil) but received it with (:all)
./spec/controllers/planning/pl_plannings/pl_plannings_controller_edit_spec.rb:41:

7)
'Planning::PlPlanningsController GET edit should assign a pl_planning' FAILED
expected instance_of?(PlPlanning(id: integer, title: string, created_at: datetime, updated_at: datetime)) to return true, got false
./spec/controllers/planning/pl_plannings/pl_plannings_controller_edit_spec.rb:36:

8)
'Planning::PlPlanningsController GET index_deleted should render the index_deleted template' FAILED
expected "index_deleted", got "planning/pl_plannings/index"
./spec/controllers/planning/pl_plannings/pl_plannings_controller_index_deleted_spec.rb:47:

9)
Spec::Mocks::MockExpectationError in 'Planning::PlPlanningsController GET index_deleted should call the find method of the PlPlanning::Deleted class'
<PlPlanning::Deleted(id: integer, title: string, created_at: datetime, updated_at: datetime, deleted_at: datetime) (class)> expected :find with (:all, {:order=>"title"}) once, but received it 0 times
./spec/controllers/planning/pl_plannings/pl_plannings_controller_index_deleted_spec.rb:41:

10)
'Planning::PlPlanningsController GET index_deleted should assign deleted_pl_plannings' FAILED
expected instance_of?(Array) to return true, got false
./spec/controllers/planning/pl_plannings/pl_plannings_controller_index_deleted_spec.rb:36:

11)
ActiveRecord::RecordNotFound in 'Planning::PlPlanningsController PUT undestroy should redirect to the PlPlannings list'
Couldn't find PlPlanning without an ID
C:/InstantRails-2.0-win/rails_apps/myapplication/app/controllers/planning/pl_plannings_controller.rb:78:in `update'
./spec/controllers/planning/pl_plannings/pl_plannings_controller_update_spec.rb:6:in `do_put'
./spec/controllers/planning/pl_plannings/pl_plannings_controller_undestroy_spec.rb:53:

12)
ActiveRecord::RecordNotFound in 'Planning::PlPlanningsController PUT undestroy should undestroy the PlPlanning'
Couldn't find PlPlanning without an ID
C:/InstantRails-2.0-win/rails_apps/myapplication/app/controllers/planning/pl_plannings_controller.rb:78:in `update'
./spec/controllers/planning/pl_plannings/pl_plannings_controller_update_spec.rb:6:in `do_put'
./spec/controllers/planning/pl_plannings/pl_plannings_controller_undestroy_spec.rb:49:

13)
ActiveRecord::RecordNotFound in 'Planning::PlPlanningsController PUT undestroy should call the find method of the PlPlanning::Deleted class'
Couldn't find PlPlanning without an ID
C:/InstantRails-2.0-win/rails_apps/myapplication/app/controllers/planning/pl_plannings_controller.rb:78:in `update'
./spec/controllers/planning/pl_plannings/pl_plannings_controller_update_spec.rb:6:in `do_put'
./spec/controllers/planning/pl_plannings/pl_plannings_controller_undestroy_spec.rb:44:

14)
ActiveRecord::RecordNotFound in 'Planning::PlPlanningsController PUT undestroy should assign a pl_planning'
Couldn't find PlPlanning without an ID
C:/InstantRails-2.0-win/rails_apps/myapplication/app/controllers/planning/pl_plannings_controller.rb:78:in `update'
./spec/controllers/planning/pl_plannings/pl_plannings_controller_update_spec.rb:6:in `do_put'
./spec/controllers/planning/pl_plannings/pl_plannings_controller_undestroy_spec.rb:37:

15)
ActiveRecord::RecordNotFound in 'Planning::PlPlanningsController PUT undestroy should be successfully redirected'
Couldn't find PlPlanning without an ID
C:/InstantRails-2.0-win/rails_apps/myapplication/app/controllers/planning/pl_plannings_controller.rb:78:in `update'
./spec/controllers/planning/pl_plannings/pl_plannings_controller_update_spec.rb:6:in `do_put'
./spec/controllers/planning/pl_plannings/pl_plannings_controller_undestroy_spec.rb:32:

Finished in 1.417 seconds

75 examples, 15 failures
rake aborted!
Command C:/InstantRails-2.0-win/ruby/bin/ruby
 -I"C:/InstantRails-2.0-win/rails_apps/myapplication/vendor/plugins/rspec/lib" 
 "C:/InstantRails-2.0-win/rails_apps/myapplication/vendor/plugins/rspec/bin/spec" 
 "spec/controllers/planning/pl_plannings/pl_plannings_controller_create_spec.rb" 
 "spec/controllers/planning/pl_plannings/pl_plannings_controller_edit_spec.rb" 
 "spec/controllers/planning/pl_plannings/pl_plannings_controller_index_deleted_spec.rb" 
 "spec/controllers/planning/pl_plannings/pl_plannings_controller_index_spec.rb" 
 "spec/controllers/planning/pl_plannings/pl_plannings_controller_new_spec.rb" 
 "spec/controllers/planning/pl_plannings/pl_plannings_controller_show_spec.rb" 
 "spec/controllers/planning/pl_plannings/pl_plannings_controller_undestroy_spec.rb" 
 "spec/controllers/planning/pl_plannings/pl_plannings_controller_update_spec.rb" 
 "spec/helpers/pl_plannings_helper_spec.rb" "spec/models/planning/pl_planning_spec.rb" 
 "spec/views/planning/pl_plannings/edit_rhtml_spec.rb" 
 "spec/views/planning/pl_plannings/index_deleted_rhtml_spec.rb" 
 "spec/views/planning/pl_plannings/index_rhtml_spec.rb" 
 "spec/views/planning/pl_plannings/new_rhtml_spec.rb" 
 "spec/views/planning/pl_plannings/show_rhtml_spec.rb" 
 "spec/views/planning/pl_plannings/_form_rhtml_spec.rb" 
 "spec/views/planning/pl_plannings/_table_rhtml_spec.rb"
 --options "C:/InstantRails-2.0-win/rails_apps/myapplication/spec/spec.opts" failed
 
 
C:/InstantRails-2.0-win/rails_apps/myapplication/vendor/plugins/rspec/lib/spec/rake/spectask.rb:175:in `define'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1090:in `verbose'
C:/InstantRails-2.0-win/rails_apps/myapplication/vendor/plugins/rspec/lib/spec/rake/spectask.rb:151:in `define'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `call'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `execute'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `each'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `execute'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:578:in `invoke_with_call_chain'
C:/InstantRails-2.0-win/ruby/lib/ruby/1.8/monitor.rb:242:in `synchronize'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:571:in `invoke_with_call_chain'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:564:in `invoke'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:2019:in `invoke_task'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `each'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:2036:in `standard_exception_handling'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1991:in `top_level'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1970:in `run'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:2036:in `standard_exception_handling'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/lib/rake.rb:1967:in `run'
C:/InstantRails-2.0-win/ruby/lib/ruby/gems/1.8/gems/rake-0.8.3/bin/rake:31
C:/InstantRails-2.0-win/ruby/bin/rake:19:in `load'
C:/InstantRails-2.0-win/ruby/bin/rake:19


-------------------------------------------------------------------------------

Perhaps do I have to make some configurations ?

Thanks in advance
Andrea

 


	
DSL zum Nulltarif + 20 Euro Extrapr?mie bei Online-Bestellung ?ber die 
DSL Freundschaftswerbung! *http://dsl.web.de/?ac=OM.AD.AD008K15279B7069a* [http://dsl.web.de/?ac=OM.AD.AD008K15279B7069a] 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090305/ca3bbbed/attachment-0001.html>

From dchelimsky at gmail.com  Thu Mar  5 12:27:34 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 5 Mar 2009 11:27:34 -0600
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <8d961d900903050855h28dab74bof0f1d0d0d3cade33@mail.gmail.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
	<57c63afe0903050645n7d4a580bo2606baef85e6429f@mail.gmail.com>
	<c98dd5bee32f2a1b18dd64d72cd74210@ruby-forum.com>
	<8d961d900903050855h28dab74bof0f1d0d0d3cade33@mail.gmail.com>
Message-ID: <57c63afe0903050927k39e1caabj887df484e67a72e8@mail.gmail.com>

On Thu, Mar 5, 2009 at 10:55 AM, aslak hellesoy
<aslak.hellesoy at gmail.com> wrote:
> On Thu, Mar 5, 2009 at 4:43 PM, John Small <lists at ruby-forum.com> wrote:
>> David Chelimsky wrote:
>>> On Thu, Mar 5, 2009 at 8:21 AM, John Small <lists at ruby-forum.com> wrote:
>>>> Where do I put cucumber.yml? I can't find anything mentioned in the
>>>> documentation.
>>>
>>> In the project root (or wherever you're typing commands from).
>>>
>>> Cheers,
>>> David
>>
>> Ok, I tried config and features to no avail, I guess that's the only
>> option left
>>
>> Is this documented anywhere, or are people expected to just know it?
>>
>
> You didn't read the mail I sent 20 minutes ago?
>
> http://wiki.github.com/aslakhellesoy/cucumber/running-features

Since ppl are having a hard time finding this, I added
http://wiki.github.com/aslakhellesoy/cucumber/cucumberyml, which
references http://wiki.github.com/aslakhellesoy/cucumber/running-features.
I also changed the header of the relevant section to "Defining
?profiles? in cucumber.yml"

Should be easy to find now.

Cheers,
David

>
> Aslak
>
>> Ta
>>
>> John Small
>> --
>> Posted via http://www.ruby-forum.com/.
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
>
> --
> Aslak (::)
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From f.mischa at gmail.com  Thu Mar  5 12:29:11 2009
From: f.mischa at gmail.com (Mischa Fierer)
Date: Thu, 5 Mar 2009 11:29:11 -0600
Subject: [rspec-users] OT: AR Default Values
In-Reply-To: <36c7a89533c59fc78edb2fd5f07d43fc@ruby-forum.com>
References: <6ec7f496f43a7c6085465ef3c738d329@ruby-forum.com>
	<32093C1D-CCFE-4F2B-B6D3-0869069FCFFD@railsnewbie.com>
	<36c7a89533c59fc78edb2fd5f07d43fc@ruby-forum.com>
Message-ID: <ae16b71e0903050929t3bf27eb3y31956da575caaa99@mail.gmail.com>

Not sure if this is what you're looking for, but there is also this:
http://github.com/FooBarWidget/default_value_for/tree/master

On Wed, Mar 4, 2009 at 1:58 PM, James Byrne <lists at ruby-forum.com> wrote:

> Scott Taylor wrote:
>
> > You could try this plugin:
> >
> > http://github.com/aussiegeek/active_record_defaults/tree/master
> >
> > Scott
>
> Thanks, I will try this out.
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090305/820d7b18/attachment.html>

From dchelimsky at gmail.com  Thu Mar  5 12:39:13 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 5 Mar 2009 11:39:13 -0600
Subject: [rspec-users] Can I construct the controller myself in a
	controller spec?
In-Reply-To: <49AFEEAB.5020602@benmabey.com>
References: <1c319b810903042038g19ee5248m4de5e644fce7e9a1@mail.gmail.com>
	<57c63afe0903042202r4cb79dc1h9697cb67889f216d@mail.gmail.com>
	<011E39CE-1EF6-4E7E-A215-0995FC1A28A8@mattwynne.net>
	<57c63afe0903050626w1e9c4401k5d004729b7092fec@mail.gmail.com>
	<49AFEEAB.5020602@benmabey.com>
Message-ID: <57c63afe0903050939s4785fb7enab06dc23ec7220cb@mail.gmail.com>

On Thu, Mar 5, 2009 at 9:24 AM, Ben Mabey <ben at benmabey.com> wrote:
> David Chelimsky wrote:
>>
>> On Thu, Mar 5, 2009 at 3:31 AM, Matt Wynne <matt at mattwynne.net> wrote:
>>
>>>
>>> On 5 Mar 2009, at 06:02, David Chelimsky wrote:
>>>
>>>
>>>>
>>>> On Wed, Mar 4, 2009 at 10:38 PM, Perryn Fowler <pezlists at gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>> Hi
>>>>>
>>>>> I am experimenting with Constructor based dependency injection for
>>>>> rails controllers.
>>>>>
>>>>> So I have something like this
>>>>>
>>>>> class LoginSessionsController < ApplicationController
>>>>>
>>>>> ?def initialize(authenticator = ?TheRealAuthenticator)
>>>>> ?@authenticator = authenticator
>>>>> ?end
>>>>>
>>>>> ?....
>>>>> end
>>>>>
>>>>>
>>>>> The plan was to override the authenticator used when testing with
>>>>> something like
>>>>>
>>>>> describe LoginSessionsController.new(MyMockAuthenticator) do
>>>>> ?......
>>>>> end
>>>>>
>>>>> but rspec seems to insist on constructing the controller itself
>>>>>
>>>>
>>>> No, Rails insists upon constructing the controller itself. rspec-rails
>>>> just wraps rails' testing framework. I'd much rather be constructing
>>>> the objects myself.
>>>>
>>>> As for DI, there is a wealth of discussion about DI in Ruby in various
>>>> user lists - general consensus is don't do it. I concur. You don't
>>>> need it. You might be particularly interested in
>>>> http://rubyconf2008.confreaks.com/recovering-from-enterprise.html, in
>>>> which Jamis Buck, who authored a DI library for Ruby named needle,
>>>> explains why that was unnecessary.
>>>>
>>>
>>> That sounds a little bit like throwing the baby out with the bathwater
>>> though - you still need to be able to do some kind of DI if you're doing
>>> TDD, so that you can swap in a fake dependency, no? DI doesn't have to
>>> mean
>>> you use some fancy framework.
>>>
>>
>> Agreed. I think I reacted to the term DI, about which J.B. Rainsberger
>> once commented "Oh, you mean parameters." I totally agree that we need
>> strategies for introducing doubles.
>>
>>
>>>
>>> As Pat said, this is hard when the object you want to test (in this case,
>>> a
>>> Rails ActionController) is so damn awkward to instantiate in a test.
>>>
>>> One approach would be to change the references to @authenticator in your
>>> controller to call a local #authenticator method, then override this with
>>> a
>>> TestController subclass and use that subclass instead in your test.
>>>
>>> David, how would you suggest the OP injects his MockAuthenticator? stub
>>> out
>>> Authenticator.new? I guess that's what I mostly do.
>>>
>>
>> That's what I usually do as well. If you think of it, in this case
>> Authenticator is the factory, and you're providing a stub factory with
>> this approach - something that would require more elaborate measures
>> in other languages.
>>
>> Maybe we should make this easier by providing some facility in the
>> mock framework to express the following in one statement:
>>
>> @authenticator = stub('authenticator')
>> Authenticator.stub!(:new).and_return(@authenticator)
>>
>> Sure, you could make that a one liner:
>>
>> Authenticator.stub!(:new).and_return(@authenticator =
>> stub('authenticator')
>>
>> But I mean something like:
>>
>> @authenticator = Authenticator.stub!
>>
>> I don't think *that* is the answer - but something that concise would be
>> nice.
>>
>> Thoughts?
>>
>> David
>>
>>
>
> I like the conciseness, but it isn't very clear what it is doing IMO.
> ?Perhaps something a little more intention-revealing like:
>
> @authenticator = Authenticator.stub_new!

That's the right direction. Not in love with that either - especially
since it requires adding a new method to Object.

How about something like:

stub_factory(Authenticator)

This would configure Authenticator to return the same test double
every time it receives #new. So you could say:

stub_factory(Authenticator)
@authenticator = Authenticator.new

Or, perhaps:

@authenticator = stub_factory(Authenticator).new

Not there yet (that's a bit confusing), but I think you can see where
this is headed. More ideas?

David





>
> -Ben
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From r_j_h_box-sf at yahoo.com  Thu Mar  5 13:16:08 2009
From: r_j_h_box-sf at yahoo.com (r_j_h_box-sf at yahoo.com)
Date: Thu, 5 Mar 2009 10:16:08 -0800 (PST)
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <8d961d900903050917o7f4a48bfi3ebdceb78040b344@mail.gmail.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
	<57c63afe0903050645n7d4a580bo2606baef85e6429f@mail.gmail.com>
	<c98dd5bee32f2a1b18dd64d72cd74210@ruby-forum.com>
	<32974.97429.qm@web31805.mail.mud.yahoo.com>
	<8d961d900903050917o7f4a48bfi3ebdceb78040b344@mail.gmail.com>
Message-ID: <321292.98913.qm@web31802.mail.mud.yahoo.com>


Aslak:

> some gmail lag issue going on here?


Not sure who's causing the lag, but yeah.

My hope was to help in a way that I could, freeing the "big guns" to focus on things I'm less suited for at this moment.

Randy

From BrianPatrickDunn at gmail.com  Thu Mar  5 13:32:00 2009
From: BrianPatrickDunn at gmail.com (Higgaion)
Date: Thu, 5 Mar 2009 10:32:00 -0800 (PST)
Subject: [rspec-users] --options file quirky with --drb
Message-ID: <79ed71c5-38d9-45e4-a7c4-470e0bfa5885@q30g2000prq.googlegroups.com>

putting --drb in my spec.opts file has some unexpected results.

$ spec --drb --colour --format specdoc --loadby mtime --reverse -G
spec/spec.opts
$ spec spec/models/a_model_spec.rb -O spec/spec.opts
$

it just returns right away, with no output.


but...
$ spec --colour --format specdoc --loadby mtime --reverse -G spec/
spec.opts
$ spec spec/models/campaign_spec.rb -O spec/spec.opts
:
:
lots of pretty spec output
:
:
$

interestingly, if i include a spec file in the call that generates the
options file, like
$ spec spec/models/campaign_spec.rb --drb --colour --format specdoc --
loadby mtime --reverse -G spec/spec.opts
then running those options like this works as expected, even with --
drb.
$ spec spec/models/a_model_spec.rb -O spec/spec.opts

of course, that isn't a very useful way to use rspec, and its
incompatible with my rspec holy grail dreams:
http://wiki.github.com/dchelimsky/rspec/spec_server-autospec-nearly-pure-bdd-joy

it seems that this would be a problem with options file loading, no?
anyone else able to reproduce this issue?

From dchelimsky at gmail.com  Thu Mar  5 14:09:32 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 5 Mar 2009 13:09:32 -0600
Subject: [rspec-users] --options file quirky with --drb
In-Reply-To: <79ed71c5-38d9-45e4-a7c4-470e0bfa5885@q30g2000prq.googlegroups.com>
References: <79ed71c5-38d9-45e4-a7c4-470e0bfa5885@q30g2000prq.googlegroups.com>
Message-ID: <57c63afe0903051109p4fb8e410s48cca3cf313582a@mail.gmail.com>

On Thu, Mar 5, 2009 at 12:32 PM, Higgaion <BrianPatrickDunn at gmail.com> wrote:
> putting --drb in my spec.opts file has some unexpected results.
>
> $ spec --drb --colour --format specdoc --loadby mtime --reverse -G
> spec/spec.opts
> $ spec spec/models/a_model_spec.rb -O spec/spec.opts
> $
>
> it just returns right away, with no output.

What version of rspec are you running? This should be fixed in git.

> but...
> $ spec --colour --format specdoc --loadby mtime --reverse -G spec/
> spec.opts
> $ spec spec/models/campaign_spec.rb -O spec/spec.opts
> :
> :
> lots of pretty spec output
> :
> :
> $
>
> interestingly, if i include a spec file in the call that generates the
> options file, like
> $ spec spec/models/campaign_spec.rb --drb --colour --format specdoc --
> loadby mtime --reverse -G spec/spec.opts
> then running those options like this works as expected, even with --
> drb.
> $ spec spec/models/a_model_spec.rb -O spec/spec.opts

Never heard that before :) - obviously not intended.

>
> of course, that isn't a very useful way to use rspec, and its
> incompatible with my rspec holy grail dreams:
> http://wiki.github.com/dchelimsky/rspec/spec_server-autospec-nearly-pure-bdd-joy
>
> it seems that this would be a problem with options file loading, no?
> anyone else able to reproduce this issue?
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From mark at mwilden.com  Thu Mar  5 15:38:37 2009
From: mark at mwilden.com (Mark Wilden)
Date: Thu, 5 Mar 2009 12:38:37 -0800
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <8d961d900903050837h2941770cp1fe1c871e8a8105e@mail.gmail.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
	<8d961d900903050837h2941770cp1fe1c871e8a8105e@mail.gmail.com>
Message-ID: <3c30da400903051238k3e0d618cm4f39505d38013218@mail.gmail.com>

That reminds me: Was there a reason for using <file>:<line> to run a
feature at a line instead of spec's -l <line> ?

///ark

From BrianPatrickDunn at gmail.com  Thu Mar  5 16:18:34 2009
From: BrianPatrickDunn at gmail.com (Higgaion)
Date: Thu, 5 Mar 2009 13:18:34 -0800 (PST)
Subject: [rspec-users] --options file quirky with --drb
In-Reply-To: <57c63afe0903051109p4fb8e410s48cca3cf313582a@mail.gmail.com>
References: <79ed71c5-38d9-45e4-a7c4-470e0bfa5885@q30g2000prq.googlegroups.com>
	<57c63afe0903051109p4fb8e410s48cca3cf313582a@mail.gmail.com>
Message-ID: <677b3e90-d8f2-4b73-93ff-5fcc08051db0@k19g2000prh.googlegroups.com>

On Mar 5, 1:09?pm, David Chelimsky <dchelim... at gmail.com> wrote:
> On Thu, Mar 5, 2009 at 12:32 PM, Higgaion <BrianPatrickD... at gmail.com> wrote:
> > putting --drb in my spec.opts file has some unexpected results.
>
> > $ spec --drb --colour --format specdoc --loadby mtime --reverse -G
> > spec/spec.opts
> > $ spec spec/models/a_model_spec.rb -O spec/spec.opts
> > $
>
> > it just returns right away, with no output.
>
> What version of rspec are you running? This should be fixed in git.
>

rspec 1.1.12.

i installed the plugins from git, as per the instructions here:
http://wiki.github.com/dchelimsky/rspec/rails
and it worked beautifully, as in spec_server and autospec talking
together*

one issue: now all of my route generation specs that illustrate
differentiation on http method are failing. ex:

Test::Unit::AssertionFailedError in 'UsersController route generation
should route users's 'update' action correctly'
The recognized options <{"action"=>"show", "id"=>"1",
"controller"=>"users"}> did not match <{"action"=>"update", "id"=>"1",
"controller"=>"users"}>, difference: <{"action"=>"update"}>

here it thought put was get.

i guess that's why its the edge version :)



* with one minor change:

vendor/plugins/rspec/lib/spec/runner/drb_command_line.rb
-          DRb.start_service("druby://localhost:0")
+          DRb.start_service("druby://127.0.0.1:0")

i always have to change that because i build ruby from macports.


>
>
>
>
> > but...
> > $ spec --colour --format specdoc --loadby mtime --reverse -G spec/
> > spec.opts
> > $ spec spec/models/campaign_spec.rb -O spec/spec.opts
> > :
> > :
> > lots of pretty spec output
> > :
> > :
> > $
>
> > interestingly, if i include a spec file in the call that generates the
> > options file, like
> > $ spec spec/models/campaign_spec.rb --drb --colour --format specdoc --
> > loadby mtime --reverse -G spec/spec.opts
> > then running those options like this works as expected, even with --
> > drb.
> > $ spec spec/models/a_model_spec.rb -O spec/spec.opts
>
> Never heard that before :) - obviously not intended.
>
>
>
> > of course, that isn't a very useful way to use rspec, and its
> > incompatible with my rspec holy grail dreams:
> >http://wiki.github.com/dchelimsky/rspec/spec_server-autospec-nearly-p...
>
> > it seems that this would be a problem with options file loading, no?
> > anyone else able to reproduce this issue?
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From ben at benmabey.com  Thu Mar  5 16:30:30 2009
From: ben at benmabey.com (Ben Mabey)
Date: Thu, 05 Mar 2009 14:30:30 -0700
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <3c30da400903051238k3e0d618cm4f39505d38013218@mail.gmail.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>	<8d961d900903050837h2941770cp1fe1c871e8a8105e@mail.gmail.com>
	<3c30da400903051238k3e0d618cm4f39505d38013218@mail.gmail.com>
Message-ID: <49B04476.7030209@benmabey.com>

Mark Wilden wrote:
> That reminds me: Was there a reason for using <file>:<line> to run a
> feature at a line instead of spec's -l <line> ?
>
> ///ark
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>   
I think it was to keep in line with how Cucumber outputs the backtrace 
in the CLI.  So you can simply copy and paste the line from the output 
to run just that one scenario.

I actually much prefer the concise notation and I would like to see 
RSpec adopt it.

-Ben

From BrianPatrickDunn at gmail.com  Thu Mar  5 16:49:58 2009
From: BrianPatrickDunn at gmail.com (Higgaion)
Date: Thu, 5 Mar 2009 13:49:58 -0800 (PST)
Subject: [rspec-users] --options file quirky with --drb
In-Reply-To: <677b3e90-d8f2-4b73-93ff-5fcc08051db0@k19g2000prh.googlegroups.com>
References: <79ed71c5-38d9-45e4-a7c4-470e0bfa5885@q30g2000prq.googlegroups.com>
	<57c63afe0903051109p4fb8e410s48cca3cf313582a@mail.gmail.com> 
	<677b3e90-d8f2-4b73-93ff-5fcc08051db0@k19g2000prh.googlegroups.com>
Message-ID: <ccc7ec8a-19f2-4b42-8470-8af1c9811948@v35g2000pro.googlegroups.com>



On Mar 5, 3:18?pm, Higgaion <BrianPatrickD... at gmail.com> wrote:
> On Mar 5, 1:09?pm, David Chelimsky <dchelim... at gmail.com> wrote:
>
> > On Thu, Mar 5, 2009 at 12:32 PM, Higgaion <BrianPatrickD... at gmail.com> wrote:
> > > putting --drb in my spec.opts file has some unexpected results.
>
> > > $ spec --drb --colour --format specdoc --loadby mtime --reverse -G
> > > spec/spec.opts
> > > $ spec spec/models/a_model_spec.rb -O spec/spec.opts
> > > $
>
> > > it just returns right away, with no output.
>
> > What version of rspec are you running? This should be fixed in git.
>
> rspec 1.1.12.
>
> i installed the plugins from git, as per the instructions here:http://wiki.github.com/dchelimsky/rspec/rails
> and it worked beautifully, as in spec_server and autospec talking
> together*
>
> one issue: now all of my route generation specs that illustrate
> differentiation on http method are failing. ex:
>
> Test::Unit::AssertionFailedError in 'UsersController route generation
> should route users's 'update' action correctly'
> The recognized options <{"action"=>"show", "id"=>"1",
> "controller"=>"users"}> did not match <{"action"=>"update", "id"=>"1",
> "controller"=>"users"}>, difference: <{"action"=>"update"}>
>
> here it thought put was get.
>
> i guess that's why its the edge version :)
>

ok, i read some code and i see that rspec is now using
assert_recognizes, which expects a :method option. so if i change

route_for(:controller => 'users', :action => 'update', :id =>
'1').should == "/users/1"

to

route_for(:controller => 'users', :action => 'update', :id =>
'1').should == { :path => "/users/1", :method => :put }

the assertion passes (and is a little more descriptive).


> * with one minor change:
>
> vendor/plugins/rspec/lib/spec/runner/drb_command_line.rb
> - ? ? ? ? ?DRb.start_service("druby://localhost:0")
> + ? ? ? ? ?DRb.start_service("druby://127.0.0.1:0")
>
> i always have to change that because i build ruby from macports.
>
>
>
>
>
>
>
> > > but...
> > > $ spec --colour --format specdoc --loadby mtime --reverse -G spec/
> > > spec.opts
> > > $ spec spec/models/campaign_spec.rb -O spec/spec.opts
> > > :
> > > :
> > > lots of pretty spec output
> > > :
> > > :
> > > $
>
> > > interestingly, if i include a spec file in the call that generates the
> > > options file, like
> > > $ spec spec/models/campaign_spec.rb --drb --colour --format specdoc --
> > > loadby mtime --reverse -G spec/spec.opts
> > > then running those options like this works as expected, even with --
> > > drb.
> > > $ spec spec/models/a_model_spec.rb -O spec/spec.opts
>
> > Never heard that before :) - obviously not intended.
>
> > > of course, that isn't a very useful way to use rspec, and its
> > > incompatible with my rspec holy grail dreams:
> > >http://wiki.github.com/dchelimsky/rspec/spec_server-autospec-nearly-p...
>
> > > it seems that this would be a problem with options file loading, no?
> > > anyone else able to reproduce this issue?
> > > _______________________________________________
> > > rspec-users mailing list
> > > rspec-us... at rubyforge.org
> > >http://rubyforge.org/mailman/listinfo/rspec-users
>
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From dchelimsky at gmail.com  Thu Mar  5 16:52:59 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 5 Mar 2009 15:52:59 -0600
Subject: [rspec-users] --options file quirky with --drb
In-Reply-To: <677b3e90-d8f2-4b73-93ff-5fcc08051db0@k19g2000prh.googlegroups.com>
References: <79ed71c5-38d9-45e4-a7c4-470e0bfa5885@q30g2000prq.googlegroups.com>
	<57c63afe0903051109p4fb8e410s48cca3cf313582a@mail.gmail.com>
	<677b3e90-d8f2-4b73-93ff-5fcc08051db0@k19g2000prh.googlegroups.com>
Message-ID: <57c63afe0903051352g4b12416ayd64504ba342357fa@mail.gmail.com>

On Thu, Mar 5, 2009 at 3:18 PM, Higgaion <BrianPatrickDunn at gmail.com> wrote:
> On Mar 5, 1:09?pm, David Chelimsky <dchelim... at gmail.com> wrote:
>> On Thu, Mar 5, 2009 at 12:32 PM, Higgaion <BrianPatrickD... at gmail.com> wrote:
>> > putting --drb in my spec.opts file has some unexpected results.
>>
>> > $ spec --drb --colour --format specdoc --loadby mtime --reverse -G
>> > spec/spec.opts
>> > $ spec spec/models/a_model_spec.rb -O spec/spec.opts
>> > $
>>
>> > it just returns right away, with no output.
>>
>> What version of rspec are you running? This should be fixed in git.
>>
>
> rspec 1.1.12.
>
> i installed the plugins from git, as per the instructions here:
> http://wiki.github.com/dchelimsky/rspec/rails
> and it worked beautifully, as in spec_server and autospec talking
> together*

Great.

>
> one issue: now all of my route generation specs that illustrate
> differentiation on http method are failing. ex:
>
> Test::Unit::AssertionFailedError in 'UsersController route generation
> should route users's 'update' action correctly'
> The recognized options <{"action"=>"show", "id"=>"1",
> "controller"=>"users"}> did not match <{"action"=>"update", "id"=>"1",
> "controller"=>"users"}>, difference: <{"action"=>"update"}>
>
> here it thought put was get.
>
> i guess that's why its the edge version :)

This is doc'd here:
http://github.com/dchelimsky/rspec-rails/blob/master/Upgrade.markdown

> * with one minor change:
>
> vendor/plugins/rspec/lib/spec/runner/drb_command_line.rb
> - ? ? ? ? ?DRb.start_service("druby://localhost:0")
> + ? ? ? ? ?DRb.start_service("druby://127.0.0.1:0")
>
> i always have to change that because i build ruby from macports.

Maybe we need to make that configurable.

Thanks,
David

>> > but...
>> > $ spec --colour --format specdoc --loadby mtime --reverse -G spec/
>> > spec.opts
>> > $ spec spec/models/campaign_spec.rb -O spec/spec.opts
>> > :
>> > :
>> > lots of pretty spec output
>> > :
>> > :
>> > $
>>
>> > interestingly, if i include a spec file in the call that generates the
>> > options file, like
>> > $ spec spec/models/campaign_spec.rb --drb --colour --format specdoc --
>> > loadby mtime --reverse -G spec/spec.opts
>> > then running those options like this works as expected, even with --
>> > drb.
>> > $ spec spec/models/a_model_spec.rb -O spec/spec.opts
>>
>> Never heard that before :) - obviously not intended.
>>
>>
>>
>> > of course, that isn't a very useful way to use rspec, and its
>> > incompatible with my rspec holy grail dreams:
>> >http://wiki.github.com/dchelimsky/rspec/spec_server-autospec-nearly-p...
>>
>> > it seems that this would be a problem with options file loading, no?
>> > anyone else able to reproduce this issue?
>> > _______________________________________________
>> > rspec-users mailing list
>> > rspec-us... at rubyforge.org
>> >http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From joe at josephwilk.net  Thu Mar  5 17:28:28 2009
From: joe at josephwilk.net (Joseph Wilk)
Date: Thu, 05 Mar 2009 22:28:28 +0000
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <49B04476.7030209@benmabey.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>	<8d961d900903050837h2941770cp1fe1c871e8a8105e@mail.gmail.com>	<3c30da400903051238k3e0d618cm4f39505d38013218@mail.gmail.com>
	<49B04476.7030209@benmabey.com>
Message-ID: <49B0520C.6070205@josephwilk.net>

Ben Mabey wrote:
> Mark Wilden wrote:
>> That reminds me: Was there a reason for using <file>:<line> to run a
>> feature at a line instead of spec's -l <line> ?
>>
>> ///ark
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>   
> I think it was to keep in line with how Cucumber outputs the backtrace 
> in the CLI.  So you can simply copy and paste the line from the output 
> to run just that one scenario.
>
> I actually much prefer the concise notation and I would like to see 
> RSpec adopt it.
>
Exactly as Ben said. In addition it was also used as it made it nicer 
when running multiple lines in the same file

file:10:11:14:15

-- 
Joseph Wilk
http://blog.josephwilk.net


> -Ben
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



From dchelimsky at gmail.com  Thu Mar  5 17:47:40 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 5 Mar 2009 16:47:40 -0600
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <49B04476.7030209@benmabey.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
	<8d961d900903050837h2941770cp1fe1c871e8a8105e@mail.gmail.com>
	<3c30da400903051238k3e0d618cm4f39505d38013218@mail.gmail.com>
	<49B04476.7030209@benmabey.com>
Message-ID: <57c63afe0903051447y49c60b98i7b5cd15c0907daad@mail.gmail.com>

On Thu, Mar 5, 2009 at 3:30 PM, Ben Mabey <ben at benmabey.com> wrote:
> Mark Wilden wrote:
>>
>> That reminds me: Was there a reason for using <file>:<line> to run a
>> feature at a line instead of spec's -l <line> ?
>>
>> ///ark
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
> I think it was to keep in line with how Cucumber outputs the backtrace in
> the CLI. ?So you can simply copy and paste the line from the output to run
> just that one scenario.
>
> I actually much prefer the concise notation and I would like to see RSpec
> adopt it.

I agree. RSpec will adopt it as soon as it receives your patch :)

>
> -Ben
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From mark at mwilden.com  Thu Mar  5 19:03:35 2009
From: mark at mwilden.com (Mark Wilden)
Date: Thu, 5 Mar 2009 16:03:35 -0800
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <57c63afe0903051447y49c60b98i7b5cd15c0907daad@mail.gmail.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
	<8d961d900903050837h2941770cp1fe1c871e8a8105e@mail.gmail.com>
	<3c30da400903051238k3e0d618cm4f39505d38013218@mail.gmail.com>
	<49B04476.7030209@benmabey.com>
	<57c63afe0903051447y49c60b98i7b5cd15c0907daad@mail.gmail.com>
Message-ID: <3c30da400903051603q244edb76ub02e98691bf3f5ec@mail.gmail.com>

On Thu, Mar 5, 2009 at 2:47 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
>>
>> I actually much prefer the concise notation and I would like to see RSpec
>> adopt it.
>
> I agree. RSpec will adopt it as soon as it receives your patch :)

That would be great. I've been used to seeing the colon notation for a
quarter of a century. :)

///ark

From ben at benmabey.com  Thu Mar  5 19:30:44 2009
From: ben at benmabey.com (Ben Mabey)
Date: Thu, 05 Mar 2009 17:30:44 -0700
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <57c63afe0903051447y49c60b98i7b5cd15c0907daad@mail.gmail.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>	<8d961d900903050837h2941770cp1fe1c871e8a8105e@mail.gmail.com>	<3c30da400903051238k3e0d618cm4f39505d38013218@mail.gmail.com>	<49B04476.7030209@benmabey.com>
	<57c63afe0903051447y49c60b98i7b5cd15c0907daad@mail.gmail.com>
Message-ID: <49B06EB4.90909@benmabey.com>

David Chelimsky wrote:
> On Thu, Mar 5, 2009 at 3:30 PM, Ben Mabey <ben at benmabey.com> wrote:
>   
>> Mark Wilden wrote:
>>     
>>> That reminds me: Was there a reason for using <file>:<line> to run a
>>> feature at a line instead of spec's -l <line> ?
>>>
>>> ///ark
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>>       
>> I think it was to keep in line with how Cucumber outputs the backtrace in
>> the CLI.  So you can simply copy and paste the line from the output to run
>> just that one scenario.
>>
>> I actually much prefer the concise notation and I would like to see RSpec
>> adopt it.
>>     
>
> I agree. RSpec will adopt it as soon as it receives your patch :)
>   

I really need to stop suggesting things on this list...  :)
>   
>> -Ben
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>>     
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>   


From dchelimsky at gmail.com  Thu Mar  5 20:11:42 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 5 Mar 2009 19:11:42 -0600
Subject: [rspec-users] where does cucumber.yml live?
In-Reply-To: <49B06EB4.90909@benmabey.com>
References: <b4f4114ecdf6846a55ebb9116ab3f797@ruby-forum.com>
	<8d961d900903050837h2941770cp1fe1c871e8a8105e@mail.gmail.com>
	<3c30da400903051238k3e0d618cm4f39505d38013218@mail.gmail.com>
	<49B04476.7030209@benmabey.com>
	<57c63afe0903051447y49c60b98i7b5cd15c0907daad@mail.gmail.com>
	<49B06EB4.90909@benmabey.com>
Message-ID: <57c63afe0903051711s18bc70f5h2b67eb82cdc2f48f@mail.gmail.com>

On Thu, Mar 5, 2009 at 6:30 PM, Ben Mabey <ben at benmabey.com> wrote:
> David Chelimsky wrote:
>>
>> On Thu, Mar 5, 2009 at 3:30 PM, Ben Mabey <ben at benmabey.com> wrote:
>>
>>>
>>> Mark Wilden wrote:
>>>
>>>>
>>>> That reminds me: Was there a reason for using <file>:<line> to run a
>>>> feature at a line instead of spec's -l <line> ?
>>>>
>>>> ///ark
>>>> _______________________________________________
>>>> rspec-users mailing list
>>>> rspec-users at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>>
>>>>
>>>
>>> I think it was to keep in line with how Cucumber outputs the backtrace in
>>> the CLI. ?So you can simply copy and paste the line from the output to
>>> run
>>> just that one scenario.
>>>
>>> I actually much prefer the concise notation and I would like to see RSpec
>>> adopt it.
>>>
>>
>> I agree. RSpec will adopt it as soon as it receives your patch :)
>>
>
> I really need to stop suggesting things on this list... ?:)

:)

From lists at ruby-forum.com  Fri Mar  6 01:52:11 2009
From: lists at ruby-forum.com (Raills Rocks)
Date: Fri, 6 Mar 2009 07:52:11 +0100
Subject: [rspec-users] Story / Redirection to static html within public
In-Reply-To: <c18843c60805220731v454ddf8dud16e34b505da6a03@mail.gmail.com>
References: <c9a6465b4fb5982ca94e73044fa36cdb@ruby-forum.com>
	<c18843c60805220731v454ddf8dud16e34b505da6a03@mail.gmail.com>
Message-ID: <180ac9d2fbff88301ccf62418ac20650@ruby-forum.com>

I have a story written using webat.
>  This story uses the above controller and it expects the redirection.
>
>  This story always fails as within the story it cannot follow the
>  redirection (Always gives a 500 error). It does not seem to be able to
>  access any public/ content within the story.

>Rails Integration tests talk directly to controllers, since there is
>no controller in front of static files there is no way to access them
>as far as I've seen.

You can redirect the static files by creating an extra file say some 
home.html or index.html and then specifying the path of your next html 
file(that you want to forward). From that file onwards the redirection 
takes place correctly without looking for controller.
I remind you home.html file must be rendered through controller action 
using
render :file=>".....path to html folder"/home.html
I hope this helps.
-- 
Posted via http://www.ruby-forum.com/.

From matt at mattwynne.net  Fri Mar  6 03:05:59 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Fri, 6 Mar 2009 08:05:59 +0000
Subject: [rspec-users] Can I construct the controller myself in
	a	controller spec?
In-Reply-To: <49AFEEAB.5020602@benmabey.com>
References: <1c319b810903042038g19ee5248m4de5e644fce7e9a1@mail.gmail.com>	<57c63afe0903042202r4cb79dc1h9697cb67889f216d@mail.gmail.com>	<011E39CE-1EF6-4E7E-A215-0995FC1A28A8@mattwynne.net>
	<57c63afe0903050626w1e9c4401k5d004729b7092fec@mail.gmail.com>
	<49AFEEAB.5020602@benmabey.com>
Message-ID: <745A0F9E-D5FA-42C7-A0E0-6E7D9677BD8B@mattwynne.net>


On 5 Mar 2009, at 15:24, Ben Mabey wrote:

> David Chelimsky wrote:
>> On Thu, Mar 5, 2009 at 3:31 AM, Matt Wynne <matt at mattwynne.net>  
>> wrote:
>> Maybe we should make this easier by providing some facility in the
>> mock framework to express the following in one statement:
>>
>> @authenticator = stub('authenticator')
>> Authenticator.stub!(:new).and_return(@authenticator)
>>
>> Sure, you could make that a one liner:
>>
>> Authenticator.stub!(:new).and_return(@authenticator =  
>> stub('authenticator')
>>
>> But I mean something like:
>>
>> @authenticator = Authenticator.stub!
>>
>> I don't think *that* is the answer - but something that concise  
>> would be nice.
>>
>> Thoughts?
>>
>> David
>>
>>
> I like the conciseness, but it isn't very clear what it is doing  
> IMO.  Perhaps something a little more intention-revealing like:
>
> @authenticator = Authenticator.stub_new!

I think I must mostly use constructor injection, as I don't really  
seem to have a pattern for this, but if I did I guess it would be  
something like this:

     extend StubbingHelpers

     describe "blah"
       before(:each) do
         @authenticator = mock_new_authenticator( :foo => bar )

which is implemented like

     def stub_new_authenticator( *args )
       result = mock(Authenticator, *args)
       Authenticator.stub!(:new).and_return(result)
       result
     end

I guess having something like that would be nice.


Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From Richard.T.Lloyd at gmail.com  Wed Mar  4 16:14:38 2009
From: Richard.T.Lloyd at gmail.com (Rick)
Date: Wed, 4 Mar 2009 13:14:38 -0800 (PST)
Subject: [rspec-users] rspec 1.1.99.10 rails 2.3 - help needed
Message-ID: <4839770d-d479-4ac3-8b9e-2a83355efe29@v5g2000prm.googlegroups.com>

I checked first and found no conversation that matched my problem so
here it is:

I'm trying to get rspec going on ruby 1.9.1 / rails 2.3.0 - here's my
current gem list:

*** LOCAL GEMS ***

actionmailer (2.3.0)
actionpack (2.3.0)
activerecord (2.3.0)
activeresource (2.3.0)
activesupport (2.3.0)
columnize (0.3.0)
cucumber (0.1.16)
daemons (1.0.10)
diff-lcs (1.1.2)
eventmachine (0.12.4)
git (1.0.5)
hoe (1.9.0)
mocha (0.9.5)
mysql (2.8.1)
pg (0.7.9.2009.02.26)
polyglot (0.2.5)
rack (0.9.1)
rails (2.3.0)
rake (0.8.3)
rspec (1.1.99.10)
rspec-rails (1.1.99.10)
rubyforge (1.0.3)
rubyist-aasm (2.0.5)
sqlite3-ruby (1.2.4)
term-ansicolor (1.0.3)
thin (1.0.0)
treetop (1.2.4)

As you can see, I followed David's instructions re rspec and rspec-
rails for rails 2.3.0.  Just by way of test, I did the following:

1) rails spec230test
2) cd spec230test
3) script/generate rspec
4) script/generate rspec_model User name:string email:string
5) rake db:migrate
6) rake spec:models --trace

and here's what I get for results:

rake spec:models --trace
(in /Users/rick/spec230test)
** Invoke spec:models (first_time)
** Invoke db:test:prepare (first_time)
** Invoke db:abort_if_pending_migrations (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:abort_if_pending_migrations
** Execute db:test:prepare
** Invoke db:test:load (first_time)
** Invoke db:test:purge (first_time)
** Invoke environment
** Execute db:test:purge
** Execute db:test:load
** Invoke db:schema:load (first_time)
** Invoke environment
** Execute db:schema:load
** Execute spec:models
/opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/test_case.rb:6: warning: already initialized constant
Mocha
/opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:440:in `rescue in
load_missing_constant': uninitialized constant Mocha::Standalone
(NameError)
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:436:in `load_missing_constant'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:80:in `const_missing_with_dependencies'
	from /opt/local/lib/ruby/gems/1.9.1/gems/mocha-0.9.5/lib/mocha.rb:
30:in `<class:TestCase>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/mocha-0.9.5/lib/mocha.rb:
29:in `<class:Unit>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/mocha-0.9.5/lib/mocha.rb:
28:in `<module:MiniTest>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/mocha-0.9.5/lib/mocha.rb:
27:in `<top (required)>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/test_case.rb:3:in `<top (required)>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/actionpack-2.3.0/lib/
action_controller/integration.rb:3:in `<top (required)>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-rails-1.1.99.10/lib/
spec/rails.rb:11:in `<top (required)>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /Users/rick/spec230test/spec/spec_helper.rb:6:in `<top (required)
>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /Users/rick/spec230test/spec/models/user_spec.rb:1:in `<top
(required)>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:147:in
`load_without_new_constant_marking'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:147:in `load_with_new_constant_marking'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner/example_group_runner.rb:15:in `block in load_files'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner/example_group_runner.rb:14:in `each'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner/example_group_runner.rb:14:in `load_files'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner/options.rb:87:in `run_examples'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner.rb:61:in `run'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner.rb:44:in `block in autorun'
/opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require': no such file to load
-- test/unit/testcase (MissingSourceFile)
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/test_case.rb:10:in `<top (required)>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/actionpack-2.3.0/lib/
action_controller/integration.rb:3:in `<top (required)>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-rails-1.1.99.10/lib/
spec/rails.rb:11:in `<top (required)>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
active_support/dependencies.rb:158:in `require'
	from /Users/rick/spec230test/spec/spec_helper.rb:6:in `<top (required)
>'
	from /Users/rick/spec230test/spec/models/user_spec.rb:1:in `require'
	from /Users/rick/spec230test/spec/models/user_spec.rb:1:in `<top
(required)>'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner/example_group_runner.rb:15:in `load'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner/example_group_runner.rb:15:in `block in load_files'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner/example_group_runner.rb:14:in `each'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner/example_group_runner.rb:14:in `load_files'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner/options.rb:87:in `run_examples'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
runner/command_line.rb:9:in `run'
	from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/bin/spec:
4:in `<main>'
rake aborted!
Command /opt/local/bin/ruby -I"/opt/local/lib/ruby/gems/1.9.1/gems/
rspec-1.1.99.10/lib"  "/opt/local/lib/ruby/gems/1.9.1/gems/
rspec-1.1.99.10/bin/spec" "spec/models/user_spec.rb" --options "/Users/
rick/spec230test/spec/spec.opts" failed
/opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/rake/
spectask.rb:174:in `block (2 levels) in define'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1090:in
`verbose'
/opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/rake/
spectask.rb:150:in `block in define'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:617:in
`call'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:617:in
`block in execute'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:612:in
`each'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:612:in
`execute'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:578:in
`block in invoke_with_call_chain'
/opt/local/lib/ruby/1.9.1/monitor.rb:190:in `mon_synchronize'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:571:in
`invoke_with_call_chain'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:564:in
`invoke'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:2019:in
`invoke_task'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1997:in
`block (2 levels) in top_level'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1997:in
`each'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1997:in
`block in top_level'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:2036:in
`standard_exception_handling'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1991:in
`top_level'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1970:in
`block in run'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:2036:in
`standard_exception_handling'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1967:in
`run'
/opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/bin/rake:31:in `<top
(required)>'
/opt/local/bin/rake:19:in `load'
/opt/local/bin/rake:19:in `<main>'

Compilation exited abnormally with code 1 at Wed Mar  4 11:07:37

Just by way of sanity check, in a directory that contained both
user_spec.rb and user.rb from above, I ran "spec user_spec.rb" and got
the same result.

Any thoughts on what I should try next?  BTW, the same sequence of
steps run in a Ruby1.8.7/Rails2.2.2 environment works fine of course.

thanks in advance,
Rick

From vora.manasi at gmail.com  Thu Mar  5 07:49:38 2009
From: vora.manasi at gmail.com (Manasi v)
Date: Thu, 5 Mar 2009 04:49:38 -0800 (PST)
Subject: [rspec-users] Cucumber + Webrat + Selenium + ActionMailer
In-Reply-To: <54bf7268cc8b3140727473d005e4bd29@ruby-forum.com>
References: <3aa9e123e627fd97b4d75bd5c2ca0fc4@ruby-forum.com>
	<499C693D.9090006@benmabey.com>
	<1fb4df0902181515y6d95221bw87c4706f3987f0ce@mail.gmail.com>
	<499C9955.8080804@benmabey.com>
	<1fb4df0902182021m497b243ap95b76303d7842a04@mail.gmail.com>
	<499CEA87.5000804@benmabey.com>
	<1fb4df0902182144i4d3f655eh3cf7befa27a905a5@mail.gmail.com>
	<9fa97fb652c4210d767e16757a4610e5@ruby-forum.com>
	<54bf7268cc8b3140727473d005e4bd29@ruby-forum.com>
Message-ID: <22350981.post@talk.nabble.com>




> Yeap everything worked like a charm, once again checking email contents 
> like there is no tomorrow ;-)
> 
> Rai
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
> 
> 


Hi Rai,

Good that you have found a solution.. 

but I still don't understand why you want to test sending mails from the
browser. In my project, we use Cucumber + Webrat for writing functional
features.
and Cucumber + selenium for acceptance features.

Functional tests can enable ruby code and test for the number of mails sent
and to whom, etc
Acdeptance only tests what the user would see..

Let me know if it makes sense.. and it would be great if you could elaborate
on your purpose of testing mails from the browser...

Thanks,
Manasi

-- 
View this message in context: http://www.nabble.com/Cucumber-%2B-Webrat-%2B-Selenium-%2B-ActionMailer-tp22086863p22350981.html
Sent from the rspec-users mailing list archive at Nabble.com.


From MAwiniarski at gmail.com  Wed Mar  4 04:55:25 2009
From: MAwiniarski at gmail.com (MAwiniarski)
Date: Wed, 4 Mar 2009 01:55:25 -0800 (PST)
Subject: [rspec-users] be_valid (validates_format_of ..., :on => :create)
In-Reply-To: <57c63afe0903020838g4013ac5u91637f525f046158@mail.gmail.com>
References: <38f994ca-7da0-43cc-a013-34e51a5cca7e@j8g2000yql.googlegroups.com>
	<6F193A20-D635-44D0-BB30-11F8341D12AA@gmail.com>
	<57c63afe0903020750g5936966cg85cf715a5d8c980a@mail.gmail.com> 
	<937E5EFE-C47A-433F-AD35-A76889F35434@gmail.com>
	<57c63afe0903020838g4013ac5u91637f525f046158@mail.gmail.com>
Message-ID: <e14dc202-b869-4fb9-a70e-1ca54461233b@h5g2000yqh.googlegroups.com>


> FWIW, the OP's code says :on => :create. I also happened to seehttp://mawiniarski.wordpress.com/2009/02/28/rspec-validation-on-create/,
> which reinforced for me that this is about validating on create, not
> general validation.

I've figured that out after starting a topic.

From MAwiniarski at gmail.com  Thu Mar  5 08:40:14 2009
From: MAwiniarski at gmail.com (MAwiniarski)
Date: Thu, 5 Mar 2009 05:40:14 -0800 (PST)
Subject: [rspec-users] have_tag + quantity - question
Message-ID: <44088ce1-2ad9-4fd9-a996-9d9ab6977752@w34g2000yqm.googlegroups.com>

Greetings,

Is there a way to check quantity of tags?

Something like this:

response.should have_tag('div').quantity(4)

Thanks.

From kyleoba at gmail.com  Thu Mar  5 17:02:20 2009
From: kyleoba at gmail.com (mudphone)
Date: Thu, 5 Mar 2009 14:02:20 -0800 (PST)
Subject: [rspec-users] Trouble with (Rails) Nested Model Directories
Message-ID: <0285e7e0-a22e-4a42-b328-0c2677c4d8f6@d36g2000prf.googlegroups.com>

Hi folks,

In order to bring some order to the many model classes that I have
under /app/models, I'm created a new directory (for example):
/app/models/nestdir

I've added the required configuration line in environment.rb:
  config.load_paths += %W( #{RAILS_ROOT}/app/models/nestdir )

But, when I run my specs, I get an error such as:
...
dependencies.rb:428:in `load_missing_constant': Expected RAILS_ROOT/
app/models/nestdir/my_model.rb to define Nestdir::MyModel (LoadError)
...

>From my understanding, the models in the dir listed in
config.load_paths should be available in the root Rails namespace.  Is
this not how rspec handles things?

Is there a standard way of setting up specs for nested model
directories?  The models are not nested within a parent module (like
Nestdir, which would have matched the directory name).

Thanks,
Kyle

From dchelimsky at gmail.com  Fri Mar  6 03:52:53 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 6 Mar 2009 02:52:53 -0600
Subject: [rspec-users] Trouble with (Rails) Nested Model Directories
In-Reply-To: <0285e7e0-a22e-4a42-b328-0c2677c4d8f6@d36g2000prf.googlegroups.com>
References: <0285e7e0-a22e-4a42-b328-0c2677c4d8f6@d36g2000prf.googlegroups.com>
Message-ID: <57c63afe0903060052s25e94de4n4ac768c77518f8e@mail.gmail.com>

On Thu, Mar 5, 2009 at 4:02 PM, mudphone <kyleoba at gmail.com> wrote:
> Hi folks,
>
> In order to bring some order to the many model classes that I have
> under /app/models, I'm created a new directory (for example):
> /app/models/nestdir
>
> I've added the required configuration line in environment.rb:
> ?config.load_paths += %W( #{RAILS_ROOT}/app/models/nestdir )
>
> But, when I run my specs, I get an error such as:
> ...
> dependencies.rb:428:in `load_missing_constant': Expected RAILS_ROOT/
> app/models/nestdir/my_model.rb to define Nestdir::MyModel (LoadError)
> ...
>
> >From my understanding, the models in the dir listed in
> config.load_paths should be available in the root Rails namespace. ?Is
> this not how rspec handles things?
>
> Is there a standard way of setting up specs for nested model
> directories? ?The models are not nested within a parent module (like
> Nestdir, which would have matched the directory name).

I just created a fresh rails-2.3.0 app w/ the latest rspec (built from
git - 1.1.99.11) and not only was able to include a nested model, I
was able to run the specs under each of the following conditions:

* neither spec nor model are namespaced

describe User do
end

class User < ActiveRecord::Base
end

* model and spec are both namespaced

module Admin
  describe User do
  end
end

module Admin
  class User < ActiveRecord::Base
  end
end

* config is modifed per your example above
* config is NOT modifed per your example above

What versions of rspec and rails are you using?

>
> Thanks,
> Kyle
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Fri Mar  6 03:55:33 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 6 Mar 2009 02:55:33 -0600
Subject: [rspec-users] have_tag + quantity - question
In-Reply-To: <44088ce1-2ad9-4fd9-a996-9d9ab6977752@w34g2000yqm.googlegroups.com>
References: <44088ce1-2ad9-4fd9-a996-9d9ab6977752@w34g2000yqm.googlegroups.com>
Message-ID: <57c63afe0903060055v260fd1behb8dbf81e84278b19@mail.gmail.com>

On Thu, Mar 5, 2009 at 7:40 AM, MAwiniarski <MAwiniarski at gmail.com> wrote:
> Greetings,
>
> Is there a way to check quantity of tags?
>
> Something like this:
>
> response.should have_tag('div').quantity(4)

response.should have_tag('div', 4)

Check the assert_select docs (have_tag wraps it) at
http://api.rubyonrails.org/classes/ActionController/Assertions/SelectorAssertions.html#M000547

Cheers,
David

>
> Thanks.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Fri Mar  6 04:52:45 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 6 Mar 2009 03:52:45 -0600
Subject: [rspec-users] rspec 1.1.99.10 rails 2.3 - help needed
In-Reply-To: <4839770d-d479-4ac3-8b9e-2a83355efe29@v5g2000prm.googlegroups.com>
References: <4839770d-d479-4ac3-8b9e-2a83355efe29@v5g2000prm.googlegroups.com>
Message-ID: <57c63afe0903060152v67b90319oeff1d78e83e27536@mail.gmail.com>

On Wed, Mar 4, 2009 at 3:14 PM, Rick <Richard.T.Lloyd at gmail.com> wrote:
> I checked first and found no conversation that matched my problem so
> here it is:
>
> I'm trying to get rspec going on ruby 1.9.1 / rails 2.3.0 - here's my
> current gem list:

rspec-rails does not yet work with Ruby 1.9.1 - this is one item on a
rather long list. As of the latest code in git, there are no errors or
failures, but there is simply no feedback whatsoever.

Patches welcome!

>
> *** LOCAL GEMS ***
>
> actionmailer (2.3.0)
> actionpack (2.3.0)
> activerecord (2.3.0)
> activeresource (2.3.0)
> activesupport (2.3.0)
> columnize (0.3.0)
> cucumber (0.1.16)
> daemons (1.0.10)
> diff-lcs (1.1.2)
> eventmachine (0.12.4)
> git (1.0.5)
> hoe (1.9.0)
> mocha (0.9.5)
> mysql (2.8.1)
> pg (0.7.9.2009.02.26)
> polyglot (0.2.5)
> rack (0.9.1)
> rails (2.3.0)
> rake (0.8.3)
> rspec (1.1.99.10)
> rspec-rails (1.1.99.10)
> rubyforge (1.0.3)
> rubyist-aasm (2.0.5)
> sqlite3-ruby (1.2.4)
> term-ansicolor (1.0.3)
> thin (1.0.0)
> treetop (1.2.4)
>
> As you can see, I followed David's instructions re rspec and rspec-
> rails for rails 2.3.0. ?Just by way of test, I did the following:
>
> 1) rails spec230test
> 2) cd spec230test
> 3) script/generate rspec
> 4) script/generate rspec_model User name:string email:string
> 5) rake db:migrate
> 6) rake spec:models --trace
>
> and here's what I get for results:
>
> rake spec:models --trace
> (in /Users/rick/spec230test)
> ** Invoke spec:models (first_time)
> ** Invoke db:test:prepare (first_time)
> ** Invoke db:abort_if_pending_migrations (first_time)
> ** Invoke environment (first_time)
> ** Execute environment
> ** Execute db:abort_if_pending_migrations
> ** Execute db:test:prepare
> ** Invoke db:test:load (first_time)
> ** Invoke db:test:purge (first_time)
> ** Invoke environment
> ** Execute db:test:purge
> ** Execute db:test:load
> ** Invoke db:schema:load (first_time)
> ** Invoke environment
> ** Execute db:schema:load
> ** Execute spec:models
> /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/test_case.rb:6: warning: already initialized constant
> Mocha
> /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:440:in `rescue in
> load_missing_constant': uninitialized constant Mocha::Standalone
> (NameError)
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:436:in `load_missing_constant'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:80:in `const_missing_with_dependencies'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/mocha-0.9.5/lib/mocha.rb:
> 30:in `<class:TestCase>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/mocha-0.9.5/lib/mocha.rb:
> 29:in `<class:Unit>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/mocha-0.9.5/lib/mocha.rb:
> 28:in `<module:MiniTest>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/mocha-0.9.5/lib/mocha.rb:
> 27:in `<top (required)>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/test_case.rb:3:in `<top (required)>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/actionpack-2.3.0/lib/
> action_controller/integration.rb:3:in `<top (required)>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-rails-1.1.99.10/lib/
> spec/rails.rb:11:in `<top (required)>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /Users/rick/spec230test/spec/spec_helper.rb:6:in `<top (required)
>>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /Users/rick/spec230test/spec/models/user_spec.rb:1:in `<top
> (required)>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:147:in
> `load_without_new_constant_marking'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:147:in `load_with_new_constant_marking'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner/example_group_runner.rb:15:in `block in load_files'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner/example_group_runner.rb:14:in `each'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner/example_group_runner.rb:14:in `load_files'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner/options.rb:87:in `run_examples'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner.rb:61:in `run'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner.rb:44:in `block in autorun'
> /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require': no such file to load
> -- test/unit/testcase (MissingSourceFile)
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/test_case.rb:10:in `<top (required)>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/actionpack-2.3.0/lib/
> action_controller/integration.rb:3:in `<top (required)>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-rails-1.1.99.10/lib/
> spec/rails.rb:11:in `<top (required)>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/activesupport-2.3.0/lib/
> active_support/dependencies.rb:158:in `require'
> ? ? ? ?from /Users/rick/spec230test/spec/spec_helper.rb:6:in `<top (required)
>>'
> ? ? ? ?from /Users/rick/spec230test/spec/models/user_spec.rb:1:in `require'
> ? ? ? ?from /Users/rick/spec230test/spec/models/user_spec.rb:1:in `<top
> (required)>'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner/example_group_runner.rb:15:in `load'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner/example_group_runner.rb:15:in `block in load_files'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner/example_group_runner.rb:14:in `each'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner/example_group_runner.rb:14:in `load_files'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner/options.rb:87:in `run_examples'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/
> runner/command_line.rb:9:in `run'
> ? ? ? ?from /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/bin/spec:
> 4:in `<main>'
> rake aborted!
> Command /opt/local/bin/ruby -I"/opt/local/lib/ruby/gems/1.9.1/gems/
> rspec-1.1.99.10/lib" ?"/opt/local/lib/ruby/gems/1.9.1/gems/
> rspec-1.1.99.10/bin/spec" "spec/models/user_spec.rb" --options "/Users/
> rick/spec230test/spec/spec.opts" failed
> /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/rake/
> spectask.rb:174:in `block (2 levels) in define'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1090:in
> `verbose'
> /opt/local/lib/ruby/gems/1.9.1/gems/rspec-1.1.99.10/lib/spec/rake/
> spectask.rb:150:in `block in define'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:617:in
> `call'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:617:in
> `block in execute'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:612:in
> `each'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:612:in
> `execute'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:578:in
> `block in invoke_with_call_chain'
> /opt/local/lib/ruby/1.9.1/monitor.rb:190:in `mon_synchronize'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:571:in
> `invoke_with_call_chain'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:564:in
> `invoke'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:2019:in
> `invoke_task'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1997:in
> `block (2 levels) in top_level'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1997:in
> `each'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1997:in
> `block in top_level'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:2036:in
> `standard_exception_handling'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1991:in
> `top_level'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1970:in
> `block in run'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:2036:in
> `standard_exception_handling'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/lib/rake.rb:1967:in
> `run'
> /opt/local/lib/ruby/gems/1.9.1/gems/rake-0.8.3/bin/rake:31:in `<top
> (required)>'
> /opt/local/bin/rake:19:in `load'
> /opt/local/bin/rake:19:in `<main>'
>
> Compilation exited abnormally with code 1 at Wed Mar ?4 11:07:37
>
> Just by way of sanity check, in a directory that contained both
> user_spec.rb and user.rb from above, I ran "spec user_spec.rb" and got
> the same result.
>
> Any thoughts on what I should try next? ?BTW, the same sequence of
> steps run in a Ruby1.8.7/Rails2.2.2 environment works fine of course.
>
> thanks in advance,
> Rick
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Fri Mar  6 05:59:15 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 6 Mar 2009 04:59:15 -0600
Subject: [rspec-users] Help make rspec-1.2 a smooth upgrade
Message-ID: <57c63afe0903060259g33679ae6odd05ee14e670fe67@mail.gmail.com>

Hi all,

I'm planning to release rspec-1.2 and rspec-rails-1.2 shortly after
rails-2.3 goes final (rails-2.3.1 was just released as RC2). There are
a couple of loose ends right now, and I need your help in two
important areas. I've curtailed releasing github gems, so please
clone, build and install the latest [1] if you wish to help out.

== Testing the release

As rails' internals have changed and rspec-rails has kept up with
those changes, I've also been taking the opportunity to clean up much
of rspec-rails' internals (along with those of rspec core). While the
public API has remain *mostly* unchanged [2], the changes to the
internals present some risk for any extension libraries or any of your
own customizations that monkey patch internals. To this end, it would
be very helpful if you would run your rails apps with the latest
rspec/rspec-rails code, and let me know (via reports to
http://rspec.lighthouseapp.com) if you run into any problems.

== Ruby 1.9

RSpec core's specs are all running against ruby 1.9 now. Not so much
with rspec-rails. With rails-2.3.1 (RC2), rspec/rspec-rails-1.1.99.12
[1] and ruby-1.9.1, there is zero feedback. No failures. No errors.
Just nothing.

It would be most appreciated by many if the bold among you could help
to resolve this issue and get rspec-rails working with ruby-1.9.1.

Thanks in advance for your assistance.

Cheers,
David

[1] rspec and rspec-rails > 1.1.99.9 require that you clone the github
repo and build/install locally. Instructions:
http://wiki.github.com/dchelimsky/rspec/releases-and-gems

[2] There is some rspec-rails code that needlessly duplicates
functionality already available in rails' testing framework. To reduce
the maintenance burden, as changes to rails cause problems with
rspec-rails, I've been looking for opportunities to access rails via
public APIs rather than internals. In some cases, this resulted in
changes to rspec-rails. I've documented what I know in
Upgrade.markdown in the root of the rspec-rails source.

From lists at ruby-forum.com  Fri Mar  6 06:23:19 2009
From: lists at ruby-forum.com (Raimond Garcia)
Date: Fri, 6 Mar 2009 12:23:19 +0100
Subject: [rspec-users] Cucumber + Webrat + Selenium + ActionMailer
In-Reply-To: <22350981.post@talk.nabble.com>
References: <3aa9e123e627fd97b4d75bd5c2ca0fc4@ruby-forum.com>
	<499C693D.9090006@benmabey.com>
	<1fb4df0902181515y6d95221bw87c4706f3987f0ce@mail.gmail.com>
	<499C9955.8080804@benmabey.com>
	<1fb4df0902182021m497b243ap95b76303d7842a04@mail.gmail.com>
	<499CEA87.5000804@benmabey.com>
	<1fb4df0902182144i4d3f655eh3cf7befa27a905a5@mail.gmail.com>
	<9fa97fb652c4210d767e16757a4610e5@ruby-forum.com>
	<54bf7268cc8b3140727473d005e4bd29@ruby-forum.com>
	<22350981.post@talk.nabble.com>
Message-ID: <ff4884304918f2ac150225482c969d43@ruby-forum.com>

Manasi Vora wrote:
>> 
>> 
> 
> 
> Hi Rai,
> 
> Good that you have found a solution..
> 
> but I still don't understand why you want to test sending mails from the
> browser. In my project, we use Cucumber + Webrat for writing functional
> features.
> and Cucumber + selenium for acceptance features.
> 
> Functional tests can enable ruby code and test for the number of mails 
> sent
> and to whom, etc
> Acdeptance only tests what the user would see..
> 
> Let me know if it makes sense.. and it would be great if you could 
> elaborate
> on your purpose of testing mails from the browser...
> 
> Thanks,
> Manasi

Hi Manasi,

We have a bit of both, sometimes we can test email sending with Cucumber 
+ Webrat, but in this particular case, the feature that sent out emails 
also used Javascript.

We could have split the feature in two, one to test the Javascript with 
a Selenium feature and one to test the emails with a Webrat feature, but 
IMHO adding a couple of steps to the selenium feature to check for 
emails, is a good choice to help to clearly see the whole intent of the 
feature.

Rai
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Fri Mar  6 07:27:42 2009
From: lists at ruby-forum.com (Tom Ten thij)
Date: Fri, 6 Mar 2009 13:27:42 +0100
Subject: [rspec-users] Cucumber 0.2 final release date?
In-Reply-To: <8d961d900902230636te143bc6o92ca13f709688ee9@mail.gmail.com>
References: <7ac2300c0902190749x3d659b40w7cc84e5a6f8aedea@mail.gmail.com>
	<8d961d900902230636te143bc6o92ca13f709688ee9@mail.gmail.com>
Message-ID: <3202c5a31a4c97a8dcc16b22d901ef18@ruby-forum.com>


> I'm afraid I can't give a release date. 0.2 is fixed(ish) scope, and
> therefore time can't be fixed at the same time. I have a lot of travel
> the next month, so it will take a least a month I'm afraid.

I know I for one would sure like to see 0.2 come out soon. The scope of 
the two 0.2 tickets in lighthouse seem a bit big. Are there any tasks 
that I could assist on?

Tom.
-- 
Posted via http://www.ruby-forum.com/.

From mark at mwilden.com  Fri Mar  6 10:03:03 2009
From: mark at mwilden.com (Mark Wilden)
Date: Fri, 6 Mar 2009 07:03:03 -0800
Subject: [rspec-users] have_tag + quantity - question
In-Reply-To: <44088ce1-2ad9-4fd9-a996-9d9ab6977752@w34g2000yqm.googlegroups.com>
References: <44088ce1-2ad9-4fd9-a996-9d9ab6977752@w34g2000yqm.googlegroups.com>
Message-ID: <3c30da400903060703o3911ddb9n95c6f560f594f588@mail.gmail.com>

On Thu, Mar 5, 2009 at 5:40 AM, MAwiniarski <MAwiniarski at gmail.com> wrote:
> Greetings,
>
> Is there a way to check quantity of tags?
>
> Something like this:
>
> response.should have_tag('div').quantity(4)

Another great resource is
http://labnotes.org/svn/public/ruby/rails_plugins/assert_select/cheat/assert_select.html

///ark

From stevemolitor at gmail.com  Fri Mar  6 11:23:52 2009
From: stevemolitor at gmail.com (Steve Molitor)
Date: Fri, 6 Mar 2009 10:23:52 -0600
Subject: [rspec-users] Webrat - Fill in text field by id
Message-ID: <3e21ad60903060823t901c6f5jad329fd5acc6e278@mail.gmail.com>

Is there a way to locate and 'fill in' a text field (or check a check box,
select an option, etc.) by id?  It seems that the fill_in method takes
either the text of the label pointing to the field or the field name.  The
are cases when writing cucumber steps when using the HTML id of the input
element would be easier, especially when a page has multiple forms with the
same labels and input names.
Thanks,

Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090306/6b4db7f4/attachment-0001.html>

From zach.dennis at gmail.com  Fri Mar  6 11:24:35 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Fri, 6 Mar 2009 11:24:35 -0500
Subject: [rspec-users] Can I construct the controller myself in a
	controller spec?
In-Reply-To: <745A0F9E-D5FA-42C7-A0E0-6E7D9677BD8B@mattwynne.net>
References: <1c319b810903042038g19ee5248m4de5e644fce7e9a1@mail.gmail.com>
	<57c63afe0903042202r4cb79dc1h9697cb67889f216d@mail.gmail.com>
	<011E39CE-1EF6-4E7E-A215-0995FC1A28A8@mattwynne.net>
	<57c63afe0903050626w1e9c4401k5d004729b7092fec@mail.gmail.com>
	<49AFEEAB.5020602@benmabey.com>
	<745A0F9E-D5FA-42C7-A0E0-6E7D9677BD8B@mattwynne.net>
Message-ID: <85d99afe0903060824q2e8d409fh916ae1e6ce6d7471@mail.gmail.com>

On Fri, Mar 6, 2009 at 3:05 AM, Matt Wynne <matt at mattwynne.net> wrote:
>
> On 5 Mar 2009, at 15:24, Ben Mabey wrote:
>
>> David Chelimsky wrote:
>>>
>>> On Thu, Mar 5, 2009 at 3:31 AM, Matt Wynne <matt at mattwynne.net> wrote:
>>> Maybe we should make this easier by providing some facility in the
>>> mock framework to express the following in one statement:
>>>
>>> @authenticator = stub('authenticator')
>>> Authenticator.stub!(:new).and_return(@authenticator)
>>>
>>> Sure, you could make that a one liner:
>>>
>>> Authenticator.stub!(:new).and_return(@authenticator =
>>> stub('authenticator')
>>>
>>> But I mean something like:
>>>
>>> @authenticator = Authenticator.stub!
>>>
>>> I don't think *that* is the answer - but something that concise would be
>>> nice.
>>>
>>> Thoughts?
>>>
>>> David
>>>
>>>
>> I like the conciseness, but it isn't very clear what it is doing IMO.
>> ?Perhaps something a little more intention-revealing like:
>>
>> @authenticator = Authenticator.stub_new!
>
> I think I must mostly use constructor injection, as I don't really seem to
> have a pattern for this, but if I did I guess it would be something like
> this:
>
> ? ?extend StubbingHelpers
>
> ? ?describe "blah"
> ? ? ?before(:each) do
> ? ? ? ?@authenticator = mock_new_authenticator( :foo => bar )
>
> which is implemented like
>
> ? ?def stub_new_authenticator( *args )
> ? ? ?result = mock(Authenticator, *args)
> ? ? ?Authenticator.stub!(:new).and_return(result)
> ? ? ?result
> ? ?end
>
> I guess having something like that would be nice.

This is how I do it,

Zach


>
>
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From hayafirst at gmail.com  Fri Mar  6 11:55:36 2009
From: hayafirst at gmail.com (Yi)
Date: Fri, 6 Mar 2009 10:55:36 -0600
Subject: [rspec-users] Webrat - Fill in text field by id
In-Reply-To: <3e21ad60903060823t901c6f5jad329fd5acc6e278@mail.gmail.com>
References: <3e21ad60903060823t901c6f5jad329fd5acc6e278@mail.gmail.com>
Message-ID: <ee6f48c00903060855s64dfcfa4j92073dd20533b865@mail.gmail.com>

It does take id. At least in the trunk webrat

On Fri, Mar 6, 2009 at 10:23 AM, Steve Molitor <stevemolitor at gmail.com>wrote:

> Is there a way to locate and 'fill in' a text field (or check a check box,
> select an option, etc.) by id?  It seems that the fill_in method takes
> either the text of the label pointing to the field or the field name.  The
> are cases when writing cucumber steps when using the HTML id of the input
> element would be easier, especially when a page has multiple forms with the
> same labels and input names.
> Thanks,
>
> Steve
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090306/8b158fab/attachment.html>

From lists at ruby-forum.com  Fri Mar  6 12:03:48 2009
From: lists at ruby-forum.com (James Byrne)
Date: Fri, 6 Mar 2009 18:03:48 +0100
Subject: [rspec-users] Webrat - Fill in text field by id
In-Reply-To: <3e21ad60903060823t901c6f5jad329fd5acc6e278@mail.gmail.com>
References: <3e21ad60903060823t901c6f5jad329fd5acc6e278@mail.gmail.com>
Message-ID: <baa63be43dd40508eeaf4fdce23f6b20@ruby-forum.com>

Steve Molitor wrote:
> Is there a way to locate and 'fill in' a text field (or check a check 
> box,
> select an option, etc.) by id?  It seems that the fill_in method takes
> either the text of the label pointing to the field or the field name. 
> The
> are cases when writing cucumber steps when using the HTML id of the 
> input
> element would be easier, especially when a page has multiple forms with 
> the
> same labels and input names.
> Thanks,
> 
> Steve


Yes, just provide the text of the id selector, do not add anything else.

So, for an id="test_this_id" on a button you can write in your 
test/definition:

click_button("test-this_id")
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Fri Mar  6 12:04:23 2009
From: lists at ruby-forum.com (James Byrne)
Date: Fri, 6 Mar 2009 18:04:23 +0100
Subject: [rspec-users] Webrat - Fill in text field by id
In-Reply-To: <baa63be43dd40508eeaf4fdce23f6b20@ruby-forum.com>
References: <3e21ad60903060823t901c6f5jad329fd5acc6e278@mail.gmail.com>
	<baa63be43dd40508eeaf4fdce23f6b20@ruby-forum.com>
Message-ID: <f2055537eeb1f4d4bf2cafa5c4fcd7e3@ruby-forum.com>

James Byrne wrote:
S/B
> 
> click_button("test_this_id")

-- 
Posted via http://www.ruby-forum.com/.

From stevemolitor at gmail.com  Fri Mar  6 14:22:06 2009
From: stevemolitor at gmail.com (Steve Molitor)
Date: Fri, 6 Mar 2009 13:22:06 -0600
Subject: [rspec-users] Webrat - Fill in text field by id
In-Reply-To: <baa63be43dd40508eeaf4fdce23f6b20@ruby-forum.com>
References: <3e21ad60903060823t901c6f5jad329fd5acc6e278@mail.gmail.com>
	<baa63be43dd40508eeaf4fdce23f6b20@ruby-forum.com>
Message-ID: <3e21ad60903061122k1dcf85b4q3feef247a70555a8@mail.gmail.com>

Well I'm reading the 0.4.2 webrat rdoc for fill_in, at it says:
"field can be either the value of a name attribute (i.e. user[email]) or the
text inside a <label>element that points at the <input> field."

Does it also try the id?

Steve

On Fri, Mar 6, 2009 at 11:03 AM, James Byrne <lists at ruby-forum.com> wrote:

> Steve Molitor wrote:
> > Is there a way to locate and 'fill in' a text field (or check a check
> > box,
> > select an option, etc.) by id?  It seems that the fill_in method takes
> > either the text of the label pointing to the field or the field name.
> > The
> > are cases when writing cucumber steps when using the HTML id of the
> > input
> > element would be easier, especially when a page has multiple forms with
> > the
> > same labels and input names.
> > Thanks,
> >
> > Steve
>
>
> Yes, just provide the text of the id selector, do not add anything else.
>
> So, for an id="test_this_id" on a button you can write in your
> test/definition:
>
> click_button("test-this_id")
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090306/cc5319b3/attachment.html>

From sfeley at gmail.com  Fri Mar  6 15:33:40 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Fri, 6 Mar 2009 15:33:40 -0500
Subject: [rspec-users] Webrat - Fill in text field by id
In-Reply-To: <3e21ad60903061122k1dcf85b4q3feef247a70555a8@mail.gmail.com>
References: <3e21ad60903060823t901c6f5jad329fd5acc6e278@mail.gmail.com>
	<baa63be43dd40508eeaf4fdce23f6b20@ruby-forum.com>
	<3e21ad60903061122k1dcf85b4q3feef247a70555a8@mail.gmail.com>
Message-ID: <1fb4df0903061233x62b9d152n9ce72140476ecca5@mail.gmail.com>

On Fri, Mar 6, 2009 at 2:22 PM, Steve Molitor <stevemolitor at gmail.com> wrote:
> Well I'm reading the 0.4.2 webrat rdoc for fill_in, at it says:
> "field?can be either the value of a name attribute (i.e.?user[email]) or the
> text inside a?<label>element that points at the?<input>?field."
> Does it also try the id?

Try it!  (Or read the code.  Or both.)



-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From sfeley at gmail.com  Fri Mar  6 15:40:36 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Fri, 6 Mar 2009 15:40:36 -0500
Subject: [rspec-users] have_tag + quantity - question
In-Reply-To: <57c63afe0903060055v260fd1behb8dbf81e84278b19@mail.gmail.com>
References: <44088ce1-2ad9-4fd9-a996-9d9ab6977752@w34g2000yqm.googlegroups.com>
	<57c63afe0903060055v260fd1behb8dbf81e84278b19@mail.gmail.com>
Message-ID: <1fb4df0903061240v4260f1bdw5a5e09ed965f7c53@mail.gmail.com>

On Fri, Mar 6, 2009 at 3:55 AM, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Thu, Mar 5, 2009 at 7:40 AM, MAwiniarski <MAwiniarski at gmail.com> wrote:
>>
>> Is there a way to check quantity of tags?
>
> response.should have_tag('div', 4)

Ooh!  Thank you; I wish I'd known that before.  All this time I've
been using annoyingly complicated xpath tests:

Then /^I should see (\d+) people$/ do |num|
  response.should have_xpath("//*[count(*[contains(@class,'person')])=#{num}]")
end


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From hayafirst at gmail.com  Fri Mar  6 15:50:58 2009
From: hayafirst at gmail.com (Yi)
Date: Fri, 6 Mar 2009 14:50:58 -0600
Subject: [rspec-users] Webrat - Fill in text field by id
In-Reply-To: <3e21ad60903061122k1dcf85b4q3feef247a70555a8@mail.gmail.com>
References: <3e21ad60903060823t901c6f5jad329fd5acc6e278@mail.gmail.com>
	<baa63be43dd40508eeaf4fdce23f6b20@ruby-forum.com>
	<3e21ad60903061122k1dcf85b4q3feef247a70555a8@mail.gmail.com>
Message-ID: <ee6f48c00903061250n21e581e0wbe95308929051deb@mail.gmail.com>

Could you just try it?

On Fri, Mar 6, 2009 at 1:22 PM, Steve Molitor <stevemolitor at gmail.com>wrote:

> Well I'm reading the 0.4.2 webrat rdoc for fill_in, at it says:
> "field can be either the value of a name attribute (i.e. user[email]) or
> the text inside a <label>element that points at the <input> field."
>
> Does it also try the id?
>
> Steve
>
> On Fri, Mar 6, 2009 at 11:03 AM, James Byrne <lists at ruby-forum.com> wrote:
>
>> Steve Molitor wrote:
>> > Is there a way to locate and 'fill in' a text field (or check a check
>> > box,
>> > select an option, etc.) by id?  It seems that the fill_in method takes
>> > either the text of the label pointing to the field or the field name.
>> > The
>> > are cases when writing cucumber steps when using the HTML id of the
>> > input
>> > element would be easier, especially when a page has multiple forms with
>> > the
>> > same labels and input names.
>> > Thanks,
>> >
>> > Steve
>>
>>
>> Yes, just provide the text of the id selector, do not add anything else.
>>
>> So, for an id="test_this_id" on a button you can write in your
>> test/definition:
>>
>> click_button("test-this_id")
>> --
>> Posted via http://www.ruby-forum.com/.
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090306/04f99e50/attachment-0001.html>

From patnakajima at gmail.com  Fri Mar  6 17:42:24 2009
From: patnakajima at gmail.com (Pat Nakajima)
Date: Fri, 6 Mar 2009 17:42:24 -0500
Subject: [rspec-users] have_tag + quantity - question
In-Reply-To: <1fb4df0903061240v4260f1bdw5a5e09ed965f7c53@mail.gmail.com>
References: <44088ce1-2ad9-4fd9-a996-9d9ab6977752@w34g2000yqm.googlegroups.com>
	<57c63afe0903060055v260fd1behb8dbf81e84278b19@mail.gmail.com>
	<1fb4df0903061240v4260f1bdw5a5e09ed965f7c53@mail.gmail.com>
Message-ID: <97ae2db00903061442s38dcb7beocd9f8682ca597311@mail.gmail.com>

I've posted it on this list before, but if you're writing view tests, check
out Elementor:
http://pivotallabs.com/users/patn/blog/articles/608-better-view-testing-with-elementor.
It provides a much cleaner way of asserting on markup, and doesn't require
you to litter your expectations with CSS selectors.

On Fri, Mar 6, 2009 at 3:40 PM, Stephen Eley <sfeley at gmail.com> wrote:

> On Fri, Mar 6, 2009 at 3:55 AM, David Chelimsky <dchelimsky at gmail.com>
> wrote:
> > On Thu, Mar 5, 2009 at 7:40 AM, MAwiniarski <MAwiniarski at gmail.com>
> wrote:
> >>
> >> Is there a way to check quantity of tags?
> >
> > response.should have_tag('div', 4)
>
> Ooh!  Thank you; I wish I'd known that before.  All this time I've
> been using annoyingly complicated xpath tests:
>
> Then /^I should see (\d+) people$/ do |num|
>  response.should
> have_xpath("//*[count(*[contains(@class,'person')])=#{num}]")
> end
>
>
> --
> Have Fun,
>   Steve Eley (sfeley at gmail.com)
>   ESCAPE POD - The Science Fiction Podcast Magazine
>   http://www.escapepod.org
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090306/0efb3605/attachment.html>

From lists at ruby-forum.com  Fri Mar  6 18:03:22 2009
From: lists at ruby-forum.com (Sebastian W.)
Date: Sat, 7 Mar 2009 00:03:22 +0100
Subject: [rspec-users] Shared behaviors in Cucumber?
Message-ID: <9e6728196c11e7f7c7f389849a6fdfbd@ruby-forum.com>

Hello RSpec group, is there a way to do RSpec-style shared behaviors in
Cucumber? Or something similar?
-- 
Posted via http://www.ruby-forum.com/.

From matt at mattwynne.net  Fri Mar  6 18:19:32 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Fri, 6 Mar 2009 23:19:32 +0000
Subject: [rspec-users] Shared behaviors in Cucumber?
In-Reply-To: <9e6728196c11e7f7c7f389849a6fdfbd@ruby-forum.com>
References: <9e6728196c11e7f7c7f389849a6fdfbd@ruby-forum.com>
Message-ID: <309A48DD-AFB0-46A4-B580-FA8B04FD87FA@mattwynne.net>

You have Background in the new 0.2 version (not released yet) which  
lets you specify some Given steps for all the scenarios in a feature.

Other than that there's the super-steps, which also give you really  
nice re-use:
http://blog.mattwynne.net/2008/11/14/dry-up-your-cucumber-steps/


On 6 Mar 2009, at 23:03, Sebastian W. wrote:

> Hello RSpec group, is there a way to do RSpec-style shared behaviors  
> in
> Cucumber? Or something similar?
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From ben at benmabey.com  Fri Mar  6 18:35:00 2009
From: ben at benmabey.com (Ben Mabey)
Date: Fri, 06 Mar 2009 16:35:00 -0700
Subject: [rspec-users] Shared behaviors in Cucumber?
In-Reply-To: <309A48DD-AFB0-46A4-B580-FA8B04FD87FA@mattwynne.net>
References: <9e6728196c11e7f7c7f389849a6fdfbd@ruby-forum.com>
	<309A48DD-AFB0-46A4-B580-FA8B04FD87FA@mattwynne.net>
Message-ID: <49B1B324.6090105@benmabey.com>

Matt Wynne wrote:
> You have Background in the new 0.2 version (not released yet) which 
> lets you specify some Given steps for all the scenarios in a feature.
>
> Other than that there's the super-steps, which also give you really 
> nice re-use:
> http://blog.mattwynne.net/2008/11/14/dry-up-your-cucumber-steps/

Plus you can use Scenario Outlines to DRY up similar scenarios:
http://wiki.github.com/aslakhellesoy/cucumber/scenario-outlines

-Ben
>
>
> On 6 Mar 2009, at 23:03, Sebastian W. wrote:
>
>> Hello RSpec group, is there a way to do RSpec-style shared behaviors in
>> Cucumber? Or something similar?
>> -- 
>> Posted via http://www.ruby-forum.com/.
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From matt at mattwynne.net  Fri Mar  6 18:56:25 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Fri, 6 Mar 2009 23:56:25 +0000
Subject: [rspec-users] Shared behaviors in Cucumber?
In-Reply-To: <49B1B324.6090105@benmabey.com>
References: <9e6728196c11e7f7c7f389849a6fdfbd@ruby-forum.com>
	<309A48DD-AFB0-46A4-B580-FA8B04FD87FA@mattwynne.net>
	<49B1B324.6090105@benmabey.com>
Message-ID: <BB37F512-8FC8-4896-92B7-D871D8D947D9@mattwynne.net>


On 6 Mar 2009, at 23:35, Ben Mabey wrote:

> Matt Wynne wrote:
>> You have Background in the new 0.2 version (not released yet) which  
>> lets you specify some Given steps for all the scenarios in a feature.
>>
>> Other than that there's the super-steps, which also give you really  
>> nice re-use:
>> http://blog.mattwynne.net/2008/11/14/dry-up-your-cucumber-steps/
>
> Plus you can use Scenario Outlines to DRY up similar scenarios:
> http://wiki.github.com/aslakhellesoy/cucumber/scenario-outlines
>
> -Ben


*slaps forehead* thanks Ben - I missed the big hitter!


Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From phlip2005 at gmail.com  Sat Mar  7 01:32:54 2009
From: phlip2005 at gmail.com (Phlip)
Date: Fri, 06 Mar 2009 22:32:54 -0800
Subject: [rspec-users] what has RSpec got against stack traces?
Message-ID: <got4en$8qs$1@ger.gmane.org>

Here's an error message. The details are not important (beyond to_xml on a 
virtual AR database via fixture_dependencies). I know how to work the actual 
problem.

   NoMethodError in 'BlogMindMap should create XML'
   undefined method `macro' for nil:NilClass
   spec/blog_mind_map_spec.rb:192:
   spec/blog_mind_map_spec.rb:11:

Line 192 contains neither a stray nil nor a method 'macro'.

The question is why did RSpec throw away the backtrace? Am I the first person in 
history to hit a programming error inside RSpec??

-- 
   Phlip


From scott at railsnewbie.com  Sat Mar  7 01:52:32 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Sat, 07 Mar 2009 01:52:32 -0500
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <got4en$8qs$1@ger.gmane.org>
References: <got4en$8qs$1@ger.gmane.org>
Message-ID: <49B219B0.9010004@railsnewbie.com>

Phlip wrote:
> Here's an error message. The details are not important (beyond to_xml 
> on a virtual AR database via fixture_dependencies). I know how to work 
> the actual problem.
>
>   NoMethodError in 'BlogMindMap should create XML'
>   undefined method `macro' for nil:NilClass
>   spec/blog_mind_map_spec.rb:192:
>   spec/blog_mind_map_spec.rb:11:
>
> Line 192 contains neither a stray nil nor a method 'macro'.
>
> The question is why did RSpec throw away the backtrace? Am I the first 
> person in history to hit a programming error inside RSpec??
>
Nope, but this probably isn't one of them. 

Can you post your spec and any relevant code?

Scott

From phlip2005 at gmail.com  Sat Mar  7 02:53:58 2009
From: phlip2005 at gmail.com (Phlip)
Date: Fri, 06 Mar 2009 23:53:58 -0800
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <49B219B0.9010004@railsnewbie.com>
References: <got4en$8qs$1@ger.gmane.org> <49B219B0.9010004@railsnewbie.com>
Message-ID: <got96n$ghe$1@ger.gmane.org>

>> The question is why did RSpec throw away the backtrace? Am I the first 
>> person in history to hit a programming error inside RSpec??

> Nope, but this probably isn't one of them.

I said it wrong. The complete venting goes "Am I the first person in history to 
use RSpec, and then hit a programming error?" The comma , makes the phrases 
non-restrictive.

And I don't give a darn if RSpec itself had a programming error, so long as it 
traced it!

> Can you post your spec and any relevant code?

Nope. Try 1/0 inside a sub-method - you won't get a stack trace to it, right?


From tero at tilus.net  Sat Mar  7 03:00:04 2009
From: tero at tilus.net (Tero Tilus)
Date: Sat, 7 Mar 2009 10:00:04 +0200
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <got4en$8qs$1@ger.gmane.org>
References: <got4en$8qs$1@ger.gmane.org>
Message-ID: <20090307080004.GF20002@uivelo.tilus.net>

2009-03-06 22:32, Phlip:
> Line 192 contains neither a stray nil nor a method 'macro'.

So what exactly _is_ there?  Do you know that particular line causes
(or noes not cause) the error?  

In situations like this I usually pop to debugger right before the
problematic line and then poke around (eval the problematic expression
in smaller parts, move up in the call stack and look for anomalies) to
find out whats up.

> The question is why did RSpec throw away the backtrace?

How do you know it did that?  From the information you gave us, I
can't deduce that.  ...and maybe I just suck at deduction.  ;)

> Am I the first person in history to hit a programming error inside
> RSpec??

What makes you suspect you are?

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/

From scott at railsnewbie.com  Sat Mar  7 03:25:54 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Sat, 07 Mar 2009 03:25:54 -0500
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <got96n$ghe$1@ger.gmane.org>
References: <got4en$8qs$1@ger.gmane.org> <49B219B0.9010004@railsnewbie.com>
	<got96n$ghe$1@ger.gmane.org>
Message-ID: <49B22F92.1090103@railsnewbie.com>

Phlip wrote:
>>> The question is why did RSpec throw away the backtrace? Am I the 
>>> first person in history to hit a programming error inside RSpec??
>
>> Nope, but this probably isn't one of them.
>
> I said it wrong. The complete venting goes "Am I the first person in 
> history to use RSpec, and then hit a programming error?" The comma , 
> makes the phrases non-restrictive.
>
> And I don't give a darn if RSpec itself had a programming error, so 
> long as it traced it!

I don't think it rewrites the callstack in anyway.  More than likely the 
object you are calling the method on is nil.  If you can't figure it out 
just by looking at the spec, I'd suggest running the debugger right 
before the line the line that fails.  Insert this into your spec:

it "...." do
  ...
  require 'rubygems'; require 'ruby-debug'; debugger
   ... # the failing line
end

Run your specs, and you should be confronted by the debugger - this will 
allow you live introspection of the process and results right before 
they happen.  ( search for a ruby-debug guide out there on the interwebs 
if you've never used it before).

If you are correct, you should be able to show (via the debugger, by 
stepping into any relevant functions) that the stack is being rewritten.

>
>> Can you post your spec and any relevant code?
>
> Nope. Try 1/0 inside a sub-method - you won't get a stack trace to it, 
> right?
Usually it does:

 >> def foo
 >>   1/0
 >>   end
=> nil
 >> def bar
 >>   foo
 >>   end
=> nil
 >> bar
ZeroDivisionError: divided by 0
    from (irb):43:in `/'
    from (irb):43:in `foo'
    from (irb):46:in `bar'
    from (irb):48


Hope that helps,

Scott


From phlip2005 at gmail.com  Sat Mar  7 04:08:32 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sat, 07 Mar 2009 01:08:32 -0800
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <49B22F92.1090103@railsnewbie.com>
References: <got4en$8qs$1@ger.gmane.org>
	<49B219B0.9010004@railsnewbie.com>	<got96n$ghe$1@ger.gmane.org>
	<49B22F92.1090103@railsnewbie.com>
Message-ID: <gotdih$oik$1@ger.gmane.org>

>> Nope. Try 1/0 inside a sub-method - you won't get a stack trace to it, 
>> right?

> Usually it does:
> 
>  >> def foo
>  >>   1/0
>  >>   end
> => nil
>  >> def bar
>  >>   foo
>  >>   end
> => nil
>  >> bar
> ZeroDivisionError: divided by 0
>    from (irb):43:in `/'
>    from (irb):43:in `foo'
>    from (irb):46:in `bar'
>    from (irb):48

I don't see any RSpec above that in the call stack.



From phlip2005 at gmail.com  Sat Mar  7 04:12:12 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sat, 07 Mar 2009 01:12:12 -0800
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <20090307080004.GF20002@uivelo.tilus.net>
References: <got4en$8qs$1@ger.gmane.org>
	<20090307080004.GF20002@uivelo.tilus.net>
Message-ID: <gotdpd$p6r$1@ger.gmane.org>

Tero Tilus wrote:

>> Line 192 contains neither a stray nil nor a method 'macro'.
> 
> So what exactly _is_ there?  Do you know that particular line causes
> (or noes not cause) the error?  

Test::Unit::TestCase said the error was ~20 layers deeper - but exactly below 
the same to_xml() call as RSpec indicated. RSpec threw the stack trace away.

Please please please focus: Nobody is asking how to debug, or how to call 
to_xml() correctly. (The problem turned out to be :include => :authors instead 
of :include => :author, where the belongs_to used :author singular. Big deal!)


From phlip2005 at gmail.com  Sat Mar  7 04:17:47 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sat, 07 Mar 2009 01:17:47 -0800
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <49B22F92.1090103@railsnewbie.com>
References: <got4en$8qs$1@ger.gmane.org>
	<49B219B0.9010004@railsnewbie.com>	<got96n$ghe$1@ger.gmane.org>
	<49B22F92.1090103@railsnewbie.com>
Message-ID: <gote3r$piu$1@ger.gmane.org>

   def really_div_by_zero
     1/0
   end

   def div_by_zero
     really_div_by_zero
   end

   it 'should trace my stack' do
     div_by_zero
   end

And that hits the correct line:

ZeroDivisionError in 'Whatever should trace my stack'
divided by 0
spec/blog_mind_map_spec.rb:192:in `/'
spec/blog_mind_map_spec.rb:192:in `really_div_by_zero'
spec/blog_mind_map_spec.rb:196:in `div_by_zero'
spec/blog_mind_map_spec.rb:200:
spec/blog_mind_map_spec.rb:11:

So the question becomes: Why do we sometimes get the correct stack trace and 
sometimes we don't?


From chris at octopod.info  Sat Mar  7 04:31:41 2009
From: chris at octopod.info (Chris McGrath)
Date: Sat, 7 Mar 2009 09:31:41 +0000
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <49B22F92.1090103@railsnewbie.com>
References: <got4en$8qs$1@ger.gmane.org> <49B219B0.9010004@railsnewbie.com>
	<got96n$ghe$1@ger.gmane.org> <49B22F92.1090103@railsnewbie.com>
Message-ID: <23e3fe0f0903070131o7f5c7a6cg430fca7a24f6bc9c@mail.gmail.com>

On Sat, Mar 7, 2009 at 8:25 AM, Scott Taylor <scott at railsnewbie.com> wrote:
> Phlip wrote:
>>>>
>>>> The question is why did RSpec throw away the backtrace? Am I the first
>>>> person in history to hit a programming error inside RSpec??

script/spec -b /path/to/spec.rb will give a full backtrace. You can
also add --backtrace to your spec.opts.

Cheers,

Chris

From scott at railsnewbie.com  Sat Mar  7 04:46:24 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Sat, 07 Mar 2009 04:46:24 -0500
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <gotdpd$p6r$1@ger.gmane.org>
References: <got4en$8qs$1@ger.gmane.org>	<20090307080004.GF20002@uivelo.tilus.net>
	<gotdpd$p6r$1@ger.gmane.org>
Message-ID: <49B24270.9030806@railsnewbie.com>

Phlip wrote:
> Tero Tilus wrote:
>
>>> Line 192 contains neither a stray nil nor a method 'macro'.
>>
>> So what exactly _is_ there?  Do you know that particular line causes
>> (or noes not cause) the error?  
>
> Test::Unit::TestCase said the error was ~20 layers deeper - but 
> exactly below the same to_xml() call as RSpec indicated. RSpec threw 
> the stack trace away.
>
> Please please please focus: Nobody is asking how to debug, or how to 
> call to_xml() correctly. (The problem turned out to be :include => 
> :authors instead of :include => :author, where the belongs_to used 
> :author singular. Big deal!)
Go and file a bug report then, but if you only give this level of 
detail, the bug will never get fixed.

Even if you can't post code (because it's closed-source or what 
have-you),  usually you can at least post a spec.  Please please please 
focus: We can't read your specs nor your code, and without that we are 
poking around in the dark.

Scott

From tero at tilus.net  Sat Mar  7 05:08:57 2009
From: tero at tilus.net (Tero Tilus)
Date: Sat, 7 Mar 2009 12:08:57 +0200
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <gotdpd$p6r$1@ger.gmane.org>
References: <got4en$8qs$1@ger.gmane.org>
	<20090307080004.GF20002@uivelo.tilus.net>
	<gotdpd$p6r$1@ger.gmane.org>
Message-ID: <20090307100857.GG20002@uivelo.tilus.net>

2009-03-07 01:12, Phlip:
> Test::Unit::TestCase said the error was ~20 layers deeper - but
> exactly below the same to_xml() call as RSpec indicated. RSpec threw
> the stack trace away.

You could have told that right away.  :-/

It seems I cant reproduce the trace mangling.  Do have steps to
reproduce?

> Please please please focus: Nobody is asking how to debug

We are trying.  You did not tell you did debugging, so we told you
to try it, because it is usually the first step.  Please, don't take
it personally that we might not all know you and your debug-fu.  ;)

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/

From tero at tilus.net  Sat Mar  7 05:13:20 2009
From: tero at tilus.net (Tero Tilus)
Date: Sat, 7 Mar 2009 12:13:20 +0200
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <gote3r$piu$1@ger.gmane.org>
References: <got4en$8qs$1@ger.gmane.org> <49B219B0.9010004@railsnewbie.com>
	<got96n$ghe$1@ger.gmane.org> <49B22F92.1090103@railsnewbie.com>
	<gote3r$piu$1@ger.gmane.org>
Message-ID: <20090307101320.GH20002@uivelo.tilus.net>

2009-03-07 01:17, Phlip:
> So the question becomes: Why do we sometimes get the correct stack
> trace and sometimes we don't?

What do you mean by "correct"?  To my knowledge you havent posted any
single somehow incorrect stack trace.  If you by "correct" mean
"complete", I dare to ask if you do script/spec -b or something else?

-- 
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/

From lists at ruby-forum.com  Sat Mar  7 07:11:28 2009
From: lists at ruby-forum.com (Alexis Richardson)
Date: Sat, 7 Mar 2009 13:11:28 +0100
Subject: [rspec-users] Writing specs for AMQP clients.
In-Reply-To: <d391a7990903040937sa31069em9886f8e3a6ad692d@mail.gmail.com>
References: <d391a7990903040254x3690f6f0o6aa38deb1fe260ff@mail.gmail.com>
	<57c63afe0903040502u66f98051y55d7cfa8f9169c58@mail.gmail.com>
	<49AEABE8.8090602@benmabey.com>
	<d391a7990903040937sa31069em9886f8e3a6ad692d@mail.gmail.com>
Message-ID: <ff637c86de19199cc63245bf6f5147fe@ruby-forum.com>

Bira, and Ben,

Bira wrote:
> David and Ben,
> 
> Thank you very much for your advice :).

Hi, Alexis here from RabbitMQ.  +1 to what Ben said.

Ben - that's a really nice project you've set up there Ben.  Could you 
introduce it on the rabbitmq-discuss list some time perhaps?

Bira - may I leave you with some links that may also help:

* Ruby client discusion group: http://groups.google.com/group/ruby-amqp/
* Intro info, Ruby links and 'how to create your own client': 
http://www.rabbitmq.com/how.html

Hope this helps!

alexis





> --
> Bira
> http://compexplicita.wordpress.com
> http://compexplicita.tumblr.com

-- 
Posted via http://www.ruby-forum.com/.

From phlip2005 at gmail.com  Sat Mar  7 08:34:30 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sat, 07 Mar 2009 05:34:30 -0800
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <23e3fe0f0903070131o7f5c7a6cg430fca7a24f6bc9c@mail.gmail.com>
References: <got4en$8qs$1@ger.gmane.org>
	<49B219B0.9010004@railsnewbie.com>	<got96n$ghe$1@ger.gmane.org>
	<49B22F92.1090103@railsnewbie.com>
	<23e3fe0f0903070131o7f5c7a6cg430fca7a24f6bc9c@mail.gmail.com>
Message-ID: <gott56$t4a$1@ger.gmane.org>

> script/spec -b /path/to/spec.rb will give a full backtrace. You can
> also add --backtrace to your spec.opts.
> 
> Cheers,
> 
> Chris

Yay! txkbye!


From phlip2005 at gmail.com  Sat Mar  7 08:49:43 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sat, 07 Mar 2009 05:49:43 -0800
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <49B24270.9030806@railsnewbie.com>
References: <got4en$8qs$1@ger.gmane.org>	<20090307080004.GF20002@uivelo.tilus.net>	<gotdpd$p6r$1@ger.gmane.org>
	<49B24270.9030806@railsnewbie.com>
Message-ID: <gotu1p$vl5$1@ger.gmane.org>

Scott Taylor wrote:

> Go and file a bug report then, but if you only give this level of 
> detail, the bug will never get fixed.

I am not reporting any bug in RSpec. Read the Subject line.

I think I know why RSpec has an option (-b) to turn off incomplete stack traces. 
The various Ruby editors have feeble support for Fault Navigation. At fault 
time, I would like keystrokes that move, optionally, to each line that threw an 
error, or each line in project code on the stack trace above an error, or even 
each line in library code above an error.

So RSpec, assuming its editor cannot support that simple feature, simply picks 
the short trace, to emphasize its own .should lines that faulted.

(Many's the time we have squinted at a humongoid stack trace from Rails, trying 
to see the difference between all the library code and our own lines!)

-- 
   Phlip
   http://www.oreillynet.com/onlamp/blog/2008/05/dynamic_languages_vs_editors.html


From rockrep at gmail.com  Fri Mar  6 17:02:59 2009
From: rockrep at gmail.com (rockrep)
Date: Fri, 6 Mar 2009 14:02:59 -0800 (PST)
Subject: [rspec-users] rspec,
	rspec-rails 1.1.99-12 and script/spec 'no such file to load -- spec'
Message-ID: <b1c4d55f-1ac2-4b11-b758-44b5ebd2baf1@x29g2000prf.googlegroups.com>

Hi David, all:

I just recently upgraded to Rails 2.3.1RC2 (Mac OS.X 10.5.6, ruby
1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9])  and have been
dilligently following the instructions for upgrading rspec and rspec-
rails according to:  http://wiki.github.com/dchelimsky/rspec/rails-with-rspec-gems.
I have successfully built the rspec and rspec-rails gems, installed
and unpacked them, and ran script/generate rspec successfully.

'rake spec' works fine, however 'script/spec' fails with error:
$ script/spec spec
script/spec:3:in `require': no such file to load -- spec (LoadError)

script/spec looks like:
#!/usr/bin/env ruby
$LOAD_PATH.unshift(File.expand_path(File.dirname(__FILE__) + "/../
vendor/plugins/rspec/lib"))
require 'spec'
exit ::Spec::Runner::CommandLine.run

and 'rake gems RAILS_ENV=test' returns:
 - [R] rspec >= 1.1.99.12
 - [F] rspec-rails >= 1.1.99.12
    - [R] rspec = 1.1.99.12
    - [F] rack = 0.9.1
    - [ ] cucumber >= 0.1.13
    - [ ] hoe >= 1.9.0

I = Installed
F = Frozen
R = Framework (loaded before rails starts)

rspec does not exist in vendor/gems, but rspec-rails does.  It seems
it's marked as 'R' which (1) I'm not certain I understand why, and (2)
seems to prevent unpacking into vendor/gems.   In any case, I would
like to resolve the issue with script/spec.

Since rspec is also not installed in vendor/plugins the LOAD_PATH line
in script/spec looks odd, but I'm not sure it's the cause.

Any pointers greatly appreciated.  Thanks,

Michael


From kyleoba at gmail.com  Sat Mar  7 01:01:08 2009
From: kyleoba at gmail.com (mudphone)
Date: Fri, 6 Mar 2009 22:01:08 -0800 (PST)
Subject: [rspec-users] Trouble with (Rails) Nested Model Directories
In-Reply-To: <57c63afe0903060052s25e94de4n4ac768c77518f8e@mail.gmail.com>
References: <0285e7e0-a22e-4a42-b328-0c2677c4d8f6@d36g2000prf.googlegroups.com>
	<57c63afe0903060052s25e94de4n4ac768c77518f8e@mail.gmail.com>
Message-ID: <fc7f2a2c-92d0-41df-8d41-4a3adaf765e0@e18g2000yqo.googlegroups.com>

David,

Thanks for your help and for setting me straight.  I am running Rails
2.2.2 and rspec 1.1.12.

I started a new Rails project as well, and have discovered that my
problem is that I have root-level model class, with the same name as
the nested directory.  It looks like this:

app/models/thing.rb
app/models/thing/nested_thing.rb

This set-up causes errors. If I move the thing.rb class to the "thing"
directory, or rename the "thing" directory to something else, all is
good.

Again, thanks for your help.

Kyle

On Mar 6, 12:52?am, David Chelimsky <dchelim... at gmail.com> wrote:
> On Thu, Mar 5, 2009 at 4:02 PM, mudphone <kyle... at gmail.com> wrote:
> > Hi folks,
>
> > In order to bring some order to the many model classes that I have
> > under /app/models, I'm created a new directory (for example):
> > /app/models/nestdir
>
> > I've added the required configuration line in environment.rb:
> > ?config.load_paths += %W( #{RAILS_ROOT}/app/models/nestdir )
>
> > But, when I run my specs, I get an error such as:
> > ...
> > dependencies.rb:428:in `load_missing_constant': Expected RAILS_ROOT/
> > app/models/nestdir/my_model.rb to define Nestdir::MyModel (LoadError)
> > ...
>
> > >From my understanding, the models in the dir listed in
> > config.load_paths should be available in the root Rails namespace. ?Is
> > this not how rspec handles things?
>
> > Is there a standard way of setting up specs for nested model
> > directories? ?The models are not nested within a parent module (like
> > Nestdir, which would have matched the directory name).
>
> I just created a fresh rails-2.3.0 app w/ the latest rspec (built from
> git - 1.1.99.11) and not only was able to include a nested model, I
> was able to run the specs under each of the following conditions:
>
> * neither spec nor model are namespaced
>
> describe User do
> end
>
> class User < ActiveRecord::Base
> end
>
> * model and spec are both namespaced
>
> module Admin
> ? describe User do
> ? end
> end
>
> module Admin
> ? class User < ActiveRecord::Base
> ? end
> end
>
> * config is modifed per your example above
> * config is NOT modifed per your example above
>
> What versions of rspec and rails are you using?
>
>
>
> > Thanks,
> > Kyle
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From MAwiniarski at gmail.com  Sat Mar  7 02:35:17 2009
From: MAwiniarski at gmail.com (MAwiniarski)
Date: Fri, 6 Mar 2009 23:35:17 -0800 (PST)
Subject: [rspec-users] have_tag + quantity - question
In-Reply-To: <97ae2db00903061442s38dcb7beocd9f8682ca597311@mail.gmail.com>
References: <44088ce1-2ad9-4fd9-a996-9d9ab6977752@w34g2000yqm.googlegroups.com>
	<57c63afe0903060055v260fd1behb8dbf81e84278b19@mail.gmail.com> 
	<1fb4df0903061240v4260f1bdw5a5e09ed965f7c53@mail.gmail.com> 
	<97ae2db00903061442s38dcb7beocd9f8682ca597311@mail.gmail.com>
Message-ID: <654bd27c-9c48-463d-bd70-a530a36971b6@w34g2000yqm.googlegroups.com>

Thanks.

On 6 Mar, 23:42, Pat Nakajima <patnakaj... at gmail.com> wrote:
> I've posted it on this list before, but if you're writing view tests, check
> out Elementor:http://pivotallabs.com/users/patn/blog/articles/608-better-view-testi....
> It provides a much cleaner way of asserting on markup, and doesn't require
> you to litter your expectations with CSS selectors.
>
> On Fri, Mar 6, 2009 at 3:40 PM, Stephen Eley <sfe... at gmail.com> wrote:
> > On Fri, Mar 6, 2009 at 3:55 AM, David Chelimsky <dchelim... at gmail.com>
> > wrote:
> > > On Thu, Mar 5, 2009 at 7:40 AM, MAwiniarski <MAwiniar... at gmail.com>
> > wrote:
>
> > >> Is there a way to check quantity of tags?
>
> > > response.should have_tag('div', 4)
>
> > Ooh! ?Thank you; I wish I'd known that before. ?All this time I've
> > been using annoyingly complicated xpath tests:
>
> > Then /^I should see (\d+) people$/ do |num|
> > ?response.should
> > have_xpath("//*[count(*[contains(@class,'person')])=#{num}]")
> > end
>
> > --
> > Have Fun,
> > ? Steve Eley (sfe... at gmail.com)
> > ? ESCAPE POD - The Science Fiction Podcast Magazine
> > ?http://www.escapepod.org
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From dchelimsky at gmail.com  Sat Mar  7 09:50:40 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sat, 7 Mar 2009 08:50:40 -0600
Subject: [rspec-users] rspec,
	rspec-rails 1.1.99-12 and script/spec 'no such file to load -- spec'
In-Reply-To: <b1c4d55f-1ac2-4b11-b758-44b5ebd2baf1@x29g2000prf.googlegroups.com>
References: <b1c4d55f-1ac2-4b11-b758-44b5ebd2baf1@x29g2000prf.googlegroups.com>
Message-ID: <57c63afe0903070650w5de9e136u72ecb143b4a62db1@mail.gmail.com>

On Fri, Mar 6, 2009 at 4:02 PM, rockrep <rockrep at gmail.com> wrote:
> Hi David, all:
>
> I just recently upgraded to Rails 2.3.1RC2 (Mac OS.X 10.5.6, ruby
> 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9]) ?and have been
> dilligently following the instructions for upgrading rspec and rspec-
> rails according to: ?http://wiki.github.com/dchelimsky/rspec/rails-with-rspec-gems.
> I have successfully built the rspec and rspec-rails gems, installed
> and unpacked them, and ran script/generate rspec successfully.
>
> 'rake spec' works fine, however 'script/spec' fails with error:
> $ script/spec spec
> script/spec:3:in `require': no such file to load -- spec (LoadError)
>
> script/spec looks like:
> #!/usr/bin/env ruby
> $LOAD_PATH.unshift(File.expand_path(File.dirname(__FILE__) + "/../
> vendor/plugins/rspec/lib"))

This bit is a bug that I plan to fix (today), but that's not the only
problem here.

> require 'spec'
> exit ::Spec::Runner::CommandLine.run
>
> and 'rake gems RAILS_ENV=test' returns:
> ?- [R] rspec >= 1.1.99.12
> ?- [F] rspec-rails >= 1.1.99.12
> ? ?- [R] rspec = 1.1.99.12
> ? ?- [F] rack = 0.9.1
> ? ?- [ ] cucumber >= 0.1.13
> ? ?- [ ] hoe >= 1.9.0
>
> I = Installed
> F = Frozen
> R = Framework (loaded before rails starts)
>
> rspec does not exist in vendor/gems, but rspec-rails does. ?It seems
> it's marked as 'R' which (1) I'm not certain I understand why, and (2)
> seems to prevent unpacking into vendor/gems. ? In any case, I would
> like to resolve the issue with script/spec.

I've seen this with older versions of lib/tasks/rspec.rake that
required 'spec'. Basically, when you run any rake task in rails, rake
loads up the Rakefile in the project root *and* all of the .rake files
in lib/tasks before executing anything. So if any of those files
require 'spec', then the rails/gems framework will consider rspec to
be loaded already, and won't let you unpack it.

Try this:

rm lib/tasks/rspec.rake
rake gems RAILS_ENV='test'

If that changes rspec to [I], then you can unpack it and you should be
good to go.

>
> Since rspec is also not installed in vendor/plugins the LOAD_PATH line
> in script/spec looks odd, but I'm not sure it's the cause.
>
> Any pointers greatly appreciated. ?Thanks,
>
> Michael
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Sat Mar  7 10:12:34 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sat, 7 Mar 2009 09:12:34 -0600
Subject: [rspec-users] Trouble with (Rails) Nested Model Directories
In-Reply-To: <fc7f2a2c-92d0-41df-8d41-4a3adaf765e0@e18g2000yqo.googlegroups.com>
References: <0285e7e0-a22e-4a42-b328-0c2677c4d8f6@d36g2000prf.googlegroups.com>
	<57c63afe0903060052s25e94de4n4ac768c77518f8e@mail.gmail.com>
	<fc7f2a2c-92d0-41df-8d41-4a3adaf765e0@e18g2000yqo.googlegroups.com>
Message-ID: <57c63afe0903070712rd3f98c1w2bb901cdd1005fd7@mail.gmail.com>

On Sat, Mar 7, 2009 at 12:01 AM, mudphone <kyleoba at gmail.com> wrote:
> David,
>
> Thanks for your help and for setting me straight. ?I am running Rails
> 2.2.2 and rspec 1.1.12.
>
> I started a new Rails project as well, and have discovered that my
> problem is that I have root-level model class, with the same name as
> the nested directory. ?It looks like this:
>
> app/models/thing.rb
> app/models/thing/nested_thing.rb
>
> This set-up causes errors. If I move the thing.rb class to the "thing"
> directory, or rename the "thing" directory to something else, all is
> good.
>
> Again, thanks for your help.

You're welcome. Glad you got it figured out.

Cheers,
David

>
> Kyle
>
> On Mar 6, 12:52?am, David Chelimsky <dchelim... at gmail.com> wrote:
>> On Thu, Mar 5, 2009 at 4:02 PM, mudphone <kyle... at gmail.com> wrote:
>> > Hi folks,
>>
>> > In order to bring some order to the many model classes that I have
>> > under /app/models, I'm created a new directory (for example):
>> > /app/models/nestdir
>>
>> > I've added the required configuration line in environment.rb:
>> > ?config.load_paths += %W( #{RAILS_ROOT}/app/models/nestdir )
>>
>> > But, when I run my specs, I get an error such as:
>> > ...
>> > dependencies.rb:428:in `load_missing_constant': Expected RAILS_ROOT/
>> > app/models/nestdir/my_model.rb to define Nestdir::MyModel (LoadError)
>> > ...
>>
>> > >From my understanding, the models in the dir listed in
>> > config.load_paths should be available in the root Rails namespace. ?Is
>> > this not how rspec handles things?
>>
>> > Is there a standard way of setting up specs for nested model
>> > directories? ?The models are not nested within a parent module (like
>> > Nestdir, which would have matched the directory name).
>>
>> I just created a fresh rails-2.3.0 app w/ the latest rspec (built from
>> git - 1.1.99.11) and not only was able to include a nested model, I
>> was able to run the specs under each of the following conditions:
>>
>> * neither spec nor model are namespaced
>>
>> describe User do
>> end
>>
>> class User < ActiveRecord::Base
>> end
>>
>> * model and spec are both namespaced
>>
>> module Admin
>> ? describe User do
>> ? end
>> end
>>
>> module Admin
>> ? class User < ActiveRecord::Base
>> ? end
>> end
>>
>> * config is modifed per your example above
>> * config is NOT modifed per your example above
>>
>> What versions of rspec and rails are you using?
>>
>>
>>
>> > Thanks,
>> > Kyle
>> > _______________________________________________
>> > rspec-users mailing list
>> > rspec-us... at rubyforge.org
>> >http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Sat Mar  7 11:53:56 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sat, 7 Mar 2009 10:53:56 -0600
Subject: [rspec-users] rspec,
	rspec-rails 1.1.99-12 and script/spec 'no such file to load -- spec'
In-Reply-To: <57c63afe0903070650w5de9e136u72ecb143b4a62db1@mail.gmail.com>
References: <b1c4d55f-1ac2-4b11-b758-44b5ebd2baf1@x29g2000prf.googlegroups.com>
	<57c63afe0903070650w5de9e136u72ecb143b4a62db1@mail.gmail.com>
Message-ID: <57c63afe0903070853q7f00fa5j310c8eeaa34a7075@mail.gmail.com>

On Sat, Mar 7, 2009 at 8:50 AM, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Fri, Mar 6, 2009 at 4:02 PM, rockrep <rockrep at gmail.com> wrote:
>> Hi David, all:
>>
>> I just recently upgraded to Rails 2.3.1RC2 (Mac OS.X 10.5.6, ruby
>> 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9]) ?and have been
>> dilligently following the instructions for upgrading rspec and rspec-
>> rails according to: ?http://wiki.github.com/dchelimsky/rspec/rails-with-rspec-gems.
>> I have successfully built the rspec and rspec-rails gems, installed
>> and unpacked them, and ran script/generate rspec successfully.
>>
>> 'rake spec' works fine, however 'script/spec' fails with error:
>> $ script/spec spec
>> script/spec:3:in `require': no such file to load -- spec (LoadError)
>>
>> script/spec looks like:
>> #!/usr/bin/env ruby
>> $LOAD_PATH.unshift(File.expand_path(File.dirname(__FILE__) + "/../
>> vendor/plugins/rspec/lib"))
>
> This bit is a bug that I plan to fix (today), but that's not the only
> problem here.

This fixed and pushed to github

http://github.com/dchelimsky/rspec-rails/commit/cd15dd5cbd6ca9cf2cd2f8ae873e0a8901e84662

>
>> require 'spec'
>> exit ::Spec::Runner::CommandLine.run
>>
>> and 'rake gems RAILS_ENV=test' returns:
>> ?- [R] rspec >= 1.1.99.12
>> ?- [F] rspec-rails >= 1.1.99.12
>> ? ?- [R] rspec = 1.1.99.12
>> ? ?- [F] rack = 0.9.1
>> ? ?- [ ] cucumber >= 0.1.13
>> ? ?- [ ] hoe >= 1.9.0

Just an FYI about the listed dependencies - cucumber and hoe are
developer dependencies of rspec, so you don't need them to run rspec.
It looks like rails gem management system doesn't make that
distinction, and shows all dependencies regardless of type.

>>
>> I = Installed
>> F = Frozen
>> R = Framework (loaded before rails starts)
>>
>> rspec does not exist in vendor/gems, but rspec-rails does. ?It seems
>> it's marked as 'R' which (1) I'm not certain I understand why, and (2)
>> seems to prevent unpacking into vendor/gems. ? In any case, I would
>> like to resolve the issue with script/spec.
>
> I've seen this with older versions of lib/tasks/rspec.rake that
> required 'spec'. Basically, when you run any rake task in rails, rake
> loads up the Rakefile in the project root *and* all of the .rake files
> in lib/tasks before executing anything. So if any of those files
> require 'spec', then the rails/gems framework will consider rspec to
> be loaded already, and won't let you unpack it.
>
> Try this:
>
> rm lib/tasks/rspec.rake
> rake gems RAILS_ENV='test'
>
> If that changes rspec to [I], then you can unpack it and you should be
> good to go.
>
>>
>> Since rspec is also not installed in vendor/plugins the LOAD_PATH line
>> in script/spec looks odd, but I'm not sure it's the cause.
>>
>> Any pointers greatly appreciated. ?Thanks,
>>
>> Michael
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>

From pat.maddox at gmail.com  Sat Mar  7 13:17:49 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Sat, 7 Mar 2009 10:17:49 -0800
Subject: [rspec-users] what has RSpec got against stack traces?
In-Reply-To: <gotu1p$vl5$1@ger.gmane.org>
References: <got4en$8qs$1@ger.gmane.org>	<20090307080004.GF20002@uivelo.tilus.net>	<gotdpd$p6r$1@ger.gmane.org>
	<49B24270.9030806@railsnewbie.com> <gotu1p$vl5$1@ger.gmane.org>
Message-ID: <C378F8C3-AF53-4278-974D-52272C7AF2ED@gmail.com>

On Mar 7, 2009, at 5:49 AM, Phlip wrote:

> Scott Taylor wrote:
>
>> Go and file a bug report then, but if you only give this level of  
>> detail, the bug will never get fixed.
>
> I am not reporting any bug in RSpec. Read the Subject line.
>
> I think I know why RSpec has an option (-b) to turn off incomplete  
> stack traces. The various Ruby editors have feeble support for Fault  
> Navigation. At fault time, I would like keystrokes that move,  
> optionally, to each line that threw an error, or each line in  
> project code on the stack trace above an error, or even each line in  
> library code above an error.

RSpec modifies the stack trace, filtering out internal lines to reduce  
noise.  It's possible that it's filtering too much.

Anyway, as Scott has said numerous times, there's not really anything  
we can do if you're not interested in helping us help you.  Besides  
the suggestion to use the -b switch, anyway.

Pat

From mark at mwilden.com  Sat Mar  7 13:20:54 2009
From: mark at mwilden.com (Mark Wilden)
Date: Sat, 7 Mar 2009 10:20:54 -0800
Subject: [rspec-users] [cucumber] Cucumber and Chronic
In-Reply-To: <3c30da400903011107n7057e73fy89b2913085d222c0@mail.gmail.com>
References: <1ebf5a4d0903010850l54c7ee19i58dbbc48150a9339@mail.gmail.com>
	<3c30da400903011107n7057e73fy89b2913085d222c0@mail.gmail.com>
Message-ID: <3c30da400903071020s2a9831c2redf4e93bbb05805f@mail.gmail.com>

On Sun, Mar 1, 2009 at 11:07 AM, Mark Wilden <mark at mwilden.com> wrote:
>
> Just be careful when when basing durations from "now" that daylight
> savings time doesn't affect anything.

Like it did today, when two specs that used 'Time.now.advance(:hours
=> 24).utc' started failing.

///ark

From phlip2005 at gmail.com  Sun Mar  8 13:00:45 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 08 Mar 2009 10:00:45 -0700
Subject: [rspec-users] response.body.should be_xml_with -- how to do nested
	xpath matches
Message-ID: <gp0tk0$7n7$1@ger.gmane.org>

RSpecsters:

I like nested XPath expressions, because the outer XPath assertion can clip the 
diagnostic of the inner XPath assertion. You don't get the whole page spewed 
into your face when you fault!

This specification, for example, tests Yury Kotlyarov's user login page, from:

   http://github.com/yura/howto-rspec-custom-matchers/tree/master

   it 'should have xpathic tags' do
     render '/users/new'

     response.body.should be_xml_with{
       xpath :form, :action => '/users' do
         xpath :fieldset do
           xpath :'legend[ contains(., "Personal Information") ]' and
           xpath :'label[ contains(., "First name") ]' and
           xpath :input, :type => 'text', :name => 'user[first_name]'
         end
       end
     }
   end

That tests this (otherwise innocuous) new.html.erb:

<form action="/users">
   <fieldset>
     <legend>Personal Information</legend>
     <ol>
       <li id="control_user_first_name">
         <label for="user_first_name">First name</label>
         <input type="text" name="user[first_name]" id="user_first_name" />
       </li>
     </ol>
   </fieldset>
</form>

If that code had any major complex <%= erb %> activity, the tests^W 
specifications would keep it honest.

Let's change the specification, to simulate a bug, and try it:

     xpath :input, :type => 'text', :name => 'user[first_nome]' # was _name

That provides this mind-blast of errata:

'/users/new should have xpathic tags' FAILED
xpath: "descendant-or-self::input[@type = $type and @name = $name]"
arguments: {"name"=>"user[first_nome]", "type"=>"text"}

xml context:

<fieldset>
   <legend>
     Personal Information
   </legend>
   <ol>
     <li id='control_user_first_name'>
       <label for='user_first_name'>
         First name
       </label>
       <input name='user[first_name]' type='text' id='user_first_name'/>
     </li>
   </ol>
</fieldset>

assert{ ( ( xpath(:"legend[ contains(., \"Personal Information\") ]") ) and
      ( ( ( xpath(:"label[ contains(., \"First name\") ]") ) and
     ( xpath(:input, { :type => "text", :name => "user[first_nome]" }) ) ) ) ) }
   --> nil - should pass 


xpath(:"legend[ contains(., \"Personal Information\") ]")
   --> <legend> ... </>

xpath(:"label[ contains(., \"First name\") ]")
   --> <label for='user_first_name'> ... </>

xpath(:input, { :type => "text", :name => "user[first_nome]" })
   --> nil

./spec/views/users/new.html.erb_spec.rb:63:
script/spec:5:

Finished in 0.116823 seconds

2 examples, 1 failure

Note that the error message restricted itself to the XHTML inside the <form> 
tag. This is a major benefit when diagnosing a huge page that failed. (But also 
note that your HTML, like your code, should come in small reusable snippets, 
such as partials, and that these should get tested directly!)

Soon I will upgrade this system to use Nokogiri instead of (>cough<) REXML.

Now, while I go and put the "simple" matcher that does this onto Twitter, 
YouTube, Mingle, Facebook, Mindfuck, Reddit, Tumblog, LinkedIn, and Gist, you 
all can just read it below my sig.

-- 
   Phlip
   http://www.zeroplayer.com/

require File.dirname(__FILE__) + "/../../spec_helper"
require 'assert2/xpath'
require 'spec/matchers/wrap_expectation'

Spec::Runner.configure do |c|
   c.include Test::Unit::Assertions
end  #  TODO blog this

describe "/users/new" do

   it "should have user form" do
     render '/users/new'
     response.should have_form('/users') do
       with_field_set 'Personal Information' do
         with_text_field 'First name', 'user', 'first_name'
       end
     end
   end

   class BeXmlWith

     def initialize(scope, &block)
       @scope, @block = scope, block
     end

     def matches?(stwing, &block)
       waz_xdoc = @xdoc

       @scope.wrap_expectation self do
         @scope.assert_xhtml stwing
         return (block || @block || proc{}).call
       end
     ensure
       @xdoc = waz_xdoc
     end

     attr_accessor :failure_message

     def negative_failure_message
       "yack yack yack"
     end
   end

   def be_xml_with(&block)
     BeXmlWith.new(self, &block)
   end

   def be_xml_with_(&block)
     waz_xdoc = @xdoc
     simple_matcher 'yo' do |given, matcher|
       wrap_expectation matcher do
         assert_xhtml given  #  this works
         block.call  #  crashes with a nil.first error!
       end
     end
   ensure
     @xdoc = waz_xdoc
   end

   it 'should have xpathic tags' do
     render '/users/new'

     response.body.should be_xml_with{
       xpath :form, :action => '/users' do
         xpath :fieldset do
           xpath :'legend[ contains(., "Personal Information") ]' and
           xpath :'label[ contains(., "First name") ]' and
           xpath :input, :type => 'text', :name => 'user[first_name]'
         end
       end
     }
   end

end


From dchelimsky at gmail.com  Sun Mar  8 14:03:15 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 8 Mar 2009 13:03:15 -0500
Subject: [rspec-users] response.body.should be_xml_with -- how to do
	nested xpath matches
In-Reply-To: <gp0tk0$7n7$1@ger.gmane.org>
References: <gp0tk0$7n7$1@ger.gmane.org>
Message-ID: <57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>

On Sun, Mar 8, 2009 at 12:00 PM, Phlip <phlip2005 at gmail.com> wrote:
> RSpecsters:
>
> I like nested XPath expressions, because the outer XPath assertion can clip
> the diagnostic of the inner XPath assertion. You don't get the whole page
> spewed into your face when you fault!
>
> This specification, for example, tests Yury Kotlyarov's user login page,
> from:
>
> ?http://github.com/yura/howto-rspec-custom-matchers/tree/master
>
> ?it 'should have xpathic tags' do
> ? ?render '/users/new'
>
> ? ?response.body.should be_xml_with{
> ? ? ?xpath :form, :action => '/users' do
> ? ? ? ?xpath :fieldset do
> ? ? ? ? ?xpath :'legend[ contains(., "Personal Information") ]' and
> ? ? ? ? ?xpath :'label[ contains(., "First name") ]' and
> ? ? ? ? ?xpath :input, :type => 'text', :name => 'user[first_name]'
> ? ? ? ?end
> ? ? ?end
> ? ?}
> ?end

This is nice, but the abstractions are operating at different levels.
The keyword is "xpath" but the args passed to that look nothing like
xpath. How about something like:

response.body.should be_xml_with do
  form :action => '/users' do
    fieldset do
      legend "Personal Information"
      label "First name"
      input :type => 'text', :name => 'user[first_name]'
    end
  end
end




>
> That tests this (otherwise innocuous) new.html.erb:
>
> <form action="/users">
> ?<fieldset>
> ? ?<legend>Personal Information</legend>
> ? ?<ol>
> ? ? ?<li id="control_user_first_name">
> ? ? ? ?<label for="user_first_name">First name</label>
> ? ? ? ?<input type="text" name="user[first_name]" id="user_first_name" />
> ? ? ?</li>
> ? ?</ol>
> ?</fieldset>
> </form>
>
> If that code had any major complex <%= erb %> activity, the tests^W
> specifications would keep it honest.
>
> Let's change the specification, to simulate a bug, and try it:
>
> ? ?xpath :input, :type => 'text', :name => 'user[first_nome]' # was _name
>
> That provides this mind-blast of errata:
>
> '/users/new should have xpathic tags' FAILED
> xpath: "descendant-or-self::input[@type = $type and @name = $name]"
> arguments: {"name"=>"user[first_nome]", "type"=>"text"}
>
> xml context:
>
> <fieldset>
> ?<legend>
> ? ?Personal Information
> ?</legend>
> ?<ol>
> ? ?<li id='control_user_first_name'>
> ? ? ?<label for='user_first_name'>
> ? ? ? ?First name
> ? ? ?</label>
> ? ? ?<input name='user[first_name]' type='text' id='user_first_name'/>
> ? ?</li>
> ?</ol>
> </fieldset>
>
> assert{ ( ( xpath(:"legend[ contains(., \"Personal Information\") ]") ) and
> ? ? ( ( ( xpath(:"label[ contains(., \"First name\") ]") ) and
> ? ?( xpath(:input, { :type => "text", :name => "user[first_nome]" }) ) ) ) )
> }
> ?--> nil - should pass
>
> xpath(:"legend[ contains(., \"Personal Information\") ]")
> ?--> <legend> ... </>
>
> xpath(:"label[ contains(., \"First name\") ]")
> ?--> <label for='user_first_name'> ... </>
>
> xpath(:input, { :type => "text", :name => "user[first_nome]" })
> ?--> nil
>
> ./spec/views/users/new.html.erb_spec.rb:63:
> script/spec:5:
>
> Finished in 0.116823 seconds
>
> 2 examples, 1 failure
>
> Note that the error message restricted itself to the XHTML inside the <form>
> tag. This is a major benefit when diagnosing a huge page that failed. (But
> also note that your HTML, like your code, should come in small reusable
> snippets, such as partials, and that these should get tested directly!)
>
> Soon I will upgrade this system to use Nokogiri instead of (>cough<) REXML.
>
> Now, while I go and put the "simple" matcher that does this onto Twitter,
> YouTube, Mingle, Facebook, Mindfuck, Reddit, Tumblog, LinkedIn, and Gist,
> you all can just read it below my sig.
>
> --
> ?Phlip
> ?http://www.zeroplayer.com/
>
> require File.dirname(__FILE__) + "/../../spec_helper"
> require 'assert2/xpath'
> require 'spec/matchers/wrap_expectation'
>
> Spec::Runner.configure do |c|
> ?c.include Test::Unit::Assertions
> end ?# ?TODO blog this
>
> describe "/users/new" do
>
> ?it "should have user form" do
> ? ?render '/users/new'
> ? ?response.should have_form('/users') do
> ? ? ?with_field_set 'Personal Information' do
> ? ? ? ?with_text_field 'First name', 'user', 'first_name'
> ? ? ?end
> ? ?end
> ?end
>
> ?class BeXmlWith
>
> ? ?def initialize(scope, &block)
> ? ? ?@scope, @block = scope, block
> ? ?end
>
> ? ?def matches?(stwing, &block)
> ? ? ?waz_xdoc = @xdoc
>
> ? ? ?@scope.wrap_expectation self do
> ? ? ? ?@scope.assert_xhtml stwing
> ? ? ? ?return (block || @block || proc{}).call
> ? ? ?end
> ? ?ensure
> ? ? ?@xdoc = waz_xdoc
> ? ?end
>
> ? ?attr_accessor :failure_message
>
> ? ?def negative_failure_message
> ? ? ?"yack yack yack"
> ? ?end
> ?end
>
> ?def be_xml_with(&block)
> ? ?BeXmlWith.new(self, &block)
> ?end
>
> ?def be_xml_with_(&block)
> ? ?waz_xdoc = @xdoc
> ? ?simple_matcher 'yo' do |given, matcher|
> ? ? ?wrap_expectation matcher do
> ? ? ? ?assert_xhtml given ?# ?this works
> ? ? ? ?block.call ?# ?crashes with a nil.first error!
> ? ? ?end
> ? ?end
> ?ensure
> ? ?@xdoc = waz_xdoc
> ?end
>
> ?it 'should have xpathic tags' do
> ? ?render '/users/new'
>
> ? ?response.body.should be_xml_with{
> ? ? ?xpath :form, :action => '/users' do
> ? ? ? ?xpath :fieldset do
> ? ? ? ? ?xpath :'legend[ contains(., "Personal Information") ]' and
> ? ? ? ? ?xpath :'label[ contains(., "First name") ]' and
> ? ? ? ? ?xpath :input, :type => 'text', :name => 'user[first_name]'
> ? ? ? ?end
> ? ? ?end
> ? ?}
> ?end
>
> end
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From zach.dennis at gmail.com  Sun Mar  8 14:23:05 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Sun, 8 Mar 2009 14:23:05 -0400
Subject: [rspec-users] response.body.should be_xml_with -- how to do
	nested xpath matches
In-Reply-To: <57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
References: <gp0tk0$7n7$1@ger.gmane.org>
	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
Message-ID: <85d99afe0903081123rcd7b479tf3cc93fc5301ba09@mail.gmail.com>

On Sun, Mar 8, 2009 at 2:03 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Sun, Mar 8, 2009 at 12:00 PM, Phlip <phlip2005 at gmail.com> wrote:
>> RSpecsters:
>>
>> I like nested XPath expressions, because the outer XPath assertion can clip
>> the diagnostic of the inner XPath assertion. You don't get the whole page
>> spewed into your face when you fault!
>>
>> This specification, for example, tests Yury Kotlyarov's user login page,
>> from:
>>
>> ?http://github.com/yura/howto-rspec-custom-matchers/tree/master
>>
>> ?it 'should have xpathic tags' do
>> ? ?render '/users/new'
>>
>> ? ?response.body.should be_xml_with{
>> ? ? ?xpath :form, :action => '/users' do
>> ? ? ? ?xpath :fieldset do
>> ? ? ? ? ?xpath :'legend[ contains(., "Personal Information") ]' and
>> ? ? ? ? ?xpath :'label[ contains(., "First name") ]' and
>> ? ? ? ? ?xpath :input, :type => 'text', :name => 'user[first_name]'
>> ? ? ? ?end
>> ? ? ?end
>> ? ?}
>> ?end
>
> This is nice, but the abstractions are operating at different levels.
> The keyword is "xpath" but the args passed to that look nothing like
> xpath. How about something like:
>
> response.body.should be_xml_with do
> ?form :action => '/users' do
> ? ?fieldset do
> ? ? ?legend "Personal Information"
> ? ? ?label "First name"
> ? ? ?input :type => 'text', :name => 'user[first_name]'
> ? ?end
> ?end
> end
>

I like this a lot.

>
>
>
>>
>> That tests this (otherwise innocuous) new.html.erb:
>>
>> <form action="/users">
>> ?<fieldset>
>> ? ?<legend>Personal Information</legend>
>> ? ?<ol>
>> ? ? ?<li id="control_user_first_name">
>> ? ? ? ?<label for="user_first_name">First name</label>
>> ? ? ? ?<input type="text" name="user[first_name]" id="user_first_name" />
>> ? ? ?</li>
>> ? ?</ol>
>> ?</fieldset>
>> </form>
>>
>> If that code had any major complex <%= erb %> activity, the tests^W
>> specifications would keep it honest.
>>
>> Let's change the specification, to simulate a bug, and try it:
>>
>> ? ?xpath :input, :type => 'text', :name => 'user[first_nome]' # was _name
>>
>> That provides this mind-blast of errata:
>>
>> '/users/new should have xpathic tags' FAILED
>> xpath: "descendant-or-self::input[@type = $type and @name = $name]"
>> arguments: {"name"=>"user[first_nome]", "type"=>"text"}
>>
>> xml context:
>>
>> <fieldset>
>> ?<legend>
>> ? ?Personal Information
>> ?</legend>
>> ?<ol>
>> ? ?<li id='control_user_first_name'>
>> ? ? ?<label for='user_first_name'>
>> ? ? ? ?First name
>> ? ? ?</label>
>> ? ? ?<input name='user[first_name]' type='text' id='user_first_name'/>
>> ? ?</li>
>> ?</ol>
>> </fieldset>
>>
>> assert{ ( ( xpath(:"legend[ contains(., \"Personal Information\") ]") ) and
>> ? ? ( ( ( xpath(:"label[ contains(., \"First name\") ]") ) and
>> ? ?( xpath(:input, { :type => "text", :name => "user[first_nome]" }) ) ) ) )
>> }
>> ?--> nil - should pass
>>
>> xpath(:"legend[ contains(., \"Personal Information\") ]")
>> ?--> <legend> ... </>
>>
>> xpath(:"label[ contains(., \"First name\") ]")
>> ?--> <label for='user_first_name'> ... </>
>>
>> xpath(:input, { :type => "text", :name => "user[first_nome]" })
>> ?--> nil
>>
>> ./spec/views/users/new.html.erb_spec.rb:63:
>> script/spec:5:
>>
>> Finished in 0.116823 seconds
>>
>> 2 examples, 1 failure
>>
>> Note that the error message restricted itself to the XHTML inside the <form>
>> tag. This is a major benefit when diagnosing a huge page that failed. (But
>> also note that your HTML, like your code, should come in small reusable
>> snippets, such as partials, and that these should get tested directly!)
>>
>> Soon I will upgrade this system to use Nokogiri instead of (>cough<) REXML.
>>
>> Now, while I go and put the "simple" matcher that does this onto Twitter,
>> YouTube, Mingle, Facebook, Mindfuck, Reddit, Tumblog, LinkedIn, and Gist,
>> you all can just read it below my sig.
>>
>> --
>> ?Phlip
>> ?http://www.zeroplayer.com/
>>
>> require File.dirname(__FILE__) + "/../../spec_helper"
>> require 'assert2/xpath'
>> require 'spec/matchers/wrap_expectation'
>>
>> Spec::Runner.configure do |c|
>> ?c.include Test::Unit::Assertions
>> end ?# ?TODO blog this
>>
>> describe "/users/new" do
>>
>> ?it "should have user form" do
>> ? ?render '/users/new'
>> ? ?response.should have_form('/users') do
>> ? ? ?with_field_set 'Personal Information' do
>> ? ? ? ?with_text_field 'First name', 'user', 'first_name'
>> ? ? ?end
>> ? ?end
>> ?end
>>
>> ?class BeXmlWith
>>
>> ? ?def initialize(scope, &block)
>> ? ? ?@scope, @block = scope, block
>> ? ?end
>>
>> ? ?def matches?(stwing, &block)
>> ? ? ?waz_xdoc = @xdoc
>>
>> ? ? ?@scope.wrap_expectation self do
>> ? ? ? ?@scope.assert_xhtml stwing
>> ? ? ? ?return (block || @block || proc{}).call
>> ? ? ?end
>> ? ?ensure
>> ? ? ?@xdoc = waz_xdoc
>> ? ?end
>>
>> ? ?attr_accessor :failure_message
>>
>> ? ?def negative_failure_message
>> ? ? ?"yack yack yack"
>> ? ?end
>> ?end
>>
>> ?def be_xml_with(&block)
>> ? ?BeXmlWith.new(self, &block)
>> ?end
>>
>> ?def be_xml_with_(&block)
>> ? ?waz_xdoc = @xdoc
>> ? ?simple_matcher 'yo' do |given, matcher|
>> ? ? ?wrap_expectation matcher do
>> ? ? ? ?assert_xhtml given ?# ?this works
>> ? ? ? ?block.call ?# ?crashes with a nil.first error!
>> ? ? ?end
>> ? ?end
>> ?ensure
>> ? ?@xdoc = waz_xdoc
>> ?end
>>
>> ?it 'should have xpathic tags' do
>> ? ?render '/users/new'
>>
>> ? ?response.body.should be_xml_with{
>> ? ? ?xpath :form, :action => '/users' do
>> ? ? ? ?xpath :fieldset do
>> ? ? ? ? ?xpath :'legend[ contains(., "Personal Information") ]' and
>> ? ? ? ? ?xpath :'label[ contains(., "First name") ]' and
>> ? ? ? ? ?xpath :input, :type => 'text', :name => 'user[first_name]'
>> ? ? ? ?end
>> ? ? ?end
>> ? ?}
>> ?end
>>
>> end
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From phlip2005 at gmail.com  Sun Mar  8 14:41:43 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 08 Mar 2009 11:41:43 -0700
Subject: [rspec-users] response.body.should be_xml_with -- how to do
 nested xpath matches
In-Reply-To: <57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
References: <gp0tk0$7n7$1@ger.gmane.org>
	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
Message-ID: <gp13hb$oul$1@ger.gmane.org>

David Chelimsky wrote:

>>          xpath :'legend[ contains(., "Personal Information") ]' and
>>          xpath :'label[ contains(., "First name") ]' and
>>          xpath :input, :type => 'text', :name => 'user[first_name]'

> This is nice, but the abstractions are operating at different levels.
> The keyword is "xpath" but the args passed to that look nothing like
> xpath.

That's because it's a DSL. You can use raw XPath, XPath with one convenience 
(:'div[ @class = "content" ]' as a symbol implies "any descendant"), or you can 
use an option hash that generates XPath.

The DSL's benefit is tags like :attribute => foo will automatically escape their 
strings correctly. (That's why the top line of the diagnostic was a little 
cluttered!) foo could contain mixed ' and " payload, and we don't care.

 > How about something like:

> response.body.should be_xml_with do
>   form :action => '/users' do
>     fieldset do
>       legend "Personal Information"
>       label "First name"

Because I'm not webrat?

Yes it would be kewt if label('yo') went into method_missing and came out as 
//label[ contains(., "yo") ]. But I have found that spot checks of algorithmic 
details, such as eRB tags, are more valuable to development than slavishly 
matching your tests to your HTML contents.

If you write this HTML...

  <form blah>
     <input blah>
     <input blah>
     <input blah>
  </form>

...and if you test it with a sequence of assertions that exactly match it...

   page.should contain
     form blah
       input blah
       input blah
       input blah
     end
   end

...then you are not really doing TDD. You are merely replicating your code as 
your test, and that will only cause irritation at upgrade time or bug time.

Here's an example from our projects at work:

     get :thanks_for_purchasing
     assert_xpath :'center[ . = "Your order has been accepted!" ]'
     assert_xpath :div, :align => :center do
       a = assert_xpath(:'p[ contains(., "questions about your membership") ]/a')
       assert{ a.text == a[:href] }
       assert{ a[:href] == SubscriptionController::CUSTOMER_SERVICE_LINK }
     end

Note how much that specifies in the customer acknowledgment page.

  - the confirmation is centered
  - the explanation div is centered (yes, we could identify it better!)
  - part of the explanation div's contents contains "questions..."
  - next to the "questions..." is an <a>
  - the <a> contains an href matching its own text contents
  - the href links to our customer service system

I call this topic "XPath can see around corners":

http://www.oreillynet.com/onlamp/blog/2007/08/xpath_checker_and_assert_xpath.html

We are using XPath to pin down several elements in a page, allowing the other 
elements to change freely, but forcing them to maintain their correlations. That 
test would fail, for example, if the <a> somehow moved away from its 
introductory paragraph.

-- 
   Phlip
   http://www.zeroplayer.com/


From phlip2005 at gmail.com  Sun Mar  8 14:45:13 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 08 Mar 2009 11:45:13 -0700
Subject: [rspec-users] response.body.should be_xml_with -- how to do
 nested xpath matches
In-Reply-To: <85d99afe0903081123rcd7b479tf3cc93fc5301ba09@mail.gmail.com>
References: <gp0tk0$7n7$1@ger.gmane.org>	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
	<85d99afe0903081123rcd7b479tf3cc93fc5301ba09@mail.gmail.com>
Message-ID: <gp13nr$oul$3@ger.gmane.org>

Zach Dennis wrote:

>> response.body.should be_xml_with do
>>  form :action => '/users' do
>>    fieldset do
>>      legend "Personal Information"
>>      label "First name"
>>      input :type => 'text', :name => 'user[first_name]'
>>    end
>>  end
>> end

> I like this a lot.

Then it should be ".should be_html_with"...

...and the diagnostics should be as comprehensive & detailed as mine!



From dchelimsky at gmail.com  Sun Mar  8 15:30:23 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 8 Mar 2009 14:30:23 -0500
Subject: [rspec-users] response.body.should be_xml_with -- how to do
	nested xpath matches
In-Reply-To: <gp13hb$oul$1@ger.gmane.org>
References: <gp0tk0$7n7$1@ger.gmane.org>
	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
	<gp13hb$oul$1@ger.gmane.org>
Message-ID: <57c63afe0903081230v360048f0w3a49b9da8baa5c53@mail.gmail.com>

On Sun, Mar 8, 2009 at 1:41 PM, Phlip <phlip2005 at gmail.com> wrote:
> David Chelimsky wrote:
>
>>> ? ? ? ? xpath :'legend[ contains(., "Personal Information") ]' and
>>> ? ? ? ? xpath :'label[ contains(., "First name") ]' and
>>> ? ? ? ? xpath :input, :type => 'text', :name => 'user[first_name]'
>
>> This is nice, but the abstractions are operating at different levels.
>> The keyword is "xpath" but the args passed to that look nothing like
>> xpath.
>
> That's because it's a DSL. You can use raw XPath, XPath with one convenience
> (:'div[ @class = "content" ]' as a symbol implies "any descendant"), or you
> can use an option hash that generates XPath.
>
> The DSL's benefit is tags like :attribute => foo will automatically escape
> their strings correctly. (That's why the top line of the diagnostic was a
> little cluttered!) foo could contain mixed ' and " payload, and we don't
> care.
>
>> How about something like:
>
>> response.body.should be_xml_with do
>> ?form :action => '/users' do
>> ? ?fieldset do
>> ? ? ?legend "Personal Information"
>> ? ? ?label "First name"
>
> Because I'm not webrat?
>
> Yes it would be kewt if label('yo') went into method_missing and came out as
> //label[ contains(., "yo") ]. But I have found that spot checks of
> algorithmic details, such as eRB tags, are more valuable to development than
> slavishly matching your tests to your HTML contents.
>
> If you write this HTML...
>
> ?<form blah>
> ? ?<input blah>
> ? ?<input blah>
> ? ?<input blah>
> ?</form>
>
> ...and if you test it with a sequence of assertions that exactly match it...
>
> ?page.should contain
> ? ?form blah
> ? ? ?input blah
> ? ? ?input blah
> ? ? ?input blah
> ? ?end
> ?end
>
> ...then you are not really doing TDD. You are merely replicating your code
> as your test, and that will only cause irritation at upgrade time or bug
> time.


I'm only talking about syntax of the DSL - I don't see how changing
the syntax would make you suddenly start writing crappy examples or
not doing TDD.

- David


> Here's an example from our projects at work:
>
> ? ?get :thanks_for_purchasing
> ? ?assert_xpath :'center[ . = "Your order has been accepted!" ]'
> ? ?assert_xpath :div, :align => :center do
> ? ? ?a = assert_xpath(:'p[ contains(., "questions about your membership")
> ]/a')
> ? ? ?assert{ a.text == a[:href] }
> ? ? ?assert{ a[:href] == SubscriptionController::CUSTOMER_SERVICE_LINK }
> ? ?end
>
> Note how much that specifies in the customer acknowledgment page.
>
> ?- the confirmation is centered
> ?- the explanation div is centered (yes, we could identify it better!)
> ?- part of the explanation div's contents contains "questions..."
> ?- next to the "questions..." is an <a>
> ?- the <a> contains an href matching its own text contents
> ?- the href links to our customer service system
>
> I call this topic "XPath can see around corners":
>
> http://www.oreillynet.com/onlamp/blog/2007/08/xpath_checker_and_assert_xpath.html
>
> We are using XPath to pin down several elements in a page, allowing the
> other elements to change freely, but forcing them to maintain their
> correlations. That test would fail, for example, if the <a> somehow moved
> away from its introductory paragraph.
>
> --
> ?Phlip
> ?http://www.zeroplayer.com/
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From zach.dennis at gmail.com  Sun Mar  8 15:55:58 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Sun, 8 Mar 2009 15:55:58 -0400
Subject: [rspec-users] response.body.should be_xml_with -- how to do
	nested xpath matches
In-Reply-To: <gp13hb$oul$1@ger.gmane.org>
References: <gp0tk0$7n7$1@ger.gmane.org>
	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
	<gp13hb$oul$1@ger.gmane.org>
Message-ID: <85d99afe0903081255t1fe64178va3b7ee7fd5bd3d0@mail.gmail.com>

On Sun, Mar 8, 2009 at 2:41 PM, Phlip <phlip2005 at gmail.com> wrote:
> David Chelimsky wrote:
>
>>>         xpath :'legend[ contains(., "Personal Information") ]' and
>>>         xpath :'label[ contains(., "First name") ]' and
>>>         xpath :input, :type => 'text', :name => 'user[first_name]'
>
>> This is nice, but the abstractions are operating at different levels.
>> The keyword is "xpath" but the args passed to that look nothing like
>> xpath.
>
> That's because it's a DSL. You can use raw XPath, XPath with one convenience
> (:'div[ @class = "content" ]' as a symbol implies "any descendant"), or you
> can use an option hash that generates XPath.
>
> The DSL's benefit is tags like :attribute => foo will automatically escape
> their strings correctly. (That's why the top line of the diagnostic was a
> little cluttered!) foo could contain mixed ' and " payload, and we don't
> care.
>
>> How about something like:
>
>> response.body.should be_xml_with do
>>  form :action => '/users' do
>>    fieldset do
>>      legend "Personal Information"
>>      label "First name"
>
> Because I'm not webrat?
>
> Yes it would be kewt if label('yo') went into method_missing and came out as
> //label[ contains(., "yo") ]. But I have found that spot checks of
> algorithmic details, such as eRB tags, are more valuable to development than
> slavishly matching your tests to your HTML contents.
>
> If you write this HTML...
>
>  <form blah>
>    <input blah>
>    <input blah>
>    <input blah>
>  </form>
>
> ...and if you test it with a sequence of assertions that exactly match it...
>
>  page.should contain
>    form blah
>      input blah
>      input blah
>      input blah
>    end
>  end
>
> ...then you are not really doing TDD. You are merely replicating your code
> as your test, and that will only cause irritation at upgrade time or bug
> time.

This doesn't make a whole lot sense. How does the following move you
from TDD to non-TDD?

   xpath :input, :name => "foo"
to
   input :name => "foo"

XPath is merely the mechanism in which you're allowed to find
particular elements on a page. After typing:

   xpath :input, :name => "foo"
   xpath :input, :name => "bar"
   xpath :input, :name => "baz"

I would probably write my own wrapper so I could omit the redundant
"xpath" call all over the place. After all, I only care that the input
is found, if it uses XPath to do it--awesome.


>
> Here's an example from our projects at work:
>
>    get :thanks_for_purchasing
>    assert_xpath :'center[ . = "Your order has been accepted!" ]'
>    assert_xpath :div, :align => :center do
>      a = assert_xpath(:'p[ contains(., "questions about your membership")
> ]/a')
>      assert{ a.text == a[:href] }
>      assert{ a[:href] == SubscriptionController::CUSTOMER_SERVICE_LINK }
>    end
>
> Note how much that specifies in the customer acknowledgment page.
>
>  - the confirmation is centered
>  - the explanation div is centered (yes, we could identify it better!)
>  - part of the explanation div's contents contains "questions..."
>  - next to the "questions..." is an <a>
>  - the <a> contains an href matching its own text contents
>  - the href links to our customer service system

In my experience relying on the syntactic details of the page is
extremely brittle and cumbersome. Writing semantic HTML and semantic
view specs (whether you use rspec or assert2.0 or whatever) seems to
remove unnecessary overhead, such as caring about a "div" or a "p" tag
on the page. Some tags have both syntactic and semantic meaning, such
as forms, labels, fieldsets, and anchor tags.

Given your above assertions, if you replaced your <center> tag (which
is deprecated in HTML 4.01) with a div, and made it centered via CSS,
your assertion would fail. But should it? The presentation is changing
without affecting the behaviour of the view--it's still displaying the
"Your order has been accepted" confirmation. Why not utilize semantic
HTML to not be affected by a syntactic details that doesn't affect
whether or not your view is doing the right thing.

I'd apply the same considerations to the div and the p tags you're
making assertions against.


>
> I call this topic "XPath can see around corners":
>
> http://www.oreillynet.com/onlamp/blog/2007/08/xpath_checker_and_assert_xpath.html
>
> We are using XPath to pin down several elements in a page, allowing the
> other elements to change freely, but forcing them to maintain their
> correlations. That test would fail, for example, if the <a> somehow moved
> away from its introductory paragraph.

Are these correlations best managed by specs? Our customers and
designers move things around on the page all of the time without
affecting behaviour, merely presentation, and having those changes
break all of the view specs is painful. It also seems unnecessary if
they move from a series of "div" tags to a "ul" with "li" elements.


>
> --
>  Phlip
>  http://www.zeroplayer.com/
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From phlip2005 at gmail.com  Sun Mar  8 16:14:19 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 08 Mar 2009 13:14:19 -0700
Subject: [rspec-users] response.body.should be_xml_with -- how to do
 nested xpath matches
In-Reply-To: <85d99afe0903081123rcd7b479tf3cc93fc5301ba09@mail.gmail.com>
References: <gp0tk0$7n7$1@ger.gmane.org>	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
	<85d99afe0903081123rcd7b479tf3cc93fc5301ba09@mail.gmail.com>
Message-ID: <gp18uu$9dp$1@ger.gmane.org>

Zach Dennis wrote:

>> response.body.should be_xml_with do
>>  form :action => '/users' do
>>    fieldset do
>>      legend "Personal Information"
>>      label "First name"
>>      input :type => 'text', :name => 'user[first_name]'
>>    end
>>  end
>> end

> I like this a lot.

I just thought of about 3 truly sick ways to do that.

Let me write them up, and then we will resume this thread.

I expect to also throw in Strict XHTML compliance checking as an option. <a> 
cannot be around <div>, etc; stuff like that. (Or whatever those rules are!)

If I were evil, I would also permit :type => /e/, for those who want any type 
with an /e/ in it!

-- 
   Phlip
   http://www.zeroplayer.com/


From rockrep at gmail.com  Sun Mar  8 16:32:13 2009
From: rockrep at gmail.com (Michael K)
Date: Sun, 8 Mar 2009 13:32:13 -0700 (PDT)
Subject: [rspec-users] rspec,
	rspec-rails 1.1.99-12 and script/spec 'no such file to load -- spec'
In-Reply-To: <57c63afe0903070853q7f00fa5j310c8eeaa34a7075@mail.gmail.com>
References: <b1c4d55f-1ac2-4b11-b758-44b5ebd2baf1@x29g2000prf.googlegroups.com>
	<57c63afe0903070650w5de9e136u72ecb143b4a62db1@mail.gmail.com> 
	<57c63afe0903070853q7f00fa5j310c8eeaa34a7075@mail.gmail.com>
Message-ID: <be82a1b7-0481-4f61-ae37-6d5fb899c975@q9g2000yqc.googlegroups.com>

Hi David,

Thanks for the quick reply, info, and patch.

>
> This fixed and pushed to github
>
> http://github.com/dchelimsky/rspec-rails/commit/cd15dd5cbd6ca9cf2cd2f...
>
>

> > I've seen this with older versions of lib/tasks/rspec.rake that
> > required 'spec'. Basically, when you run any rake task in rails, rake
> > loads up the Rakefile in the project root *and* all of the .rake files
> > in lib/tasks before executing anything. So if any of those files
> > require 'spec', then the rails/gems framework will consider rspec to
> > be loaded already, and won't let you unpack it.
>
> > Try this:
>
> > rm lib/tasks/rspec.rake
> > rake gems RAILS_ENV='test'
>
> > If that changes rspec to [I], then you can unpack it and you should be
> > good to go.
>

I tried removing rspec.rake again as suggested, but it did not help,
and rspec would still not unpack using 'rake gems:unpack
RAILS_ENV=test'.   The rspec dependency of rspec-rails was marked as
'I', but it still had an 'R' next to the top-level rspec.  I also
tried removing uuidtools (and searched all the other .rake files in my
source tree for references to require 'spec') to see if that had any
effect since it lists a dependency on rspec, but that also did not
help.  I'm showing the full list of my RAILS_ENV=test gem dependencies
here in case the additional info helps.

 - [F] uuidtools
    - [I] rake = 0.8.3
    - [I] rspec = 1.1.99.12
 - [F] faker
 - [F] populator
 - [F] mislav-will_paginate ~> 2.3.7
 - [R] hpricot = 0.6.164
 - [R] rspec >= 1.1.99.12
 - [F] rspec-rails >= 1.1.99.12
    - [I] rspec = 1.1.99.12
    - [F] rack = 0.9.1
    - [ ] cucumber >= 0.1.13
    - [ ] hoe >= 1.9.0

On a positive note, I managed to resolve this issue by manually
unpacking rspec using 'gem unpack' instead of 'rails gem:unpack'.
Here are the steps I took.  Maybe this will help someone else who runs
into this issue.   Note: config/environments/test.rb already is
configured for rspec and rspec-rails as gem dependencies.

* sudo gem uninstall rspec -v 1.1.99.12
* sudo gem uninstall rspec-rails -v 1.1.99.12
* re-cloned, re-built, and re-installed both rspec-1.1.99.12 and rspec-
rails-1.1.99.12 to pick up your patch as described in
http://wiki.github.com/dchelimsky/rspec/edge
* cd RAILS_ROOT
* rm lib/tasks/rspec.rake
* rm -rf vendor/gems/rspec-1.1.99.12
* rm -rf vendor/gems/rspec-rails-1.1.99.12
* cd vendor/gems
* sudo gem unpack rspec -v 1.1.99.12
* sudo chown -R michael:staff rspec-1.1.99.12
* cd RAILS_ROOT
* rake gems:refresh_specs RAILS_ENV=test   # this because gem unpack
does not create a .specification file
* sudo rake gems:unpack RAILS_ENV=test    # unpacks rspec-rails
* sudo rake gems:unpack:dependencies RAILS_ENV=test    # I had already
done this previously, so didn't need this step, but listed here in
case someone following this hasn't yet
* script/generate rspec

And voila!,  'script/spec' works again!     'rake gems RAILS_ENV=test'
still doesn't show rspec as 'F' which makes me slightly nervous, but
everything is functional again.

-Michael


From hayafirst at gmail.com  Sun Mar  8 22:49:43 2009
From: hayafirst at gmail.com (Yi)
Date: Sun, 8 Mar 2009 21:49:43 -0500
Subject: [rspec-users] route_for
Message-ID: <ee6f48c00903081949p7a987402x33ae1ff222af1369@mail.gmail.com>

Get restful-authentication and rspec trunk from github. And a couple tests
fail. One of them is this assertion:

route_for(:controller => 'users', :action => 'destroy', :id => '1').should
== "/users/1"

error msg is:

should route users's 'destroy' action correctly

The recognized options <{"action"=>"show", "id"=>"1",
"controller"=>"users"}> did not match <{"action"=>"destroy", "id"=>"1",
"controller"=>"users"}>, difference: <{"action"=>"destroy"}>

But  assert_generates from rails works fine.

I myself never used route_for helper before. So I am not sure is this is the
problem of the method, or restful_authentication author misused it, or rails
2.3RC2 breaks it.

Thanks

Yi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090308/165f6243/attachment.html>

From dchelimsky at gmail.com  Sun Mar  8 23:15:29 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 8 Mar 2009 22:15:29 -0500
Subject: [rspec-users] route_for
In-Reply-To: <ee6f48c00903081949p7a987402x33ae1ff222af1369@mail.gmail.com>
References: <ee6f48c00903081949p7a987402x33ae1ff222af1369@mail.gmail.com>
Message-ID: <57c63afe0903082015h23a658c7mbc024786123688d1@mail.gmail.com>

On Sun, Mar 8, 2009 at 9:49 PM, Yi <hayafirst at gmail.com> wrote:
> Get restful-authentication and rspec trunk from github. And a couple tests
> fail. One of them is this assertion:
>
> route_for(:controller => 'users', :action => 'destroy', :id => '1').should
> == "/users/1"
>
> error msg is:
>
> should route users's 'destroy' action correctly
>
> The recognized options <{"action"=>"show", "id"=>"1",
> "controller"=>"users"}> did not match <{"action"=>"destroy", "id"=>"1",
> "controller"=>"users"}>, difference: <{"action"=>"destroy"}>
>
> But? assert_generates from rails works fine.
>
> I myself never used route_for helper before. So I am not sure is this is the
> problem of the method, or restful_authentication author misused it, or rails
> 2.3RC2 breaks it.

Actually, it's rspec's edge that breaks it, documented here:

http://github.com/dchelimsky/rspec-rails/blob/master/Upgrade.markdown

Somebody should probably offer up a patch to restful_authentication.
I'll do it unless anybody else cares to volunteer.

Cheers,
David

>
> Thanks
>
> Yi
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Sun Mar  8 23:21:10 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 8 Mar 2009 22:21:10 -0500
Subject: [rspec-users] route_for
In-Reply-To: <57c63afe0903082015h23a658c7mbc024786123688d1@mail.gmail.com>
References: <ee6f48c00903081949p7a987402x33ae1ff222af1369@mail.gmail.com>
	<57c63afe0903082015h23a658c7mbc024786123688d1@mail.gmail.com>
Message-ID: <57c63afe0903082021w678e5a20tad3d0732ff9f9d18@mail.gmail.com>

On Sun, Mar 8, 2009 at 10:15 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Sun, Mar 8, 2009 at 9:49 PM, Yi <hayafirst at gmail.com> wrote:
>> Get restful-authentication and rspec trunk from github. And a couple tests
>> fail. One of them is this assertion:
>>
>> route_for(:controller => 'users', :action => 'destroy', :id => '1').should
>> == "/users/1"
>>
>> error msg is:
>>
>> should route users's 'destroy' action correctly
>>
>> The recognized options <{"action"=>"show", "id"=>"1",
>> "controller"=>"users"}> did not match <{"action"=>"destroy", "id"=>"1",
>> "controller"=>"users"}>, difference: <{"action"=>"destroy"}>
>>
>> But? assert_generates from rails works fine.
>>
>> I myself never used route_for helper before. So I am not sure is this is the
>> problem of the method, or restful_authentication author misused it, or rails
>> 2.3RC2 breaks it.
>
> Actually, it's rspec's edge that breaks it, documented here:
>
> http://github.com/dchelimsky/rspec-rails/blob/master/Upgrade.markdown
>
> Somebody should probably offer up a patch to restful_authentication.
> I'll do it unless anybody else cares to volunteer.

Actually, I'm already on it.

>
> Cheers,
> David
>
>>
>> Thanks
>>
>> Yi
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>

From dchelimsky at gmail.com  Sun Mar  8 23:45:27 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 8 Mar 2009 22:45:27 -0500
Subject: [rspec-users] route_for
In-Reply-To: <57c63afe0903082021w678e5a20tad3d0732ff9f9d18@mail.gmail.com>
References: <ee6f48c00903081949p7a987402x33ae1ff222af1369@mail.gmail.com>
	<57c63afe0903082015h23a658c7mbc024786123688d1@mail.gmail.com>
	<57c63afe0903082021w678e5a20tad3d0732ff9f9d18@mail.gmail.com>
Message-ID: <57c63afe0903082045y7818563dyfae2a90070a2a7cb@mail.gmail.com>

On Sun, Mar 8, 2009 at 10:21 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Sun, Mar 8, 2009 at 10:15 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
>> On Sun, Mar 8, 2009 at 9:49 PM, Yi <hayafirst at gmail.com> wrote:
>>> Get restful-authentication and rspec trunk from github. And a couple tests
>>> fail. One of them is this assertion:
>>>
>>> route_for(:controller => 'users', :action => 'destroy', :id => '1').should
>>> == "/users/1"
>>>
>>> error msg is:
>>>
>>> should route users's 'destroy' action correctly
>>>
>>> The recognized options <{"action"=>"show", "id"=>"1",
>>> "controller"=>"users"}> did not match <{"action"=>"destroy", "id"=>"1",
>>> "controller"=>"users"}>, difference: <{"action"=>"destroy"}>
>>>
>>> But? assert_generates from rails works fine.
>>>
>>> I myself never used route_for helper before. So I am not sure is this is the
>>> problem of the method, or restful_authentication author misused it, or rails
>>> 2.3RC2 breaks it.
>>
>> Actually, it's rspec's edge that breaks it, documented here:
>>
>> http://github.com/dchelimsky/rspec-rails/blob/master/Upgrade.markdown
>>
>> Somebody should probably offer up a patch to restful_authentication.
>> I'll do it unless anybody else cares to volunteer.
>
> Actually, I'm already on it.

Here it is:

http://github.com/dchelimsky/restful-authentication/commit/ad92c6cb52500c37ef81e30ac4e79adffc2f4d39

I've sent technoweenie a pull request.

Thanks for bringing this to my attention.

Cheers,
David

>
>>
>> Cheers,
>> David
>>
>>>
>>> Thanks
>>>
>>> Yi
>>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>
>

From hayafirst at gmail.com  Sun Mar  8 23:54:02 2009
From: hayafirst at gmail.com (Yi)
Date: Sun, 8 Mar 2009 22:54:02 -0500
Subject: [rspec-users] route_for
In-Reply-To: <57c63afe0903082045y7818563dyfae2a90070a2a7cb@mail.gmail.com>
References: <ee6f48c00903081949p7a987402x33ae1ff222af1369@mail.gmail.com>
	<57c63afe0903082015h23a658c7mbc024786123688d1@mail.gmail.com>
	<57c63afe0903082021w678e5a20tad3d0732ff9f9d18@mail.gmail.com>
	<57c63afe0903082045y7818563dyfae2a90070a2a7cb@mail.gmail.com>
Message-ID: <ee6f48c00903082054y3a585935k52f85152e1fe5cbc@mail.gmail.com>

David, thanks very much

Yi

On Sun, Mar 8, 2009 at 10:45 PM, David Chelimsky <dchelimsky at gmail.com>wrote:

> On Sun, Mar 8, 2009 at 10:21 PM, David Chelimsky <dchelimsky at gmail.com>
> wrote:
> > On Sun, Mar 8, 2009 at 10:15 PM, David Chelimsky <dchelimsky at gmail.com>
> wrote:
> >> On Sun, Mar 8, 2009 at 9:49 PM, Yi <hayafirst at gmail.com> wrote:
> >>> Get restful-authentication and rspec trunk from github. And a couple
> tests
> >>> fail. One of them is this assertion:
> >>>
> >>> route_for(:controller => 'users', :action => 'destroy', :id =>
> '1').should
> >>> == "/users/1"
> >>>
> >>> error msg is:
> >>>
> >>> should route users's 'destroy' action correctly
> >>>
> >>> The recognized options <{"action"=>"show", "id"=>"1",
> >>> "controller"=>"users"}> did not match <{"action"=>"destroy", "id"=>"1",
> >>> "controller"=>"users"}>, difference: <{"action"=>"destroy"}>
> >>>
> >>> But  assert_generates from rails works fine.
> >>>
> >>> I myself never used route_for helper before. So I am not sure is this
> is the
> >>> problem of the method, or restful_authentication author misused it, or
> rails
> >>> 2.3RC2 breaks it.
> >>
> >> Actually, it's rspec's edge that breaks it, documented here:
> >>
> >> http://github.com/dchelimsky/rspec-rails/blob/master/Upgrade.markdown
> >>
> >> Somebody should probably offer up a patch to restful_authentication.
> >> I'll do it unless anybody else cares to volunteer.
> >
> > Actually, I'm already on it.
>
> Here it is:
>
>
> http://github.com/dchelimsky/restful-authentication/commit/ad92c6cb52500c37ef81e30ac4e79adffc2f4d39
>
> I've sent technoweenie a pull request.
>
> Thanks for bringing this to my attention.
>
> Cheers,
> David
>
> >
> >>
> >> Cheers,
> >> David
> >>
> >>>
> >>> Thanks
> >>>
> >>> Yi
> >>>
> >>> _______________________________________________
> >>> rspec-users mailing list
> >>> rspec-users at rubyforge.org
> >>> http://rubyforge.org/mailman/listinfo/rspec-users
> >>>
> >>
> >
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090308/5f47133f/attachment.html>

From phlip2005 at gmail.com  Mon Mar  9 02:43:05 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 08 Mar 2009 23:43:05 -0700
Subject: [rspec-users] response.body.should be_xml_with -- how to do
 nested xpath matches
In-Reply-To: <85d99afe0903081255t1fe64178va3b7ee7fd5bd3d0@mail.gmail.com>
References: <gp0tk0$7n7$1@ger.gmane.org>	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>	<gp13hb$oul$1@ger.gmane.org>
	<85d99afe0903081255t1fe64178va3b7ee7fd5bd3d0@mail.gmail.com>
Message-ID: <gp2dpt$p7t$1@ger.gmane.org>

Zach Dennis wrote:

> XPath is merely the mechanism in which you're allowed to find
> particular elements on a page. After typing:
> 
>    xpath :input, :name => "foo"
>    xpath :input, :name => "bar"
>    xpath :input, :name => "baz"
> 
> I would probably write my own wrapper so I could omit the redundant
> "xpath" call all over the place. After all, I only care that the input
> is found, if it uses XPath to do it--awesome.

Yet such a wrapper can fit quite comfortably on the application side - not 
necessarily on the vendor side. For example, if I care that a given sequence of 
inputs have a class keyed to the current user's permissions, then that (and the 
naughty xpath) go inside the new custom assertion: assert_input_for(@user). Such 
wrappers obviously should not fall on the vendor side.

I like leaving the XPath hanging out because its operators and axes are always 
available _without_ more DSLization.

Your remaining points are noted - the answers are either "violent agreement" or 
"then don't do it like that". Augmented by my next post!

-- 
  Phlip
  http://www.zeroplayer.com/


From phlip2005 at gmail.com  Mon Mar  9 02:59:14 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 08 Mar 2009 23:59:14 -0700
Subject: [rspec-users] custom, nested HTML matchers in RSpec
Message-ID: <49B4BE42.1020109@gmail.com>

Zach Dennis wrote:

 >> response.body.should be_xml_with do
 >>  form :action => '/users' do
 >>    fieldset do
 >>      legend "Personal Information"
 >>      label "First name"
 >>      input :type => 'text', :name => 'user[first_name]'
 >>    end
 >>  end
 >> end

 > I like this a lot.

Boom: http://gist.github.com/76136

   it 'should have a form with a fieldset' do
     render '/users/new'

     response.body.should be_html_with{
       form :action => '/users' do
         fieldset do
           legend 'Personal Information'
           label 'First name'
           input :type => 'text', :name => 'user[first_name]'
         end
       end
     }
   end

I think I never got around to writing that because I just always assumed someone 
already had. I have to watch that about myself!

Only one feature is missing: At fault time, the matcher naturally prints out a 
diagnostic containing two snips of HTML - the specification's reference, and 
your page's sample. (Both, of course, are restricted to the fault's context - 
not the whole page.) But...

The samples are not indented! The specification's reference is all run together, 
and your page's sample is (unfortunately!) exactly the way your View system 
generated it. I have a question out to Nokogiri about this...

-- 
   Phlip
   http://www.zeroplayer.com/


From oliver.beddows at googlemail.com  Mon Mar  9 05:44:04 2009
From: oliver.beddows at googlemail.com (karmacoma)
Date: Mon, 9 Mar 2009 02:44:04 -0700 (PDT)
Subject: [rspec-users] Rails 2.2.2 Problem - button_to_function -
	nil.with_output_buffer
Message-ID: <a04e8041-976c-4b09-9e4f-cadaeda85b2a@p20g2000yqi.googlegroups.com>

Hi,
I am in the process of upgrading my rails application to be compatible
with rails 2.2.2. All is going well apart from a few remaining issues.

My problem is: I am experiencing a test failure with what seems to be
related to the "with_output_buffer" method found in "lib/action_view/
helpers/capture_helper.rb" and my use of the "button_to_function"
method.

The code itself works fine. It is simply the test itself that won't
pass due to a NoMethodError exception.

Note: I am currently using rspec & rspec-rails (1.1.99.12), although
the same problem also exists when tested with the current stable
version: 1.1.12.

So, given the following helper module:
---
module ImagesHelper
 def hide_images_button
   content_tag :div, :class => :hide_images_button do
     button_to_function "Hide Images", :id => :hide_images_button do |
page|
       page[:more_images_button].toggle
       page[:image_browser].toggle
     end
   end
 end
end
---

With the accompanying test:
---
require File.expand_path(File.dirname(__FILE__) + '/../spec_helper')

describe ImagesHelper do
 it "should render a hide_images_button" do
   helper.hide_images_button.should have_tag('div[class=?]',
'hide_images_button') do
     with_tag('input[id=?][type=?][value=?][onclick^=?]',
'hide_images_button', 'button', 'Hide Images', "$
(&quot;more_images_button&quot;).toggle();\n$
(&quot;image_browser&quot;).toggle();;")
   end
 end
end
---

I am getting the following failure:
---
F

1)
NoMethodError in 'ImagesHelper should render a hide_images_button'
You have a nil object when you didn't expect it!
The error occurred while evaluating nil.with_output_buffer
/home/oliver/git/greyville/app/helpers/images_helper.rb:4:in
`hide_images_button'
/home/oliver/git/greyville/app/helpers/images_helper.rb:3:in
`hide_images_button'
spec/helpers/images_helper_spec.rb:5:

Finished in 0.025206 seconds

1 example, 1 failure
---

Any bright ideas on how I can fix this issue? Your help would be much
appreciated.
Regards, Oliver Beddows.

From dchelimsky at gmail.com  Mon Mar  9 07:25:55 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 9 Mar 2009 06:25:55 -0500
Subject: [rspec-users] Rails 2.2.2 Problem - button_to_function -
	nil.with_output_buffer
In-Reply-To: <a04e8041-976c-4b09-9e4f-cadaeda85b2a@p20g2000yqi.googlegroups.com>
References: <a04e8041-976c-4b09-9e4f-cadaeda85b2a@p20g2000yqi.googlegroups.com>
Message-ID: <57c63afe0903090425l6f8c31f3k9f5355362be37676@mail.gmail.com>

On Mon, Mar 9, 2009 at 4:44 AM, karmacoma <oliver.beddows at googlemail.com> wrote:
> Hi,
> I am in the process of upgrading my rails application to be compatible
> with rails 2.2.2. All is going well apart from a few remaining issues.
>
> My problem is: I am experiencing a test failure with what seems to be
> related to the "with_output_buffer" method found in "lib/action_view/
> helpers/capture_helper.rb" and my use of the "button_to_function"
> method.
>
> The code itself works fine. It is simply the test itself that won't
> pass due to a NoMethodError exception.
>
> Note: I am currently using rspec & rspec-rails (1.1.99.12), although
> the same problem also exists when tested with the current stable
> version: 1.1.12.
>
> So, given the following helper module:
> ---
> module ImagesHelper
> ?def hide_images_button
> ? content_tag :div, :class => :hide_images_button do
> ? ? button_to_function "Hide Images", :id => :hide_images_button do |
> page|
> ? ? ? page[:more_images_button].toggle
> ? ? ? page[:image_browser].toggle
> ? ? end
> ? end
> ?end
> end
> ---
>
> With the accompanying test:
> ---
> require File.expand_path(File.dirname(__FILE__) + '/../spec_helper')
>
> describe ImagesHelper do
> ?it "should render a hide_images_button" do
> ? helper.hide_images_button.should have_tag('div[class=?]',
> 'hide_images_button') do
> ? ? with_tag('input[id=?][type=?][value=?][onclick^=?]',
> 'hide_images_button', 'button', 'Hide Images', "$
> (&quot;more_images_button&quot;).toggle();\n$
> (&quot;image_browser&quot;).toggle();;")
> ? end
> ?end
> end
> ---
>
> I am getting the following failure:
> ---
> F
>
> 1)
> NoMethodError in 'ImagesHelper should render a hide_images_button'
> You have a nil object when you didn't expect it!
> The error occurred while evaluating nil.with_output_buffer
> /home/oliver/git/greyville/app/helpers/images_helper.rb:4:in
> `hide_images_button'
> /home/oliver/git/greyville/app/helpers/images_helper.rb:3:in
> `hide_images_button'
> spec/helpers/images_helper_spec.rb:5:
>
> Finished in 0.025206 seconds
>
> 1 example, 1 failure
> ---
>
> Any bright ideas on how I can fix this issue? Your help would be much
> appreciated.

Please report bugs to http://rspec.lighthouseapp.com.

Cheers,
David

> Regards, Oliver Beddows.

From aslak.hellesoy at gmail.com  Mon Mar  9 11:46:39 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Mon, 9 Mar 2009 16:46:39 +0100
Subject: [rspec-users] Cucumber 0.2 final release date?
In-Reply-To: <3202c5a31a4c97a8dcc16b22d901ef18@ruby-forum.com>
References: <7ac2300c0902190749x3d659b40w7cc84e5a6f8aedea@mail.gmail.com>
	<8d961d900902230636te143bc6o92ca13f709688ee9@mail.gmail.com>
	<3202c5a31a4c97a8dcc16b22d901ef18@ruby-forum.com>
Message-ID: <8d961d900903090846k56824fd9pee311eb8c7c50c5@mail.gmail.com>

On Fri, Mar 6, 2009 at 1:27 PM, Tom Ten thij <lists at ruby-forum.com> wrote:

>
> > I'm afraid I can't give a release date. 0.2 is fixed(ish) scope, and
> > therefore time can't be fixed at the same time. I have a lot of travel
> > the next month, so it will take a least a month I'm afraid.
>
> I know I for one would sure like to see 0.2 come out soon. The scope of
> the two 0.2 tickets in lighthouse seem a bit big. Are there any tasks
> that I could assist on?
>

Hi Tom,

I appreciate your offer, but unfortunately it's still too much in napkin,
moleskine, idea state:
http://www.ruby-forum.com/topic/179995

I just got back from holiday, and I expect to finish things within the next
2 weeks. From then on it should be easier to contribute again.

Cheers,
Aslak


>
> Tom.
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090309/6f5e8c68/attachment.html>

From lists at ruby-forum.com  Mon Mar  9 12:08:06 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 9 Mar 2009 17:08:06 +0100
Subject: [rspec-users] Presentation Testing and CSS ids
In-Reply-To: <85d99afe0903081255t1fe64178va3b7ee7fd5bd3d0@mail.gmail.com>
References: <gp0tk0$7n7$1@ger.gmane.org>
	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
	<gp13hb$oul$1@ger.gmane.org>
	<85d99afe0903081255t1fe64178va3b7ee7fd5bd3d0@mail.gmail.com>
Message-ID: <71d2b98da3f45f61b8fe3d7709d2f164@ruby-forum.com>

Zach Dennis wrote:

> In my experience relying on the syntactic details of the page is
> extremely brittle and cumbersome. ... Some tags have both syntactic
> and semantic meaning, such as forms, labels, fieldsets, and anchor tags.
> 

Is it "brittle" to test for specific css selectors that are tied to page 
details?  A typical case is where one has a button to drive in webrat 
and instead of using the button text we use the associated id value 
instead.
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Mon Mar  9 13:18:37 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 9 Mar 2009 18:18:37 +0100
Subject: [rspec-users] Cucumber - RSpec matcher
Message-ID: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>

I must be missing something obvious here but I cannot seem to see it.

I have this step definition:

When /entity named "(.*)" has a legal name "(.*)"/ do |name, legal|
  myentity = Entity.find_by_entity_common_name!(name.hll_keycase)
  myentity.entity_legal_name.should equal legal.hll_keycase
end

Which fails with this:

    And the entity named "Myuser" has a legal name "Myuser Legal Name"
# features/app/models/entities/step_definitions/entity_steps.rb:20
      expected #<ActiveSupport::Multibyte::Chars:0x2b4bb29e73d8
@wrapped_string="myuser legal name">, got "myuser legal name" (using
.equal?)

which to me says that I got what I expected (myuser legal name) but
which fails the equality test nonetheless.

However, if I switch the test to this:

  assert_equal(myentity.entity_legal_name,legal.hll_keycase)

Then the step definition passes.
-- 
Posted via http://www.ruby-forum.com/.

From aslak.hellesoy at gmail.com  Mon Mar  9 13:52:33 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Mon, 9 Mar 2009 18:52:33 +0100
Subject: [rspec-users] Cucumber - RSpec matcher
In-Reply-To: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
References: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
Message-ID: <8d961d900903091052i7dc4bbbasaece193b10d30375@mail.gmail.com>

On Mon, Mar 9, 2009 at 6:18 PM, James Byrne <lists at ruby-forum.com> wrote:

> I must be missing something obvious here but I cannot seem to see it.
>
> I have this step definition:
>
> When /entity named "(.*)" has a legal name "(.*)"/ do |name, legal|
>  myentity = Entity.find_by_entity_common_name!(name.hll_keycase)
>  myentity.entity_legal_name.should equal legal.hll_keycase
> end
>
> Which fails with this:
>
>    And the entity named "Myuser" has a legal name "Myuser Legal Name"
> # features/app/models/entities/step_definitions/entity_steps.rb:20
>      expected #<ActiveSupport::Multibyte::Chars:0x2b4bb29e73d8
> @wrapped_string="myuser legal name">, got "myuser legal name" (using
> .equal?)
>

Looks like you're expecting an instance of ActiveSupport::Multibyte::Chars,
but actually got an instance of String.

I'm not familiar with the ActiveSupport::Multibyte::Chars API, but as a
general rule, two object won't be #equal? unless they have the same type.

Aslak


>
> which to me says that I got what I expected (myuser legal name) but
> which fails the equality test nonetheless.
>
> However, if I switch the test to this:
>
>  assert_equal(myentity.entity_legal_name,legal.hll_keycase)
>
> Then the step definition passes.
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090309/3c5e5f22/attachment.html>

From pat.maddox at gmail.com  Mon Mar  9 13:54:06 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Mon, 9 Mar 2009 10:54:06 -0700
Subject: [rspec-users] Cucumber - RSpec matcher
In-Reply-To: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
References: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
Message-ID: <DB49C85A-9ECF-48EA-A6D9-4CE30D37E872@gmail.com>

Use should == instead of equal.  == is equality, equal is object  
identity.  You very rarely want to use equal.

 >> "foo".equal? "foo"
=> false
 >> "foo" == "foo"
=> true

Pat


On Mar 9, 2009, at 10:18 AM, James Byrne wrote:

> I must be missing something obvious here but I cannot seem to see it.
>
> I have this step definition:
>
> When /entity named "(.*)" has a legal name "(.*)"/ do |name, legal|
>  myentity = Entity.find_by_entity_common_name!(name.hll_keycase)
>  myentity.entity_legal_name.should equal legal.hll_keycase
> end
>
> Which fails with this:
>
>    And the entity named "Myuser" has a legal name "Myuser Legal Name"
> # features/app/models/entities/step_definitions/entity_steps.rb:20
>      expected #<ActiveSupport::Multibyte::Chars:0x2b4bb29e73d8
> @wrapped_string="myuser legal name">, got "myuser legal name" (using
> .equal?)
>
> which to me says that I got what I expected (myuser legal name) but
> which fails the equality test nonetheless.
>
> However, if I switch the test to this:
>
>  assert_equal(myentity.entity_legal_name,legal.hll_keycase)
>
> Then the step definition passes.
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From rdm at cfcl.com  Mon Mar  9 15:32:16 2009
From: rdm at cfcl.com (Rich Morin)
Date: Mon, 9 Mar 2009 11:32:16 -0800
Subject: [rspec-users] Cucumber - RSpec matcher
In-Reply-To: <DB49C85A-9ECF-48EA-A6D9-4CE30D37E872@gmail.com>
References: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
	<DB49C85A-9ECF-48EA-A6D9-4CE30D37E872@gmail.com>
Message-ID: <p0623090ac5db1eb12131@[192.168.1.205]>

At 10:54 -0700 3/9/09, Pat Maddox wrote:
> Use should == instead of equal.  == is equality, equal
> is object identity.  You very rarely want to use equal.

It's probably far too late to change this, but it might
have made more sense to define same_obj_as?() for the
object identity case, leaving equal?() available for the
more common test.

-r
-- 
http://www.cfcl.com/rdm            Rich Morin
http://www.cfcl.com/rdm/resume     rdm at cfcl.com
http://www.cfcl.com/rdm/weblog     +1 650-873-7841

Technical editing and writing, programming, and web development

From lists at ruby-forum.com  Mon Mar  9 14:56:19 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 9 Mar 2009 19:56:19 +0100
Subject: [rspec-users] Cucumber - RSpec matcher
In-Reply-To: <DB49C85A-9ECF-48EA-A6D9-4CE30D37E872@gmail.com>
References: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
	<DB49C85A-9ECF-48EA-A6D9-4CE30D37E872@gmail.com>
Message-ID: <669ebfb8925637d900f55c84ecb0875d@ruby-forum.com>

Pat Maddox wrote:
> Use should == instead of equal.  == is equality, equal is object
> identity.  You very rarely want to use equal.
> 
>  >> "foo".equal? "foo"
> => false
>  >> "foo" == "foo"
> => true
> 
> Pat

Thanks.  Although, if I recall correctly then I am advised to use the 
form

 "x.should be == y" .

;->
-- 
Posted via http://www.ruby-forum.com/.

From phlip2005 at gmail.com  Mon Mar  9 14:52:53 2009
From: phlip2005 at gmail.com (Phlip)
Date: Mon, 09 Mar 2009 11:52:53 -0700
Subject: [rspec-users] Presentation Testing and CSS ids
In-Reply-To: <71d2b98da3f45f61b8fe3d7709d2f164@ruby-forum.com>
References: <gp0tk0$7n7$1@ger.gmane.org>	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>	<gp13hb$oul$1@ger.gmane.org>	<85d99afe0903081255t1fe64178va3b7ee7fd5bd3d0@mail.gmail.com>
	<71d2b98da3f45f61b8fe3d7709d2f164@ruby-forum.com>
Message-ID: <gp3oi5$8s2$4@ger.gmane.org>

James Byrne wrote:
> Zach Dennis wrote:

>> In my experience relying on the syntactic details of the page is
>> extremely brittle and cumbersome. ... Some tags have both syntactic
>> and semantic meaning, such as forms, labels, fieldsets, and anchor tags.

> Is it "brittle" to test for specific css selectors that are tied to page 
> details?  A typical case is where one has a button to drive in webrat 
> and instead of using the button text we use the associated id value 
> instead.

It is if your art department refuses to stop putting styles on ID tags!

Other than that, if you need more than one TR, for example, and your test should 
scrape them up and look at them, searching for their class is nice.

Does anyone here allow their art departments to directly edit and check in 
html.erb files? I suppose that would change things!

-- 
   Phlip


From dchelimsky at gmail.com  Mon Mar  9 15:08:25 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 9 Mar 2009 14:08:25 -0500
Subject: [rspec-users] Cucumber - RSpec matcher
In-Reply-To: <p0623090ac5db1eb12131@192.168.1.205>
References: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
	<DB49C85A-9ECF-48EA-A6D9-4CE30D37E872@gmail.com>
	<p0623090ac5db1eb12131@192.168.1.205>
Message-ID: <57c63afe0903091208o471f3f4em569043ef57bd2869@mail.gmail.com>

On Mon, Mar 9, 2009 at 2:32 PM, Rich Morin <rdm at cfcl.com> wrote:
> At 10:54 -0700 3/9/09, Pat Maddox wrote:
>> Use should == instead of equal. ?== is equality, equal
>> is object identity. ?You very rarely want to use equal.
>
> It's probably far too late to change this, but it might
> have made more sense to define same_obj_as?() for the
> object identity case, leaving equal?() available for the
> more common test.

You're about two years too late. If I had it to do over again, I'd
probably stick with the original version:

"this".should equal(this)
:this.should be(:this)

But changing that back now would result in mutiny. C'est la vie.

>
> -r
> --
> http://www.cfcl.com/rdm ? ? ? ? ? ?Rich Morin
> http://www.cfcl.com/rdm/resume ? ? rdm at cfcl.com
> http://www.cfcl.com/rdm/weblog ? ? +1 650-873-7841
>
> Technical editing and writing, programming, and web development
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Mon Mar  9 15:21:52 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 9 Mar 2009 14:21:52 -0500
Subject: [rspec-users] Cucumber - RSpec matcher
In-Reply-To: <669ebfb8925637d900f55c84ecb0875d@ruby-forum.com>
References: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
	<DB49C85A-9ECF-48EA-A6D9-4CE30D37E872@gmail.com>
	<669ebfb8925637d900f55c84ecb0875d@ruby-forum.com>
Message-ID: <AA5E686C-F58A-440F-9B65-FA7DBC1F9F03@gmail.com>



Sent from my iPhone

On Mar 9, 2009, at 1:56 PM, James Byrne <lists at ruby-forum.com> wrote:

> Pat Maddox wrote:
>> Use should == instead of equal.  == is equality, equal is object
>> identity.  You very rarely want to use equal.
>>
>>>> "foo".equal? "foo"
>> => false
>>>> "foo" == "foo"
>> => true
>>
>> Pat
>
> Thanks.  Although, if I recall correctly then I am advised to use the
> form
>
> "x.should be == y" .

No, no, no :)

5.should == 5
6.should be > 5

Read them aloud and they.should make(:sense).

Cheers,
David


>
>
> ;->
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

From lists at ruby-forum.com  Mon Mar  9 15:36:06 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 9 Mar 2009 20:36:06 +0100
Subject: [rspec-users] Question on SQL exceptions
Message-ID: <3c23e108653d66177bb578f68466196f@ruby-forum.com>

To prevent duplicate values in the DBMS I use a unique index on those
columns.  I am testing that duplicate values cannot, in fact, be added.

This is the cucumber scenario:

  Scenario: The legal name must be unique
    Given I do have a user named "admin"
      And the user named "admin" is authenticated
      And the user named "admin" is authorized to "add" "entities"
      And I do have an entity named "Myuser"
      And the entity named "Myuser" has a legal name "Myuser Legal Name"
    When they visit the add a new entity page
      And they enter valid entity data
      And they enter the entity legal name "MyUser  LEGAL  NAME"
      And I press "Create"
    Then they should see a save error message

This is the step definition that should be triggered:

When /should see a save error message/ do
  response.body.should =~ /errors? prohibited this (.*) from being
saved/im
end

But what happens is that SQLite3 throws an SQL exception:
  SQLite3::SQLException: column entity_legal_name is not unique:...;

that is not caught by this controller:

  def create
    @entity = Entity.new(params[:entity])

    # need this to strip out observer attributes for datebalks plugin
    # see config/initializers/hash_addins.rb

    @client = @entity.build_client(params[:client].datebalk!)

    respond_to do |format|
      if @entity.save
        flash[:notice] = 'Client was successfully created.'
        format.html { redirect_to(@client) }
        format.xml  { render :xml => @client,
          :status => :created, :location => @client }
      else
        format.html { render :action => "new" }
        format.xml  { render :xml => @client.errors,
          :status => :unprocessable_entity }
      end
    end

I thought, probably incorrectly, that when #save is called then any
errors are returned to the controller to handle.  This is evidently not
happening so can someone tell me how this is supposed to be handled?
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Mon Mar  9 15:48:18 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 9 Mar 2009 20:48:18 +0100
Subject: [rspec-users] Cucumber - RSpec matcher
In-Reply-To: <AA5E686C-F58A-440F-9B65-FA7DBC1F9F03@gmail.com>
References: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
	<DB49C85A-9ECF-48EA-A6D9-4CE30D37E872@gmail.com>
	<669ebfb8925637d900f55c84ecb0875d@ruby-forum.com>
	<AA5E686C-F58A-440F-9B65-FA7DBC1F9F03@gmail.com>
Message-ID: <cf2e0fd8efdeb5f34484bcf6c1778c7e@ruby-forum.com>

David Chelimsky wrote:
>
> No, no, no :)
> 
> 5.should == 5
> 6.should be > 5
> 
> Read them aloud and they.should make(:sense).
> 
> Cheers,
> David

Perhaps it is my dialect, but what is wrong with:

   "5 should be equal to 5"

which generally is how I read "=="?  Actually, I tend to read "==" (in 
Ruby) as "is equal to".
-- 
Posted via http://www.ruby-forum.com/.

From pat.maddox at gmail.com  Mon Mar  9 15:59:46 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Mon, 9 Mar 2009 12:59:46 -0700
Subject: [rspec-users] Question on SQL exceptions
In-Reply-To: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
References: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
Message-ID: <1E9AE5E8-D92E-42E4-B637-A622E7B8D95F@gmail.com>

ActiveRecord doesn't know anything about db constraint errors.  If one  
is violated, the error propagates up in the form of an exception.

Put a validates_uniqueness_of :login_name on your User class, and  
you'll get the behavior you want.  You can keep the db constraint in  
as a safety net against possible race conditions at the app layer.

Pat



On Mar 9, 2009, at 12:36 PM, James Byrne wrote:

> To prevent duplicate values in the DBMS I use a unique index on those
> columns.  I am testing that duplicate values cannot, in fact, be  
> added.
>
> This is the cucumber scenario:
>
>  Scenario: The legal name must be unique
>    Given I do have a user named "admin"
>      And the user named "admin" is authenticated
>      And the user named "admin" is authorized to "add" "entities"
>      And I do have an entity named "Myuser"
>      And the entity named "Myuser" has a legal name "Myuser Legal  
> Name"
>    When they visit the add a new entity page
>      And they enter valid entity data
>      And they enter the entity legal name "MyUser  LEGAL  NAME"
>      And I press "Create"
>    Then they should see a save error message
>
> This is the step definition that should be triggered:
>
> When /should see a save error message/ do
>  response.body.should =~ /errors? prohibited this (.*) from being
> saved/im
> end
>
> But what happens is that SQLite3 throws an SQL exception:
>  SQLite3::SQLException: column entity_legal_name is not unique:...;
>
> that is not caught by this controller:
>
>  def create
>    @entity = Entity.new(params[:entity])
>
>    # need this to strip out observer attributes for datebalks plugin
>    # see config/initializers/hash_addins.rb
>
>    @client = @entity.build_client(params[:client].datebalk!)
>
>    respond_to do |format|
>      if @entity.save
>        flash[:notice] = 'Client was successfully created.'
>        format.html { redirect_to(@client) }
>        format.xml  { render :xml => @client,
>          :status => :created, :location => @client }
>      else
>        format.html { render :action => "new" }
>        format.xml  { render :xml => @client.errors,
>          :status => :unprocessable_entity }
>      end
>    end
>
> I thought, probably incorrectly, that when #save is called then any
> errors are returned to the controller to handle.  This is evidently  
> not
> happening so can someone tell me how this is supposed to be handled?
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From lists at ruby-forum.com  Mon Mar  9 16:00:19 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 9 Mar 2009 21:00:19 +0100
Subject: [rspec-users] Question on SQL exceptions
In-Reply-To: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
References: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
Message-ID: <39b9be9b27d41e77554fdf35d75fc733@ruby-forum.com>

James Byrne wrote:

Q.
> To prevent duplicate values in the DBMS I use a unique index on those
> columns.  I am testing that duplicate values cannot, in fact, be added.

> I thought, probably incorrectly, that when #save is called then any
> errors are returned to the controller to handle.  This is evidently not
> happening so can someone tell me how this is supposed to be handled?

A. rescue ActiveRecord::StatementInvalid
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Mon Mar  9 16:53:22 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 9 Mar 2009 21:53:22 +0100
Subject: [rspec-users] Question on SQL exceptions
In-Reply-To: <1E9AE5E8-D92E-42E4-B637-A622E7B8D95F@gmail.com>
References: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
	<1E9AE5E8-D92E-42E4-B637-A622E7B8D95F@gmail.com>
Message-ID: <a5dd30803999f3a632c16063c255dbfc@ruby-forum.com>

Pat Maddox wrote:
> ActiveRecord doesn't know anything about db constraint errors.  If one
> is violated, the error propagates up in the form of an exception.
> 

I realize that, but the exception is of the 
ActiveRecord:StatementInvalid class, which I should be able to catch in 
the controller with a rescue clause.  But, I am not getting this to work 
at the moment.  I thought that this should at least produce some out put 
but it never does:


  def create
    @entity = Entity.new(params[:entity])
    ...
    respond_to do |format|
      ...
      end
    end
  rescue => my_exception
    puts "Rescue clause invoked!"
    puts my_exception
  end


For now, all I want is to see the rescue clause invoked, but it is not.
have I put this clause in the wrong place? Am I specifying it wrong?

-- 
Posted via http://www.ruby-forum.com/.

From scott at railsnewbie.com  Mon Mar  9 16:59:33 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Mon, 9 Mar 2009 16:59:33 -0400
Subject: [rspec-users] Question on SQL exceptions
In-Reply-To: <a5dd30803999f3a632c16063c255dbfc@ruby-forum.com>
References: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
	<1E9AE5E8-D92E-42E4-B637-A622E7B8D95F@gmail.com>
	<a5dd30803999f3a632c16063c255dbfc@ruby-forum.com>
Message-ID: <0D47F466-6AC8-4725-9591-69B88BAD4D58@railsnewbie.com>


On Mar 9, 2009, at 4:53 PM, James Byrne wrote:

> Pat Maddox wrote:
>> ActiveRecord doesn't know anything about db constraint errors.  If  
>> one
>> is violated, the error propagates up in the form of an exception.
>>
>
> I realize that, but the exception is of the
> ActiveRecord:StatementInvalid class, which I should be able to catch  
> in
> the controller with a rescue clause.  But, I am not getting this to  
> work
> at the moment.  I thought that this should at least produce some out  
> put
> but it never does:
>
>
>  def create
>    @entity = Entity.new(params[:entity])
>    ...
>    respond_to do |format|
>      ...
>      end
>    end
>  rescue => my_exception
>    puts "Rescue clause invoked!"
>    puts my_exception
>  end
>
>
> For now, all I want is to see the rescue clause invoked, but it is  
> not.
> have I put this clause in the wrong place? Am I specifying it wrong?

You can try "rescue Exception" which rescues from all exceptions, not  
just ones which inherit from StandardError.  (rescue without an  
explicit error class *only* rescues from StandardExceptions and error  
classes which derive from it):

http://gist.github.com/76474

Also - I believe this only works in 1.8.6 and above, so if you're  
still on 1.8.5 I'd recommend an upgrade.

Scott


>
>
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From tim at pivotib.com  Mon Mar  9 17:22:03 2009
From: tim at pivotib.com (Tim Glen)
Date: Mon, 9 Mar 2009 17:22:03 -0400
Subject: [rspec-users] Question on SQL exceptions
In-Reply-To: <a5dd30803999f3a632c16063c255dbfc@ruby-forum.com>
References: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
	<1E9AE5E8-D92E-42E4-B637-A622E7B8D95F@gmail.com>
	<a5dd30803999f3a632c16063c255dbfc@ruby-forum.com>
Message-ID: <932FBF08-F62E-4940-8835-B066C5FC96EC@pivotib.com>

>> ActiveRecord doesn't know anything about db constraint errors.  If  
>> one
>> is violated, the error propagates up in the form of an exception.
>>
>
> I realize that, but the exception is of the
> ActiveRecord:StatementInvalid class, which I should be able to catch  
> in
> the controller with a rescue clause.  But, I am not getting this to  
> work
> at the moment.  I thought that this should at least produce some out  
> put
> but it never does:
>
>
>  def create
>    @entity = Entity.new(params[:entity])
>    ...
>    respond_to do |format|
>      ...
>      end
>    end
>  rescue => my_exception
>    puts "Rescue clause invoked!"
>    puts my_exception
>  end
>
>
> For now, all I want is to see the rescue clause invoked, but it is  
> not.
> have I put this clause in the wrong place? Am I specifying it wrong?

Just a stab in the dark, but I haven't seen any mention of calling  
save vs. save!. save just puts any errors in the model, save! will  
raise the exception if there are any errors. That may not be the case  
for ActiveRecord:StatementInvalid exception, but I thought i'd mention  
it anyway.

timg


From dchelimsky at gmail.com  Mon Mar  9 17:30:14 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 9 Mar 2009 16:30:14 -0500
Subject: [rspec-users] Cucumber - RSpec matcher
In-Reply-To: <cf2e0fd8efdeb5f34484bcf6c1778c7e@ruby-forum.com>
References: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
	<DB49C85A-9ECF-48EA-A6D9-4CE30D37E872@gmail.com>
	<669ebfb8925637d900f55c84ecb0875d@ruby-forum.com>
	<AA5E686C-F58A-440F-9B65-FA7DBC1F9F03@gmail.com>
	<cf2e0fd8efdeb5f34484bcf6c1778c7e@ruby-forum.com>
Message-ID: <57c63afe0903091430t7403e17bg9282a6dd8a4d7fef@mail.gmail.com>

On Mon, Mar 9, 2009 at 2:48 PM, James Byrne <lists at ruby-forum.com> wrote:
> David Chelimsky wrote:
>>
>> No, no, no :)
>>
>> 5.should == 5
>> 6.should be > 5
>>
>> Read them aloud and they.should make(:sense).
>>
>> Cheers,
>> David
>
> Perhaps it is my dialect, but what is wrong with:
>
> ? "5 should be equal to 5"
>
> which generally is how I read "=="? ?Actually, I tend to read "==" (in
> Ruby) as "is equal to".

Really? Are we still debating this?

From aslak.hellesoy at gmail.com  Mon Mar  9 18:00:19 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Mon, 9 Mar 2009 23:00:19 +0100
Subject: [rspec-users] Cucumber - RSpec matcher
In-Reply-To: <cf2e0fd8efdeb5f34484bcf6c1778c7e@ruby-forum.com>
References: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
	<DB49C85A-9ECF-48EA-A6D9-4CE30D37E872@gmail.com>
	<669ebfb8925637d900f55c84ecb0875d@ruby-forum.com>
	<AA5E686C-F58A-440F-9B65-FA7DBC1F9F03@gmail.com>
	<cf2e0fd8efdeb5f34484bcf6c1778c7e@ruby-forum.com>
Message-ID: <8d961d900903091500u48d3183bo5dc7a3024dc30236@mail.gmail.com>

On Mon, Mar 9, 2009 at 8:48 PM, James Byrne <lists at ruby-forum.com> wrote:

> David Chelimsky wrote:
> >
> > No, no, no :)
> >
> > 5.should == 5
> > 6.should be > 5
> >
> > Read them aloud and they.should make(:sense).
> >
> > Cheers,
> > David
>
> Perhaps it is my dialect, but what is wrong with:
>
>   "5 should be equal to 5"
>
> which generally is how I read "=="?  Actually, I tend to read "==" (in
> Ruby) as "is equal to".


RSpec does - and will - use Ruby's semantics for equality:
http://www.ruby-doc.org/core/classes/Object.html
Homemade semantics will not be implemented, as inconsistency with Ruby's
semantics will lead to confusion.

Aslak


>
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090309/ef5b61ed/attachment.html>

From zach.dennis at gmail.com  Mon Mar  9 18:01:10 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Mon, 9 Mar 2009 18:01:10 -0400
Subject: [rspec-users] Presentation Testing and CSS ids
In-Reply-To: <71d2b98da3f45f61b8fe3d7709d2f164@ruby-forum.com>
References: <gp0tk0$7n7$1@ger.gmane.org>
	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
	<gp13hb$oul$1@ger.gmane.org>
	<85d99afe0903081255t1fe64178va3b7ee7fd5bd3d0@mail.gmail.com>
	<71d2b98da3f45f61b8fe3d7709d2f164@ruby-forum.com>
Message-ID: <85d99afe0903091501g6736bfex7e43007804ba7880@mail.gmail.com>

On Mon, Mar 9, 2009 at 12:08 PM, James Byrne <lists at ruby-forum.com> wrote:
> Zach Dennis wrote:
>
>> In my experience relying on the syntactic details of the page is
>> extremely brittle and cumbersome. ... Some tags have both syntactic
>> and semantic meaning, such as forms, labels, fieldsets, and anchor tags.
>>
>
> Is it "brittle" to test for specific css selectors that are tied to page
> details?

I think it depends on what details you're tying them to. :)

> ?A typical case is where one has a button to drive in webrat
> and instead of using the button text we use the associated id value
> instead.

Does the id have meaning? Or is it something that communicates nothing
about what it is?  ie:

  click_button "add_new_item"

vs.

   click_button "foobar

-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From phlip2005 at gmail.com  Mon Mar  9 19:20:56 2009
From: phlip2005 at gmail.com (Phlip)
Date: Mon, 09 Mar 2009 16:20:56 -0700
Subject: [rspec-users] custom, nested HTML matchers in RSpec
In-Reply-To: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>
References: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>
Message-ID: <gp488o$3i8$1@ger.gmane.org>

> http://gist.github.com/76136

>     response.body.should be_html_with{
>       form :action => '/users' do
>         fieldset do
>           legend 'Personal Information'
>           label 'First name'
>           input :type => 'text', :name => 'user[first_name]'
>         end
>       end
>     }

Has anyone tried this? is it useful?


From lists at ruby-forum.com  Mon Mar  9 19:31:03 2009
From: lists at ruby-forum.com (James Byrne)
Date: Tue, 10 Mar 2009 00:31:03 +0100
Subject: [rspec-users] Question on SQL exceptions
In-Reply-To: <932FBF08-F62E-4940-8835-B066C5FC96EC@pivotib.com>
References: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
	<1E9AE5E8-D92E-42E4-B637-A622E7B8D95F@gmail.com>
	<a5dd30803999f3a632c16063c255dbfc@ruby-forum.com>
	<932FBF08-F62E-4940-8835-B066C5FC96EC@pivotib.com>
Message-ID: <74a4d391da1e0b4d3861454a31584a95@ruby-forum.com>

Tim Glen wrote:

> Just a stab in the dark, but I haven't seen any mention of calling
> save vs. save!. save just puts any errors in the model, save! will
> raise the exception if there are any errors. That may not be the case
> for ActiveRecord:StatementInvalid exception, but I thought i'd mention
> it anyway.
> 
> timg

I wondered about this but I think that since the DBMS exception is not 
being trapped at all that it makes no difference. However, I will check 
if if it does or not anyway.

and

Scott Taylor wrote:

> You can try "rescue Exception" which rescues from all exceptions, not
> just ones which inherit from StandardError.  

  Tried that one and it did not work either.

> Also - I believe this only works in 1.8.6 and above, so if you're
> still on 1.8.5 I'd recommend an upgrade.

This may be the case.  The target host runs CentOS-5.3 which ships with 
Ruby-1.8.5.  I will see if I get different results on a 1.8.6 machine.
-- 
Posted via http://www.ruby-forum.com/.

From patnakajima at gmail.com  Mon Mar  9 19:49:07 2009
From: patnakajima at gmail.com (Pat Nakajima)
Date: Mon, 9 Mar 2009 19:49:07 -0400
Subject: [rspec-users] custom, nested HTML matchers in RSpec
In-Reply-To: <gp488o$3i8$1@ger.gmane.org>
References: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>
	<gp488o$3i8$1@ger.gmane.org>
Message-ID: <97ae2db00903091649u1e464c9n5658d4c41841d345@mail.gmail.com>

>
> Has anyone tried this? is it useful?
>

It looks interesting, though it could be confused for trying to exactly
mimic the actual markup, not just specify interesting parts.

On Mon, Mar 9, 2009 at 7:20 PM, Phlip <phlip2005 at gmail.com> wrote:

> http://gist.github.com/76136
>>
>
>     response.body.should be_html_with{
>>      form :action => '/users' do
>>        fieldset do
>>          legend 'Personal Information'
>>          label 'First name'
>>          input :type => 'text', :name => 'user[first_name]'
>>        end
>>      end
>>    }
>>
>
> Has anyone tried this? is it useful?
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090309/bab690f4/attachment.html>

From dchelimsky at gmail.com  Mon Mar  9 19:56:03 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 9 Mar 2009 18:56:03 -0500
Subject: [rspec-users] custom, nested HTML matchers in RSpec
In-Reply-To: <gp488o$3i8$1@ger.gmane.org>
References: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>
	<gp488o$3i8$1@ger.gmane.org>
Message-ID: <57c63afe0903091656t3e916c48meffb0269d8a37cd5@mail.gmail.com>

On Mon, Mar 9, 2009 at 6:20 PM, Phlip <phlip2005 at gmail.com> wrote:
>> http://gist.github.com/76136
>
>> ? ?response.body.should be_html_with{
>> ? ? ?form :action => '/users' do
>> ? ? ? ?fieldset do
>> ? ? ? ? ?legend 'Personal Information'
>> ? ? ? ? ?label 'First name'
>> ? ? ? ? ?input :type => 'text', :name => 'user[first_name]'
>> ? ? ? ?end
>> ? ? ?end
>> ? ?}
>
> Has anyone tried this? is it useful?

I haven't tried it yet, but it does seem very useful. The project I'm
focused on right now is all json all the time, so I don't personally
have a real world case for this at the moment. Anybody doing an app w/
html views willing to try this out?

From dchelimsky at gmail.com  Mon Mar  9 20:04:47 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 9 Mar 2009 19:04:47 -0500
Subject: [rspec-users] custom, nested HTML matchers in RSpec
In-Reply-To: <97ae2db00903091649u1e464c9n5658d4c41841d345@mail.gmail.com>
References: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>
	<gp488o$3i8$1@ger.gmane.org>
	<97ae2db00903091649u1e464c9n5658d4c41841d345@mail.gmail.com>
Message-ID: <57c63afe0903091704u3f1a9777u6d8af0f1fa470f2e@mail.gmail.com>

On Mon, Mar 9, 2009 at 6:49 PM, Pat Nakajima <patnakajima at gmail.com> wrote:
>> Has anyone tried this? is it useful?
>
> It looks interesting, though it could be confused for trying to exactly
> mimic the actual markup, not just specify?interesting?parts.

What is the method name was be_html_including instead of be_html_with???

> On Mon, Mar 9, 2009 at 7:20 PM, Phlip <phlip2005 at gmail.com> wrote:
>>>
>>> http://gist.github.com/76136
>>
>>> ? ?response.body.should be_html_with{
>>> ? ? ?form :action => '/users' do
>>> ? ? ? ?fieldset do
>>> ? ? ? ? ?legend 'Personal Information'
>>> ? ? ? ? ?label 'First name'
>>> ? ? ? ? ?input :type => 'text', :name => 'user[first_name]'
>>> ? ? ? ?end
>>> ? ? ?end
>>> ? ?}
>>
>> Has anyone tried this? is it useful?
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From phlip2005 at gmail.com  Mon Mar  9 21:52:03 2009
From: phlip2005 at gmail.com (Phlip)
Date: Mon, 09 Mar 2009 18:52:03 -0700
Subject: [rspec-users] custom, nested HTML matchers in RSpec
In-Reply-To: <97ae2db00903091649u1e464c9n5658d4c41841d345@mail.gmail.com>
References: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>	<gp488o$3i8$1@ger.gmane.org>
	<97ae2db00903091649u1e464c9n5658d4c41841d345@mail.gmail.com>
Message-ID: <gp4h4p$o3b$1@ger.gmane.org>

Pat Nakajima wrote:

>     Has anyone tried this? is it useful?

> It looks interesting, though it could be confused for trying to exactly 
> mimic the actual markup, not just specify interesting parts.

It only specifies interesting parts. The gist writeup explained that, for 
example, it skipped over intermediate <ol><li> tags. And it naturally skips 
blanks in contents, and unlisted attributes.

It is exactly the same as the XPath version I posted before. That used explicit 
XPath queries to skip over uninteresting parts.

David Chelimsky wrote:

 > What is the method name was be_html_including instead of be_html_with???

('be_html_including'.length - 'be_html_with'.length) / 17 =~ 30%.

So 30% fewer people would bother to type it!


From tim at pivotib.com  Mon Mar  9 21:56:28 2009
From: tim at pivotib.com (Tim Glen)
Date: Mon, 9 Mar 2009 21:56:28 -0400
Subject: [rspec-users] Question on SQL exceptions
In-Reply-To: <74a4d391da1e0b4d3861454a31584a95@ruby-forum.com>
References: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
	<1E9AE5E8-D92E-42E4-B637-A622E7B8D95F@gmail.com>
	<a5dd30803999f3a632c16063c255dbfc@ruby-forum.com>
	<932FBF08-F62E-4940-8835-B066C5FC96EC@pivotib.com>
	<74a4d391da1e0b4d3861454a31584a95@ruby-forum.com>
Message-ID: <3B51E9F0-504F-48A9-95D5-285E326F4D5B@pivotib.com>

>> Just a stab in the dark, but I haven't seen any mention of calling
>> save vs. save!. save just puts any errors in the model, save! will
>> raise the exception if there are any errors. That may not be the case
>> for ActiveRecord:StatementInvalid exception, but I thought i'd  
>> mention
>> it anyway.

> I wondered about this but I think that since the DBMS exception is not
> being trapped at all that it makes no difference. However, I will  
> check
> if if it does or not anyway.

Right - this is from the validates_uniqueness_of documentation:
#   When the database catches such a duplicate insertion,
#   ActiveRecord::Base#save will raise an ActiveRecord::StatementInvalid
#   exception. You can either choose to let this error propagate (which
#   will result in the default Rails exception page being shown), or you
#   can catch it and restart the transaction (e.g. by telling the user
#   that the title already exists, and asking him to re-enter the  
title).
#   This technique is also known as optimistic concurrency control:
#   http://en.wikipedia.org/wiki/Optimistic_concurrency_control

so it _should_ be bubbling through. Odd that it would change in Ruby  
1.8.6, but it's worth a try.

timg

From pat.maddox at gmail.com  Mon Mar  9 22:04:40 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Mon, 9 Mar 2009 19:04:40 -0700
Subject: [rspec-users] Question on SQL exceptions
In-Reply-To: <a5dd30803999f3a632c16063c255dbfc@ruby-forum.com>
References: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
	<1E9AE5E8-D92E-42E4-B637-A622E7B8D95F@gmail.com>
	<a5dd30803999f3a632c16063c255dbfc@ruby-forum.com>
Message-ID: <85349409-000E-42E9-B82F-08FA6BB6E9D1@gmail.com>

On Mar 9, 2009, at 1:53 PM, James Byrne wrote:

> Pat Maddox wrote:
>> ActiveRecord doesn't know anything about db constraint errors.  If  
>> one
>> is violated, the error propagates up in the form of an exception.
>>
>
> I realize that, but the exception is of the
> ActiveRecord:StatementInvalid class, which I should be able to catch  
> in
> the controller with a rescue clause.  But, I am not getting this to  
> work
> at the moment.

Not sure what your problem is.  Here's a gist that demonstrates what  
you're trying to do, and works fine.  http://gist.github.com/76667

Pat

From lists at ruby-forum.com  Mon Mar  9 23:02:23 2009
From: lists at ruby-forum.com (aa aa)
Date: Tue, 10 Mar 2009 04:02:23 +0100
Subject: [rspec-users] rspec and prawn
Message-ID: <d30b24ac46c39a98c7318a432be80489@ruby-forum.com>

Hi,
I've just started using prawn but am at a bit of a loss how to create my
view specs for it.
For example, my normal view spec has things like
response.should have_tag("blah")
or
response.body.should =~ /something/

How do I do this with prawn output?
-- 
Posted via http://www.ruby-forum.com/.

From phlip2005 at gmail.com  Mon Mar  9 23:04:15 2009
From: phlip2005 at gmail.com (Phlip)
Date: Mon, 09 Mar 2009 20:04:15 -0700
Subject: [rspec-users] custom, nested HTML matchers in RSpec
In-Reply-To: <57c63afe0903091656t3e916c48meffb0269d8a37cd5@mail.gmail.com>
References: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>	<gp488o$3i8$1@ger.gmane.org>
	<57c63afe0903091656t3e916c48meffb0269d8a37cd5@mail.gmail.com>
Message-ID: <gp4lbk$uua$1@ger.gmane.org>

> I haven't tried it yet, but it does seem very useful. The project I'm
> focused on right now is all json all the time, so I don't personally
> have a real world case for this at the moment. Anybody doing an app w/
> html views willing to try this out?

I put it into my current project today (as a >cough< TestCase assertion), 
replaced a couple of xpath assertions with it, and showed it to my colleagues.

I injected a fault, and show the diagnostic with the two batches of HTML in it - 
the reference and sample.

One of them was like, "Nice, but where's the syntax highlighting?"

This refers to eyes rolling --> @-/


From phlip2005 at gmail.com  Tue Mar 10 07:47:15 2009
From: phlip2005 at gmail.com (Phlip)
Date: Tue, 10 Mar 2009 04:47:15 -0700
Subject: [rspec-users] rspec and prawn
In-Reply-To: <d30b24ac46c39a98c7318a432be80489@ruby-forum.com>
References: <d30b24ac46c39a98c7318a432be80489@ruby-forum.com>
Message-ID: <gp5k05$la$1@ger.gmane.org>

aa aa wrote:
> Hi,
> I've just started using prawn but am at a bit of a loss how to create my
> view specs for it.
> For example, my normal view spec has things like
> response.should have_tag("blah")
> or
> response.body.should =~ /something/
> 
> How do I do this with prawn output?

In what language is prawn output?

Generally speaking, a View is 2D or 3D, yet our tests must run in 1 dimension. 
In HTML, we do that by parsing the elements back into a DOM, and inspecting 
this. We don't necessarily do it by rendering a page and looking at it!

So if prawn were PS, can you get a post script parser, parse it, and look for 
your details?

(Note, too, that .should =~ is only a cheap approximation of parsing...)

-- 
   Phlip


From zuperinfinite at gmail.com  Tue Mar 10 08:16:24 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Tue, 10 Mar 2009 13:16:24 +0100
Subject: [rspec-users] Testing for the number of occurrences of a word
Message-ID: <67795CF2-2A2A-4ECC-BD3F-D95370BD546B@gmail.com>

Hey list,

Quick question: How can I check that a given word appears a number of  
times on a page?
The page in question includes some XML, rendered with &lts and &gts  
and I want to test that a given node exists 10 times on that page.

thanks!
bartz

From phlip2005 at gmail.com  Tue Mar 10 08:27:05 2009
From: phlip2005 at gmail.com (Phlip)
Date: Tue, 10 Mar 2009 05:27:05 -0700
Subject: [rspec-users] rspec and prawn
In-Reply-To: <d30b24ac46c39a98c7318a432be80489@ruby-forum.com>
References: <d30b24ac46c39a98c7318a432be80489@ruby-forum.com>
Message-ID: <gp5maq$78o$1@ger.gmane.org>

aa aa wrote:
> Hi,
> I've just started using prawn but am at a bit of a loss how to create my
> view specs for it.
> For example, my normal view spec has things like
> response.should have_tag("blah")
> or
> response.body.should =~ /something/
> 
> How do I do this with prawn output?

How do prawn's own unit tests work?


From zach.dennis at gmail.com  Tue Mar 10 08:43:51 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Tue, 10 Mar 2009 08:43:51 -0400
Subject: [rspec-users] rspec and prawn
In-Reply-To: <d30b24ac46c39a98c7318a432be80489@ruby-forum.com>
References: <d30b24ac46c39a98c7318a432be80489@ruby-forum.com>
Message-ID: <85d99afe0903100543o66815e0byb3dc45a92b9a9e5d@mail.gmail.com>

On Mon, Mar 9, 2009 at 11:02 PM, aa aa <lists at ruby-forum.com> wrote:
> Hi,
> I've just started using prawn but am at a bit of a loss how to create my
> view specs for it.
> For example, my normal view spec has things like
> response.should have_tag("blah")
> or
> response.body.should =~ /something/
>
> How do I do this with prawn output?

Short answer, you can't--at least not yet. PDF is not a plain text
markup language like HTML so its not a problem so easily solved. I
haven't spec'd a PDF, but when looking into it at one point I came
across PDF Reader.

http://github.com/yob/pdf-wrapper/tree

Perhaps that will help you find a starting place.


> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From zach.dennis at gmail.com  Tue Mar 10 08:44:13 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Tue, 10 Mar 2009 08:44:13 -0400
Subject: [rspec-users] rspec and prawn
In-Reply-To: <85d99afe0903100543o66815e0byb3dc45a92b9a9e5d@mail.gmail.com>
References: <d30b24ac46c39a98c7318a432be80489@ruby-forum.com>
	<85d99afe0903100543o66815e0byb3dc45a92b9a9e5d@mail.gmail.com>
Message-ID: <85d99afe0903100544u70f885bdp939a475e509eaebb@mail.gmail.com>

On Tue, Mar 10, 2009 at 8:43 AM, Zach Dennis <zach.dennis at gmail.com> wrote:
> On Mon, Mar 9, 2009 at 11:02 PM, aa aa <lists at ruby-forum.com> wrote:
>> Hi,
>> I've just started using prawn but am at a bit of a loss how to create my
>> view specs for it.
>> For example, my normal view spec has things like
>> response.should have_tag("blah")
>> or
>> response.body.should =~ /something/
>>
>> How do I do this with prawn output?
>
> Short answer, you can't--at least not yet. PDF is not a plain text
> markup language like HTML so its not a problem so easily solved. I
> haven't spec'd a PDF, but when looking into it at one point I came
> across PDF Reader.
>
> http://github.com/yob/pdf-wrapper/tree

Oops wrong URL:

http://github.com/yob/pdf-reader/tree

>
> Perhaps that will help you find a starting place.
>
>
>> --
>> Posted via http://www.ruby-forum.com/.
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
>
> --
> Zach Dennis
> http://www.continuousthinking.com
> http://www.mutuallyhuman.com
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From zach.dennis at gmail.com  Tue Mar 10 08:51:38 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Tue, 10 Mar 2009 08:51:38 -0400
Subject: [rspec-users] stubbing before filters
Message-ID: <85d99afe0903100551w20658fc3r846390eee15a32b0@mail.gmail.com>

Can folks who write controller specs and deal with before filters read
and comment on this ticket:
http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/724-stub_before_filters#ticket-724-2

I'm on the fence and would like others thoughts on the matter, Thanks

-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From zach.dennis at gmail.com  Tue Mar 10 09:00:46 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Tue, 10 Mar 2009 09:00:46 -0400
Subject: [rspec-users] Testing for the number of occurrences of a word
In-Reply-To: <67795CF2-2A2A-4ECC-BD3F-D95370BD546B@gmail.com>
References: <67795CF2-2A2A-4ECC-BD3F-D95370BD546B@gmail.com>
Message-ID: <85d99afe0903100600x74e90ec0m4712d4bccb868027@mail.gmail.com>

On Tue, Mar 10, 2009 at 8:16 AM, Bart Zonneveld <zuperinfinite at gmail.com> wrote:
> Hey list,
>
> Quick question: How can I check that a given word appears a number of times
> on a page?
> The page in question includes some XML, rendered with &lts and &gts and I
> want to test that a given node exists 10 times on that page.

You want to make sure you have 10 nodes? Or that text shows up 10
times inside of any node?

You can utilize Webrat's #have_selector to count the nodes, ie:

        response.should have_selector("li", :count => 3)


>
> thanks!
> bartz
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From aslak.hellesoy at gmail.com  Tue Mar 10 09:05:51 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Tue, 10 Mar 2009 14:05:51 +0100
Subject: [rspec-users] Testing for the number of occurrences of a word
In-Reply-To: <67795CF2-2A2A-4ECC-BD3F-D95370BD546B@gmail.com>
References: <67795CF2-2A2A-4ECC-BD3F-D95370BD546B@gmail.com>
Message-ID: <8d961d900903100605k11489fdft81cbaed223adcd7e@mail.gmail.com>

On Tue, Mar 10, 2009 at 1:16 PM, Bart Zonneveld <zuperinfinite at gmail.com>wrote:

> Hey list,
>
> Quick question: How can I check that a given word appears a number of times
> on a page?
> The page in question includes some XML, rendered with &lts and &gts and I
> want to test that a given node exists 10 times on that page.
>

Here are a couple of ways to do it:
http://lmgtfy.com/?q=ruby+count+occurrence+words

count = # one of the solutions above
count.should == 10

Cheers,
Aslak


>
> thanks!
> bartz
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090310/6fbb837e/attachment.html>

From lists at ruby-forum.com  Tue Mar 10 09:20:26 2009
From: lists at ruby-forum.com (James Byrne)
Date: Tue, 10 Mar 2009 14:20:26 +0100
Subject: [rspec-users] Question on SQL exceptions
In-Reply-To: <85349409-000E-42E9-B82F-08FA6BB6E9D1@gmail.com>
References: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
	<1E9AE5E8-D92E-42E4-B637-A622E7B8D95F@gmail.com>
	<a5dd30803999f3a632c16063c255dbfc@ruby-forum.com>
	<85349409-000E-42E9-B82F-08FA6BB6E9D1@gmail.com>
Message-ID: <bb60a496e3dcf8b1fb82235141b9bbe7@ruby-forum.com>

Pat Maddox wrote:

> 
> Not sure what your problem is.  Here's a gist that demonstrates what
> you're trying to do, and works fine.  http://gist.github.com/76667
> 
> Pat

I do not know what I am doing wrong either.  I tried much the same thing 
as you suggest last night in the console:

>> def my_exception(x=false)
>>   raise ActiveRecord::StatementInvalid if x
>>   puts "No Exception"
>> rescue ActiveRecord::StatementInvalid
>>   puts "exception rescued"
>> end
=> nil
>> my_exception(false)
No Exception
=> nil
>> my_exception(true)
exception rescued
=> nil

So, my version of Ruby has nothing to do with whatever is happening.  I 
will poke at things some more and see if I can discover what my 
misunderstanding is.  It has to be something simple that I just do not 
see at the moment.
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Tue Mar 10 09:32:53 2009
From: lists at ruby-forum.com (James Byrne)
Date: Tue, 10 Mar 2009 14:32:53 +0100
Subject: [rspec-users] Question on SQL exceptions
In-Reply-To: <bb60a496e3dcf8b1fb82235141b9bbe7@ruby-forum.com>
References: <3c23e108653d66177bb578f68466196f@ruby-forum.com>
	<1E9AE5E8-D92E-42E4-B637-A622E7B8D95F@gmail.com>
	<a5dd30803999f3a632c16063c255dbfc@ruby-forum.com>
	<85349409-000E-42E9-B82F-08FA6BB6E9D1@gmail.com>
	<bb60a496e3dcf8b1fb82235141b9bbe7@ruby-forum.com>
Message-ID: <6637f3c5faaabe9b6df7f0ce47bca5fb@ruby-forum.com>

James Byrne wrote:

> 
> I do not know what I am doing wrong either.  I tried much the same thing 
> as you suggest last night in the console:

Well, whatever I was doing wrong I seem to have fixed it.  Things now 
seem to be working as I intended.
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Tue Mar 10 10:14:18 2009
From: lists at ruby-forum.com (Tom Ten Thij)
Date: Tue, 10 Mar 2009 15:14:18 +0100
Subject: [rspec-users] nokogiri selector help
In-Reply-To: <85d99afe0902031947h21b6404bm7e519eb750833d21@mail.gmail.com>
References: <51054F01-B154-4D21-9B11-96AEF17F7B15@parkerhill.com>
	<85d99afe0901250858we266949l2473e4da56b8d1ed@mail.gmail.com>
	<A2972B74-F217-45AF-AF4E-E0B7823C3058@parkerhill.com>
	<85d99afe0902031947h21b6404bm7e519eb750833d21@mail.gmail.com>
Message-ID: <6389f1bb80f2f5fafa96e43da734fd16@ruby-forum.com>


> Sorry for the late reply, but this is a bug in webrat not a nokogiri
> issue. I've created a ticket for it at lighthouse:
> 
> http://webrat.lighthouseapp.com/projects/10503-webrat/tickets/153-within-should-support-xpath

I wrote an ugly duckpunch that fixes the error for now. I have submitted 
it as a comment on the ticket
-- 
Posted via http://www.ruby-forum.com/.

From lenny at aps.org  Tue Mar 10 11:30:02 2009
From: lenny at aps.org (Lenny Marks)
Date: Tue, 10 Mar 2009 11:30:02 -0400
Subject: [rspec-users] ArgumentError mystery with jruby/rspec-1.1.11
In-Reply-To: <49AEDD1F.6020600@aps.org>
References: <4DD7A591-4B03-4407-911F-512D5FCB1293@aps.org>
	<49AEDD1F.6020600@aps.org>
Message-ID: <EEBD3F40-4340-4774-9C15-44B8FD533F31@aps.org>

It seems this is actually related to the java package name containing  
'context'. I've posted a rspec bug for this along with a simple case  
to demonstrate. I realize this may wind up kicked over to the JRuby  
people...

http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/728-rspecjruby-gives-argumenterror-when-java-class-with-context-in-package-name-is-referenced

-lenny

On Mar 4, 2009, at 2:57 PM, Arthur Smith wrote:

> We've seen this behavior again, this time with rspec-1.1.12 and  
> jruby 1.2.0RC1; the common factors seem to be:
>
> (1) jruby
> (2) rspec 1.1.11 or 1.1.12
> (3) naming a java class with the string 'context' or 'Context' in  
> its name.
>
> In this case the bit of ruby causing trouble was:
>
>      SecurityContextHolder =  
> Java::org.acegisecurity.context.SecurityContextHolder
>
> And running 'jruby script/spec -b ...' gave:
>
> ArgumentError in 'ManuscriptPublishedController check_unauthorized  
> should respond with unauthorized for create if user does not have  
> privilege'
> ArgumentError
> [...]/jruby-1.2.0RC1/lib/ruby/gems/1.8/gems/rspec-1.1.12/lib/spec/ 
> example/example_group_factory.rb:54:in `create_example_group'
> [...]/jruby-1.2.0RC1/lib/ruby/gems/1.8/gems/rspec-1.1.12/lib/spec/ 
> dsl/main.rb:25:in `describe'
> [...]
>
> Replacing the above SecurityContextHolder definition with an import:
>
>        import 'org.acegisecurity.context.SecurityContextHolder'
>
> fixed the errors. Any explanations out there?
>
>      Arthur Smith
>
> Lenny Marks wrote:
>> I just got bitten by a strange issue with rspec-1.1.11 and jruby  
>> 1.1.3-1.1.6RC1. I'd love to know what the problem was if anyone has  
>> any ideas. It's almost as if, rspec didn't like something about  
>> this particular class since substituting others worked fine. It  
>> does work with Rspec edge so I guess its not too important.  
>> Hopefully if anyone else runs into this they'll hit upon this.
>>
>> -lenny
>>
>> # reproduce.rb
>>
>> require './spring.jar'
>>
>> describe "test with spring" do
>>
>>   it "should not raise ArgumentError" do
>>       
>> Java 
>> ::org 
>> .springframework.context.support.ClassPathXmlApplicationContext #  
>> line 7
>>   end
>>
>> end
>>
>> > jruby-1.1.3/bin/jruby -v -S spec -v
>> jruby 1.1.3 (ruby 1.8.6 patchlevel 114) (2008-12-08 rev 6586)  
>> [x86_64-java]
>> rspec 1.1.11
>>
>>
>> >  jruby-1.1.3/bin/jruby -S spec -fs -b reproduce.rb
>>
>> test with spring
>> - should not raise ArgumentError (ERROR - 1)
>>
>> 1)
>> ArgumentError in 'test with spring should not raise ArgumentError'
>> ArgumentError
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/extensions/ 
>> main.rb:23:in `describe'
>> /home/jis/compsvc/lenny/tmp/x/./reproduce.rb:7:
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/ 
>> example_methods.rb:81:in `instance_eval'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/ 
>> example_methods.rb:81:in `eval_block'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/ 
>> example_methods.rb:15:in `execute'
>> /Users/Shared/eds_test/share/jruby-1.1.3/lib/ruby/1.8/timeout.rb: 
>> 48:in `timeout'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/ 
>> example_methods.rb:12:in `execute'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/ 
>> example_group_methods.rb:245:in `execute_examples'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/ 
>> example_group_methods.rb:244:in `each'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/ 
>> example_group_methods.rb:244:in `execute_examples'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/example/ 
>> example_group_methods.rb:141:in `run'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/runner/ 
>> example_group_runner.rb:22:in `run'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/runner/ 
>> example_group_runner.rb:21:in `each'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/runner/ 
>> example_group_runner.rb:21:in `run'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/runner/ 
>> options.rb:115:in `run_examples'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/lib/spec/runner/ 
>> command_line.rb:10:in `run'
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/bin/spec:4:
>> /Users/Shared/RubyGems/1.8/gems/rspec-1.1.11/bin/spec:19:in `load'
>> /Users/Shared/eds_test/share/jruby-1.1.3/bin/spec:19:
>>
>>
>> /jruby-1.1.3/bin/jruby -v rspec/bin/spec  -v
>> jruby 1.1.3 (ruby 1.8.6 patchlevel 114) (2008-12-08 rev 6586)  
>> [x86_64-java]
>> rspec 1.1.11.1
>>
>> > jruby-1.1.3/bin/jruby rspec/bin/spec -fs reproduce.rb
>>
>> test with spring
>> - should not raise ArgumentError
>>
>> Finished in 0.329 seconds
>>
>> 1 example, 0 failures
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>


From zuperinfinite at gmail.com  Tue Mar 10 11:37:13 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Tue, 10 Mar 2009 16:37:13 +0100
Subject: [rspec-users] Testing for the number of occurrences of a word
In-Reply-To: <8d961d900903100605k11489fdft81cbaed223adcd7e@mail.gmail.com>
References: <67795CF2-2A2A-4ECC-BD3F-D95370BD546B@gmail.com>
	<8d961d900903100605k11489fdft81cbaed223adcd7e@mail.gmail.com>
Message-ID: <9570500D-D53D-4F52-BFF9-13D94C259F31@gmail.com>


On 10 mrt 2009, at 14:05, aslak hellesoy wrote:

>
>
> On Tue, Mar 10, 2009 at 1:16 PM, Bart Zonneveld <zuperinfinite at gmail.com 
> > wrote:
> Hey list,
>
> Quick question: How can I check that a given word appears a number  
> of times on a page?
> The page in question includes some XML, rendered with &lts and &gts  
> and I want to test that a given node exists 10 times on that page.
>
> Here are a couple of ways to do it: http://lmgtfy.com/?q=ruby+count+occurrence+words
>
> count = # one of the solutions above
> count.should == 10

Argh, thanks to both of you.
I was thinking too difficult, along the lines of have_tag('my_div',  
'word', 10)...

cheers,
bartz


From lists at ruby-forum.com  Tue Mar 10 12:46:12 2009
From: lists at ruby-forum.com (James Byrne)
Date: Tue, 10 Mar 2009 17:46:12 +0100
Subject: [rspec-users] Cucumber - RSpec matcher
In-Reply-To: <8d961d900903091500u48d3183bo5dc7a3024dc30236@mail.gmail.com>
References: <fb1ae02662c3daec0f0878919406dfb4@ruby-forum.com>
	<DB49C85A-9ECF-48EA-A6D9-4CE30D37E872@gmail.com>
	<669ebfb8925637d900f55c84ecb0875d@ruby-forum.com>
	<AA5E686C-F58A-440F-9B65-FA7DBC1F9F03@gmail.com>
	<cf2e0fd8efdeb5f34484bcf6c1778c7e@ruby-forum.com>
	<8d961d900903091500u48d3183bo5dc7a3024dc30236@mail.gmail.com>
Message-ID: <b7565a4ba900548b3e7dc731e3d55f8c@ruby-forum.com>

Aslak Helles?y wrote:
> On Mon, Mar 9, 2009 at 8:48 PM, James Byrne <lists at ruby-forum.com> 
> wrote:
> 
>> > David
>>
>> Perhaps it is my dialect, but what is wrong with:
>>
>>   "5 should be equal to 5"
>>
>> which generally is how I read "=="?  Actually, I tend to read "==" (in
>> Ruby) as "is equal to".
> 
> 
> RSpec does - and will - use Ruby's semantics for equality:
> http://www.ruby-doc.org/core/classes/Object.html
> Homemade semantics will not be implemented, as inconsistency with Ruby's
> semantics will lead to confusion.

Ruby semantics are not at issue.  I read "==" to mean "is equal to" in 
its English sense and no other, as in "two plus five is equal to seven".

-- 
Posted via http://www.ruby-forum.com/.

From loop at superinfinite.com  Tue Mar 10 11:53:20 2009
From: loop at superinfinite.com (Bart Zonneveld)
Date: Tue, 10 Mar 2009 16:53:20 +0100
Subject: [rspec-users] Testing for the number of occurrences of a word
In-Reply-To: <9570500D-D53D-4F52-BFF9-13D94C259F31@gmail.com>
References: <67795CF2-2A2A-4ECC-BD3F-D95370BD546B@gmail.com>
	<8d961d900903100605k11489fdft81cbaed223adcd7e@mail.gmail.com>
	<9570500D-D53D-4F52-BFF9-13D94C259F31@gmail.com>
Message-ID: <708C2BAA-1B4A-4F07-B0B9-781BB0A10E42@superinfinite.com>


On 10 mrt 2009, at 16:37, Bart Zonneveld wrote:

> On 10 mrt 2009, at 14:05, aslak hellesoy wrote:
>
>> On Tue, Mar 10, 2009 at 1:16 PM, Bart Zonneveld <zuperinfinite at gmail.com 
>> > wrote:
>> Hey list,
>>
>> Quick question: How can I check that a given word appears a number  
>> of times on a page?
>> The page in question includes some XML, rendered with &lts and &gts  
>> and I want to test that a given node exists 10 times on that page.
>>
>> Here are a couple of ways to do it: http://lmgtfy.com/?q=ruby+count+occurrence+words
>>
>> count = # one of the solutions above
>> count.should == 10
>
> Argh, thanks to both of you.
> I was thinking too difficult, along the lines of have_tag('my_div',  
> 'word', 10)...

In case anyone was wondering how to do this:

Then "I should see the last $num statuses of the user" do |num|
   matches = response.body.scan(/&lt;record&gt;/)
   matches.length.should == num.to_i
end

From memberships.andi at gmail.com  Wed Mar 11 04:30:50 2009
From: memberships.andi at gmail.com (Andi Schacke)
Date: Wed, 11 Mar 2009 09:30:50 +0100
Subject: [rspec-users] [rspec, rails] Restful Routes in controller specs
Message-ID: <2d9218930903110130g4e3012d1r2b4aa9dfa2024bde@mail.gmail.com>

Hi,

how is it possible that I can use the restful routes helpers (e.g.
new_user_path) in controller specs? I browsed the source code but I
couldn't find the magic. I'm just curious and would appreciate any
hint...

thanks
Andi

From jonathan at parkerhill.com  Wed Mar 11 09:35:23 2009
From: jonathan at parkerhill.com (Jonathan Linowes)
Date: Wed, 11 Mar 2009 09:35:23 -0400
Subject: [rspec-users] [rspec, rails] Restful Routes in controller specs
In-Reply-To: <2d9218930903110130g4e3012d1r2b4aa9dfa2024bde@mail.gmail.com>
References: <2d9218930903110130g4e3012d1r2b4aa9dfa2024bde@mail.gmail.com>
Message-ID: <1563490C-2F08-4BE8-AD74-A9626E8DAB58@parkerhill.com>


On Mar 11, 2009, at 4:30 AM, Andi Schacke wrote:

> Hi,
>
> how is it possible that I can use the restful routes helpers (e.g.
> new_user_path) in controller specs? I browsed the source code but I
> couldn't find the magic. I'm just curious and would appreciate any
> hint...
>
> thanks
> Andi
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


You can use them -after- the request, eg

	post :create
	response.should redirect_to( foo_path )

You can't before the request because they're not loaded yet.

Actually, I have a routes_spec.rb that goes something like this:

	class FoosController < ApplicationController
		def foo
		end
	end

	describe FoosController, "named routes" do
		before do
	  		get :foo
    		end

		it "should route /users/:id" do
     			user_path('123').should == '/users/123'
     			params_from(:get, '/users/123').should == {:controller =>  
'users', :action => 'show', :id => '123'}
   		end
	end



From dchelimsky at gmail.com  Wed Mar 11 09:39:41 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 11 Mar 2009 08:39:41 -0500
Subject: [rspec-users] [rspec, rails] Restful Routes in controller specs
In-Reply-To: <2d9218930903110130g4e3012d1r2b4aa9dfa2024bde@mail.gmail.com>
References: <2d9218930903110130g4e3012d1r2b4aa9dfa2024bde@mail.gmail.com>
Message-ID: <57c63afe0903110639m488f1975j16a72c6ac712112c@mail.gmail.com>

On Wed, Mar 11, 2009 at 3:30 AM, Andi Schacke
<memberships.andi at gmail.com> wrote:
> Hi,
>
> how is it possible that I can use the restful routes helpers (e.g.
> new_user_path) in controller specs? I browsed the source code but I
> couldn't find the magic. I'm just curious and would appreciate any
> hint...

If you're asking how to do it, you just do. There's nothing you have
to do. They're there for free.

If you're asking how they are there for free, controllers specs wrap
rails functional tests, so they have all the services provided by
rails.

Cheers,
David

>
> thanks
> Andi
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From memberships.andi at gmail.com  Wed Mar 11 10:04:26 2009
From: memberships.andi at gmail.com (Andi Schacke)
Date: Wed, 11 Mar 2009 07:04:26 -0700 (PDT)
Subject: [rspec-users] [rspec, rails] Restful Routes in controller specs
In-Reply-To: <57c63afe0903110639m488f1975j16a72c6ac712112c@mail.gmail.com>
References: <2d9218930903110130g4e3012d1r2b4aa9dfa2024bde@mail.gmail.com> 
	<57c63afe0903110639m488f1975j16a72c6ac712112c@mail.gmail.com>
Message-ID: <23530715-f5d7-4bbf-bf78-b8493c18c2ab@w35g2000yqm.googlegroups.com>

Thanks a lot David, my question was 'how' they are for free. That
explains why I didn't find it in the rspec-rails sourcecode.

Cheers
Andi

On Mar 11, 2:39?pm, David Chelimsky <dchelim... at gmail.com> wrote:
> On Wed, Mar 11, 2009 at 3:30 AM, Andi Schacke
>
> <memberships.a... at gmail.com> wrote:
> > Hi,
>
> > how is it possible that I can use the restful routes helpers (e.g.
> > new_user_path) in controller specs? I browsed the source code but I
> > couldn't find the magic. I'm just curious and would appreciate any
> > hint...
>
> If you're asking how to do it, you just do. There's nothing you have
> to do. They're there for free.
>
> If you're asking how they are there for free, controllers specs wrap
> rails functional tests, so they have all the services provided by
> rails.
>
> Cheers,
> David
>
>
>
> > thanks
> > Andi
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From walketim at gmail.com  Wed Mar 11 11:12:39 2009
From: walketim at gmail.com (Tim Walker)
Date: Wed, 11 Mar 2009 09:12:39 -0600
Subject: [rspec-users] [cucumber] getting scenario name in hook
Message-ID: <1ebf5a4d0903110812i6291ec87i58541e1a94812574@mail.gmail.com>

Hi Guys,

If I am generating diagnostics from a before do step can I get the
name of the scenario?

Many thanks,

Tim

From aslak.hellesoy at gmail.com  Wed Mar 11 12:21:50 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Wed, 11 Mar 2009 17:21:50 +0100
Subject: [rspec-users] [cucumber] getting scenario name in hook
In-Reply-To: <1ebf5a4d0903110812i6291ec87i58541e1a94812574@mail.gmail.com>
References: <1ebf5a4d0903110812i6291ec87i58541e1a94812574@mail.gmail.com>
Message-ID: <8d961d900903110921h79d8134cv42df0804affbef5d@mail.gmail.com>

On Wed, Mar 11, 2009 at 4:12 PM, Tim Walker <walketim at gmail.com> wrote:

> Hi Guys,
>
> If I am generating diagnostics from a before do step can I get the
> name of the scenario?
>

This is implemented in 0.1.99.x:
http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/44

Aslak


>
> Many thanks,
>
> Tim
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090311/9066344f/attachment.html>

From davids at tower-mt.com  Wed Mar 11 13:40:07 2009
From: davids at tower-mt.com (David Schmidt)
Date: Wed, 11 Mar 2009 10:40:07 -0700
Subject: [rspec-users] stubbing Time.zone.now for model tests fails for
	Rails 2.3.1
Message-ID: <5D52D0F4-0223-4C74-8215-2CAEB90FC993@tower-mt.com>

Our application has some code to schedule recurring tasks, with code  
to skip holidays and weekends.

In order to test the schedule model we need to have a fixed time  
returned when the model is run so that the tests will run the same no  
matter what day they are run.  (The first set of tests written would  
all pass until run on a weekend, when the skip code would schedule a  
task days later in order to skip a weekend day.)

Our solution under Rails 2.1 was to set an instance variable to a  
fixed time and then to stub the time returned, similar to the method  
that David Chelimsky recommended:

now = Time.now
Time.stub!(:now).and_return(now)

However, our app is using Time.zone.now in order to return local time  
in the user's local time zone.  The following code works in Rails 2.1:

@now = Time.now
@timezone = TimeZone.new('UTC')
Time.stub!(:zone).and_return(@timezone)
@timezone.stub!(:now).and_return(@new)

In Rails 2.1 this properly returned @now when the model accessed  
Time.zone.now.

After upgrading to Rails 2.3.1 (and RSpec 1.1.99.12) *all* tests that  
use this method fail.  They appear to fail as soon as a time from  
Time.zone.now is saved to a model and then accessed, even though the  
time in the record appears fine.

The error we're getting is:

"You have a nil object when you didn't expect it!
The error occurred while evaluating nil.period_for_utc"

If I comment out the last two lines above ("Time.stub!" and  
"@timezone.stub!") then I don't get that error, but without fixed  
times some of our tests fail due to the variable time.

Has anyone else run into this problem and come up with a solution to  
getting a fixed time back from Time.zone.now?

David Schmidt
davids at tower-mt.com

From dchelimsky at gmail.com  Wed Mar 11 13:57:57 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 11 Mar 2009 12:57:57 -0500
Subject: [rspec-users] stubbing Time.zone.now for model tests fails for
	Rails 2.3.1
In-Reply-To: <5D52D0F4-0223-4C74-8215-2CAEB90FC993@tower-mt.com>
References: <5D52D0F4-0223-4C74-8215-2CAEB90FC993@tower-mt.com>
Message-ID: <57c63afe0903111057v1bdaa240l44721e5a5115d85d@mail.gmail.com>

On Wed, Mar 11, 2009 at 12:40 PM, David Schmidt <davids at tower-mt.com> wrote:
> Our application has some code to schedule recurring tasks, with code to skip
> holidays and weekends.
>
> In order to test the schedule model we need to have a fixed time returned
> when the model is run so that the tests will run the same no matter what day
> they are run. ?(The first set of tests written would all pass until run on a
> weekend, when the skip code would schedule a task days later in order to
> skip a weekend day.)
>
> Our solution under Rails 2.1 was to set an instance variable to a fixed time
> and then to stub the time returned, similar to the method that David
> Chelimsky recommended:
>
> now = Time.now
> Time.stub!(:now).and_return(now)
>
> However, our app is using Time.zone.now in order to return local time in the
> user's local time zone. ?The following code works in Rails 2.1:
>
> @now = Time.now
> @timezone = TimeZone.new('UTC')
> Time.stub!(:zone).and_return(@timezone)
> @timezone.stub!(:now).and_return(@new)

How about:

@now = Time.now
@zone = mock('timezone')
@zone.stub!(:now).and_return(@now)
Time.stub!(:zone).and_return(@zone)

Now you're not depending on TimeZone in the examples. Let us know if it works.

Cheers,
David

>
> In Rails 2.1 this properly returned @now when the model accessed
> Time.zone.now.
>
> After upgrading to Rails 2.3.1 (and RSpec 1.1.99.12) *all* tests that use
> this method fail. ?They appear to fail as soon as a time from Time.zone.now
> is saved to a model and then accessed, even though the time in the record
> appears fine.
>
> The error we're getting is:
>
> "You have a nil object when you didn't expect it!
> The error occurred while evaluating nil.period_for_utc"
>
> If I comment out the last two lines above ("Time.stub!" and
> "@timezone.stub!") then I don't get that error, but without fixed times some
> of our tests fail due to the variable time.
>
> Has anyone else run into this problem and come up with a solution to getting
> a fixed time back from Time.zone.now?
>
> David Schmidt
> davids at tower-mt.com
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From lists at ruby-forum.com  Wed Mar 11 14:02:56 2009
From: lists at ruby-forum.com (James Byrne)
Date: Wed, 11 Mar 2009 19:02:56 +0100
Subject: [rspec-users] How to dummy a DB adapter?
Message-ID: <c579a2241a4fd4c029b68732bc0b47ea@ruby-forum.com>

I am writing a library module to handle certain StatementInvalid type AR
exceptions.  I wish to catch the case where the db adapter in use is not
supported by the module.  I would like to test this situation and have
only a vague idea as to how to proceed.

My exception handling method selects the parsing method based on the
adapter_name value.

  def hll_ar_exception(exception)
    raise exception unless exception.class.to_s ==
                           'ActiveRecord::StatementInvalid'
    acan =  self.connection.adapter_name
    case acan
    when 'MySQL'
      hll_parse_mysql
    when 'PostgreSQL'
      hll_parse_postgresql
    when 'SQLite'
      hll_parse_sqlite(exception)
    else
      Rails::logger.warn("Adapter #{acan} not supported by
hll_ar_exception.")
      raise exception
    end
  end

I am thinking about simply opening SQLiteAdapter and overriding the
adapter_name method to some arbitrary value for the test.  However, it
occurs to me that there are probably better ways to do what I am trying
to accomplish so I welcome any suggestions on how to proceed.
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Wed Mar 11 14:52:48 2009
From: lists at ruby-forum.com (Balint Erdi)
Date: Wed, 11 Mar 2009 19:52:48 +0100
Subject: [rspec-users] [cucumber] accessing session variables
Message-ID: <896a69ff319435ef12204ab0c163647a@ruby-forum.com>

Hey,

I have the following simple scenario and the step definitions:

Scenario: Create album
  Given I am logged in as "pepito"
  When I go to my profile page
  ...

Given /^the user (.*) exists$/ do |login_name|
  User.find_by_login(login_name) || Factory(:user_with_password, :login
=> login_name)
end

Given /^I log in as (.*)$/ do |login_name|
  user = User.find_by_login(login_name)
  # it is supposed that the user was generated by the
:user_with_password fixture
  # that has the 'secret' password
  post "/session", :login => user.login, :password => 'secret'
end

Given /^I am logged in as "(.*)"$/ do |login_name|
  Given "the user #{login_name} exists"
  Given "I log in as #{login_name}"
end

When /^I go to (.+)$/ do |page_name|
  visit path_to(page_name)
end

def path_to(page_name)
  case page_name

  when /my profile page/i
    member_profile_path(:id => session[:user_id])
  ...
end

I receive the following error:

When I go to my profile page  #
features/step_definitions/webrat_steps.rb:6
  You have a nil object when you didn't expect it!
  The error occurred while evaluating nil.session (NoMethodError)
     /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/test_process.rb:429:in
`session'

So it seems like the session is not accessible -or not this way- in the
step definitions. I finally came up with that workaround:

def path_to(page_name)
  case page_name

  when /my profile page/i
    member_profile_path(:id => User.first)
  ...
end

However, I am not at all content with this hack. It does not go to the
profile page of the logged in user but to the first one. This can be the
same -and in this scenario it is- but there is no guarantee for that.

I wonder if there is a way to retrieve things stored in the session.
Ideally I could even write:

  when /my profile page/i
      member_profile_path(:id => current_user)

Where current_user is defined in a helper class, and will also use a
session variable behind the scenes (I received an undefined method
"current_user" error when I tried this).

Could someone enlighten me about how to do this or whether this is
considered bad practice because current_user is more state-based (as
opposed to behavior-based_?

Thank you,
Balint
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Wed Mar 11 15:03:02 2009
From: lists at ruby-forum.com (Balint Erdi)
Date: Wed, 11 Mar 2009 20:03:02 +0100
Subject: [rspec-users] [cucumber] open source projects with cucumber features
Message-ID: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>

Hi,

I was looking for some "real-world" cucumber features (mainly on github)
to see how more complex features are built but I have not really found
any. Could you point me to some?

Thank you,
Balint
-- 
Posted via http://www.ruby-forum.com/.

From zach.dennis at gmail.com  Wed Mar 11 15:46:20 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Wed, 11 Mar 2009 15:46:20 -0400
Subject: [rspec-users] [cucumber] open source projects with cucumber
	features
In-Reply-To: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
References: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
Message-ID: <85d99afe0903111246x33b4a028r499253683fcf25c5@mail.gmail.com>

On Wed, Mar 11, 2009 at 3:03 PM, Balint Erdi <lists at ruby-forum.com> wrote:
> Hi,
>
> I was looking for some "real-world" cucumber features (mainly on github)
> to see how more complex features are built but I have not really found
> any. Could you point me to some?

For seeing different ways to utilize scenarios and step definitions I
would look at Cucumber and RSpec. They both have feature files and
have good examples of different ways to utilize scenarios and step
definitions:

  http://github.com/aslakhellesoy/cucumber
  http://github.com/dchelimsky/rspec


-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From apremdas at gmail.com  Wed Mar 11 17:02:29 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Wed, 11 Mar 2009 21:02:29 +0000
Subject: [rspec-users] Presentation Testing and CSS ids
In-Reply-To: <71d2b98da3f45f61b8fe3d7709d2f164@ruby-forum.com>
References: <gp0tk0$7n7$1@ger.gmane.org>
	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
	<gp13hb$oul$1@ger.gmane.org>
	<85d99afe0903081255t1fe64178va3b7ee7fd5bd3d0@mail.gmail.com>
	<71d2b98da3f45f61b8fe3d7709d2f164@ruby-forum.com>
Message-ID: <88fd8ddc0903111402s64809bdcpa79038c8789de184@mail.gmail.com>

The key phrase is semantic meaning. Its good to use CSS to give semantic
meaning to things that appear on web pages. Not only can these id's or
classes be useful for using with screen readers, they should be stable
things that don't change even if the design of the page does. It should be
easy to say to designers don't change these tags - they can either add extra
classes or change the style definition.

However if you label things with poor semantic meaning then don't be
suprised when they change. Testing for a mediumBlueBox is asking for a
kicking!

Finally finding good semantic descriptions is not easy. I think
"submitCustomerDetails" is better than "submitForm", "submitButton" or even
"submitCustomerDetailsButton". But I have no idea whether anyone else would
agree with me :).

2009/3/9 James Byrne <lists at ruby-forum.com>

> Zach Dennis wrote:
>
> > In my experience relying on the syntactic details of the page is
> > extremely brittle and cumbersome. ... Some tags have both syntactic
> > and semantic meaning, such as forms, labels, fieldsets, and anchor tags.
> >
>
> Is it "brittle" to test for specific css selectors that are tied to page
> details?  A typical case is where one has a button to drive in webrat
> and instead of using the button text we use the associated id value
> instead.
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090311/504dc759/attachment-0001.html>

From apremdas at gmail.com  Wed Mar 11 17:09:31 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Wed, 11 Mar 2009 21:09:31 +0000
Subject: [rspec-users] [cucumber] open source projects with cucumber
	features
In-Reply-To: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
References: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
Message-ID: <88fd8ddc0903111409r41c2d9e8pf3d748681182da8@mail.gmail.com>

You could have a look at fbrp on github, which has rewritten features for
RestfulAuthentication. Hopefully its a reasonably gentle introduction and at
least a bit real world.


2009/3/11 Balint Erdi <lists at ruby-forum.com>

> Hi,
>
> I was looking for some "real-world" cucumber features (mainly on github)
> to see how more complex features are built but I have not really found
> any. Could you point me to some?
>
> Thank you,
> Balint
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090311/58314146/attachment.html>

From rdm at cfcl.com  Wed Mar 11 18:16:28 2009
From: rdm at cfcl.com (Rich Morin)
Date: Wed, 11 Mar 2009 14:16:28 -0800
Subject: [rspec-users] [cucumber] open source projects with cucumber
 features
In-Reply-To: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
References: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
Message-ID: <p06230927c5dde087914f@[192.168.1.205]>

At 20:03 +0100 3/11/09, Balint Erdi wrote:
> I was looking for some "real-world" cucumber features (mainly
> on github) to see how more complex features are built but I
> have not really found any.  Could you point me to some?

I asked about this on #github.  Lenary helped out massively.

Procedure:

  Go to http://github.com/search
  Search "Code" using "Ruby" for "require cucumber"

http://github.com/search?type=Code&language=rb
  &q=require+cucumber&repo=&langOverride=&x=0&y=0

Very cool...

-r
-- 
http://www.cfcl.com/rdm            Rich Morin
http://www.cfcl.com/rdm/resume     rdm at cfcl.com
http://www.cfcl.com/rdm/weblog     +1 650-873-7841

Technical editing and writing, programming, and web development

From oli.azevedo.barnes at gmail.com  Wed Mar 11 18:35:11 2009
From: oli.azevedo.barnes at gmail.com (Oliver Barnes)
Date: Wed, 11 Mar 2009 19:35:11 -0300
Subject: [rspec-users] [cucumber] open source projects with cucumber
	features
In-Reply-To: <88fd8ddc0903111409r41c2d9e8pf3d748681182da8@mail.gmail.com>
References: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
	<88fd8ddc0903111409r41c2d9e8pf3d748681182da8@mail.gmail.com>
Message-ID: <6466d9040903111535m10a04869qfc9975ff35bb26c7@mail.gmail.com>

+1
I'm also looking for examples... I've seen several
authentication-related ones, but very few examples of features that
users would actually care a lot about, and that would help in learning
outside-in development...

2009/3/11 Andrew Premdas <apremdas at gmail.com>:
> You could have a look at fbrp on github, which has rewritten features for
> RestfulAuthentication. Hopefully its a reasonably gentle introduction and at
> least a bit real world.
>
>
> 2009/3/11 Balint Erdi <lists at ruby-forum.com>
>>
>> Hi,
>>
>> I was looking for some "real-world" cucumber features (mainly on github)
>> to see how more complex features are built but I have not really found
>> any. Could you point me to some?
>>
>> Thank you,
>> Balint
>> --
>> Posted via http://www.ruby-forum.com/.
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From walketim at gmail.com  Wed Mar 11 20:12:58 2009
From: walketim at gmail.com (Tim Walker)
Date: Wed, 11 Mar 2009 18:12:58 -0600
Subject: [rspec-users] [cucumber] getting scenario name in hook
In-Reply-To: <8d961d900903110921h79d8134cv42df0804affbef5d@mail.gmail.com>
References: <1ebf5a4d0903110812i6291ec87i58541e1a94812574@mail.gmail.com>
	<8d961d900903110921h79d8134cv42df0804affbef5d@mail.gmail.com>
Message-ID: <1ebf5a4d0903111712j354a23f0hc82c2e2e55acb39e@mail.gmail.com>

That did the trick. Thanks Aslak! Took a little while to figure out
where it was in the Scenario object but it was pretty straight forward
from there.

T

On Wed, Mar 11, 2009 at 10:21 AM, aslak hellesoy
<aslak.hellesoy at gmail.com> wrote:
>
>
> On Wed, Mar 11, 2009 at 4:12 PM, Tim Walker <walketim at gmail.com> wrote:
>>
>> Hi Guys,
>>
>> If I am generating diagnostics from a before do step can I get the
>> name of the scenario?
>
> This is implemented in 0.1.99.x:
> http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/44
>
> Aslak
>
>>
>> Many thanks,
>>
>> Tim
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From matt at mattwynne.net  Wed Mar 11 22:34:37 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Thu, 12 Mar 2009 02:34:37 +0000
Subject: [rspec-users] [cucumber] open source projects with cucumber
	features
In-Reply-To: <85d99afe0903111246x33b4a028r499253683fcf25c5@mail.gmail.com>
References: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
	<85d99afe0903111246x33b4a028r499253683fcf25c5@mail.gmail.com>
Message-ID: <F18C5860-2A71-4124-8116-8841C33E2C8C@mattwynne.net>


On 11 Mar 2009, at 19:46, Zach Dennis wrote:

> On Wed, Mar 11, 2009 at 3:03 PM, Balint Erdi <lists at ruby-forum.com>  
> wrote:
>> Hi,
>>
>> I was looking for some "real-world" cucumber features (mainly on  
>> github)
>> to see how more complex features are built but I have not really  
>> found
>> any. Could you point me to some?

What kind of app are you looking to build? Website? GUI? Console?

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From sfeley at gmail.com  Wed Mar 11 23:22:57 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Wed, 11 Mar 2009 23:22:57 -0400
Subject: [rspec-users] stubbing Time.zone.now for model tests fails for
	Rails 2.3.1
In-Reply-To: <5D52D0F4-0223-4C74-8215-2CAEB90FC993@tower-mt.com>
References: <5D52D0F4-0223-4C74-8215-2CAEB90FC993@tower-mt.com>
Message-ID: <1fb4df0903112022t442ac3exee3bbbd9de2d1472@mail.gmail.com>

On Wed, Mar 11, 2009 at 1:40 PM, David Schmidt <davids at tower-mt.com> wrote:
>
> Has anyone else run into this problem and come up with a solution to getting
> a fixed time back from Time.zone.now?

This plugin has worked very well for me:
http://github.com/notahat/time_travel/tree/master


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From zuperinfinite at gmail.com  Thu Mar 12 04:28:30 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Thu, 12 Mar 2009 09:28:30 +0100
Subject: [rspec-users] How to dummy a DB adapter?
In-Reply-To: <c579a2241a4fd4c029b68732bc0b47ea@ruby-forum.com>
References: <c579a2241a4fd4c029b68732bc0b47ea@ruby-forum.com>
Message-ID: <CB6100F4-E2D2-4159-A452-0852DBDA1E3E@gmail.com>


On 11-mrt-2009, at 19:02, James Byrne wrote:

> I am thinking about simply opening SQLiteAdapter and overriding the
> adapter_name method to some arbitrary value for the test.  However, it
> occurs to me that there are probably better ways to do what I am  
> trying
> to accomplish so I welcome any suggestions on how to proceed.

http://rspec.info/documentation/mocks/stubs.html

Stubbing is your newfound friend.

gr,
bartz


From matt at mattwynne.net  Thu Mar 12 04:37:55 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Thu, 12 Mar 2009 08:37:55 +0000
Subject: [rspec-users] [cucumber] accessing session variables
In-Reply-To: <896a69ff319435ef12204ab0c163647a@ruby-forum.com>
References: <896a69ff319435ef12204ab0c163647a@ruby-forum.com>
Message-ID: <F1CBACC8-1277-4818-A8E3-BC19DF5306BE@mattwynne.net>


On 11 Mar 2009, at 18:52, Balint Erdi wrote:

> Hey,
>
> I have the following simple scenario and the step definitions:
>
> Scenario: Create album
>  Given I am logged in as "pepito"
>  When I go to my profile page
>  ...
>
> Given /^the user (.*) exists$/ do |login_name|
>  User.find_by_login(login_name) || Factory(:user_with_password, :login
> => login_name)
> end
>
> Given /^I log in as (.*)$/ do |login_name|
>  user = User.find_by_login(login_name)
>  # it is supposed that the user was generated by the
> :user_with_password fixture
>  # that has the 'secret' password
>  post "/session", :login => user.login, :password => 'secret'
> end
>
> Given /^I am logged in as "(.*)"$/ do |login_name|
>  Given "the user #{login_name} exists"
>  Given "I log in as #{login_name}"
> end
>
> When /^I go to (.+)$/ do |page_name|
>  visit path_to(page_name)
> end
>
> def path_to(page_name)
>  case page_name
>
>  when /my profile page/i
>    member_profile_path(:id => session[:user_id])
>  ...
> end
>
> I receive the following error:
>
> When I go to my profile page  #
> features/step_definitions/webrat_steps.rb:6
>  You have a nil object when you didn't expect it!
>  The error occurred while evaluating nil.session (NoMethodError)
>     /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/ 
> action_controller/test_process.rb:429:in
> `session'
>
> So it seems like the session is not accessible -or not this way- in  
> the
> step definitions. I finally came up with that workaround:
>
> def path_to(page_name)
>  case page_name
>
>  when /my profile page/i
>    member_profile_path(:id => User.first)
>  ...
> end
>
> However, I am not at all content with this hack. It does not go to the
> profile page of the logged in user but to the first one. This can be  
> the
> same -and in this scenario it is- but there is no guarantee for that.

IMO, trying to access implementation details like sessions from your  
acceptance tests is an anti-pattern, to be avoided.

The puzzle you've hit here is that there is state implied in your  
scenarios by the use of the phrase "*my* profile page". I think there  
are two approaches this:

(1) You remove the implicit state from the scenario by re-writing your  
step as "When I go to the profile page for the User". This means that  
you can safely now use User.first, and you can even assert at the top  
of that step that User.count.should == 1, because the step refers to  
"the User" - so there must only be one, right?

(2) You model the state implicit in the scenario within your tests by  
writing an instance variable on the Scenario's world when you log in -  
something to represent "me".

There is a third approach where you write a special 'API' on your app  
which the tests can use to find out who "me" is. That might be as  
simple as conventionally putting it in a HTML comment on the page, or  
even displaying it on every page, or as over-engineered as a REST GET  
request to a user/current or /session resource.

However you chose to do it, I would urge you to avoid going under the  
covers to grab the session object directly - it's a path to hideous  
complexity IMO. Better to keep your test layer as separate as you can  
from the code.

Does that make sense?


Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From lists at ruby-forum.com  Thu Mar 12 09:27:51 2009
From: lists at ruby-forum.com (James Byrne)
Date: Thu, 12 Mar 2009 14:27:51 +0100
Subject: [rspec-users] Presentation Testing and CSS ids
In-Reply-To: <88fd8ddc0903111402s64809bdcpa79038c8789de184@mail.gmail.com>
References: <gp0tk0$7n7$1@ger.gmane.org>
	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>
	<gp13hb$oul$1@ger.gmane.org>
	<85d99afe0903081255t1fe64178va3b7ee7fd5bd3d0@mail.gmail.com>
	<71d2b98da3f45f61b8fe3d7709d2f164@ruby-forum.com>
	<88fd8ddc0903111402s64809bdcpa79038c8789de184@mail.gmail.com>
Message-ID: <b8a63296de0b87a4ad143e325c369b76@ruby-forum.com>

Andrew Premdas wrote:
> The key phrase is semantic meaning. Its good to use CSS to give semantic
> meaning to things that appear on web pages. Not only can these id's or
> classes be useful for using with screen readers, they should be stable
> things that don't change even if the design of the page does. It should 

This is an example of my current practice, consequential on the 
discussions I have had on this list:

<h2 id="authentication_request">To Proceed Please Authenticate 
Yourself</h2>
<div id="authentication_fields">
  <form action="/user_session"
        class="new_user_session"
        id="new_user_session"
        method="post"
  >
    <label for="user_session_username">User Name</label> <br />
    <input id="user_session_username"
           name="user_session[username]"
           size="30" type="text" />
...
    <input id="user_session_submit"
           name="commit"
           type="submit"
           value="Authenticate" />
  </form>
</div>

My intent is that id values are tied to the presentation elements they 
deal with, not to the layout they find themselves in.  So I test the UI 
by calling the ids in webrat, rather than the labels.  This will ease 
any future transition to I18n.t calls in the templates.

As a side issue, in getting the input box ids to work with label ids as 
I specified in the templates, I discovered that I had misread the 
FormHelper api.  I uncovered my mistake by writing a few tests to 
exercise this feature as Rails own test/form_helper_test.rb did not.

The point is that I have submitted these tests as a patch to Rails and 
they are awaiting verification for inclusion.  Patches require three 
reviewers for consideration by the core team.  My submission has had one 
positive review already. I would appreciate a couple of more. The 
lighthouse ticket is 2096.

http://rails.lighthouseapp.com/projects/8994/tickets/2096-added-select-method-tests-to-form_helper_testrb
-- 
Posted via http://www.ruby-forum.com/.

From phlip2005 at gmail.com  Thu Mar 12 11:11:52 2009
From: phlip2005 at gmail.com (Phlip)
Date: Thu, 12 Mar 2009 08:11:52 -0700
Subject: [rspec-users] Presentation Testing and CSS ids
In-Reply-To: <b8a63296de0b87a4ad143e325c369b76@ruby-forum.com>
References: <gp0tk0$7n7$1@ger.gmane.org>	<57c63afe0903081103l5d8ae8byb934bd0ae0672032@mail.gmail.com>	<gp13hb$oul$1@ger.gmane.org>	<85d99afe0903081255t1fe64178va3b7ee7fd5bd3d0@mail.gmail.com>	<71d2b98da3f45f61b8fe3d7709d2f164@ruby-forum.com>	<88fd8ddc0903111402s64809bdcpa79038c8789de184@mail.gmail.com>
	<b8a63296de0b87a4ad143e325c369b76@ruby-forum.com>
Message-ID: <gpb8np$d0q$1@ger.gmane.org>

James Byrne wrote:

> As a side issue, in getting the input box ids to work with label ids as 
> I specified in the templates, I discovered that I had misread the 
> FormHelper api.  I uncovered my mistake by writing a few tests to 
> exercise this feature as Rails own test/form_helper_test.rb did not.
> 
> The point is that I have submitted these tests as a patch to Rails and 
> they are awaiting verification for inclusion.  Patches require three 
> reviewers for consideration by the core team.  My submission has had one 
> positive review already. I would appreciate a couple of more. The 
> lighthouse ticket is 2096.

That reminds me of form_test_helper...

The deal is, with Rails out-of-the-box, you can test that a page wrote a form 
correctly, and the next text can show the post processes the arguments correctly...

...but the test cannot show the form contained the correct fields. You could 
mis-name a field, mis-name it in the first test, name it correctly in the next 
test, and all tests would pass.

form_test_helper scrapes your @response.body, finds a target form, and then 
posts it. It would catch the mis-named field situation.

Can webrat close that gap? Can Rails integration tests close that gap?

-- 
   Phlip


From oliver.beddows at googlemail.com  Sat Mar  7 10:49:30 2009
From: oliver.beddows at googlemail.com (karmacoma)
Date: Sat, 7 Mar 2009 07:49:30 -0800 (PST)
Subject: [rspec-users] Rails 2.2.2 Problem - button_to_function -
	nil.with_output_buffer
Message-ID: <69e617a7-32d5-4d3f-9d68-57b8e992433a@h5g2000yqh.googlegroups.com>

Hi,
I am in the process of upgrading my rails application to be compatible
with rails 2.2.2. All is going well apart from a few remaining issues.

My problem is: I am experiencing a test failure with what seems to be
related to the "with_output_buffer" method found in "lib/action_view/
helpers/capture_helper.rb" and my use of the "button_to_function"
method.

The code itself works fine. It is simply the test itself that won't
pass due to a NoMethodError exception.

Note: I am currently using rspec & rspec-rails (1.1.99.12), although
the same problem also exists when tested with the current stable
version: 1.1.12.

So, given the following helper module:
---
module ImagesHelper
  def hide_images_button
    content_tag :div, :class => :hide_images_button do
      button_to_function "Hide Images", :id => :hide_images_button do |
page|
        page[:more_images_button].toggle
        page[:image_browser].toggle
      end
    end
  end
end
---

With the accompanying test:
---
require File.expand_path(File.dirname(__FILE__) + '/../spec_helper')

describe ImagesHelper do
  it "should render a hide_images_button" do
    helper.hide_images_button.should have_tag('div[class=?]',
'hide_images_button') do
      with_tag('input[id=?][type=?][value=?][onclick^=?]',
'hide_images_button', 'button', 'Hide Images', "$
(&quot;more_images_button&quot;).toggle();\n$
(&quot;image_browser&quot;).toggle();;")
    end
  end
end
---

I am getting the following failure:
---
F

1)
NoMethodError in 'ImagesHelper should render a hide_images_button'
You have a nil object when you didn't expect it!
The error occurred while evaluating nil.with_output_buffer
/home/oliver/git/greyville/app/helpers/images_helper.rb:4:in
`hide_images_button'
/home/oliver/git/greyville/app/helpers/images_helper.rb:3:in
`hide_images_button'
spec/helpers/images_helper_spec.rb:5:

Finished in 0.025206 seconds

1 example, 1 failure
---

Any bright ideas on how I can fix this issue? Your help would be much
appreciated.
Regards, Oliver Beddows.

From nshb at inimit.com  Sat Mar  7 15:03:38 2009
From: nshb at inimit.com (Nathaniel Brown)
Date: Sat, 7 Mar 2009 12:03:38 -0800 (PST)
Subject: [rspec-users] [rspec/tm] When running the textmate bundle hook
	using command-r I get an error about missing rubygems
Message-ID: <d96af48a-fcee-4923-8cfe-d5b12ac6a6ed@f11g2000vbf.googlegroups.com>

I get the following error using both edge version of the TM bundle and
rspec/rspec-rails in vendor/plugins.

/Users/nshb/Library/Application Support/TextMate/Bundles/
RSpec.tmbundle/Support/lib/spec/mate.rb:2:in `require': No such file
to load -- rubygems (LoadError) from /Users/nshb/Library/Application
Support/TextMate/Bundles/RSpec.tmbundle/Support/lib/spec/mate.rb:2
from /tmp/textmate-command-20424.rb:2:in `require' from /tmp/textmate-
command-20424.rb:2

Any ideas? IRB loads rubygems fine, not sure why it's not working here.

From zegomesjf at gmail.com  Sun Mar  8 19:19:55 2009
From: zegomesjf at gmail.com (=?ISO-8859-1?Q?Jos=E9_Gomes_Jr=2E?=)
Date: Sun, 8 Mar 2009 16:19:55 -0700 (PDT)
Subject: [rspec-users] rspec 1.1.99.12, Rails 2.3.1,
	undefined method `rspec_options='
Message-ID: <81fd84b6-6093-4984-9a23-d4ce3ce8c62a@q9g2000yqc.googlegroups.com>

Hi David, all:

I recently upgraded to Rails 2.3.1RC2 (Ubuntu 8.10, ruby 1.8.7
(2008-08-11 patchlevel 72) [i486-linux]) and have been dilligently
following the instructions for upgrading rspec and rspec-rails
according to:  http://wiki.github.com/dchelimsky/rspec/rails-with-rspec-gems.
and when I run 'rake gem' fails with error:

rake aborted!
undefined method `rspec_options=' for #<Hoe:0xb782caf0>
/rspec/Rakefile:24


rspec / Rakefile look like
# -*- ruby -*-

$:.unshift(File.join(File.dirname(__FILE__), 'lib'))
require 'hoe'
require 'spec/version'
require 'spec/rake/spectask'
require 'cucumber/rake/task'

class Hoe
  def extra_deps
    @extra_deps.reject! { |x| Array(x).first == 'hoe' }
    @extra_deps
  end
end

Hoe.new('rspec', Spec::VERSION::STRING) do |p|
  p.summary = Spec::VERSION::SUMMARY
  p.url = 'http://rspec.info/'
  p.description = "Behaviour Driven Development for Ruby."
  p.rubyforge_name = 'rspec'
  p.developer('RSpec Development Team', 'rspec-devel at rubyforge.org')
  p.extra_dev_deps = [["cucumber",">= 0.1.13"]]
  p.remote_rdoc_dir = "rspec/#{Spec::VERSION::STRING}"
  p.rspec_options = ['--options', 'spec/spec.opts']
end

Thanks in advance for your assistance,
Jos? Gomes J?nior

From analytics.google at allproducts.info  Thu Mar 12 03:38:11 2009
From: analytics.google at allproducts.info (Anton)
Date: Thu, 12 Mar 2009 00:38:11 -0700 (PDT)
Subject: [rspec-users] Run rake spec with a halt-on-errors mode?
Message-ID: <9e9a6a83-e1ba-481b-8b2b-422dda5ac061@p20g2000yqi.googlegroups.com>

Hello everybody!

I am using rspec for quite a time now, and it is really a great tool!

The only thing that I haven't figured out is how to set the spec
runner to a halt-on-error mode. For example a lot of browser tests
depend on Google maps and if I have no internet connection none of
them makes sense. Some other errors are unwanted test dependencies -
and I don't want to analyze hundrets of test or run them manually just
to check what is wrong.

So it would be great if I could tell the spec runner to stop on the
first error in such cases. Would be a big time saver for me if someone
could give me a hint...

Thank you very much in advance,

Anton

From dchelimsky at gmail.com  Thu Mar 12 12:44:10 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 12 Mar 2009 11:44:10 -0500
Subject: [rspec-users] rspec 1.1.99.12, Rails 2.3.1,
	undefined method 	`rspec_options='
In-Reply-To: <81fd84b6-6093-4984-9a23-d4ce3ce8c62a@q9g2000yqc.googlegroups.com>
References: <81fd84b6-6093-4984-9a23-d4ce3ce8c62a@q9g2000yqc.googlegroups.com>
Message-ID: <57c63afe0903120944l2c38385fp96034c7723f73f5@mail.gmail.com>

On Sun, Mar 8, 2009 at 6:19 PM, Jos? Gomes Jr. <zegomesjf at gmail.com> wrote:
> Hi David, all:
>
> I recently upgraded to Rails 2.3.1RC2 (Ubuntu 8.10, ruby 1.8.7
> (2008-08-11 patchlevel 72) [i486-linux]) and have been dilligently
> following the instructions for upgrading rspec and rspec-rails
> according to: ?http://wiki.github.com/dchelimsky/rspec/rails-with-rspec-gems.
> and when I run 'rake gem' fails with error:
>
> rake aborted!
> undefined method `rspec_options=' for #<Hoe:0xb782caf0>
> /rspec/Rakefile:24
>
>
> rspec / Rakefile look like
> # -*- ruby -*-
>
> $:.unshift(File.join(File.dirname(__FILE__), 'lib'))
> require 'hoe'
> require 'spec/version'
> require 'spec/rake/spectask'
> require 'cucumber/rake/task'
>
> class Hoe
> ?def extra_deps
> ? ?@extra_deps.reject! { |x| Array(x).first == 'hoe' }
> ? ?@extra_deps
> ?end
> end
>
> Hoe.new('rspec', Spec::VERSION::STRING) do |p|
> ?p.summary = Spec::VERSION::SUMMARY
> ?p.url = 'http://rspec.info/'
> ?p.description = "Behaviour Driven Development for Ruby."
> ?p.rubyforge_name = 'rspec'
> ?p.developer('RSpec Development Team', 'rspec-devel at rubyforge.org')
> ?p.extra_dev_deps = [["cucumber",">= 0.1.13"]]
> ?p.remote_rdoc_dir = "rspec/#{Spec::VERSION::STRING}"
> ?p.rspec_options = ['--options', 'spec/spec.opts']


[sudo] gem update hoe

rspec_options is a relatively new hoe addition.

Cheers,
David

> end
>
> Thanks in advance for your assistance,
> Jos? Gomes J?nior
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From zach.dennis at gmail.com  Thu Mar 12 16:17:26 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Thu, 12 Mar 2009 16:17:26 -0400
Subject: [rspec-users] Run rake spec with a halt-on-errors mode?
In-Reply-To: <9e9a6a83-e1ba-481b-8b2b-422dda5ac061@p20g2000yqi.googlegroups.com>
References: <9e9a6a83-e1ba-481b-8b2b-422dda5ac061@p20g2000yqi.googlegroups.com>
Message-ID: <85d99afe0903121317i5f04263dv9e1658032bcd7260@mail.gmail.com>

On Thu, Mar 12, 2009 at 3:38 AM, Anton
<analytics.google at allproducts.info> wrote:
> Hello everybody!
>
> I am using rspec for quite a time now, and it is really a great tool!
>
> The only thing that I haven't figured out is how to set the spec
> runner to a halt-on-error mode. For example a lot of browser tests
> depend on Google maps and if I have no internet connection none of
> them makes sense. Some other errors are unwanted test dependencies -
> and I don't want to analyze hundrets of test or run them manually just
> to check what is wrong.

Why not filter these specs that go to Google Maps, so you have to run
them explicitly, or only when your CI server runs?

We usually have a few specs and scenarios that test real-world
integration, and then we stub out the external dependencies in our
object-level specs. And we've added a couple rake tasks to run all of
them, just one, or just the other, and then a CI rake task that runs
all of them.



>
> So it would be great if I could tell the spec runner to stop on the
> first error in such cases. Would be a big time saver for me if someone
> could give me a hint...
>
> Thank you very much in advance,
>
> Anton
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From bill at artima.com  Thu Mar 12 17:50:05 2009
From: bill at artima.com (Bill Venners)
Date: Thu, 12 Mar 2009 14:50:05 -0700
Subject: [rspec-users] How do you use pending in RSpec?
Message-ID: <3b8d0de60903121450t457368edg1f803dbddd512fa3@mail.gmail.com>

Hi All,

I've been working on BDD support in a test framework for Scala
imaginatively called ScalaTest, and I want to add support for the
notion of pending examples. I see three different "forms" of pending
in RSpec, and I'm curious to hear which ones RSpec users find most
useful. The three forms are:

# 1. With no block you get a PENDING (Not Yet Implemented) in the report
it "should say foo"

# 2. Passing a string, but no block, to pending. You get the PENDING
(get the vocal chords working) in the report.
it "should say foo" do
  pending("get the vocal chords working")
  subject.should say("foo")
end

# 3. Pass a string and a block to pending. If the pending code raises
an exception, then you get PENDING (get the vocal chords working)k
# but if not, I believe the whole tests fails to let you know you need
to drop the pending stuff now that it works (I may be wrong).
it "should say foo" do
  pending("get the vocal chords working") do
    subject.should say("foo")
  end
end

Which of these forms do you find the most useful in practice, and are
there any that you think would be better left out?

Thanks.

Bill
----
Bill Venners
Artima, Inc.
http://www.artima.com

From scott at railsnewbie.com  Thu Mar 12 18:02:31 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Thu, 12 Mar 2009 18:02:31 -0400
Subject: [rspec-users] How do you use pending in RSpec?
In-Reply-To: <3b8d0de60903121450t457368edg1f803dbddd512fa3@mail.gmail.com>
References: <3b8d0de60903121450t457368edg1f803dbddd512fa3@mail.gmail.com>
Message-ID: <89C05CF5-9CA7-492A-B6EA-C253179B321B@railsnewbie.com>


On Mar 12, 2009, at 5:50 PM, Bill Venners wrote:

> Hi All,
>
> I've been working on BDD support in a test framework for Scala
> imaginatively called ScalaTest, and I want to add support for the
> notion of pending examples. I see three different "forms" of pending
> in RSpec, and I'm curious to hear which ones RSpec users find most
> useful. The three forms are:
>
> # 1. With no block you get a PENDING (Not Yet Implemented) in the  
> report
> it "should say foo"
>
> # 2. Passing a string, but no block, to pending. You get the PENDING
> (get the vocal chords working) in the report.
> it "should say foo" do
>  pending("get the vocal chords working")
>  subject.should say("foo")
> end
>
> # 3. Pass a string and a block to pending. If the pending code raises
> an exception, then you get PENDING (get the vocal chords working)k
> # but if not, I believe the whole tests fails to let you know you need
> to drop the pending stuff now that it works (I may be wrong).
> it "should say foo" do
>  pending("get the vocal chords working") do
>    subject.should say("foo")
>  end
> end
>
> Which of these forms do you find the most useful in practice, and are
> there any that you think would be better left out?

Don't forget xit(), either, which doesn't run a group of tests.

pending with a string is what I use most often, but pending with a  
block (with or without a string) is immensely helpful when refactoring.

Scott


From aslak.hellesoy at gmail.com  Thu Mar 12 18:05:34 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Thu, 12 Mar 2009 23:05:34 +0100
Subject: [rspec-users] How do you use pending in RSpec?
In-Reply-To: <3b8d0de60903121450t457368edg1f803dbddd512fa3@mail.gmail.com>
References: <3b8d0de60903121450t457368edg1f803dbddd512fa3@mail.gmail.com>
Message-ID: <8d961d900903121505t565eafa4yea53f38e2a00befb@mail.gmail.com>

On Thu, Mar 12, 2009 at 10:50 PM, Bill Venners <bill at artima.com> wrote:

> Hi All,
>
> I've been working on BDD support in a test framework for Scala
> imaginatively called ScalaTest, and I want to add support for the


Very cool!


>
> notion of pending examples. I see three different "forms" of pending
> in RSpec, and I'm curious to hear which ones RSpec users find most
> useful. The three forms are:
>
> # 1. With no block you get a PENDING (Not Yet Implemented) in the report
> it "should say foo"
>

I rarely use this, as I don't write a lot of specs up front.


>
> # 2. Passing a string, but no block, to pending. You get the PENDING
> (get the vocal chords working) in the report.
> it "should say foo" do
>  pending("get the vocal chords working")
>  subject.should say("foo")
> end
>

I find myself using #2 the most. I use it when I want to reduce noise diring
a refactoring that breaks a lot.


>
> # 3. Pass a string and a block to pending. If the pending code raises
> an exception, then you get PENDING (get the vocal chords working)k
> # but if not, I believe the whole tests fails to let you know you need
> to drop the pending stuff now that it works (I may be wrong).
> it "should say foo" do
>  pending("get the vocal chords working") do
>    subject.should say("foo")
>  end
> end
>

I sometimes use this when I'm not sure why the example is failing, but don't
want to look into it right now.


>
> Which of these forms do you find the most useful in practice, and are
> there any that you think would be better left out?
>

Cheers,
Aslak


>
> Thanks.
>
> Bill
> ----
> Bill Venners
> Artima, Inc.
> http://www.artima.com
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090312/3ef1b87d/attachment-0001.html>

From bill at artima.com  Thu Mar 12 19:23:51 2009
From: bill at artima.com (Bill Venners)
Date: Thu, 12 Mar 2009 16:23:51 -0700
Subject: [rspec-users] How do you use pending in RSpec?
In-Reply-To: <8d961d900903121505t565eafa4yea53f38e2a00befb@mail.gmail.com>
References: <3b8d0de60903121450t457368edg1f803dbddd512fa3@mail.gmail.com>
	<8d961d900903121505t565eafa4yea53f38e2a00befb@mail.gmail.com>
Message-ID: <3b8d0de60903121623xd68a81aj483a54fafab28c3f@mail.gmail.com>

Hi Aslak and Scott,

Thanks for your replies. I have a couple quick follow up questions.

On Thu, Mar 12, 2009 at 3:05 PM, aslak hellesoy
<aslak.hellesoy at gmail.com> wrote:
>
>
> On Thu, Mar 12, 2009 at 10:50 PM, Bill Venners <bill at artima.com> wrote:
>>
>> Hi All,
>>
>> I've been working on BDD support in a test framework for Scala
>> imaginatively called ScalaTest, and I want to add support for the
>
> Very cool!
>
>> notion of pending examples. I see three different "forms" of pending
>> in RSpec, and I'm curious to hear which ones RSpec users find most
>> useful. The three forms are:
>>
>> # 1. With no block you get a PENDING (Not Yet Implemented) in the report
>> it "should say foo"
>
> I rarely use this, as I don't write a lot of specs up front.
>
OK. One use case I see for pending is writing the spec text before the
example code. No one yet has said they actually do this in practice.
Anyone care to admit this feature is important to them?

>>
>> # 2. Passing a string, but no block, to pending. You get the PENDING
>> (get the vocal chords working) in the report.
>> it "should say foo" do
>>  pending("get the vocal chords working")
>>  subject.should say("foo")
>> end
>
> I find myself using #2 the most. I use it when I want to reduce noise diring
> a refactoring that breaks a lot.
>
You know there's already an "ignore" feature in ScalaTest's Spec,
which I think is probably like xit in RSpec. You just select "it" and
change it to "ignore". That means temporarily ignore this test, which
most likely broke because I'm doing refactoring. What's missing is
that there's no way with ignore to specify a string like you can with
pending #2. What do you usually put in that string?

>>
>> # 3. Pass a string and a block to pending. If the pending code raises
>> an exception, then you get PENDING (get the vocal chords working)k
>> # but if not, I believe the whole tests fails to let you know you need
>> to drop the pending stuff now that it works (I may be wrong).
>> it "should say foo" do
>>  pending("get the vocal chords working") do
>>    subject.should say("foo")
>>  end
>> end
>
> I sometimes use this when I'm not sure why the example is failing, but don't
> want to look into it right now.
>
I guess I'm curious:

1) How important is it to you to be able to just "strike out" the
lines of code within an example that are failing (as you can with
RSpec's #3 pending form), versus just "striking out" the entire
example as you can with ignore in ScalaTest.

2) How important is it to you to be able to add a string message to
your stricken code, as you can with either #2 or #3 in RSpec? How does
that string help you?

Thanks.

Bill
----
Bill Venners
Artima, Inc.
http://www.artima.com/

From scott at railsnewbie.com  Thu Mar 12 19:40:53 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Thu, 12 Mar 2009 19:40:53 -0400
Subject: [rspec-users] How do you use pending in RSpec?
In-Reply-To: <3b8d0de60903121623xd68a81aj483a54fafab28c3f@mail.gmail.com>
References: <3b8d0de60903121450t457368edg1f803dbddd512fa3@mail.gmail.com>	<8d961d900903121505t565eafa4yea53f38e2a00befb@mail.gmail.com>
	<3b8d0de60903121623xd68a81aj483a54fafab28c3f@mail.gmail.com>
Message-ID: <49B99D85.2040603@railsnewbie.com>

Bill Venners wrote:
> Hi Aslak and Scott,
>
> Thanks for your replies. I have a couple quick follow up questions.
>
> On Thu, Mar 12, 2009 at 3:05 PM, aslak hellesoy
> <aslak.hellesoy at gmail.com> wrote:
>   
>> On Thu, Mar 12, 2009 at 10:50 PM, Bill Venners <bill at artima.com> wrote:
>>     
>>> Hi All,
>>>
>>> I've been working on BDD support in a test framework for Scala
>>> imaginatively called ScalaTest, and I want to add support for the
>>>       
>> Very cool!
>>
>>     
>>> notion of pending examples. I see three different "forms" of pending
>>> in RSpec, and I'm curious to hear which ones RSpec users find most
>>> useful. The three forms are:
>>>
>>> # 1. With no block you get a PENDING (Not Yet Implemented) in the report
>>> it "should say foo"
>>>       
>> I rarely use this, as I don't write a lot of specs up front.
>>
>>     
> OK. One use case I see for pending is writing the spec text before the
> example code. No one yet has said they actually do this in practice.
> Anyone care to admit this feature is important to them?
>
>   
Sure, I'll use it occasionally: I'll add three or four cases and then go 
to work.

It probably wouldn't be a big deal if rspec didn't have it, though, as I 
never leave them before completing them.

>>> # 2. Passing a string, but no block, to pending. You get the PENDING
>>> (get the vocal chords working) in the report.
>>> it "should say foo" do
>>>  pending("get the vocal chords working")
>>>  subject.should say("foo")
>>> end
>>>       
>> I find myself using #2 the most. I use it when I want to reduce noise diring
>> a refactoring that breaks a lot.
>>
>>     
> You know there's already an "ignore" feature in ScalaTest's Spec,
> which I think is probably like xit in RSpec. You just select "it" and
> change it to "ignore". That means temporarily ignore this test, which
> most likely broke because I'm doing refactoring. What's missing is
> that there's no way with ignore to specify a string like you can with
> pending #2. What do you usually put in that string?
>   
it "should do such and such" do
  pending 'This is a bug which I can't currently figure out.  Revisit 
once feature X is done'
  ...
end

>>> # 3. Pass a string and a block to pending. If the pending code raises
>>> an exception, then you get PENDING (get the vocal chords working)k
>>> # but if not, I believe the whole tests fails to let you know you need
>>> to drop the pending stuff now that it works (I may be wrong).
>>> it "should say foo" do
>>>  pending("get the vocal chords working") do
>>>    subject.should say("foo")
>>>  end
>>> end
>>>       
>> I sometimes use this when I'm not sure why the example is failing, but don't
>> want to look into it right now.
>>
>>     
> I guess I'm curious:
>
> 1) How important is it to you to be able to just "strike out" the
> lines of code within an example that are failing (as you can with
> RSpec's #3 pending form), versus just "striking out" the entire
> example as you can with ignore in ScalaTest.
>   
Striking out the entire example is what's important - not a subset of 
the spec.

> 2) How important is it to you to be able to add a string message to
> your stricken code, as you can with either #2 or #3 in RSpec? How does
> that string help you?
>
>   
It makes it clear why I made it pending in the first place, and went 
ahead and committed it anyway without finishing it.

That's my workflow - others may be different, especially with the advent 
of rbehave / story runner / cucumber.

Scott



> Thanks.
>
> Bill
> ----
> Bill Venners
> Artima, Inc.
> http://www.artima.com/
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>   


From dchelimsky at gmail.com  Fri Mar 13 00:43:58 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 12 Mar 2009 23:43:58 -0500
Subject: [rspec-users] Rails 2.2.2 Problem - button_to_function -
	nil.with_output_buffer
In-Reply-To: <69e617a7-32d5-4d3f-9d68-57b8e992433a@h5g2000yqh.googlegroups.com>
References: <69e617a7-32d5-4d3f-9d68-57b8e992433a@h5g2000yqh.googlegroups.com>
Message-ID: <57c63afe0903122143k687e1c8aib05ac5d2d0e78de3@mail.gmail.com>

On Sat, Mar 7, 2009 at 10:49 AM, karmacoma
<oliver.beddows at googlemail.com> wrote:
> Hi,
> I am in the process of upgrading my rails application to be compatible
> with rails 2.2.2. All is going well apart from a few remaining issues.
>
> My problem is: I am experiencing a test failure with what seems to be
> related to the "with_output_buffer" method found in "lib/action_view/
> helpers/capture_helper.rb" and my use of the "button_to_function"
> method.
>
> The code itself works fine. It is simply the test itself that won't
> pass due to a NoMethodError exception.
>
> Note: I am currently using rspec & rspec-rails (1.1.99.12), although
> the same problem also exists when tested with the current stable
> version: 1.1.12.
>
> So, given the following helper module:
> ---
> module ImagesHelper
> ?def hide_images_button
> ? ?content_tag :div, :class => :hide_images_button do
> ? ? ?button_to_function "Hide Images", :id => :hide_images_button do |
> page|
> ? ? ? ?page[:more_images_button].toggle
> ? ? ? ?page[:image_browser].toggle
> ? ? ?end
> ? ?end
> ?end
> end
> ---
>
> With the accompanying test:
> ---
> require File.expand_path(File.dirname(__FILE__) + '/../spec_helper')
>
> describe ImagesHelper do
> ?it "should render a hide_images_button" do
> ? ?helper.hide_images_button.should have_tag('div[class=?]',
> 'hide_images_button') do
> ? ? ?with_tag('input[id=?][type=?][value=?][onclick^=?]',
> 'hide_images_button', 'button', 'Hide Images', "$
> (&quot;more_images_button&quot;).toggle();\n$
> (&quot;image_browser&quot;).toggle();;")
> ? ?end
> ?end
> end
> ---
>
> I am getting the following failure:
> ---
> F
>
> 1)
> NoMethodError in 'ImagesHelper should render a hide_images_button'
> You have a nil object when you didn't expect it!
> The error occurred while evaluating nil.with_output_buffer
> /home/oliver/git/greyville/app/helpers/images_helper.rb:4:in
> `hide_images_button'
> /home/oliver/git/greyville/app/helpers/images_helper.rb:3:in
> `hide_images_button'
> spec/helpers/images_helper_spec.rb:5:
>
> Finished in 0.025206 seconds
>
> 1 example, 1 failure
> ---
>
> Any bright ideas on how I can fix this issue? Your help would be much
> appreciated.

This was reported in lighthouse:
http://rspec.lighthouseapp.com/projects/5645-rspec/tickets/719

And fixed: http://github.com/dchelimsky/rspec-rails/commit/804f8cbc0468b1fe632cfb6c488de28d0ed39155

If you follow the instructions on
http://wiki.github.com/dchelimsky/rspec/edge and build 1.1.9.13 or .14
or just edge, you'll be fine.



> Regards, Oliver Beddows.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Fri Mar 13 00:44:46 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 12 Mar 2009 23:44:46 -0500
Subject: [rspec-users] [rspec/tm] When running the textmate bundle hook
	using command-r I get an error about missing rubygems
In-Reply-To: <d96af48a-fcee-4923-8cfe-d5b12ac6a6ed@f11g2000vbf.googlegroups.com>
References: <d96af48a-fcee-4923-8cfe-d5b12ac6a6ed@f11g2000vbf.googlegroups.com>
Message-ID: <57c63afe0903122144r171d7a7byfcc2d82d4bb21ea2@mail.gmail.com>

On Sat, Mar 7, 2009 at 3:03 PM, Nathaniel Brown <nshb at inimit.com> wrote:
> I get the following error using both edge version of the TM bundle and
> rspec/rspec-rails in vendor/plugins.
>
> /Users/nshb/Library/Application Support/TextMate/Bundles/
> RSpec.tmbundle/Support/lib/spec/mate.rb:2:in `require': No such file
> to load -- rubygems (LoadError) from /Users/nshb/Library/Application
> Support/TextMate/Bundles/RSpec.tmbundle/Support/lib/spec/mate.rb:2
> from /tmp/textmate-command-20424.rb:2:in `require' from /tmp/textmate-
> command-20424.rb:2
>
> Any ideas? IRB loads rubygems fine, not sure why it's not working here.

I've never seen that before - no ideas here. Anybody else?

From korny at sietsma.com  Fri Mar 13 02:55:51 2009
From: korny at sietsma.com (Korny Sietsma)
Date: Fri, 13 Mar 2009 17:55:51 +1100
Subject: [rspec-users] Cucumber seems to be running steps after failed steps
	...
Message-ID: <8e15872b0903122355u3cf782dcxd61da5daa4f34c2a@mail.gmail.com>

I'm a bit confused.
I have a scenario similar to (numbered for clarity):
  Scenario: view basic
1)     Given I am logged in as 'fred'
2)      When I navigate to the 'foo' tab
3)      And I select the 'bar' node
4)      Then the node 'baz' is displayed

Now, when I have a problem that the 'foo' tab isn't actually visible, I
expect the scenario to fail at step 2.
It seems that it *does* fail, but it also runs steps 3 and 4 silently.
The trouble is that without the 'foo' tab, the 'bar' and 'baz' nodes don't
exist.  But I have code behind the scenes that tracks selenium errors and
takes screenshots and generates log messages, which I don't really want - I
only care about the error at step 2.  (And I'm also wasting time at steps 3
and 4 waiting for selenium stuff to time out...)

Is this the expected behaviour?  I did some digging in the code, and it
seems the core functionality is in executor.rb:
    def visit_step(step)
      unless @pending || @error
        begin
...
          step.execute_in(@world, regexp, args, proc) unless @dry_run
          @after_step_procs.each{|p| p.call_in(@world, *[])}
          formatters.step_passed(step, regexp, args)
...
        rescue => e
          @failed = true
          @error = step.error = e
          formatters.step_failed(step, regexp, args)
        end
      else
        begin
...
          step.execute_in(@world, regexp, args, proc)
          formatters.step_skipped(step, regexp, args)
...
        rescue Exception
          formatters.step_skipped(step, regexp, args)
        end
      end
    end

>From reading this, it seems that once @pending or @error are set, following
steps will indeed still be run, but the output will be displayed as if they
were skipped.

Is this right?  Is there some way to bypass this and say "this is a serious
error, abort this scenario and jump to the next one" ???

- Korny

-- 
Kornelis Sietsma  korny at my surname dot com
kornys on gmail, twitter, facebook, etc.
"Every jumbled pile of person has a thinking part
that wonders what the part that isn't thinking
isn't thinking of"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090313/74269acd/attachment.html>

From korny at sietsma.com  Fri Mar 13 03:05:25 2009
From: korny at sietsma.com (Korny Sietsma)
Date: Fri, 13 Mar 2009 18:05:25 +1100
Subject: [rspec-users] Cucumber seems to be running steps after failed
	steps ...
In-Reply-To: <8e15872b0903122355u3cf782dcxd61da5daa4f34c2a@mail.gmail.com>
References: <8e15872b0903122355u3cf782dcxd61da5daa4f34c2a@mail.gmail.com>
Message-ID: <8e15872b0903130005v3b7fac55w145ead36b6331da6@mail.gmail.com>

Hmm - it might be because I had both cucumber-0.1.16 and the
aslakhellesoy-cucumber gem installed - I'll try to get rid of the old
cucumber gem and see if that helps.  (Though my initial attempts are causing
all sorts of pain with things that seem to require 'cucumber' not
'aslakhellesoy-cucumber' - I might actually give up and try again on Monday
when it might all make more sense!)

- Korny

On Fri, Mar 13, 2009 at 5:55 PM, Korny Sietsma <korny at sietsma.com> wrote:

> I'm a bit confused.
> I have a scenario similar to (numbered for clarity):
>   Scenario: view basic
> 1)     Given I am logged in as 'fred'
> 2)      When I navigate to the 'foo' tab
> 3)      And I select the 'bar' node
> 4)      Then the node 'baz' is displayed
>
> Now, when I have a problem that the 'foo' tab isn't actually visible, I
> expect the scenario to fail at step 2.
> It seems that it *does* fail, but it also runs steps 3 and 4 silently.
> The trouble is that without the 'foo' tab, the 'bar' and 'baz' nodes don't
> exist.  But I have code behind the scenes that tracks selenium errors and
> takes screenshots and generates log messages, which I don't really want - I
> only care about the error at step 2.  (And I'm also wasting time at steps 3
> and 4 waiting for selenium stuff to time out...)
>
> Is this the expected behaviour?  I did some digging in the code, and it
> seems the core functionality is in executor.rb:
>     def visit_step(step)
>       unless @pending || @error
>         begin
> ...
>           step.execute_in(@world, regexp, args, proc) unless @dry_run
>           @after_step_procs.each{|p| p.call_in(@world, *[])}
>           formatters.step_passed(step, regexp, args)
> ...
>         rescue => e
>           @failed = true
>           @error = step.error = e
>           formatters.step_failed(step, regexp, args)
>         end
>       else
>         begin
> ...
>           step.execute_in(@world, regexp, args, proc)
>           formatters.step_skipped(step, regexp, args)
> ...
>         rescue Exception
>           formatters.step_skipped(step, regexp, args)
>         end
>       end
>     end
>
> From reading this, it seems that once @pending or @error are set, following
> steps will indeed still be run, but the output will be displayed as if they
> were skipped.
>
> Is this right?  Is there some way to bypass this and say "this is a serious
> error, abort this scenario and jump to the next one" ???
>
> - Korny
>
> --
> Kornelis Sietsma  korny at my surname dot com
> kornys on gmail, twitter, facebook, etc.
> "Every jumbled pile of person has a thinking part
> that wonders what the part that isn't thinking
> isn't thinking of"
>



-- 
Kornelis Sietsma  korny at my surname dot com
kornys on gmail, twitter, facebook, etc.
"Every jumbled pile of person has a thinking part
that wonders what the part that isn't thinking
isn't thinking of"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090313/dfb6d467/attachment-0001.html>

From scott at railsnewbie.com  Fri Mar 13 03:17:11 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Fri, 13 Mar 2009 03:17:11 -0400
Subject: [rspec-users] [rspec/tm] When running the textmate bundle hook
 using command-r I get an error about missing rubygems
In-Reply-To: <57c63afe0903122144r171d7a7byfcc2d82d4bb21ea2@mail.gmail.com>
References: <d96af48a-fcee-4923-8cfe-d5b12ac6a6ed@f11g2000vbf.googlegroups.com>
	<57c63afe0903122144r171d7a7byfcc2d82d4bb21ea2@mail.gmail.com>
Message-ID: <49BA0877.6070400@railsnewbie.com>

David Chelimsky wrote:
> On Sat, Mar 7, 2009 at 3:03 PM, Nathaniel Brown <nshb at inimit.com> wrote:
>   
>> I get the following error using both edge version of the TM bundle and
>> rspec/rspec-rails in vendor/plugins.
>>
>> /Users/nshb/Library/Application Support/TextMate/Bundles/
>> RSpec.tmbundle/Support/lib/spec/mate.rb:2:in `require': No such file
>> to load -- rubygems (LoadError) from /Users/nshb/Library/Application
>> Support/TextMate/Bundles/RSpec.tmbundle/Support/lib/spec/mate.rb:2
>> from /tmp/textmate-command-20424.rb:2:in `require' from /tmp/textmate-
>> command-20424.rb:2
>>
>> Any ideas? IRB loads rubygems fine, not sure why it's not working here.
>>     
>
> I've never seen that before - no ideas here. Anybody else?
>   
I don't use textmate at all, but I'd check that it's the same ruby 
version (RUBY_VERSION, RUBY_PATCHLEVEL), and that the $LOAD_PATH is the 
same as an irb session.

How is ruby being invoked in that script?  I prefer to use "/usr/bin/env 
ruby", but on occasion I've seen absolute paths to /usr/bin/ruby or 
/usr/local/bin/ruby - both which may fail if you have, say, a ruby 
installed via macports and the one that came with OS X. 

I'd bet that a different ruby executable is being used - one which 
doesn't have rubygems installed.

Scott

> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>   


From aslak.hellesoy at gmail.com  Fri Mar 13 03:45:13 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Fri, 13 Mar 2009 08:45:13 +0100
Subject: [rspec-users] Cucumber seems to be running steps after failed
	steps ...
In-Reply-To: <8e15872b0903130005v3b7fac55w145ead36b6331da6@mail.gmail.com>
References: <8e15872b0903122355u3cf782dcxd61da5daa4f34c2a@mail.gmail.com>
	<8e15872b0903130005v3b7fac55w145ead36b6331da6@mail.gmail.com>
Message-ID: <8d961d900903130045t2d0bb605lad4829ba95baed25@mail.gmail.com>

On Fri, Mar 13, 2009 at 8:05 AM, Korny Sietsma <korny at sietsma.com> wrote:

> Hmm - it might be because I had both cucumber-0.1.16 and the
> aslakhellesoy-cucumber gem installed - I'll try to get rid of the old
> cucumber gem and see if that helps.  (Though my initial attempts are causing
> all sorts of pain with things that seem to require 'cucumber' not
> 'aslakhellesoy-cucumber' - I might actually give up and try again on Monday
> when it might all make more sense!)
>

Yes, this bug was fixed after 0.1.16, so you're better off with one of the
snapshot gems.
http://rspec.lighthouseapp.com/projects/16211/tickets/90-really-skip-skipped-steps

Aslak


>
> - Korny
>
>
> On Fri, Mar 13, 2009 at 5:55 PM, Korny Sietsma <korny at sietsma.com> wrote:
>
>> I'm a bit confused.
>> I have a scenario similar to (numbered for clarity):
>>   Scenario: view basic
>> 1)     Given I am logged in as 'fred'
>> 2)      When I navigate to the 'foo' tab
>> 3)      And I select the 'bar' node
>> 4)      Then the node 'baz' is displayed
>>
>> Now, when I have a problem that the 'foo' tab isn't actually visible, I
>> expect the scenario to fail at step 2.
>> It seems that it *does* fail, but it also runs steps 3 and 4 silently.
>> The trouble is that without the 'foo' tab, the 'bar' and 'baz' nodes don't
>> exist.  But I have code behind the scenes that tracks selenium errors and
>> takes screenshots and generates log messages, which I don't really want - I
>> only care about the error at step 2.  (And I'm also wasting time at steps 3
>> and 4 waiting for selenium stuff to time out...)
>>
>> Is this the expected behaviour?  I did some digging in the code, and it
>> seems the core functionality is in executor.rb:
>>     def visit_step(step)
>>       unless @pending || @error
>>         begin
>> ...
>>           step.execute_in(@world, regexp, args, proc) unless @dry_run
>>           @after_step_procs.each{|p| p.call_in(@world, *[])}
>>           formatters.step_passed(step, regexp, args)
>> ...
>>         rescue => e
>>           @failed = true
>>           @error = step.error = e
>>           formatters.step_failed(step, regexp, args)
>>         end
>>       else
>>         begin
>> ...
>>           step.execute_in(@world, regexp, args, proc)
>>           formatters.step_skipped(step, regexp, args)
>> ...
>>         rescue Exception
>>           formatters.step_skipped(step, regexp, args)
>>         end
>>       end
>>     end
>>
>> From reading this, it seems that once @pending or @error are set,
>> following steps will indeed still be run, but the output will be displayed
>> as if they were skipped.
>>
>> Is this right?  Is there some way to bypass this and say "this is a
>> serious error, abort this scenario and jump to the next one" ???
>>
>> - Korny
>>
>> --
>> Kornelis Sietsma  korny at my surname dot com
>> kornys on gmail, twitter, facebook, etc.
>> "Every jumbled pile of person has a thinking part
>> that wonders what the part that isn't thinking
>> isn't thinking of"
>>
>
>
>
> --
> Kornelis Sietsma  korny at my surname dot com
> kornys on gmail, twitter, facebook, etc.
> "Every jumbled pile of person has a thinking part
> that wonders what the part that isn't thinking
> isn't thinking of"
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090313/c1344afd/attachment.html>

From lists at ruby-forum.com  Fri Mar 13 04:36:23 2009
From: lists at ruby-forum.com (Fedor Fomenko)
Date: Fri, 13 Mar 2009 09:36:23 +0100
Subject: [rspec-users] [cucumber] Using worlds for loading fixtures
Message-ID: <31334be57d0859e5dec60f7922acca91@ruby-forum.com>

What is the right place to load fixtures specific to a given scenario? I
was thinking of using Worlds. Is it the right place for loading/deleting
fixtures? How do I specify which world scenario should run in?
-- 
Posted via http://www.ruby-forum.com/.

From shingler at gmail.com  Fri Mar 13 04:42:12 2009
From: shingler at gmail.com (steven shingler)
Date: Fri, 13 Mar 2009 08:42:12 +0000
Subject: [rspec-users] profile format to give overall time...?
Message-ID: <c34dd07d0903130142l92827f7h33fdadf4a3e0e66a@mail.gmail.com>

Hi all,

How can I get cucumber to tell me how long my entire feature set has
taken to run?

(In the same way that RSpec does, for example)

I have taken a look at the profile formatter, which is very cool and
useful but doesn't give the overall time for the feature 'suite'.

I know that (on *nix) I can use the 'time' command, but it would be
cool to have something within cucumber itself.

Thanks a lot,
Steven

From aslak.hellesoy at gmail.com  Fri Mar 13 05:36:30 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Fri, 13 Mar 2009 10:36:30 +0100
Subject: [rspec-users] profile format to give overall time...?
In-Reply-To: <c34dd07d0903130142l92827f7h33fdadf4a3e0e66a@mail.gmail.com>
References: <c34dd07d0903130142l92827f7h33fdadf4a3e0e66a@mail.gmail.com>
Message-ID: <8d961d900903130236o7c059222qd5841f90f23685be@mail.gmail.com>

On Fri, Mar 13, 2009 at 9:42 AM, steven shingler <shingler at gmail.com> wrote:

> Hi all,
>
> How can I get cucumber to tell me how long my entire feature set has
> taken to run?
>

By submitting a feature request :-)

http://wiki.github.com/aslakhellesoy/cucumber/get-in-touch

Aslak


>
> (In the same way that RSpec does, for example)
>
> I have taken a look at the profile formatter, which is very cool and
> useful but doesn't give the overall time for the feature 'suite'.
>
> I know that (on *nix) I can use the 'time' command, but it would be
> cool to have something within cucumber itself.
>
> Thanks a lot,
> Steven
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090313/392eaab2/attachment.html>

From joe at josephwilk.net  Fri Mar 13 05:58:19 2009
From: joe at josephwilk.net (Joseph Wilk)
Date: Fri, 13 Mar 2009 09:58:19 +0000
Subject: [rspec-users] profile format to give overall time...?
In-Reply-To: <c34dd07d0903130142l92827f7h33fdadf4a3e0e66a@mail.gmail.com>
References: <c34dd07d0903130142l92827f7h33fdadf4a3e0e66a@mail.gmail.com>
Message-ID: <49BA2E3B.70400@josephwilk.net>

steven shingler wrote:
> Hi all,
>
> How can I get cucumber to tell me how long my entire feature set has
> taken to run?
>
> (In the same way that RSpec does, for example)
>
> I have taken a look at the profile formatter, which is very cool and
> useful but doesn't give the overall time for the feature 'suite'.
>
>   
You are quite right, the profile formatter should also give you an 
overall execution time.

Would you mind raising a ticket in lighthouse for this please?

http://rspec.lighthouseapp.com/projects/16211-cucumber/overview

It would also be useful I think to show the execution time in the pretty 
formatter in the same way that Rspec does.

Thanks

-- 
Joseph Wilk
http://blog.josephwilk.net


> I know that (on *nix) I can use the 'time' command, but it would be
> cool to have something within cucumber itself.
>
> Thanks a lot,
> Steven
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
>   



From shingler at gmail.com  Fri Mar 13 05:58:56 2009
From: shingler at gmail.com (steven shingler)
Date: Fri, 13 Mar 2009 09:58:56 +0000
Subject: [rspec-users] profile format to give overall time...?
In-Reply-To: <8d961d900903130236o7c059222qd5841f90f23685be@mail.gmail.com>
References: <c34dd07d0903130142l92827f7h33fdadf4a3e0e66a@mail.gmail.com>
	<8d961d900903130236o7c059222qd5841f90f23685be@mail.gmail.com>
Message-ID: <c34dd07d0903130258r5aadeca1i55276a939638f9fc@mail.gmail.com>

done!
Thanks,
Steven

On Fri, Mar 13, 2009 at 9:36 AM, aslak hellesoy
<aslak.hellesoy at gmail.com> wrote:
>
>
> On Fri, Mar 13, 2009 at 9:42 AM, steven shingler <shingler at gmail.com> wrote:
>>
>> Hi all,
>>
>> How can I get cucumber to tell me how long my entire feature set has
>> taken to run?
>
> By submitting a feature request :-)
>
> http://wiki.github.com/aslakhellesoy/cucumber/get-in-touch
>
> Aslak
>
>>
>> (In the same way that RSpec does, for example)
>>
>> I have taken a look at the profile formatter, which is very cool and
>> useful but doesn't give the overall time for the feature 'suite'.
>>
>> I know that (on *nix) I can use the 'time' command, but it would be
>> cool to have something within cucumber itself.
>>
>> Thanks a lot,
>> Steven
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From shingler at gmail.com  Fri Mar 13 06:10:10 2009
From: shingler at gmail.com (steven shingler)
Date: Fri, 13 Mar 2009 10:10:10 +0000
Subject: [rspec-users] profile format to give overall time...?
In-Reply-To: <49BA2E3B.70400@josephwilk.net>
References: <c34dd07d0903130142l92827f7h33fdadf4a3e0e66a@mail.gmail.com>
	<49BA2E3B.70400@josephwilk.net>
Message-ID: <c34dd07d0903130310q4e4f690fra883fbe168dfb67b@mail.gmail.com>

Have jotted a ticket here:

http://rspec.lighthouseapp.com/projects/16211/tickets/228-get-cucumber-to-tell-me-how-long-my-entire-feature-set-has-taken-to-run#ticket-228-1

Please edit accordingly :)


On Fri, Mar 13, 2009 at 9:58 AM, Joseph Wilk <joe at josephwilk.net> wrote:
> steven shingler wrote:
>>
>> Hi all,
>>
>> How can I get cucumber to tell me how long my entire feature set has
>> taken to run?
>>
>> (In the same way that RSpec does, for example)
>>
>> I have taken a look at the profile formatter, which is very cool and
>> useful but doesn't give the overall time for the feature 'suite'.
>>
>>
>
> You are quite right, the profile formatter should also give you an overall
> execution time.
>
> Would you mind raising a ticket in lighthouse for this please?
>
> http://rspec.lighthouseapp.com/projects/16211-cucumber/overview
>
> It would also be useful I think to show the execution time in the pretty
> formatter in the same way that Rspec does.
>
> Thanks
>
> --
> Joseph Wilk
> http://blog.josephwilk.net
>
>
>> I know that (on *nix) I can use the 'time' command, but it would be
>> cool to have something within cucumber itself.
>>
>> Thanks a lot,
>> Steven
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From joe at josephwilk.net  Fri Mar 13 06:11:42 2009
From: joe at josephwilk.net (Joseph Wilk)
Date: Fri, 13 Mar 2009 10:11:42 +0000
Subject: [rspec-users] [cucumber] Using worlds for loading fixtures
In-Reply-To: <31334be57d0859e5dec60f7922acca91@ruby-forum.com>
References: <31334be57d0859e5dec60f7922acca91@ruby-forum.com>
Message-ID: <49BA315E.4040600@josephwilk.net>

Fedor Fomenko wrote:
> What is the right place to load fixtures specific to a given scenario? I
> was thinking of using Worlds. Is it the right place for loading/deleting
> fixtures? How do I specify which world scenario should run in?
>   
There 3 options I can think of:

1. Background Feature
This allows you to specify specific set of  steps which are only run for 
the scenarios in the relevant feature 
(http://wiki.github.com/aslakhellesoy/cucumber/background). I would 
recommend this approach if you are using the latest cucumber version 
from github.

2, In the scenario
Are you hiding state setup which would be better placed in the plain 
text scenario? You don't have to get too granular with the data setup, a 
high level "Given the system is setup...." style could be used to avoid 
noise that detracts from the scenario value.

3. Before
If you do this in a Before you can gain access to the scenario name 
(http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/44). You 
could switch this to run the relevant fixture if you wish. (This is a 
bit smelly)

HTH

-- 
Joseph Wilk
http://blog.josephwilk.net


From pat.maddox at gmail.com  Fri Mar 13 06:37:43 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Fri, 13 Mar 2009 03:37:43 -0700
Subject: [rspec-users] [cucumber] Using worlds for loading fixtures
In-Reply-To: <49BA315E.4040600@josephwilk.net>
References: <31334be57d0859e5dec60f7922acca91@ruby-forum.com>
	<49BA315E.4040600@josephwilk.net>
Message-ID: <9DA4FE59-9FFE-4CE2-B428-C08B897617F6@gmail.com>

On Mar 13, 2009, at 3:11 AM, Joseph Wilk wrote:

> Fedor Fomenko wrote:
>> What is the right place to load fixtures specific to a given  
>> scenario? I
>> was thinking of using Worlds. Is it the right place for loading/ 
>> deleting
>> fixtures? How do I specify which world scenario should run in?
>>
> There 3 options I can think of:
>
> 1. Background Feature
> This allows you to specify specific set of  steps which are only run  
> for the scenarios in the relevant feature (http://wiki.github.com/aslakhellesoy/cucumber/background 
> ). I would recommend this approach if you are using the latest  
> cucumber version from github.

Makes sense if it applies to every scenario within a feature.


> 2, In the scenario
> Are you hiding state setup which would be better placed in the plain  
> text scenario? You don't have to get too granular with the data  
> setup, a high level "Given the system is setup...." style could be  
> used to avoid noise that detracts from the scenario value.

What I do 99% of the time.


> 3. Before
> If you do this in a Before you can gain access to the scenario name (http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/44 
> ). You could switch this to run the relevant fixture if you wish.  
> (This is a bit smelly)

You could clean it up: http://gist.github.com/78518  but it's still  
horrible :P

Pat

From apremdas at gmail.com  Fri Mar 13 06:50:00 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Fri, 13 Mar 2009 10:50:00 +0000
Subject: [rspec-users] [webrat] click link by title doesn't work
Message-ID: <88fd8ddc0903130350u3c51dc72u78089a7a49d12244@mail.gmail.com>

Webrat 0.4.2 doesn't seem to allow you to click links by title. Am I missing
something stupid?
With steps below running in sequence, first passes, second fails

Then /^I should see a view (\w+) details link$/ do |object|
  response.should have_tag("a[title=#{object}_details]")
end

When /^I follow view (\w+) details link$/ do |object|
  click_link "#{object}_details}"
end

I think click link should find by

- innerHTML, with simple &nbsp; handling
-  title
-  id
-  class

Does anyone have any contradictory opinions?

In the meantime I'll have a bash at writing a patch for this

Cheers

Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090313/4f7ae199/attachment.html>

From aslak.hellesoy at gmail.com  Fri Mar 13 07:17:48 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Fri, 13 Mar 2009 12:17:48 +0100
Subject: [rspec-users] [cucumber] Using worlds for loading fixtures
In-Reply-To: <9DA4FE59-9FFE-4CE2-B428-C08B897617F6@gmail.com>
References: <31334be57d0859e5dec60f7922acca91@ruby-forum.com>
	<49BA315E.4040600@josephwilk.net>
	<9DA4FE59-9FFE-4CE2-B428-C08B897617F6@gmail.com>
Message-ID: <8d961d900903130417p69198ab1ne1d6717227a7f545@mail.gmail.com>

On Fri, Mar 13, 2009 at 11:37 AM, Pat Maddox <pat.maddox at gmail.com> wrote:

> On Mar 13, 2009, at 3:11 AM, Joseph Wilk wrote:
>
>  Fedor Fomenko wrote:
>>
>>> What is the right place to load fixtures specific to a given scenario? I
>>> was thinking of using Worlds. Is it the right place for loading/deleting
>>> fixtures? How do I specify which world scenario should run in?
>>>
>>>  There 3 options I can think of:
>>
>> 1. Background Feature
>> This allows you to specify specific set of  steps which are only run for
>> the scenarios in the relevant feature (
>> http://wiki.github.com/aslakhellesoy/cucumber/background). I would
>> recommend this approach if you are using the latest cucumber version from
>> github.
>>
>
> Makes sense if it applies to every scenario within a feature.
>
>
>  2, In the scenario
>> Are you hiding state setup which would be better placed in the plain text
>> scenario? You don't have to get too granular with the data setup, a high
>> level "Given the system is setup...." style could be used to avoid noise
>> that detracts from the scenario value.
>>
>
> What I do 99% of the time.
>
>
>  3. Before
>> If you do this in a Before you can gain access to the scenario name (
>> http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/44). You
>> could switch this to run the relevant fixture if you wish. (This is a bit
>> smelly)
>>
>
> You could clean it up: http://gist.github.com/78518  but it's still
> horrible :P
>

How about this:
http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/229-use-hooks-with-tags

Aslak


>
> Pat
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090313/eeec3ae5/attachment.html>

From ashley.moran at patchspace.co.uk  Fri Mar 13 08:17:30 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Fri, 13 Mar 2009 12:17:30 +0000
Subject: [rspec-users] [rspec] be_something accepts nils
Message-ID: <EFB8A805-F2B1-4A55-AA5F-C798C3026394@patchspace.co.uk>

Hi

Just noticed that the behaviour of

   @cow.should_not be_hungry

is not the same as

   @cow.hungry?.should == false # nil also passes

Don't know how this has escaped me for so long =)

What's the thinking behind this?  You can already do

   @cow.hungry?.should(_not) be_nil

so surely it makes more sense for be_true and be_false to check for  
booleans?

Ashley


-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From dchelimsky at gmail.com  Fri Mar 13 09:24:36 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 13 Mar 2009 08:24:36 -0500
Subject: [rspec-users] [Proposal] deprecate context() at the top level
Message-ID: <57c63afe0903130624h2f7e3f5asc72af52a056a5490@mail.gmail.com>

Hi all,

There are two tickets in lighthouse that point to problems with the
use of context() in RSpec:

* conflict with JRuby:

http://rspec.lighthouseapp.com/projects/5645/tickets/728

* request context() be deprecated

http://rspec.lighthouseapp.com/projects/5645/tickets/713

As there are a lot of people (and libraries) that mix and match
describe() and context(), I don't plan to simply remove it. However, a
couple of suggestions have come up that I'm considering. Here's the
proposal.

== deprecate and eventually remove context() ONLY AT THE TOP LEVEL

In my personal use, and from what I've seen in other libraries that
are driven with RSpec, this is the common use of context():

  describe "Something" do
    context "in some context" do

You would *still be able to do that*, but you would *not be able to do this*:

  context "Something" do
    context "in some context" do

==

I'd like to know if you think removing context a the top level will
create conflicts with your code or libraries you use. Please comment
in http://rspec.lighthouseapp.com/projects/5645/tickets/713 instead of
here - I'd like to keep the conversation in one place, if possible.

Thanks for playing,
David

From levy at levycarneiro.com  Fri Mar 13 10:04:30 2009
From: levy at levycarneiro.com (Levy Carneiro Jr.)
Date: Fri, 13 Mar 2009 11:04:30 -0300
Subject: [rspec-users] Spec'ing chained calls
Message-ID: <fca2ab280903130704h3733d6ecg9afcf6d78edfc52f@mail.gmail.com>

Hello!

I'm trying to spec a method, that has several chained calls.

http://gist.github.com/78562 (spec)
http://gist.github.com/78563 (model)

In the first spec, I'm trying to focus on the method calls that have to be
made, and the arguments they should receive.

Is there a better way to spec the behaviour for these chained calls? It just
seems too many lines to me :)


Thanks a lot!
Levy
PS: I'm using my branch of the twitter gem, at
http://github.com/levycarneiro/twitter, which just adds this method
'not_retweeted'.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090313/0a68960f/attachment.html>

From lists at ruby-forum.com  Fri Mar 13 10:12:36 2009
From: lists at ruby-forum.com (James Byrne)
Date: Fri, 13 Mar 2009 15:12:36 +0100
Subject: [rspec-users] profile format to give overall time...?
In-Reply-To: <c34dd07d0903130142l92827f7h33fdadf4a3e0e66a@mail.gmail.com>
References: <c34dd07d0903130142l92827f7h33fdadf4a3e0e66a@mail.gmail.com>
Message-ID: <1c97c60752f6ac68794ddf1cdd4799b7@ruby-forum.com>

Steven Shingler wrote:
> Hi all,
> 
> How can I get cucumber to tell me how long my entire feature set has
> taken to run?
> 

$ time rake features
...

29 scenarios
165 steps passed
4 steps failed
10 steps skipped
rake aborted!
Command failed with status (1): [/usr/bin/ruby -I 
"/usr/lib64/ruby/gems/1.8...]

(See full trace by running task with --trace)

real    3m9.355s
user    2m30.589s
sys     0m37.730s
-- 
Posted via http://www.ruby-forum.com/.

From oli.azevedo.barnes at gmail.com  Fri Mar 13 10:22:00 2009
From: oli.azevedo.barnes at gmail.com (Oliver Barnes)
Date: Fri, 13 Mar 2009 11:22:00 -0300
Subject: [rspec-users] [cucumber] open source projects with cucumber
	features
In-Reply-To: <F18C5860-2A71-4124-8116-8841C33E2C8C@mattwynne.net>
References: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
	<85d99afe0903111246x33b4a028r499253683fcf25c5@mail.gmail.com>
	<F18C5860-2A71-4124-8116-8841C33E2C8C@mattwynne.net>
Message-ID: <6466d9040903130722k5c9a4806x954306a1d1f71f94@mail.gmail.com>

I'm looking for feature examples for web apps, I imagine Balint is as well?

2009/3/11 Matt Wynne <matt at mattwynne.net>:
>
> On 11 Mar 2009, at 19:46, Zach Dennis wrote:
>
>> On Wed, Mar 11, 2009 at 3:03 PM, Balint Erdi <lists at ruby-forum.com> wrote:
>>>
>>> Hi,
>>>
>>> I was looking for some "real-world" cucumber features (mainly on github)
>>> to see how more complex features are built but I have not really found
>>> any. Could you point me to some?
>
> What kind of app are you looking to build? Website? GUI? Console?
>
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From mark at mwilden.com  Fri Mar 13 10:23:06 2009
From: mark at mwilden.com (Mark Wilden)
Date: Fri, 13 Mar 2009 07:23:06 -0700
Subject: [rspec-users] [rspec] be_something accepts nils
In-Reply-To: <EFB8A805-F2B1-4A55-AA5F-C798C3026394@patchspace.co.uk>
References: <EFB8A805-F2B1-4A55-AA5F-C798C3026394@patchspace.co.uk>
Message-ID: <3c30da400903130723v329c03e7n3f972db59e9d35ee@mail.gmail.com>

On Fri, Mar 13, 2009 at 5:17 AM, Ashley Moran >
> Just noticed that the behaviour of
>
> ?@cow.should_not be_hungry
>
> is not the same as
>
> ?@cow.hungry?.should == false # nil also passes
>
> Don't know how this has escaped me for so long =)
>
> What's the thinking behind this? ?You can already do
>
> ?@cow.hungry?.should(_not) be_nil
>
> so surely it makes more sense for be_true and be_false to check for
> booleans?

In common Ruby use, nil is usually treated the same as false, so
that's the way the dynamic matcher works - it's the most convenent.

You see explicit comparisons against true or false pretty rarely (in
my experience). Unless you have a specific need for a three-valued
truth system (e.g., true, false, and unknown), I think it's best
practice not to assume that if !x == true, then x must == false, and
vice versa.

///ark

From cflipse at gmail.com  Fri Mar 13 10:25:14 2009
From: cflipse at gmail.com (Chris Flipse)
Date: Fri, 13 Mar 2009 10:25:14 -0400
Subject: [rspec-users] Spec'ing chained calls
In-Reply-To: <fca2ab280903130704h3733d6ecg9afcf6d78edfc52f@mail.gmail.com>
References: <fca2ab280903130704h3733d6ecg9afcf6d78edfc52f@mail.gmail.com>
Message-ID: <e3e91d130903130725ob1c450avb3fd5c35e1ba1ec0@mail.gmail.com>

You might want to look into using a null object, and breaking that first
spec up into several examples
(a null object returns itself when sent a message it doesn't know how to
handle)


http://gist.github.com/78570

I've built more than a few named_scope chains using this pattern, and it
seems to work out okay.  This approach is somewhat less brittle, in that
it's not going to explode horribly if you change the order of the chain in
the main method (if something else reads better, say) ...

Downside is that it _won't_ catch if you add new methods to the chain.  If
that's a concern, you could complicate the setup a bit, to narrow the focus
to _just_ the methods you want.

     @new_search = mock(Twitter::Search)
     new_search.stub!(:containing => new_search, :since => new_search,
:not_retweeted => new_search, :fetch => new_search)


On Fri, Mar 13, 2009 at 10:04 AM, Levy Carneiro Jr.
<levy at levycarneiro.com>wrote:

> Hello!
>
> I'm trying to spec a method, that has several chained calls.
>
> http://gist.github.com/78562 (spec)
> http://gist.github.com/78563 (model)
>
> In the first spec, I'm trying to focus on the method calls that have to be
> made, and the arguments they should receive.
>
> Is there a better way to spec the behaviour for these chained calls? It
> just seems too many lines to me :)
>
>
> Thanks a lot!
> Levy
> PS: I'm using my branch of the twitter gem, at
> http://github.com/levycarneiro/twitter, which just adds this method
> 'not_retweeted'.
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
// anything worth taking seriously is worth making fun of
// http://blog.devcaffeine.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090313/37e54696/attachment.html>

From scott at railsnewbie.com  Fri Mar 13 10:59:14 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Fri, 13 Mar 2009 10:59:14 -0400
Subject: [rspec-users] Spec'ing chained calls
In-Reply-To: <fca2ab280903130704h3733d6ecg9afcf6d78edfc52f@mail.gmail.com>
References: <fca2ab280903130704h3733d6ecg9afcf6d78edfc52f@mail.gmail.com>
Message-ID: <49BA74C2.1060403@railsnewbie.com>

Levy Carneiro Jr. wrote:
> Hello!
>
> I'm trying to spec a method, that has several chained calls.
>
> http://gist.github.com/78562 (spec)
> http://gist.github.com/78563 (model)
>
> In the first spec, I'm trying to focus on the method calls that have 
> to be made, and the arguments they should receive.
>
> Is there a better way to spec the behaviour for these chained calls? 
> It just seems too many lines to me :)


http://c2.com/cgi/wiki?LawOfDemeter

Specs are as much of a design tool as a testing tool, and the use of 
mocks in your specs show just how ugly the current design is.

Either write a wrapper around the library which takes care of the method 
chaining, or write integration tests against it, stubbing out some low 
level detail of the library.

Scott


>
>
> Thanks a lot!
> Levy
> PS: I'm using my branch of the twitter gem, at 
> http://github.com/levycarneiro/twitter, which just adds this method 
> 'not_retweeted'.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From matt at mattwynne.net  Fri Mar 13 11:07:32 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Fri, 13 Mar 2009 15:07:32 +0000
Subject: [rspec-users] How do you use pending in RSpec?
In-Reply-To: <3b8d0de60903121623xd68a81aj483a54fafab28c3f@mail.gmail.com>
References: <3b8d0de60903121450t457368edg1f803dbddd512fa3@mail.gmail.com>
	<8d961d900903121505t565eafa4yea53f38e2a00befb@mail.gmail.com>
	<3b8d0de60903121623xd68a81aj483a54fafab28c3f@mail.gmail.com>
Message-ID: <9DDFC84E-CA8A-4AF7-921D-64D59C4573AA@mattwynne.net>


On 12 Mar 2009, at 23:23, Bill Venners wrote:

> I guess I'm curious:
>
> 1) How important is it to you to be able to just "strike out" the
> lines of code within an example that are failing (as you can with
> RSpec's #3 pending form), versus just "striking out" the entire
> example as you can with ignore in ScalaTest.

I don't personally ever strike out parts of an example - all or nothing

> 2) How important is it to you to be able to add a string message to
> your stricken code, as you can with either #2 or #3 in RSpec? How does
> that string help you?

Very important - it's like a TODO.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From shingler at gmail.com  Fri Mar 13 11:19:11 2009
From: shingler at gmail.com (steven shingler)
Date: Fri, 13 Mar 2009 15:19:11 +0000
Subject: [rspec-users] profile format to give overall time...?
In-Reply-To: <1c97c60752f6ac68794ddf1cdd4799b7@ruby-forum.com>
References: <c34dd07d0903130142l92827f7h33fdadf4a3e0e66a@mail.gmail.com>
	<1c97c60752f6ac68794ddf1cdd4799b7@ruby-forum.com>
Message-ID: <c34dd07d0903130819m5a0d9ef5n59484cbbf4a75bc8@mail.gmail.com>

Hi James,

Yep, I mentioned the time command in my original post, I'm looking for
a within-cucumber option. :)

Thanks,

Steven

On Fri, Mar 13, 2009 at 2:12 PM, James Byrne <lists at ruby-forum.com> wrote:
> Steven Shingler wrote:
>> Hi all,
>>
>> How can I get cucumber to tell me how long my entire feature set has
>> taken to run?
>>
>
> $ time rake features
> ...
>
> 29 scenarios
> 165 steps passed
> 4 steps failed
> 10 steps skipped
> rake aborted!
> Command failed with status (1): [/usr/bin/ruby -I
> "/usr/lib64/ruby/gems/1.8...]
>
> (See full trace by running task with --trace)
>
> real ? ?3m9.355s
> user ? ?2m30.589s
> sys ? ? 0m37.730s
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From aslak.hellesoy at gmail.com  Fri Mar 13 11:38:08 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Fri, 13 Mar 2009 16:38:08 +0100
Subject: [rspec-users] [cucumber] open source projects with cucumber
	features
In-Reply-To: <6466d9040903130722k5c9a4806x954306a1d1f71f94@mail.gmail.com>
References: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
	<85d99afe0903111246x33b4a028r499253683fcf25c5@mail.gmail.com>
	<F18C5860-2A71-4124-8116-8841C33E2C8C@mattwynne.net>
	<6466d9040903130722k5c9a4806x954306a1d1f71f94@mail.gmail.com>
Message-ID: <8d961d900903130838v6827195fp378301449b04b0a0@mail.gmail.com>

On Fri, Mar 13, 2009 at 3:22 PM, Oliver Barnes <oli.azevedo.barnes at gmail.com
> wrote:

> I'm looking for feature examples for web apps, I imagine Balint is as well?
>

What kind of webapp? Merb? JEE? Rails? Sinatra? ASP.NET? PHP? other?

Aslak


>
> 2009/3/11 Matt Wynne <matt at mattwynne.net>:
> >
> > On 11 Mar 2009, at 19:46, Zach Dennis wrote:
> >
> >> On Wed, Mar 11, 2009 at 3:03 PM, Balint Erdi <lists at ruby-forum.com>
> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I was looking for some "real-world" cucumber features (mainly on
> github)
> >>> to see how more complex features are built but I have not really found
> >>> any. Could you point me to some?
> >
> > What kind of app are you looking to build? Website? GUI? Console?
> >
> > Matt Wynne
> > http://blog.mattwynne.net
> > http://www.songkick.com
> >
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090313/1b4de558/attachment-0001.html>

From pat.maddox at gmail.com  Fri Mar 13 11:42:19 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Fri, 13 Mar 2009 08:42:19 -0700
Subject: [rspec-users] [rspec] be_something accepts nils
In-Reply-To: <EFB8A805-F2B1-4A55-AA5F-C798C3026394@patchspace.co.uk>
References: <EFB8A805-F2B1-4A55-AA5F-C798C3026394@patchspace.co.uk>
Message-ID: <6502C3C2-7404-49D1-8370-8E5E8F8CDE28@gmail.com>

On Mar 13, 2009, at 5:17 AM, Ashley Moran wrote:

> Hi
>
> Just noticed that the behaviour of
>
>  @cow.should_not be_hungry
>
> is not the same as
>
>  @cow.hungry?.should == false # nil also passes
>
> Don't know how this has escaped me for so long =)
>
> What's the thinking behind this?  You can already do
>
>  @cow.hungry?.should(_not) be_nil
>
> so surely it makes more sense for be_true and be_false to check for  
> booleans?

be_true and be_false do check for booleans :)  but you didn't use  
either of them.

The expanded form of
@cow.should_not be_hungry
is
@cow.hungry?.should_not be

Pat

From bill at artima.com  Fri Mar 13 12:07:52 2009
From: bill at artima.com (Bill Venners)
Date: Fri, 13 Mar 2009 09:07:52 -0700
Subject: [rspec-users] How do you use pending in RSpec?
In-Reply-To: <9DDFC84E-CA8A-4AF7-921D-64D59C4573AA@mattwynne.net>
References: <3b8d0de60903121450t457368edg1f803dbddd512fa3@mail.gmail.com>
	<8d961d900903121505t565eafa4yea53f38e2a00befb@mail.gmail.com>
	<3b8d0de60903121623xd68a81aj483a54fafab28c3f@mail.gmail.com>
	<9DDFC84E-CA8A-4AF7-921D-64D59C4573AA@mattwynne.net>
Message-ID: <3b8d0de60903130907p3e11fa92nb2057b8b6443b934@mail.gmail.com>

Hi Matt and others,

Thanks for your replies. I think I've settled on just using two of
RSpec's pending forms in ScalaTest. If you want to write out a few
spec texts before writing the examples, you'd put pending in parens
where you'd normally put the block of example code:

it("should do something") (pending)

it("should do something else") (pending)

If something breaks during refactoring, you can either ignore the
whole thing by changing it to ignore like this (which already is
supported):

ignore("should do something") {
  // ...
}

Or by puttting a pending with a string inside the example block of code:

it("should do something") {
  // ...
  pending("this won't start working again until I...")
  // ...
}

But I'll leave out the pending form that takes a block.

I appreciate the feedback.

Thanks.

Bill


On Fri, Mar 13, 2009 at 8:07 AM, Matt Wynne <matt at mattwynne.net> wrote:
>
> On 12 Mar 2009, at 23:23, Bill Venners wrote:
>
>> I guess I'm curious:
>>
>> 1) How important is it to you to be able to just "strike out" the
>> lines of code within an example that are failing (as you can with
>> RSpec's #3 pending form), versus just "striking out" the entire
>> example as you can with ignore in ScalaTest.
>
> I don't personally ever strike out parts of an example - all or nothing
>
>> 2) How important is it to you to be able to add a string message to
>> your stricken code, as you can with either #2 or #3 in RSpec? How does
>> that string help you?
>
> Very important - it's like a TODO.
>
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From matt at mattwynne.net  Fri Mar 13 12:34:33 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Fri, 13 Mar 2009 16:34:33 +0000
Subject: [rspec-users] [rspec] be_something accepts nils
In-Reply-To: <6502C3C2-7404-49D1-8370-8E5E8F8CDE28@gmail.com>
References: <EFB8A805-F2B1-4A55-AA5F-C798C3026394@patchspace.co.uk>
	<6502C3C2-7404-49D1-8370-8E5E8F8CDE28@gmail.com>
Message-ID: <A4C40305-6A92-455A-9C32-8070B729966E@mattwynne.net>


On 13 Mar 2009, at 15:42, Pat Maddox wrote:

> On Mar 13, 2009, at 5:17 AM, Ashley Moran wrote:
>
>> Hi
>>
>> Just noticed that the behaviour of
>>
>> @cow.should_not be_hungry
>>
>> is not the same as
>>
>> @cow.hungry?.should == false # nil also passes
>>
>> Don't know how this has escaped me for so long =)
>>
>> What's the thinking behind this?  You can already do
>>
>> @cow.hungry?.should(_not) be_nil
>>
>> so surely it makes more sense for be_true and be_false to check for  
>> booleans?
>
> be_true and be_false do check for booleans :)  but you didn't use  
> either of them.
>
> The expanded form of
> @cow.should_not be_hungry
> is
> @cow.hungry?.should_not be
>
> Pat

Like yoda sounds, that does


Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From oli.azevedo.barnes at gmail.com  Fri Mar 13 14:13:01 2009
From: oli.azevedo.barnes at gmail.com (Oliver Barnes)
Date: Fri, 13 Mar 2009 15:13:01 -0300
Subject: [rspec-users] [cucumber] open source projects with cucumber
	features
In-Reply-To: <8d961d900903130838v6827195fp378301449b04b0a0@mail.gmail.com>
References: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
	<85d99afe0903111246x33b4a028r499253683fcf25c5@mail.gmail.com>
	<F18C5860-2A71-4124-8116-8841C33E2C8C@mattwynne.net>
	<6466d9040903130722k5c9a4806x954306a1d1f71f94@mail.gmail.com>
	<8d961d900903130838v6827195fp378301449b04b0a0@mail.gmail.com>
Message-ID: <6466d9040903131113h5183e55cwa87cc4a22a7519d@mail.gmail.com>

Rails, but any other would be helpful as well, really.

Just a repo of varied real-world cucumber feature examples already
would help a lot, even without the feature steps or an actual
developed app. I've been mining samples from pasties, tutorials and
from github, but have found only a few scattered (and several
theoretical), and have not found a more evolved and cohesive set.

I'm working on a real project using cucumber right now, and though I
think I understand the principles shown on the rspec book and the
cucumber wiki, as well as on the discussions here, at times I've
gotten stuck in writing features with my client, without patterns to
draw from.

2009/3/13 aslak hellesoy <aslak.hellesoy at gmail.com>:
>
>
> On Fri, Mar 13, 2009 at 3:22 PM, Oliver Barnes
> <oli.azevedo.barnes at gmail.com> wrote:
>>
>> I'm looking for feature examples for web apps, I imagine Balint is as
>> well?
>
> What kind of webapp? Merb? JEE? Rails? Sinatra? ASP.NET? PHP? other?
>
> Aslak
>
>>
>> 2009/3/11 Matt Wynne <matt at mattwynne.net>:
>> >
>> > On 11 Mar 2009, at 19:46, Zach Dennis wrote:
>> >
>> >> On Wed, Mar 11, 2009 at 3:03 PM, Balint Erdi <lists at ruby-forum.com>
>> >> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> I was looking for some "real-world" cucumber features (mainly on
>> >>> github)
>> >>> to see how more complex features are built but I have not really found
>> >>> any. Could you point me to some?
>> >
>> > What kind of app are you looking to build? Website? GUI? Console?
>> >
>> > Matt Wynne
>> > http://blog.mattwynne.net
>> > http://www.songkick.com
>> >
>> > _______________________________________________
>> > rspec-users mailing list
>> > rspec-users at rubyforge.org
>> > http://rubyforge.org/mailman/listinfo/rspec-users
>> >
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
>
> --
> Aslak (::)
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From aslak.hellesoy at gmail.com  Fri Mar 13 15:05:39 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Fri, 13 Mar 2009 20:05:39 +0100
Subject: [rspec-users] [cucumber] open source projects with cucumber
	features
In-Reply-To: <6466d9040903131113h5183e55cwa87cc4a22a7519d@mail.gmail.com>
References: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
	<85d99afe0903111246x33b4a028r499253683fcf25c5@mail.gmail.com>
	<F18C5860-2A71-4124-8116-8841C33E2C8C@mattwynne.net>
	<6466d9040903130722k5c9a4806x954306a1d1f71f94@mail.gmail.com>
	<8d961d900903130838v6827195fp378301449b04b0a0@mail.gmail.com>
	<6466d9040903131113h5183e55cwa87cc4a22a7519d@mail.gmail.com>
Message-ID: <8d961d900903131205h77f0ed1fxdf7a55c8fd74f0c@mail.gmail.com>

On Fri, Mar 13, 2009 at 7:13 PM, Oliver Barnes <oli.azevedo.barnes at gmail.com
> wrote:

> Rails, but any other would be helpful as well, really.
>
> Just a repo of varied real-world cucumber feature examples already
> would help a lot, even without the feature steps or an actual
> developed app. I've been mining samples from pasties, tutorials and
> from github, but have found only a few scattered (and several
> theoretical), and have not found a more evolved and cohesive set.
>

Here is an application some of my colleagues have developed:
http://github.com/bekkopen/kompetansesok/tree/master

It's in Norwegian, and not the simplest app in the world (not the most
complex either). The live version is here:
http://kompetansesok.demo.bekk.no/

Hopefully someone with an English app can share....


>
> I'm working on a real project using cucumber right now, and though I
> think I understand the principles shown on the rspec book and the
> cucumber wiki, as well as on the discussions here, at times I've
> gotten stuck in writing features with my client, without patterns to
> draw from.
>
> 2009/3/13 aslak hellesoy <aslak.hellesoy at gmail.com>:
> >
> >
> > On Fri, Mar 13, 2009 at 3:22 PM, Oliver Barnes
> > <oli.azevedo.barnes at gmail.com> wrote:
> >>
> >> I'm looking for feature examples for web apps, I imagine Balint is as
> >> well?
> >
> > What kind of webapp? Merb? JEE? Rails? Sinatra? ASP.NET? PHP? other?
> >
> > Aslak
> >
> >>
> >> 2009/3/11 Matt Wynne <matt at mattwynne.net>:
> >> >
> >> > On 11 Mar 2009, at 19:46, Zach Dennis wrote:
> >> >
> >> >> On Wed, Mar 11, 2009 at 3:03 PM, Balint Erdi <lists at ruby-forum.com>
> >> >> wrote:
> >> >>>
> >> >>> Hi,
> >> >>>
> >> >>> I was looking for some "real-world" cucumber features (mainly on
> >> >>> github)
> >> >>> to see how more complex features are built but I have not really
> found
> >> >>> any. Could you point me to some?
> >> >
> >> > What kind of app are you looking to build? Website? GUI? Console?
> >> >
> >> > Matt Wynne
> >> > http://blog.mattwynne.net
> >> > http://www.songkick.com
> >> >
> >> > _______________________________________________
> >> > rspec-users mailing list
> >> > rspec-users at rubyforge.org
> >> > http://rubyforge.org/mailman/listinfo/rspec-users
> >> >
> >> _______________________________________________
> >> rspec-users mailing list
> >> rspec-users at rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/rspec-users
> >
> >
> >
> > --
> > Aslak (::)
> >
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090313/b19a26d9/attachment.html>

From ashley.moran at patchspace.co.uk  Fri Mar 13 16:29:36 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Fri, 13 Mar 2009 20:29:36 +0000
Subject: [rspec-users] [rspec] be_something accepts nils
In-Reply-To: <A4C40305-6A92-455A-9C32-8070B729966E@mattwynne.net>
References: <EFB8A805-F2B1-4A55-AA5F-C798C3026394@patchspace.co.uk>
	<6502C3C2-7404-49D1-8370-8E5E8F8CDE28@gmail.com>
	<A4C40305-6A92-455A-9C32-8070B729966E@mattwynne.net>
Message-ID: <A603DA7E-C502-4369-B98D-14ED186FA27D@patchspace.co.uk>


On 13 Mar 2009, at 16:34, Matt Wynne wrote:

>> The expanded form of
>> @cow.should_not be_hungry
>> is
>> @cow.hungry?.should_not be
>>
>> Pat
>
> Like yoda sounds, that does

And enlightened, I am =)

Thanks Pat

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From THart at picagroup.com  Fri Mar 13 17:28:53 2009
From: THart at picagroup.com (Tim Hart)
Date: Fri, 13 Mar 2009 16:28:53 -0500
Subject: [rspec-users] Cucumber - Adding a step definition
Message-ID: <C5E03A45.DAC5%THart@picagroup.com>

List,

Quick question about Cucumber/Gherkin.

I'm considering adding 'With' as a step definition to support scenarios like:

Given a policy
With a PCF practice state
And a secondary risk
...

I'm fairly new to ruby - but I can't quite get this one figured out. I've tried adding

Cucumber.alias_steps (['With'])

To my features/support/env.rb file, but when I run cucumber, I still get a Syntax error. It looks like my 'with' never gets added to the original list.

Suggestions?
--
Tim Hart
Senior Software Engineer
PICA Group
615-713-9956 :cell
timothyjhart :Y!
tjhart at me.com :AIM

*****************************************************************************

Disclaimer: This electronic message may contain information that is Confidential or legally privileged. It is intended only for the use of the individual(s) and entity named in the message. If you are not an intended recipient of this message, please notify the sender immediately and delete the material from your computer. Do not deliver, distribute or copy this message and do not disclose its contents or take any action in reliance on the information it contains.

*****************************************************************************



From aslak.hellesoy at gmail.com  Fri Mar 13 17:47:05 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Fri, 13 Mar 2009 22:47:05 +0100
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <C5E03A45.DAC5%THart@picagroup.com>
References: <C5E03A45.DAC5%THart@picagroup.com>
Message-ID: <8d961d900903131447r32b3d470i7755dc0dafafedeb@mail.gmail.com>

On Fri, Mar 13, 2009 at 10:28 PM, Tim Hart <THart at picagroup.com> wrote:

> List,
>
> Quick question about Cucumber/Gherkin.
>
> I'm considering adding 'With' as a step definition to support scenarios
> like:
>
> Given a policy
> With a PCF practice state
> And a secondary risk
> ...
>
> I'm fairly new to ruby - but I can't quite get this one figured out. I've
> tried adding
>
> Cucumber.alias_steps (['With'])
>
> To my features/support/env.rb file, but when I run cucumber, I still get a
> Syntax error. It looks like my 'with' never gets added to the original list.
>

Unfortunately, this only aliases the ruby methods (this will let you call
With /some step/ do..end in a step definition ruby file.
In order to make the plain text parser recognise other words, a change is
needed in languages.yml.

If you add a feature request in Lighthouse I'll see if I can add it.

Cheers,
Aslak


>
> Suggestions?
> --
> Tim Hart
> Senior Software Engineer
> PICA Group
> 615-713-9956 :cell
> timothyjhart :Y!
> tjhart at me.com :AIM
>
>
> *****************************************************************************
>
> Disclaimer: This electronic message may contain information that is
> Confidential or legally privileged. It is intended only for the use of the
> individual(s) and entity named in the message. If you are not an intended
> recipient of this message, please notify the sender immediately and delete
> the material from your computer. Do not deliver, distribute or copy this
> message and do not disclose its contents or take any action in reliance on
> the information it contains.
>
>
> *****************************************************************************
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090313/642a4949/attachment.html>

From luke at lukemelia.com  Sat Mar 14 02:00:21 2009
From: luke at lukemelia.com (Luke Melia)
Date: Sat, 14 Mar 2009 02:00:21 -0400
Subject: [rspec-users] [cucumber] Performance of 0.1.99?
Message-ID: <6E256357-075E-4082-90B4-5E0253B51518@lukemelia.com>

Has anyone noticed a slowdown in performance of their cucumber suite  
from 0.1 to 0.2alpha?

I haven't ruled out something in our suite itself, but the slowdown  
appeared to occur concurrently with our upgrade to 0.2alpha.

Cheers,
Luke
--
Luke Melia
luke at lukemelia.com
http://www.lukemelia.com/


From aslak.hellesoy at gmail.com  Sat Mar 14 06:06:03 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Sat, 14 Mar 2009 11:06:03 +0100
Subject: [rspec-users] [cucumber] Performance of 0.1.99?
In-Reply-To: <6E256357-075E-4082-90B4-5E0253B51518@lukemelia.com>
References: <6E256357-075E-4082-90B4-5E0253B51518@lukemelia.com>
Message-ID: <8d961d900903140306v523fb22em127f568bb6f25e47@mail.gmail.com>

On Sat, Mar 14, 2009 at 7:00 AM, Luke Melia <luke at lukemelia.com> wrote:

> Has anyone noticed a slowdown in performance of their cucumber suite from
> 0.1 to 0.2alpha?
>
> I haven't ruled out something in our suite itself, but the slowdown
> appeared to occur concurrently with our upgrade to 0.2alpha.
>

I haven't noticed anything. Do you want to create a benchmark?

Aslak


>
> Cheers,
> Luke
> --
> Luke Melia
> luke at lukemelia.com
> http://www.lukemelia.com/
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090314/58b87e7f/attachment.html>

From zuperinfinite at gmail.com  Sat Mar 14 06:27:37 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Sat, 14 Mar 2009 11:27:37 +0100
Subject: [rspec-users] stubbing Time.zone.now for model tests fails for
	Rails 2.3.1
In-Reply-To: <1fb4df0903112022t442ac3exee3bbbd9de2d1472@mail.gmail.com>
References: <5D52D0F4-0223-4C74-8215-2CAEB90FC993@tower-mt.com>
	<1fb4df0903112022t442ac3exee3bbbd9de2d1472@mail.gmail.com>
Message-ID: <B8BCE3D7-E167-4AD6-B3B3-03DFDB39B0B5@gmail.com>


On 12 mrt 2009, at 04:22, Stephen Eley wrote:

> On Wed, Mar 11, 2009 at 1:40 PM, David Schmidt <davids at tower-mt.com>  
> wrote:
>>
>> Has anyone else run into this problem and come up with a solution  
>> to getting
>> a fixed time back from Time.zone.now?
>
> This plugin has worked very well for me:
> http://github.com/notahat/time_travel/tree/master

Great! This is exactly what I need for a project I'm working on.
However, I need to run all my tests on a specific date. I'm doing  
stuff which is week-based, so "Tomorrow" and "Next week" are always  
different, and therefore I'd like to set it to a specific date for all  
my tests.
Any idea how to hook this into a Before-hook in Cucumber perhaps?

thanks,
bartz

From zuperinfinite at gmail.com  Sat Mar 14 07:01:11 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Sat, 14 Mar 2009 12:01:11 +0100
Subject: [rspec-users] stubbing Time.zone.now for model tests fails for
	Rails 2.3.1
In-Reply-To: <B8BCE3D7-E167-4AD6-B3B3-03DFDB39B0B5@gmail.com>
References: <5D52D0F4-0223-4C74-8215-2CAEB90FC993@tower-mt.com>
	<1fb4df0903112022t442ac3exee3bbbd9de2d1472@mail.gmail.com>
	<B8BCE3D7-E167-4AD6-B3B3-03DFDB39B0B5@gmail.com>
Message-ID: <FAA7A626-452E-4D0C-B4B2-1956DE55F50D@gmail.com>


On 14 mrt 2009, at 11:27, Bart Zonneveld wrote:

>
> On 12 mrt 2009, at 04:22, Stephen Eley wrote:
>
>> On Wed, Mar 11, 2009 at 1:40 PM, David Schmidt <davids at tower- 
>> mt.com> wrote:
>>>
>>> Has anyone else run into this problem and come up with a solution  
>>> to getting
>>> a fixed time back from Time.zone.now?
>>
>> This plugin has worked very well for me:
>> http://github.com/notahat/time_travel/tree/master
>
> Great! This is exactly what I need for a project I'm working on.
> However, I need to run all my tests on a specific date. I'm doing  
> stuff which is week-based, so "Tomorrow" and "Next week" are always  
> different, and therefore I'd like to set it to a specific date for  
> all my tests.
> Any idea how to hook this into a Before-hook in Cucumber perhaps?

While I was doing the dishes, I came up with the following:

World do |world|
   at_time(Time.utc(2009,1,1)) do
     world
   end
end

Unfortunately, this doesn't work :(...
Any ideas?

thanks a bunch,
bartz


From matt at mattwynne.net  Sat Mar 14 08:59:27 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Sat, 14 Mar 2009 12:59:27 +0000
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <8d961d900903131447r32b3d470i7755dc0dafafedeb@mail.gmail.com>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<8d961d900903131447r32b3d470i7755dc0dafafedeb@mail.gmail.com>
Message-ID: <B039C405-AF4A-4D6C-95AA-835E4BAEBDF6@mattwynne.net>


On 13 Mar 2009, at 21:47, aslak hellesoy wrote:

>
>
> On Fri, Mar 13, 2009 at 10:28 PM, Tim Hart <THart at picagroup.com>  
> wrote:
> List,
>
> Quick question about Cucumber/Gherkin.
>
> I'm considering adding 'With' as a step definition to support  
> scenarios like:
>
> Given a policy
> With a PCF practice state
> And a secondary risk
> ...
>
> I'm fairly new to ruby - but I can't quite get this one figured out.  
> I've tried adding
>
> Cucumber.alias_steps (['With'])
>
> To my features/support/env.rb file, but when I run cucumber, I still  
> get a Syntax error. It looks like my 'with' never gets added to the  
> original list.
>
> Unfortunately, this only aliases the ruby methods (this will let you  
> call With /some step/ do..end in a step definition ruby file.
> In order to make the plain text parser recognise other words, a  
> change is needed in languages.yml.
>
> If you add a feature request in Lighthouse I'll see if I can add it.

I'm not sure if I like this - dependency between steps seems like a  
dodgy road to go down.

When you're in a step definition, how would you know what object the  
'With' was referring to?

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From lists at ruby-forum.com  Sat Mar 14 09:12:42 2009
From: lists at ruby-forum.com (Zhenning Guan)
Date: Sat, 14 Mar 2009 14:12:42 +0100
Subject: [rspec-users] how to test this view with Rspec
Message-ID: <160c24b9652a985b669f8cd85c98925e@ruby-forum.com>

= flash_messages
- @user = User.find(1)
- if current_user == @user
  %new_forum= link_to 'new forum', new_forum_path

- @forum.each do |f|
  .group
    = link_to f.name, forum_path(f)
    - if current_user == @user
      = link_to 'edit', edit_forum_path(f)
      = link_to 'destroy', forum_path(f), :method => :delete

==
does anyone have some good example?
-- 
Posted via http://www.ruby-forum.com/.

From aslak.hellesoy at gmail.com  Sat Mar 14 09:37:43 2009
From: aslak.hellesoy at gmail.com (=?utf-8?Q?Aslak_Helles=C3=B8y?=)
Date: Sat, 14 Mar 2009 14:37:43 +0100
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <B039C405-AF4A-4D6C-95AA-835E4BAEBDF6@mattwynne.net>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<8d961d900903131447r32b3d470i7755dc0dafafedeb@mail.gmail.com>
	<B039C405-AF4A-4D6C-95AA-835E4BAEBDF6@mattwynne.net>
Message-ID: <A5A01D0D-4294-4A77-A7B7-9C6550A388A7@gmail.com>



Den 14. mars. 2009 kl. 13.59 skrev Matt Wynne <matt at mattwynne.net>:

>
> On 13 Mar 2009, at 21:47, aslak hellesoy wrote:
>
>>
>>
>> On Fri, Mar 13, 2009 at 10:28 PM, Tim Hart <THart at picagroup.com>  
>> wrote:
>> List,
>>
>> Quick question about Cucumber/Gherkin.
>>
>> I'm considering adding 'With' as a step definition to support  
>> scenarios like:
>>
>> Given a policy
>> With a PCF practice state
>> And a secondary risk
>> ...
>>
>> I'm fairly new to ruby - but I can't quite get this one figured  
>> out. I've tried adding
>>
>> Cucumber.alias_steps (['With'])
>>
>> To my features/support/env.rb file, but when I run cucumber, I  
>> still get a Syntax error. It looks like my 'with' never gets added  
>> to the original list.
>>
>> Unfortunately, this only aliases the ruby methods (this will let  
>> you call With /some step/ do..end in a step definition ruby file.
>> In order to make the plain text parser recognise other words, a  
>> change is needed in languages.yml.
>>
>> If you add a feature request in Lighthouse I'll see if I can add it.
>
> I'm not sure if I like this - dependency between steps seems like a  
> dodgy road to go down.
>
> When you're in a step definition, how would you know what object the  
> 'With' was referring to?
>

Good question Matt. Let's clarify this first. Maybe there is a better  
way to express this with the current language.

Aslak
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

From tomk32 at gmx.de  Sat Mar 14 09:50:57 2009
From: tomk32 at gmx.de (Thomas R. Koll)
Date: Sat, 14 Mar 2009 14:50:57 +0100
Subject: [rspec-users] how to test this view with Rspec
In-Reply-To: <160c24b9652a985b669f8cd85c98925e@ruby-forum.com>
References: <160c24b9652a985b669f8cd85c98925e@ruby-forum.com>
Message-ID: <C20EDFBC-9870-434E-A9BD-F18C59379E0A@gmx.de>


Am 14.03.2009 um 14:12 schrieb Zhenning Guan:

> = flash_messages
> - @user = User.find(1)

move that to the controller or a helper. always.
and if you try to find the admin with that, add a flag on the user
so you can write current_user.admin?


 > - @forum.each do |f|
 >   .group
 >     = link_to f.name, forum_path(f)

Am I wrong or shouldn't that read:
- @forums.each do |f|

And do yourself a favour and write forum not f. Otherwise easily  
mistaken as a form.


> does anyone have some good example?

About testing. Test with a current_user (e.g.  
template.should_receive(:current_user).and_return(User.find(2)),
with an admin and without any user at all.
And of course test with @forums being empty, a special response for  
that case would be nice.

ciao, tom

--
Thomas R. "TomK32" Koll || http://tomk32.de || http://ananasblau.com
just a geek trying to change the world
Skype: TomK32 || Mail: tomk32 at gmx.de
http://flickr.com/people/tomk32


From THart at picagroup.com  Sat Mar 14 10:20:24 2009
From: THart at picagroup.com (Tim Hart)
Date: Sat, 14 Mar 2009 09:20:24 -0500
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <A5A01D0D-4294-4A77-A7B7-9C6550A388A7@gmail.com>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<8d961d900903131447r32b3d470i7755dc0dafafedeb@mail.gmail.com>
	<B039C405-AF4A-4D6C-95AA-835E4BAEBDF6@mattwynne.net>
	<A5A01D0D-4294-4A77-A7B7-9C6550A388A7@gmail.com>
Message-ID: <39AE8504-DC5F-429D-82AE-16D93F9011B3@picagroup.com>

On Mar 14, 2009, at 8:49 AM, "Aslak Helles?y"  
<aslak.hellesoy at gmail.com> wrote:

>
>
> Den 14. mars. 2009 kl. 13.59 skrev Matt Wynne <matt at mattwynne.net>:
>
>>
>> On 13 Mar 2009, at 21:47, aslak hellesoy wrote:
>>
>>>
>>>
>>> On Fri, Mar 13, 2009 at 10:28 PM, Tim Hart <THart at picagroup.com>
>>> wrote:
>>> List,
>>>
>>> Quick question about Cucumber/Gherkin.
>>>
>>> I'm considering adding 'With' as a step definition to support
>>> scenarios like:
>>>
>>> Given a policy
>>> With a PCF practice state
>>> And a secondary risk
>>> ...
>>>
>>>
>>>
>>>
>>> Unfortunately, this only aliases the ruby methods (this will let
>>> you call With /some step/ do..end in a step definition ruby file.
>>> In order to make the plain text parser recognise other words, a
>>> change is needed in languages.yml.
>>>
>>> If you add a feature request in Lighthouse I'll see if I can add it.
>>
>> I'm not sure if I like this - dependency between steps seems like a
>> dodgy road to go down.
>>
>> When you're in a step definition, how would you know what object the
>> 'With' was referring to?
>>
>
> Good question Matt. Let's clarify this first. Maybe there is a better
> way to express this with the current language.
>>

As a test, I removed the 'add alias' line from my env.rb file, and  
updated languages.yaml. I updated the line that read

and: And

To read

and: And|With

Then my step_definition file can have a step definition like

Given /a PCF Practice state/ do ... end

Which I'd exactly what I was looking for.

My only concern I'd that I'd like to be able to add the 'With' to the  
language through code instead of having to update the yaml file. That  
way I have the option of varying the language for specific projects  
without having to 'polute' the basic language globally. I assumed this  
was what the 'add_alias' function would do for me in the first place. 
  
*****************************************************************************

Disclaimer: This electronic message may contain information that is Confidential or legally privileged. It is intended only for the use of the individual(s) and entity named in the message. If you are not an intended recipient of this message, please notify the sender immediately and delete the material from your computer. Do not deliver, distribute or copy this message and do not disclose its contents or take any action in reliance on the information it contains.

*****************************************************************************


From levy at levycarneiro.com  Sat Mar 14 10:51:47 2009
From: levy at levycarneiro.com (Levy Carneiro Jr.)
Date: Sat, 14 Mar 2009 11:51:47 -0300
Subject: [rspec-users] Spec'ing chained calls
In-Reply-To: <49BA74C2.1060403@railsnewbie.com>
References: <fca2ab280903130704h3733d6ecg9afcf6d78edfc52f@mail.gmail.com>
	<49BA74C2.1060403@railsnewbie.com>
Message-ID: <fca2ab280903140751n5e95c7c2xb9d6de0afef97e37@mail.gmail.com>

Hello Scott,

On Fri, Mar 13, 2009 at 11:59 AM, Scott Taylor <scott at railsnewbie.com>wrote:

> http://c2.com/cgi/wiki?LawOfDemeter
>
> Specs are as much of a design tool as a testing tool, and the use of mocks
> in your specs show just how ugly the current design is.
>
> Either write a wrapper around the library which takes care of the method
> chaining, or write integration tests against it, stubbing out some low level
> detail of the library.


Actually, the method 'fetch_new_tweets' is the wrapper. There's another
method called 'process_new_tweets', which calls some methods from the Tweet
class, including fetch_new_tweets.

But I see your point. Testing only the output from this wrapper (integration
tests), and not testing the internal actions being done inside
Twitter::Search, which Tweet shouldn't know about.

So, the ideal would be the Twitter::Search class to provide some
ready-to-use wrappers for me, the way I want it. Like the postman and wallet
example [1]. But, since it clearly doesn't have all wrappers I need,
shouldn't my own class, Tweets, be doing the several wrappers and testing
them on my own? Or, there is a better design pattern in this case?

[1]
http://www.ccs.neu.edu/research/demeter/demeter-method/LawOfDemeter/paper-boy/demeter.pdf


Regards,
Levy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090314/a8ff179a/attachment.html>

From matt at mattwynne.net  Sat Mar 14 11:05:35 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Sat, 14 Mar 2009 15:05:35 +0000
Subject: [rspec-users] [cucumber] open source projects with cucumber
	features
In-Reply-To: <6466d9040903131113h5183e55cwa87cc4a22a7519d@mail.gmail.com>
References: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
	<85d99afe0903111246x33b4a028r499253683fcf25c5@mail.gmail.com>
	<F18C5860-2A71-4124-8116-8841C33E2C8C@mattwynne.net>
	<6466d9040903130722k5c9a4806x954306a1d1f71f94@mail.gmail.com>
	<8d961d900903130838v6827195fp378301449b04b0a0@mail.gmail.com>
	<6466d9040903131113h5183e55cwa87cc4a22a7519d@mail.gmail.com>
Message-ID: <637A8CDD-D51D-4316-B50D-BD2CED07FAC8@mattwynne.net>


On 13 Mar 2009, at 18:13, Oliver Barnes wrote:

> Rails, but any other would be helpful as well, really.
>
> Just a repo of varied real-world cucumber feature examples already
> would help a lot, even without the feature steps or an actual
> developed app. I've been mining samples from pasties, tutorials and
> from github, but have found only a few scattered (and several
> theoretical), and have not found a more evolved and cohesive set.
>
> I'm working on a real project using cucumber right now, and though I
> think I understand the principles shown on the rspec book and the
> cucumber wiki, as well as on the discussions here, at times I've
> gotten stuck in writing features with my client, without patterns to
> draw from.

I think this is a problem, because most of the apps people are writing  
with Cucumber are proprietary, so there aren't any good examples in  
the public domain.

Hopefully once the code stabilizes for 0.2 we can start building the  
Cucumber web GUI as a shining example of how we like to do this.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From matt at mattwynne.net  Sat Mar 14 11:07:30 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Sat, 14 Mar 2009 15:07:30 +0000
Subject: [rspec-users] [cucumber] Performance of 0.1.99?
In-Reply-To: <8d961d900903140306v523fb22em127f568bb6f25e47@mail.gmail.com>
References: <6E256357-075E-4082-90B4-5E0253B51518@lukemelia.com>
	<8d961d900903140306v523fb22em127f568bb6f25e47@mail.gmail.com>
Message-ID: <89F1C2C9-CE73-48D2-A829-5637E7FDA992@mattwynne.net>


On 14 Mar 2009, at 10:06, aslak hellesoy wrote:

> On Sat, Mar 14, 2009 at 7:00 AM, Luke Melia <luke at lukemelia.com>  
> wrote:
> Has anyone noticed a slowdown in performance of their cucumber suite  
> from 0.1 to 0.2alpha?

Ours is getting slower all the time (as we add more features) so it's  
very hard to say. I've noticed it seems to take a little longer to  
crank up because the features are all parsed first - I'm not sure that  
happened before.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From evgeny.zislis at gmail.com  Sat Mar 14 11:29:17 2009
From: evgeny.zislis at gmail.com (Evgeny)
Date: Sat, 14 Mar 2009 17:29:17 +0200
Subject: [rspec-users] Perl 5 Cucumber
Message-ID: <b6840c770903140829r3fcc6a89he562a5d08748b65f@mail.gmail.com>

Hi all,
I have started a mini-cucumber clone written in Perl.

So for those of you working for enterprises that ruby has no foothold but
perl has fortresses, this might be a nice way to get it through ... it is in
my case anyway.

Other than that I would like to extend a plee for help, and if anyone can
help me out with this project (really small for now), then I would really
really appreciate it.


Enjoy

http://github.com/kesor/p5-cucumber



It is really minimal for now, so don't expect much.

Regards,

Evgeny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090314/0b240079/attachment.html>

From mark at mwilden.com  Sat Mar 14 11:50:16 2009
From: mark at mwilden.com (Mark Wilden)
Date: Sat, 14 Mar 2009 08:50:16 -0700
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <B039C405-AF4A-4D6C-95AA-835E4BAEBDF6@mattwynne.net>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<8d961d900903131447r32b3d470i7755dc0dafafedeb@mail.gmail.com>
	<B039C405-AF4A-4D6C-95AA-835E4BAEBDF6@mattwynne.net>
Message-ID: <3c30da400903140850o7646799bw65631399222a7c8a@mail.gmail.com>

On Sat, Mar 14, 2009 at 5:59 AM, Matt Wynne <matt at mattwynne.net> wrote:

> I'm not sure if I like this - dependency between steps seems like a dodgy
> road to go down.

I'm wondering how you'd feel about a style I've adopted:

  Scenario: Accepting a direct challenge, without leaving a comment
    Given there is a challenge
    And I am logged in
    And I have been invited to that challenge
    When I visit the challenge's page
    And I press "Accept"
    Then I should go to my attempt detail page for the challenge
    And I should see that I accepted the challenge
    And I should not see "Attempt Challenge"

Clearly, there is dependency between steps - each has to know what
challenge they're working on, for one thing. But I've found that it
reads better than the alternative

   Given there is a challenge call 'Reach from the Stars' for 'Halo 3'
    And I am logged in as Mark
    And Mark was invited to 'Reach from the Stars' for 'Halo 3' on
'Sept 1, 2009' by 'Bill'
   When I visit the challenge page for 'Reach from the Stars for 'Halo 3'
    And I press "Accept"
    Then I should go to Mark's attempt detail page for the challenge
'Reach from the Stars' for 'Halo 3'
    And I should see that 'You accepted this challenge on Sept 1,
2009'   And I should not see "Attempt Challenge"

The first one reads more like a business-level story to me and the
second one reads more like a test.

Thoughts?

///ark

From joe at josephwilk.net  Sat Mar 14 12:10:23 2009
From: joe at josephwilk.net (Joseph Wilk)
Date: Sat, 14 Mar 2009 16:10:23 +0000
Subject: [rspec-users] [cucumber] Performance of 0.1.99?
In-Reply-To: <89F1C2C9-CE73-48D2-A829-5637E7FDA992@mattwynne.net>
References: <6E256357-075E-4082-90B4-5E0253B51518@lukemelia.com>	<8d961d900903140306v523fb22em127f568bb6f25e47@mail.gmail.com>
	<89F1C2C9-CE73-48D2-A829-5637E7FDA992@mattwynne.net>
Message-ID: <49BBD6EF.6090407@josephwilk.net>

Matt Wynne wrote:
>
> On 14 Mar 2009, at 10:06, aslak hellesoy wrote:
>
>> On Sat, Mar 14, 2009 at 7:00 AM, Luke Melia <luke at lukemelia.com> wrote:
>> Has anyone noticed a slowdown in performance of their cucumber suite 
>> from 0.1 to 0.2alpha?
>
> Ours is getting slower all the time (as we add more features) so it's 
> very hard to say. I've noticed it seems to take a little longer to 
> crank up because the features are all parsed first - I'm not sure that 
> happened before.
Cuke parsed all the features (well the ones you tell it to) in its 
previous incarnations. The major difference is the new Abstract syntax 
tree structure where we represent a more complex object structure than 
before (but not massively I think). And hence we have more complex tree 
traversal but again I don't see it being huge.

It would be interesting to see some performance comparisons.

-- 
Joseph Wilk
http://blog.josephwilk.net


>
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



From dchelimsky at gmail.com  Sat Mar 14 12:48:50 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sat, 14 Mar 2009 11:48:50 -0500
Subject: [rspec-users] [Cucumber] When do you log in? (was- Adding a step
	definition)
Message-ID: <57c63afe0903140948j3d95c097w8783cfce9acfba80@mail.gmail.com>

On Sat, Mar 14, 2009 at 10:50 AM, Mark Wilden <mark at mwilden.com> wrote:
> On Sat, Mar 14, 2009 at 5:59 AM, Matt Wynne <matt at mattwynne.net> wrote:
>
>> I'm not sure if I like this - dependency between steps seems like a dodgy
>> road to go down.
>
> I'm wondering how you'd feel about a style I've adopted:
>
>  Scenario: Accepting a direct challenge, without leaving a comment
>    Given there is a challenge
>    And I am logged in

One thing I do fairly consistently is put "logged in" steps first.

Given I am logged in as "admin"
And there is a challenge
etc

the /as "admin"/ bit creates a user with login names, passwords and
roles derived from the value.

I also only include these when they are meaningful to the scenario. If
I'm working on a bit of functionality that only "admin" (for example)
can access, I'll have a separate feature talking about access, and
leave that business out of scenarios for this functionality. So
something like:

Scenario: valid vacation request
  Given I have accrued 10 days vacation
  When I submit a vacation request with:
    | start       | days |
    | next monday |    5 |
  ...

... would take care of logging in for me implicitly, as being logged
in is a fair assumption for this scenario and is spec'd elsewhere.

Any red flags for ppl? Are you doing it this way? If not, how else?

Cheers,
David

From luke at lukemelia.com  Sat Mar 14 14:01:06 2009
From: luke at lukemelia.com (Luke Melia)
Date: Sat, 14 Mar 2009 14:01:06 -0400
Subject: [rspec-users] [cucumber] Performance of 0.1.99?
In-Reply-To: <8d961d900903140306v523fb22em127f568bb6f25e47@mail.gmail.com>
References: <6E256357-075E-4082-90B4-5E0253B51518@lukemelia.com>
	<8d961d900903140306v523fb22em127f568bb6f25e47@mail.gmail.com>
Message-ID: <034D009B-192A-4939-BC4D-192C960417FB@lukemelia.com>


On Mar 14, 2009, at 6:06 AM, aslak hellesoy wrote:

> On Sat, Mar 14, 2009 at 7:00 AM, Luke Melia <luke at lukemelia.com>  
> wrote:
> Has anyone noticed a slowdown in performance of their cucumber suite  
> from 0.1 to 0.2alpha?

> I haven't noticed anything. Do you want to create a benchmark?

I just ran a subset of our suite with 0.1.x and then with master.  
Times were pretty close. Guess I need to keep hunting for the  
culprit. :-)

Cheers,
Luke

--
Luke Melia
luke at lukemelia.com
http://www.lukemelia.com/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090314/abbcc69c/attachment.html>

From joe at josephwilk.net  Sat Mar 14 14:04:59 2009
From: joe at josephwilk.net (Joseph Wilk)
Date: Sat, 14 Mar 2009 18:04:59 +0000
Subject: [rspec-users] [Cucumber] When do you log in? (was- Adding a
 step definition)
In-Reply-To: <57c63afe0903140948j3d95c097w8783cfce9acfba80@mail.gmail.com>
References: <57c63afe0903140948j3d95c097w8783cfce9acfba80@mail.gmail.com>
Message-ID: <49BBF1CB.7050504@josephwilk.net>

David Chelimsky wrote:
> On Sat, Mar 14, 2009 at 10:50 AM, Mark Wilden <mark at mwilden.com> wrote:
>   
>> On Sat, Mar 14, 2009 at 5:59 AM, Matt Wynne <matt at mattwynne.net> wrote:
>>
>>     
>>> I'm not sure if I like this - dependency between steps seems like a dodgy
>>> road to go down.
>>>       
>> I'm wondering how you'd feel about a style I've adopted:
>>
>>  Scenario: Accepting a direct challenge, without leaving a comment
>>    Given there is a challenge
>>    And I am logged in
>>     
>
> One thing I do fairly consistently is put "logged in" steps first.
>
> Given I am logged in as "admin"
> And there is a challenge
> etc
>
> the /as "admin"/ bit creates a user with login names, passwords and
> roles derived from the value.
>
> I also only include these when they are meaningful to the scenario. If
> I'm working on a bit of functionality that only "admin" (for example)
> can access, I'll have a separate feature talking about access, and
> leave that business out of scenarios for this functionality. So
> something like:
>
> Scenario: valid vacation request
>   Given I have accrued 10 days vacation
>   When I submit a vacation request with:
>     | start       | days |
>     | next monday |    5 |
>   ...
>
> ... would take care of logging in for me implicitly, as being logged
> in is a fair assumption for this scenario and is spec'd elsewhere.
>
> Any red flags for ppl? Are you doing it this way? If not, how else?
>   
I have been doing the same thing as you.

However recently I have started using Background [1] more and more when 
login is not the main focus of the feature:

Background:
  Given I'm logged in as "admin"

Scenario: valid vacation request
  Given I have accrued 10 days vacation
  When I submit a vacation request with:
    | start       | days |
    | next monday |    5 |


I quite like this as it allows me to minimise login crossover in steps 
that require login but don't want to explicitly say so. i.e.

Given I have accrued 10 days vacation

The step definition would having nothing to do with login, which might 
save having to  check if login has already been done and avoid doing it 
again in-order to make the step reusable.

-- 
Joseph Wilk
http://blog.josephwilk.net

[1] http://wiki.github.com/aslakhellesoy/cucumber/background


> Cheers,
> David
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
>   



From dchelimsky at gmail.com  Sat Mar 14 14:32:41 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sat, 14 Mar 2009 13:32:41 -0500
Subject: [rspec-users] [Cucumber] When do you log in? (was- Adding a
	step definition)
In-Reply-To: <49BBF1CB.7050504@josephwilk.net>
References: <57c63afe0903140948j3d95c097w8783cfce9acfba80@mail.gmail.com>
	<49BBF1CB.7050504@josephwilk.net>
Message-ID: <57c63afe0903141132h13890355j833f7ce9a2f0e4f5@mail.gmail.com>

On Sat, Mar 14, 2009 at 1:04 PM, Joseph Wilk <joe at josephwilk.net> wrote:
> David Chelimsky wrote:
>>
>> On Sat, Mar 14, 2009 at 10:50 AM, Mark Wilden <mark at mwilden.com> wrote:
>>
>>>
>>> On Sat, Mar 14, 2009 at 5:59 AM, Matt Wynne <matt at mattwynne.net> wrote:
>>>
>>>
>>>>
>>>> I'm not sure if I like this - dependency between steps seems like a
>>>> dodgy
>>>> road to go down.
>>>>
>>>
>>> I'm wondering how you'd feel about a style I've adopted:
>>>
>>> ?Scenario: Accepting a direct challenge, without leaving a comment
>>> ? Given there is a challenge
>>> ? And I am logged in
>>>
>>
>> One thing I do fairly consistently is put "logged in" steps first.
>>
>> Given I am logged in as "admin"
>> And there is a challenge
>> etc
>>
>> the /as "admin"/ bit creates a user with login names, passwords and
>> roles derived from the value.
>>
>> I also only include these when they are meaningful to the scenario. If
>> I'm working on a bit of functionality that only "admin" (for example)
>> can access, I'll have a separate feature talking about access, and
>> leave that business out of scenarios for this functionality. So
>> something like:
>>
>> Scenario: valid vacation request
>> ?Given I have accrued 10 days vacation
>> ?When I submit a vacation request with:
>> ? ?| start ? ? ? | days |
>> ? ?| next monday | ? ?5 |
>> ?...
>>
>> ... would take care of logging in for me implicitly, as being logged
>> in is a fair assumption for this scenario and is spec'd elsewhere.
>>
>> Any red flags for ppl? Are you doing it this way? If not, how else?
>>
>
> I have been doing the same thing as you.
>
> However recently I have started using Background [1] more and more when
> login is not the main focus of the feature:
>
> Background:
> ?Given I'm logged in as "admin"

To be completely honest, I had not looked at background yet. Might be
late in the game, but if Background is a collection of givens, then
I'd like to see it not require the Given keyword:

Background:
  I am logged in as "admin"

Scenario: .....

Thoughts? Too late? Too complex?

>
> Scenario: valid vacation request
> ?Given I have accrued 10 days vacation
> ?When I submit a vacation request with:
> ? | start ? ? ? | days |
> ? | next monday | ? ?5 |
>
>
> I quite like this as it allows me to minimise login crossover in steps that
> require login but don't want to explicitly say so. i.e.
>
> Given I have accrued 10 days vacation
>
> The step definition would having nothing to do with login, which might save
> having to ?check if login has already been done and avoid doing it again
> in-order to make the step reusable.
>
> --
> Joseph Wilk
> http://blog.josephwilk.net
>
> [1] http://wiki.github.com/aslakhellesoy/cucumber/background
>
>
>> Cheers,
>> David
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From lists at ruby-forum.com  Sat Mar 14 14:52:06 2009
From: lists at ruby-forum.com (Balint Erdi)
Date: Sat, 14 Mar 2009 19:52:06 +0100
Subject: [rspec-users] [cucumber] open source projects with cucumber
	features
In-Reply-To: <F18C5860-2A71-4124-8116-8841C33E2C8C@mattwynne.net>
References: <bd23e75cc3e397a20ee72b5059526aee@ruby-forum.com>
	<85d99afe0903111246x33b4a028r499253683fcf25c5@mail.gmail.com>
	<F18C5860-2A71-4124-8116-8841C33E2C8C@mattwynne.net>
Message-ID: <599756d8ceadc1fb4c1626b74e9420de@ruby-forum.com>

Yes, I am writing a Rails app. Anyway, I have got over the initial 
"writer's block" thanks to a very insightful thread on this forum 
(http://www.mail-archive.com/rspec-users at rubyforge.org/msg06296.html) 
and your valuable help. Thank you all!

Balint

Matt Wynne wrote:
> On 11 Mar 2009, at 19:46, Zach Dennis wrote:
> 
e?
> 
> What kind of app are you looking to build? Website? GUI? Console?
> 
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Sat Mar 14 15:11:00 2009
From: lists at ruby-forum.com (Balint Erdi)
Date: Sat, 14 Mar 2009 20:11:00 +0100
Subject: [rspec-users] [cucumber] accessing session variables
In-Reply-To: <F1CBACC8-1277-4818-A8E3-BC19DF5306BE@mattwynne.net>
References: <896a69ff319435ef12204ab0c163647a@ruby-forum.com>
	<F1CBACC8-1277-4818-A8E3-BC19DF5306BE@mattwynne.net>
Message-ID: <73615196e7bdc9afb92051724393d4ac@ruby-forum.com>

Hey Matt,

Thanks a lot for your elaborated response!

After reading this excellent thread about how to pass state between 
steps:

http://www.mail-archive.com/rspec-users at rubyforge.org/msg06296.html

I realized

1. I am not alone in this boat :)
2. that if I write "I go to", "my profile page" there is an implicit 
assumption -as you note below- that there is only one user so there is 
no harm in using this assumption in my steps. If there are several users 
in a scenario then I have to explicitly name users ("when Alice goes to 
her profile page", "when Bob presses the "Send" button, etc.)

In both cases my steps remain reusable, in fact. What does not seem nice 
to me -and what I wanted to evade- is to write this kind of feature:

Scenario: Create album from scratch
    Given I am logged in as "pepito"
    When "pepito" goes to his photos page
    And "pepito" follows "New album"

It seems redundant. Once I know I am pepito in the feature I should not 
have to define it in each step. It's like with spoken language.

3. using instance variables to pass state in the course of a features 
makes step definitions too coupled. (I have not experienced this but 
read it in the thread and it seems logical)

That said, I am still a starter with cucumber so I might come back and 
reassess my decisions :)

Once again, thank you for your suggestions!
Balint

Matt Wynne wrote:
> On 11 Mar 2009, at 18:52, Balint Erdi wrote:
> 
>>  User.find_by_login(login_name) || Factory(:user_with_password, :login
>>
>>  case page_name
>>  You have a nil object when you didn't expect it!
>>  case page_name
>>
>>  when /my profile page/i
>>    member_profile_path(:id => User.first)
>>  ...
>> end
>>
>> However, I am not at all content with this hack. It does not go to the
>> profile page of the logged in user but to the first one. This can be  
>> the
>> same -and in this scenario it is- but there is no guarantee for that.
> 
> IMO, trying to access implementation details like sessions from your
> acceptance tests is an anti-pattern, to be avoided.
> 
> The puzzle you've hit here is that there is state implied in your
> scenarios by the use of the phrase "*my* profile page". I think there
> are two approaches this:
> 
> (1) You remove the implicit state from the scenario by re-writing your
> step as "When I go to the profile page for the User". This means that
> you can safely now use User.first, and you can even assert at the top
> of that step that User.count.should == 1, because the step refers to
> "the User" - so there must only be one, right?
> 
> (2) You model the state implicit in the scenario within your tests by
> writing an instance variable on the Scenario's world when you log in -
> something to represent "me".
> 
> There is a third approach where you write a special 'API' on your app
> which the tests can use to find out who "me" is. That might be as
> simple as conventionally putting it in a HTML comment on the page, or
> even displaying it on every page, or as over-engineered as a REST GET
> request to a user/current or /session resource.
> 
> However you chose to do it, I would urge you to avoid going under the
> covers to grab the session object directly - it's a path to hideous
> complexity IMO. Better to keep your test layer as separate as you can
> from the code.
> 
> Does that make sense?
> 
> 
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com

-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Sat Mar 14 15:28:58 2009
From: lists at ruby-forum.com (Balint Erdi)
Date: Sat, 14 Mar 2009 20:28:58 +0100
Subject: [rspec-users] [webrat] click link by title doesn't work
In-Reply-To: <88fd8ddc0903130350u3c51dc72u78089a7a49d12244@mail.gmail.com>
References: <88fd8ddc0903130350u3c51dc72u78089a7a49d12244@mail.gmail.com>
Message-ID: <ba2313bef0344efb448ad3767e728be5@ruby-forum.com>

Andrew Premdas wrote:

> 
> When /^I follow view (\w+) details link$/ do |object|
>   click_link "#{object}_details}"
> end

I think the problem is that you have an extra } in the title of the link 
you are looking for. It should just be:

When /^I follow view (\w+) details link$/ do |object|
  click_link "#{object}_details"
end

Does this solve your problem?
Balint
-- 
Posted via http://www.ruby-forum.com/.

From apremdas at gmail.com  Sat Mar 14 15:54:49 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Sat, 14 Mar 2009 19:54:49 +0000
Subject: [rspec-users] [webrat] click link by title doesn't work
In-Reply-To: <ba2313bef0344efb448ad3767e728be5@ruby-forum.com>
References: <88fd8ddc0903130350u3c51dc72u78089a7a49d12244@mail.gmail.com>
	<ba2313bef0344efb448ad3767e728be5@ruby-forum.com>
Message-ID: <88fd8ddc0903141254i4c2c1905r3d49d3cedff043fc@mail.gmail.com>

Doh!, thanks alot :).

2009/3/14 Balint Erdi <lists at ruby-forum.com>

> Andrew Premdas wrote:
>
> >
> > When /^I follow view (\w+) details link$/ do |object|
> >   click_link "#{object}_details}"
> > end
>
> I think the problem is that you have an extra } in the title of the link
> you are looking for. It should just be:
>
> When /^I follow view (\w+) details link$/ do |object|
>  click_link "#{object}_details"
> end
>
> Does this solve your problem?
> Balint
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090314/9494016c/attachment-0001.html>

From apremdas at gmail.com  Sat Mar 14 16:10:20 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Sat, 14 Mar 2009 20:10:20 +0000
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <C5E03A45.DAC5%THart@picagroup.com>
References: <C5E03A45.DAC5%THart@picagroup.com>
Message-ID: <88fd8ddc0903141310s19a4e187gdafc62e9aef1d016@mail.gmail.com>

Is the syntax you're using a misreading of the wiki advice on Feature-Coupled
Steps.

Why not have

"GIven a policy with a PCF practice state and seconday risk"

This is not a featured coupled step because PCF practice state and secondary
risk are part of the Policies state and are not seperate. Seperating the
step as you have done does not reduce coupling. In fact all it does is
complicate the steps because a variable containing the policy has to now be
in the 3 steps.

Perhaps the need for a with is a 'smell' suggesting that you are seperating
a step that is intrinsically coupled. So with really shouldn't be needed at
all.

HTH

Andrew

2009/3/13 Tim Hart <THart at picagroup.com>

> List,
>
> Quick question about Cucumber/Gherkin.
>
> I'm considering adding 'With' as a step definition to support scenarios
> like:
>
> Given a policy
> With a PCF practice state
> And a secondary risk
> ...
>
> I'm fairly new to ruby - but I can't quite get this one figured out. I've
> tried adding
>
> Cucumber.alias_steps (['With'])
>
> To my features/support/env.rb file, but when I run cucumber, I still get a
> Syntax error. It looks like my 'with' never gets added to the original list.
>
> Suggestions?
> --
> Tim Hart
> Senior Software Engineer
> PICA Group
> 615-713-9956 :cell
> timothyjhart :Y!
> tjhart at me.com :AIM
>
>
> *****************************************************************************
>
> Disclaimer: This electronic message may contain information that is
> Confidential or legally privileged. It is intended only for the use of the
> individual(s) and entity named in the message. If you are not an intended
> recipient of this message, please notify the sender immediately and delete
> the material from your computer. Do not deliver, distribute or copy this
> message and do not disclose its contents or take any action in reliance on
> the information it contains.
>
>
> *****************************************************************************
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090314/1345cfc3/attachment.html>

From matt at mattwynne.net  Sat Mar 14 16:29:40 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Sat, 14 Mar 2009 20:29:40 +0000
Subject: [rspec-users] [cucumber] accessing session variables
In-Reply-To: <73615196e7bdc9afb92051724393d4ac@ruby-forum.com>
References: <896a69ff319435ef12204ab0c163647a@ruby-forum.com>
	<F1CBACC8-1277-4818-A8E3-BC19DF5306BE@mattwynne.net>
	<73615196e7bdc9afb92051724393d4ac@ruby-forum.com>
Message-ID: <1D1F406A-3AB0-4BD7-AB9B-FB44214AC8D6@mattwynne.net>


On 14 Mar 2009, at 19:11, Balint Erdi wrote:

> Hey Matt,
>
> Thanks a lot for your elaborated response!
>
> After reading this excellent thread about how to pass state between
> steps:
>
> http://www.mail-archive.com/rspec-users at rubyforge.org/msg06296.html
>
> I realized
>
> 1. I am not alone in this boat :)
> 2. that if I write "I go to", "my profile page" there is an implicit
> assumption -as you note below- that there is only one user so there is
> no harm in using this assumption in my steps. If there are several  
> users
> in a scenario then I have to explicitly name users ("when Alice goes  
> to
> her profile page", "when Bob presses the "Send" button, etc.)
>
> In both cases my steps remain reusable, in fact. What does not seem  
> nice
> to me -and what I wanted to evade- is to write this kind of feature:
>
> Scenario: Create album from scratch
>    Given I am logged in as "pepito"
>    When "pepito" goes to his photos page
>    And "pepito" follows "New album"
>
> It seems redundant. Once I know I am pepito in the feature I should  
> not
> have to define it in each step. It's like with spoken language.
>
> 3. using instance variables to pass state in the course of a features
> makes step definitions too coupled. (I have not experienced this but
> read it in the thread and it seems logical)

I think you have to be pragmatic about this. We have a @user variable  
in our steps that represents 'me' and that has worked OK for us. I  
think that's just about the only time we've had to use instance  
variables in 900 or so scenarios, but there are certainly times when  
it makes sense. You just have to be aware of the risks and not use  
them too cheaply.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From matt at mattwynne.net  Sat Mar 14 16:33:34 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Sat, 14 Mar 2009 20:33:34 +0000
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <3c30da400903140850o7646799bw65631399222a7c8a@mail.gmail.com>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<8d961d900903131447r32b3d470i7755dc0dafafedeb@mail.gmail.com>
	<B039C405-AF4A-4D6C-95AA-835E4BAEBDF6@mattwynne.net>
	<3c30da400903140850o7646799bw65631399222a7c8a@mail.gmail.com>
Message-ID: <9F79F88F-7C28-4D9A-B056-486D49EF7334@mattwynne.net>


On 14 Mar 2009, at 15:50, Mark Wilden wrote:

> On Sat, Mar 14, 2009 at 5:59 AM, Matt Wynne <matt at mattwynne.net>  
> wrote:
>
>> I'm not sure if I like this - dependency between steps seems like a  
>> dodgy
>> road to go down.
>
> I'm wondering how you'd feel about a style I've adopted:
>
>  Scenario: Accepting a direct challenge, without leaving a comment
>    Given there is a challenge
>    And I am logged in
>    And I have been invited to that challenge
>    When I visit the challenge's page
>    And I press "Accept"
>    Then I should go to my attempt detail page for the challenge
>    And I should see that I accepted the challenge
>    And I should not see "Attempt Challenge"
>
> Clearly, there is dependency between steps - each has to know what
> challenge they're working on, for one thing. But I've found that it
> reads better than the alternative
>
>   Given there is a challenge call 'Reach from the Stars' for 'Halo 3'
>    And I am logged in as Mark
>    And Mark was invited to 'Reach from the Stars' for 'Halo 3' on
> 'Sept 1, 2009' by 'Bill'
>   When I visit the challenge page for 'Reach from the Stars for  
> 'Halo 3'
>    And I press "Accept"
>    Then I should go to Mark's attempt detail page for the challenge
> 'Reach from the Stars' for 'Halo 3'
>    And I should see that 'You accepted this challenge on Sept 1,
> 2009'   And I should not see "Attempt Challenge"
>
> The first one reads more like a business-level story to me and the
> second one reads more like a test.

Totally agree with this, and I do it all the time. On my team we allow  
ourselves to use the term 'the Widget' to mean Widget.first, but we'll  
always assert Widget.count.should == 1 when we do.

We also have a nifty little convention that allows us to talk about  
'the Widget "Foo"' and 'the Widget "Bar"' because pretty much every  
entity in our domain (or at least the ones we refer to like this in  
our features) has a #name attribute.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From wolfmanjm at gmail.com  Sat Mar 14 17:10:47 2009
From: wolfmanjm at gmail.com (wolfmanjm)
Date: Sat, 14 Mar 2009 14:10:47 -0700 (PDT)
Subject: [rspec-users] [Cucumber] When do you log in? (was- Adding a
	step definition)
In-Reply-To: <57c63afe0903141132h13890355j833f7ce9a2f0e4f5@mail.gmail.com>
References: <57c63afe0903140948j3d95c097w8783cfce9acfba80@mail.gmail.com> 
	<49BBF1CB.7050504@josephwilk.net>
	<57c63afe0903141132h13890355j833f7ce9a2f0e4f5@mail.gmail.com>
Message-ID: <93afbe12-438f-4dd0-8d7f-b7229ca5cfac@i2g2000prd.googlegroups.com>

I use something similar, however as I need to have my database pre
populated with valid user accounts (the dreaded fixtures) I use
something like..

Given the following users are logged in:
      |user|
      |first|
      |second|
      |third|

When the first user sends a message to the second user
Then the second user gets a message from the first user
And the third user does not get a message from the first user

I hide the actual login and the actual login names deep within a
helper class (do_login), and I map the first, second, third users to
the real login names that were created by a fixture or other fixture-
like method in the helper close to where the database gets populated.

So the steps look like...

Given /^the following users are logged in:$/ do |users|
  ua= users.rows.collect { |u| u.first }
  do_logins(ua)
end

Given /^a (first|second|third) user is logged in$/ do |user|
  do_login(user)
end

When /^the (first|second|third) user sends a message to the (first|
second|third) user$/ do |user1,user2|
  send_message(user1, user2, "a message")
end

Then /^the (first|second|third) user gets a message from the (first|
second|third) user$/ do |user1, user2|
  # check user1 gets "a message" from user2
end

In the helpers...
  Aliases= {'first' => "FeatureTester1", 'second' => "FeatureTester2",
'third' => "FeatureTester3"}

def do_login(user)
  login(Aliases[user],  password)
end

etc...

On Mar 14, 11:32?am, David Chelimsky <dchelim... at gmail.com> wrote:
> On Sat, Mar 14, 2009 at 1:04 PM, Joseph Wilk <j... at josephwilk.net> wrote:
> > David Chelimsky wrote:
>
> >> On Sat, Mar 14, 2009 at 10:50 AM, Mark Wilden <m... at mwilden.com> wrote:
>
> >>> On Sat, Mar 14, 2009 at 5:59 AM, Matt Wynne <m... at mattwynne.net> wrote:
>
> >>>> I'm not sure if I like this - dependency between steps seems like a
> >>>> dodgy
> >>>> road to go down.
>
> >>> I'm wondering how you'd feel about a style I've adopted:
>
> >>> ?Scenario: Accepting a direct challenge, without leaving a comment
> >>> ? Given there is a challenge
> >>> ? And I am logged in
>
> >> One thing I do fairly consistently is put "logged in" steps first.
>
> >> Given I am logged in as "admin"
> >> And there is a challenge
> >> etc
>
> >> the /as "admin"/ bit creates a user with login names, passwords and
> >> roles derived from the value.
>
> >> I also only include these when they are meaningful to the scenario. If
> >> I'm working on a bit of functionality that only "admin" (for example)
> >> can access, I'll have a separate feature talking about access, and
> >> leave that business out of scenarios for this functionality. So
> >> something like:
>
> >> Scenario: valid vacation request
> >> ?Given I have accrued 10 days vacation
> >> ?When I submit a vacation request with:
> >> ? ?| start ? ? ? | days |
> >> ? ?| next monday | ? ?5 |
> >> ?...
>
> >> ... would take care of logging in for me implicitly, as being logged
> >> in is a fair assumption for this scenario and is spec'd elsewhere.
>
> >> Any red flags for ppl? Are you doing it this way? If not, how else?
>
> > I have been doing the same thing as you.
>
> > However recently I have started using Background [1] more and more when
> > login is not the main focus of the feature:
>
> > Background:
> > ?Given I'm logged in as "admin"
>
> To be completely honest, I had not looked at background yet. Might be
> late in the game, but if Background is a collection of givens, then
> I'd like to see it not require the Given keyword:
>
> Background:
> ? I am logged in as "admin"
>
> Scenario: .....
>
> Thoughts? Too late? Too complex?
>
>
>
>
>
> > Scenario: valid vacation request
> > ?Given I have accrued 10 days vacation
> > ?When I submit a vacation request with:
> > ? | start ? ? ? | days |
> > ? | next monday | ? ?5 |
>
> > I quite like this as it allows me to minimise login crossover in steps that
> > require login but don't want to explicitly say so. i.e.
>
> > Given I have accrued 10 days vacation
>
> > The step definition would having nothing to do with login, which might save
> > having to ?check if login has already been done and avoid doing it again
> > in-order to make the step reusable.
>
> > --
> > Joseph Wilk
> >http://blog.josephwilk.net
>
> > [1]http://wiki.github.com/aslakhellesoy/cucumber/background
>
> >> Cheers,
> >> David
> >> _______________________________________________
> >> rspec-users mailing list
> >> rspec-us... at rubyforge.org
> >>http://rubyforge.org/mailman/listinfo/rspec-users
>
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From ashley.moran at patchspace.co.uk  Sat Mar 14 17:26:24 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Sat, 14 Mar 2009 21:26:24 +0000
Subject: [rspec-users] Ruby - LiquidTest- Documentation
Message-ID: <561D216A-B03D-4717-AEA0-DD16134FEDD0@patchspace.co.uk>

Hi all

Just wondering if anyone here has seen and/or used LiquidTest[1]?  I  
notice they have Cucumber integration too.

Has/would anyone pay for this?  (It's out of the question for me, as  
there's no Mac support.)

Cheers
Ashley

[1] http://www.jadeliquid.com/liquidtest/docs/doku.php?id=languages:ruby:home
[2] http://www.jadeliquid.com/liquidtest/docs/doku.php?id=languages:ruby:cucumber_story_runner


-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From mark at mwilden.com  Sat Mar 14 17:35:50 2009
From: mark at mwilden.com (Mark Wilden)
Date: Sat, 14 Mar 2009 14:35:50 -0700
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <9F79F88F-7C28-4D9A-B056-486D49EF7334@mattwynne.net>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<8d961d900903131447r32b3d470i7755dc0dafafedeb@mail.gmail.com>
	<B039C405-AF4A-4D6C-95AA-835E4BAEBDF6@mattwynne.net>
	<3c30da400903140850o7646799bw65631399222a7c8a@mail.gmail.com>
	<9F79F88F-7C28-4D9A-B056-486D49EF7334@mattwynne.net>
Message-ID: <3c30da400903141435h67e7a697k1447b57c2958db40@mail.gmail.com>

On Sat, Mar 14, 2009 at 1:33 PM, Matt Wynne <matt at mattwynne.net> wrote:

> We also have a nifty little convention that allows us to talk about 'the
> Widget "Foo"' and 'the Widget "Bar"' because pretty much every entity in our
> domain (or at least the ones we refer to like this in our features) has a
> #name attribute.

That sounds like a great way to avoid the instance variable.

///ark

From matt at mattwynne.net  Sat Mar 14 17:51:55 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Sat, 14 Mar 2009 21:51:55 +0000
Subject: [rspec-users] Ruby - LiquidTest- Documentation
In-Reply-To: <561D216A-B03D-4717-AEA0-DD16134FEDD0@patchspace.co.uk>
References: <561D216A-B03D-4717-AEA0-DD16134FEDD0@patchspace.co.uk>
Message-ID: <EA5C0483-1827-4C6B-880B-E9CBD6AFBA5A@mattwynne.net>


On 14 Mar 2009, at 21:26, Ashley Moran wrote:

> Hi all
>
> Just wondering if anyone here has seen and/or used LiquidTest[1]?  I  
> notice they have Cucumber integration too.
>
> Has/would anyone pay for this?  (It's out of the question for me, as  
> there's no Mac support.)
>
> Cheers
> Ashley
>
> [1] http://www.jadeliquid.com/liquidtest/docs/doku.php?id=languages:ruby:home
> [2] http://www.jadeliquid.com/liquidtest/docs/doku.php?id=languages:ruby:cucumber_story_runner

Presumably what you're paying for is all the record / playback rubbish  
that allows the unqualified to produce brittle test suites.

Wouldn't touch it with a barge pole myself.

Still, I'm happy to hear they're supporting Cucumber.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From THart at picagroup.com  Sat Mar 14 18:01:21 2009
From: THart at picagroup.com (Tim Hart)
Date: Sat, 14 Mar 2009 17:01:21 -0500
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <88fd8ddc0903141310s19a4e187gdafc62e9aef1d016@mail.gmail.com>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<88fd8ddc0903141310s19a4e187gdafc62e9aef1d016@mail.gmail.com>
Message-ID: <3115A6E6-F971-4754-9EB3-0255B1C6CBB1@picagroup.com>

On Mar 14, 2009, at 3:38 PM, "Andrew Premdas" <apremdas at gmail.com<mailto:apremdas at gmail.com>> wrote:

Is the syntax you're using a misreading of the wiki advice on Feature-Coupled Steps.

Why not have

"GIven a policy with a PCF practice state and seconday risk"

Because the work we are currently doing is going to involve several hundred different variations of over a hundred different attributes of a policy. I need to make sure that I'm able to reuse as many statements describing that policy as I possibly can.

Another factor is that our SME is going to be heavily involved in creating these scenarios. A few concessions toward regular English will help a great deal.

This is not a featured coupled step because PCF practice state and secondary risk are part of the Policies state and are not seperate. Seperating the step as you have done does not reduce coupling. In fact all it does is complicate the steps because a variable containing the policy has to now be in the 3 steps.

Perhaps the need for a with is a 'smell' suggesting that you are seperating a step that is intrinsically coupled. So with really shouldn't be needed at all.

HTH

Andrew

2009/3/13 Tim Hart <<mailto:THart at picagroup.com>THart at picagroup.com<mailto:THart at picagroup.com>>
List,

Quick question about Cucumber/Gherkin.

I'm considering adding 'With' as a step definition to support scenarios like:

Given a policy
With a PCF practice state
And a secondary risk
...

I'm fairly new to ruby - but I can't quite get this one figured out. I've tried adding

Cucumber.alias_steps (['With'])

To my features/support/env.rb file, but when I run cucumber, I still get a Syntax error. It looks like my 'with' never gets added to the original list.

Suggestions?
--
Tim Hart
Senior Software Engineer
PICA Group
615-713-9956 :cell
timothyjhart :Y!
<mailto:tjhart at me.com>tjhart at me.com<mailto:tjhart at me.com> :AIM

*****************************************************************************

Disclaimer: This electronic message may contain information that is Confidential or legally privileged. It is intended only for the use of the individual(s) and entity named in the message. If you are not an intended recipient of this message, please notify the sender immediately and delete the material from your computer. Do not deliver, distribute or copy this message and do not disclose its contents or take any action in reliance on the information it contains.

*****************************************************************************


_______________________________________________
rspec-users mailing list
<mailto:rspec-users at rubyforge.org>rspec-users at rubyforge.org<mailto:rspec-users at rubyforge.org>
<http://rubyforge.org/mailman/listinfo/rspec-users>http://rubyforge.org/mailman/listinfo/rspec-users

_______________________________________________
rspec-users mailing list
rspec-users at rubyforge.org<mailto:rspec-users at rubyforge.org>
http://rubyforge.org/mailman/listinfo/rspec-users

From ashley.moran at patchspace.co.uk  Sat Mar 14 18:42:16 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Sat, 14 Mar 2009 22:42:16 +0000
Subject: [rspec-users] Ruby - LiquidTest- Documentation
In-Reply-To: <EA5C0483-1827-4C6B-880B-E9CBD6AFBA5A@mattwynne.net>
References: <561D216A-B03D-4717-AEA0-DD16134FEDD0@patchspace.co.uk>
	<EA5C0483-1827-4C6B-880B-E9CBD6AFBA5A@mattwynne.net>
Message-ID: <1E445E9B-96EF-4ABE-A814-058DC826F6CB@patchspace.co.uk>


On 14 Mar 2009, at 21:51, Matt Wynne wrote:

> Presumably what you're paying for is all the record / playback  
> rubbish that allows the unqualified to produce brittle test suites.
>
> Wouldn't touch it with a barge pole myself.

Well that was my initial reaction!  Although it does have distributed,  
headless test runs.  But don't see how this could be used with  
Cucumber.  Can't see anything it offers that you can't achieve with  
free tools!

Presumably their main market is waterfall companies that think they  
can reduce costs by reducing "tester" salaries.  Just a guess though...

Ashley


-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From matt at mattwynne.net  Sat Mar 14 18:58:41 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Sat, 14 Mar 2009 22:58:41 +0000
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <3115A6E6-F971-4754-9EB3-0255B1C6CBB1@picagroup.com>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<88fd8ddc0903141310s19a4e187gdafc62e9aef1d016@mail.gmail.com>
	<3115A6E6-F971-4754-9EB3-0255B1C6CBB1@picagroup.com>
Message-ID: <5F583F21-B5D3-438C-A702-1410E40B40EF@mattwynne.net>


On 14 Mar 2009, at 22:01, Tim Hart wrote:

> On Mar 14, 2009, at 3:38 PM, "Andrew Premdas" <apremdas at gmail.com<mailto:apremdas at gmail.com 
> >> wrote:
>
> Is the syntax you're using a misreading of the wiki advice on  
> Feature-Coupled Steps.
>
> Why not have
>
> "GIven a policy with a PCF practice state and seconday risk"
>
> Because the work we are currently doing is going to involve several  
> hundred different variations of over a hundred different attributes  
> of a policy. I need to make sure that I'm able to reuse as many  
> statements describing that policy as I possibly can.

Have you thought about using Scenario Outlines to express these  
several hundred variations in a tabular format?

That would enable you something like:

Given a policy with <policy features>
When blah
Then <outcome>

Examples:
| policy features                        | outcome |
| a PCF practice state and seconday risk | foo     |

Just a thought.



Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From lists at ruby-forum.com  Sat Mar 14 20:11:14 2009
From: lists at ruby-forum.com (Balint Erdi)
Date: Sun, 15 Mar 2009 01:11:14 +0100
Subject: [rspec-users] [cucumber] accessing session variables
In-Reply-To: <1D1F406A-3AB0-4BD7-AB9B-FB44214AC8D6@mattwynne.net>
References: <896a69ff319435ef12204ab0c163647a@ruby-forum.com>
	<F1CBACC8-1277-4818-A8E3-BC19DF5306BE@mattwynne.net>
	<73615196e7bdc9afb92051724393d4ac@ruby-forum.com>
	<1D1F406A-3AB0-4BD7-AB9B-FB44214AC8D6@mattwynne.net>
Message-ID: <badda985c91aa82094f44f96bae86548@ruby-forum.com>

Oh, I see. I'll heed your advice and will consider using @user for the 
logged in user in the future.

Thanks again,
Balint

Matt Wynne wrote:
> On 14 Mar 2009, at 19:11, Balint Erdi wrote:
> 
>>
>> nice
>>
>> 3. using instance variables to pass state in the course of a features
>> makes step definitions too coupled. (I have not experienced this but
>> read it in the thread and it seems logical)
> 
> I think you have to be pragmatic about this. We have a @user variable
> in our steps that represents 'me' and that has worked OK for us. I
> think that's just about the only time we've had to use instance
> variables in 900 or so scenarios, but there are certainly times when
> it makes sense. You just have to be aware of the risks and not use
> them too cheaply.
> 


-- 
Posted via http://www.ruby-forum.com/.

From joshuachisholm at gmail.com  Sat Mar 14 20:30:59 2009
From: joshuachisholm at gmail.com (Josh Chisholm)
Date: Sun, 15 Mar 2009 00:30:59 +0000
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <5F583F21-B5D3-438C-A702-1410E40B40EF@mattwynne.net>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<88fd8ddc0903141310s19a4e187gdafc62e9aef1d016@mail.gmail.com>
	<3115A6E6-F971-4754-9EB3-0255B1C6CBB1@picagroup.com>
	<5F583F21-B5D3-438C-A702-1410E40B40EF@mattwynne.net>
Message-ID: <1126d7ae0903141730w636417e8y438385391ab5f0cc@mail.gmail.com>

> That sounds like a great way to avoid the instance variable.

Why is a named record preferable to an instance variable? It seems
like the coupling between steps is the same, but the coupled state is
stored differently. Maybe that's the point - stored differently.

I've been tempted to start scenario lines with "With" as well, to get
away from the combinatorial explosion of setup steps for complex
entities (think decorator pattern). I've used tables too, but mine
looked more like this:

Given a policy with:
  | PCF practice state | secondary risk |
  | yes                         | yes                   |

Is that nasty? It means we can use one step to set all possible
boolean attributes of a policy, but it doesn't read so well.

"With ..." would mean steps that were coupled to the "last mentioned
thing". That seems like a different kind of coupling - there is only
one piece of state involved (the last thing) rather than a map of
named things. But it's less explicit and implies that the "last thing"
needs to be updated by each step that mentions things.

Matt, going back to Mark's example, it sounds like you lean towards
the latter (i.e. repeat 'Reach from the Stars for 'Halo 3' throughout
the scenario). Is that correct?

Josh



On Sat, Mar 14, 2009 at 10:58 PM, Matt Wynne <matt at mattwynne.net> wrote:
>
> On 14 Mar 2009, at 22:01, Tim Hart wrote:
>
>> On Mar 14, 2009, at 3:38 PM, "Andrew Premdas"
>> <apremdas at gmail.com<mailto:apremdas at gmail.com>> wrote:
>>
>> Is the syntax you're using a misreading of the wiki advice on
>> Feature-Coupled Steps.
>>
>> Why not have
>>
>> "GIven a policy with a PCF practice state and seconday risk"
>>
>> Because the work we are currently doing is going to involve several
>> hundred different variations of over a hundred different attributes of a
>> policy. I need to make sure that I'm able to reuse as many statements
>> describing that policy as I possibly can.
>
> Have you thought about using Scenario Outlines to express these several
> hundred variations in a tabular format?
>
> That would enable you something like:
>
> Given a policy with <policy features>
> When blah
> Then <outcome>
>
> Examples:
> | policy features ? ? ? ? ? ? ? ? ? ? ? ?| outcome |
> | a PCF practice state and seconday risk | foo ? ? |
>
> Just a thought.
>
>
>
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From zegomesjf at gmail.com  Sat Mar 14 20:54:43 2009
From: zegomesjf at gmail.com (=?ISO-8859-1?Q?Jos=E9_Gomes_Jr=2E?=)
Date: Sat, 14 Mar 2009 17:54:43 -0700 (PDT)
Subject: [rspec-users] rspec 1.1.99.12, Rails 2.3.1,
	undefined method  `rspec_options='
In-Reply-To: <57c63afe0903120944l2c38385fp96034c7723f73f5@mail.gmail.com>
References: <81fd84b6-6093-4984-9a23-d4ce3ce8c62a@q9g2000yqc.googlegroups.com>
	<57c63afe0903120944l2c38385fp96034c7723f73f5@mail.gmail.com>
Message-ID: <a118ee31-c1d9-4841-98a0-fbd6491ddb59@o36g2000yqh.googlegroups.com>


Thank you for providing the requested information.


On 12 mar, 13:44, David Chelimsky <dchelim... at gmail.com> wrote:
> On Sun, Mar 8, 2009 at 6:19 PM,Jos?Gomes Jr. <zegome... at gmail.com> wrote:
>
>
>
> > Hi David, all:
>
> > I recently upgraded to Rails 2.3.1RC2 (Ubuntu 8.10, ruby 1.8.7
> > (2008-08-11 patchlevel 72) [i486-linux]) and have been dilligently
> > following the instructions for upgrading rspec and rspec-rails
> > according to: ?http://wiki.github.com/dchelimsky/rspec/rails-with-rspec-gems.
> > and when I run 'rake gem' fails with error:
>
> > rake aborted!
> > undefined method `rspec_options=' for #<Hoe:0xb782caf0>
> > /rspec/Rakefile:24
>
> > rspec / Rakefile look like
> > # -*- ruby -*-
>
> > $:.unshift(File.join(File.dirname(__FILE__), 'lib'))
> > require 'hoe'
> > require 'spec/version'
> > require 'spec/rake/spectask'
> > require 'cucumber/rake/task'
>
> > class Hoe
> > ?def extra_deps
> > ? ?@extra_deps.reject! { |x| Array(x).first == 'hoe' }
> > ? ?@extra_deps
> > ?end
> > end
>
> > Hoe.new('rspec', Spec::VERSION::STRING) do |p|
> > ?p.summary = Spec::VERSION::SUMMARY
> > ?p.url = 'http://rspec.info/'
> > ?p.description = "Behaviour Driven Development for Ruby."
> > ?p.rubyforge_name = 'rspec'
> > ?p.developer('RSpec Development Team', 'rspec-de... at rubyforge.org')
> > ?p.extra_dev_deps = [["cucumber",">= 0.1.13"]]
> > ?p.remote_rdoc_dir = "rspec/#{Spec::VERSION::STRING}"
> > ?p.rspec_options = ['--options', 'spec/spec.opts']
>
> [sudo] gem update hoe
>
> rspec_options is a relatively new hoe addition.
>
> Cheers,
> David
>
> > end
>
> > Thanks in advance for your assistance,
> >Jos?Gomes J?nior
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From matt at mattwynne.net  Sat Mar 14 21:18:46 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Sun, 15 Mar 2009 01:18:46 +0000
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <1126d7ae0903141730w636417e8y438385391ab5f0cc@mail.gmail.com>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<88fd8ddc0903141310s19a4e187gdafc62e9aef1d016@mail.gmail.com>
	<3115A6E6-F971-4754-9EB3-0255B1C6CBB1@picagroup.com>
	<5F583F21-B5D3-438C-A702-1410E40B40EF@mattwynne.net>
	<1126d7ae0903141730w636417e8y438385391ab5f0cc@mail.gmail.com>
Message-ID: <4DCC2C10-05CF-48D3-BC0B-5CF38B5D3DD3@mattwynne.net>


On 15 Mar 2009, at 00:30, Josh Chisholm wrote:

>> That sounds like a great way to avoid the instance variable.
>
> Why is a named record preferable to an instance variable? It seems
> like the coupling between steps is the same, but the coupled state is
> stored differently. Maybe that's the point - stored differently.

I guess my view is that having the state out front in the scenario is  
preferable whenever possible (without cluttering up the feature with  
noise) because it's clear, and there's less risk of a gap opening up  
between what the step appears to do given its name, and what it  
actually does when it runs. I take this gap seriously because I put a  
great deal of trust our features.

> I've been tempted to start scenario lines with "With" as well, to get
> away from the combinatorial explosion of setup steps for complex
> entities (think decorator pattern). I've used tables too, but mine
> looked more like this:
>
> Given a policy with:
>  | PCF practice state | secondary risk |
>  | yes                         | yes                   |
>
> Is that nasty? It means we can use one step to set all possible
> boolean attributes of a policy, but it doesn't read so well.

I don't think that's nasty, it seems entirely appropriate for that  
type of problem. It sounds like the type of acceptance tests I hear  
people like Keith Braithwaite talking about putting together for  
traders using Excel and Fit, and they seem to work really well.

Thinking about this some more though, maybe there's an argument for  
breaking the feature up into multiple features, and using Background  
to set up the common state of the objects, then have a few scenarios  
that build on this with different steps to tweak the objects. Just  
another idea - it's really hard to judge without seeing more of the  
specific features.

> "With ..." would mean steps that were coupled to the "last mentioned
> thing". That seems like a different kind of coupling - there is only
> one piece of state involved (the last thing) rather than a map of
> named things. But it's less explicit and implies that the "last thing"
> needs to be updated by each step that mentions things.

I know what you mean, and it would certainly make for nice readable  
scenarios. My worry is how maintainable the steps would be in the long  
run. I'm used to seeing steps like this:

Given /the Policy has a secondary risk/ do
   Policy.count.should == 1
   policy = Policy.first
   policy.secondary_risk = true
   policy.save
end

Which are pretty explicit and leave no room for accidental abuse. What  
the OP suggested would give you something more like this:

Given /a Policy/ do
   @it = Factory(:policy)
end

With /a secondary risk/ do
   @it.secondary_risk = true
   @it.save
end

I dunno actually. Now I type it out it doesn't seem so bad :)


> Matt, going back to Mark's example, it sounds like you lean towards
> the latter (i.e. repeat 'Reach from the Stars for 'Halo 3' throughout
> the scenario). Is that correct?

I guess my heuristic is something like this:

1. If I can simply refer to "the Widget" then I do, wherever possible.

2. If some attribute of the Widget is important in the scenario, I'll  
explicitly set that attribute, and mention it again later in the  
assertions. e.g.
   Given a Widget named "Foo"
   When I delete the Widget
   Then I should see the text "bye bye Foo"

3. If I have to refer to multiple objects of the same class in one  
scenario, then I use names to differentiate between them. e.g.
   Given some Widgets named "Foo, Bar"
   When I delete the Widget "Foo"
   Then I should see 1 Widget
   And I should see the text "Bar"


Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From julien.genestoux at gmail.com  Thu Mar 12 19:21:55 2009
From: julien.genestoux at gmail.com (Julien)
Date: Thu, 12 Mar 2009 16:21:55 -0700 (PDT)
Subject: [rspec-users] Rspec and EventMachine
Message-ID: <d7ee19d1-2476-4587-818b-b96df6b7f2b9@40g2000prx.googlegroups.com>

Hey Guys,

I am trying to create a app that makes use of EventMachine.
As I recently fell in love with Rspec, I was trying to use it with our
EM. However, I have no idea how to do this. Also, I want to remove
network connections from the tests (as I might not be connected when
running them), so I think I should mock them up, but again... I don't
know how to do this!

Any tips?

Thanks

From evgeny.zislis at gmail.com  Fri Mar 13 07:23:47 2009
From: evgeny.zislis at gmail.com (Evgeny)
Date: Fri, 13 Mar 2009 04:23:47 -0700 (PDT)
Subject: [rspec-users] [cucumber] A Perl 5 mini-cucumber
Message-ID: <1063a4bc-b85f-4a1e-a4e4-d8659b5d517e@v19g2000yqn.googlegroups.com>

Hi All,

I wrote a Cucumber version in Perl 5.
It's very minimal, but maybe someone will find it interesting.

Check it out on http://github.com/kesor/p5-cucumber


-
evgeny

From THart at picagroup.com  Fri Mar 13 12:27:40 2009
From: THart at picagroup.com (Tim Hart)
Date: Fri, 13 Mar 2009 11:27:40 -0500
Subject: [rspec-users] Cucumber - adding a step definition
Message-ID: <C5DFF3AC.DA78%THart@picagroup.com>

List,

Quick question about Cucumber/Gherkin.

I'm considering adding 'With' as a step definition to support scenarios like:

Given a policy
With a PCF practice state
And a secondary risk
...

I'm fairly new to ruby - but I can't quite get this one figured out. I've tried adding

Cucumber.alias_steps (['With'])

To my features/support/env.rb file, but when I run cucumber, I still get a Syntax error. It looks like my 'with' never gets added to the original list.

Suggestions?
--
Tim Hart
Senior Software Engineer
PICA Group
615-713-9956 :cell
timothyjhart :Y!
tjhart at me.com :AIM

*****************************************************************************

Disclaimer: This electronic message may contain information that is Confidential or legally privileged. It is intended only for the use of the individual(s) and entity named in the message. If you are not an intended recipient of this message, please notify the sender immediately and delete the material from your computer. Do not deliver, distribute or copy this message and do not disclose its contents or take any action in reliance on the information it contains.

*****************************************************************************



From geetarista at gmail.com  Fri Mar 13 15:48:44 2009
From: geetarista at gmail.com (geetarista)
Date: Fri, 13 Mar 2009 12:48:44 -0700 (PDT)
Subject: [rspec-users] rspec,
	rspec-rails 1.1.99-12 and script/spec 'no such file to load -- spec'
In-Reply-To: <b1c4d55f-1ac2-4b11-b758-44b5ebd2baf1@x29g2000prf.googlegroups.com>
References: <b1c4d55f-1ac2-4b11-b758-44b5ebd2baf1@x29g2000prf.googlegroups.com>
Message-ID: <a2568c0b-673b-4f7c-a09b-9d84cf9d4ab7@k19g2000prh.googlegroups.com>

I'm having similar issues, but when I run the CMD + R command in
Textmate:

/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such
file to load -- spec (LoadError) from /System/Library/Frameworks/
Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rubygems/
custom_require.rb:27:in `require' from /Users/robbyc/Library/
Application Support/TextMate/Bundles/RSpec.tmbundle/Support/lib/spec/
mate.rb:14 from /tmp/textmate-command-5945.rb:2:in `require' from /tmp/
textmate-command-5945.rb:2

On Mar 6, 3:02?pm, rockrep <rock... at gmail.com> wrote:
> Hi David, all:
>
> I just recently upgraded to Rails 2.3.1RC2 (Mac OS.X 10.5.6, ruby
> 1.8.7 (2008-08-11 patchlevel 72) [i686-darwin9]) ?and have been
> dilligently following the instructions for upgrading rspec and rspec-
> rails according to: ?http://wiki.github.com/dchelimsky/rspec/rails-with-rspec-gems.
> I have successfully built the rspec and rspec-rails gems, installed
> and unpacked them, and ran script/generate rspec successfully.
>
> 'rakespec' works fine, however 'script/spec' fails with error:
> $ script/specspec
> script/spec:3:in `require':nosuchfiletoload--spec(LoadError)
>
> script/speclooks like:
> #!/usr/bin/env ruby
> $LOAD_PATH.unshift(File.expand_path(File.dirname(__FILE__) + "/../
> vendor/plugins/rspec/lib"))
> require 'spec'
> exit ::Spec::Runner::CommandLine.run
>
> and 'rake gems RAILS_ENV=test' returns:
> ?- [R] rspec >= 1.1.99.12
> ?- [F] rspec-rails >= 1.1.99.12
> ? ? - [R] rspec = 1.1.99.12
> ? ? - [F] rack = 0.9.1
> ? ? - [ ] cucumber >= 0.1.13
> ? ? - [ ] hoe >= 1.9.0
>
> I = Installed
> F = Frozen
> R = Framework (loaded before rails starts)
>
> rspec does not exist in vendor/gems, but rspec-rails does. ?It seems
> it's marked as 'R' which (1) I'm not certain I understand why, and (2)
> seems to prevent unpacking into vendor/gems. ? In any case, I would
> like to resolve the issue with script/spec.
>
> Since rspec is also not installed in vendor/plugins the LOAD_PATH line
> in script/speclooks odd, but I'm not sure it's the cause.
>
> Any pointers greatly appreciated. ?Thanks,
>
> Michael
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From vagostino at gmail.com  Sat Mar 14 21:37:23 2009
From: vagostino at gmail.com (Val)
Date: Sat, 14 Mar 2009 18:37:23 -0700 (PDT)
Subject: [rspec-users] How to use different mocking frameworks?
Message-ID: <a439235d-7e07-41f0-ad60-33e201da0f89@v18g2000pro.googlegroups.com>

Hi,

I'm pretty new to Rspec, so hope someone can help me out with this.

I'm leveraging a couple pre-existing applications in my current
project, both have fairly robust test suites in Rspec already.
However, one is using Rspec's builit in mocking, and the other is
using mocha.

If I set config.mock_with mocha in spec_helper.rb, then all of the
rspec mocks fail.  If I comment this out, all of the specs with mocha
fail.

Is there some way to set the mocking framework on a test and/or file
basis?  I've been all over Google, and can't seem to find a resolution
to this.  I really don't want to have to back through and rewrite
someone else's test suite that is already working.

Thanks in advance for your help,
Val

From dchelimsky at gmail.com  Sun Mar 15 01:01:19 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 15 Mar 2009 00:01:19 -0500
Subject: [rspec-users] How to use different mocking frameworks?
In-Reply-To: <a439235d-7e07-41f0-ad60-33e201da0f89@v18g2000pro.googlegroups.com>
References: <a439235d-7e07-41f0-ad60-33e201da0f89@v18g2000pro.googlegroups.com>
Message-ID: <57c63afe0903142201h47fccdcbsc9cf8f5e8c8a03c9@mail.gmail.com>

On Sat, Mar 14, 2009 at 8:37 PM, Val <vagostino at gmail.com> wrote:
> Hi,
>
> I'm pretty new to Rspec, so hope someone can help me out with this.
>
> I'm leveraging a couple pre-existing applications in my current
> project, both have fairly robust test suites in Rspec already.
> However, one is using Rspec's builit in mocking, and the other is
> using mocha.
>
> If I set config.mock_with mocha in spec_helper.rb, then all of the
> rspec mocks fail. ?If I comment this out, all of the specs with mocha
> fail.
>
> Is there some way to set the mocking framework on a test and/or file
> basis?

Nope. Gotta pick one or the other. Reason - diff mock frameworks
invade Object in diff ways - mixing and matching is dangerous to your
health.

> I've been all over Google, and can't seem to find a resolution
> to this. ?I really don't want to have to back through and rewrite
> someone else's test suite that is already working.
>
> Thanks in advance for your help,
> Val
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Sun Mar 15 01:01:59 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 15 Mar 2009 00:01:59 -0500
Subject: [rspec-users] How to use different mocking frameworks?
In-Reply-To: <57c63afe0903142201h47fccdcbsc9cf8f5e8c8a03c9@mail.gmail.com>
References: <a439235d-7e07-41f0-ad60-33e201da0f89@v18g2000pro.googlegroups.com>
	<57c63afe0903142201h47fccdcbsc9cf8f5e8c8a03c9@mail.gmail.com>
Message-ID: <57c63afe0903142201p895c417q4de2932bceaec98d@mail.gmail.com>

On Sun, Mar 15, 2009 at 12:01 AM, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Sat, Mar 14, 2009 at 8:37 PM, Val <vagostino at gmail.com> wrote:
>> Hi,
>>
>> I'm pretty new to Rspec, so hope someone can help me out with this.
>>
>> I'm leveraging a couple pre-existing applications in my current
>> project, both have fairly robust test suites in Rspec already.
>> However, one is using Rspec's builit in mocking, and the other is
>> using mocha.
>>
>> If I set config.mock_with mocha in spec_helper.rb, then all of the
>> rspec mocks fail. ?If I comment this out, all of the specs with mocha
>> fail.
>>
>> Is there some way to set the mocking framework on a test and/or file
>> basis?
>
> Nope. Gotta pick one or the other. Reason - diff mock frameworks
> invade Object in diff ways - mixing and matching is dangerous to your
> health.

I mean within one project. Of course you can use rspec/mocks in one,
mocha in another, flexmock and rr in others.

>
>> I've been all over Google, and can't seem to find a resolution
>> to this. ?I really don't want to have to back through and rewrite
>> someone else's test suite that is already working.
>>
>> Thanks in advance for your help,
>> Val
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>

From joshuachisholm at gmail.com  Sun Mar 15 03:55:43 2009
From: joshuachisholm at gmail.com (Josh Chisholm)
Date: Sun, 15 Mar 2009 07:55:43 +0000
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <4DCC2C10-05CF-48D3-BC0B-5CF38B5D3DD3@mattwynne.net>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<88fd8ddc0903141310s19a4e187gdafc62e9aef1d016@mail.gmail.com>
	<3115A6E6-F971-4754-9EB3-0255B1C6CBB1@picagroup.com>
	<5F583F21-B5D3-438C-A702-1410E40B40EF@mattwynne.net>
	<1126d7ae0903141730w636417e8y438385391ab5f0cc@mail.gmail.com>
	<4DCC2C10-05CF-48D3-BC0B-5CF38B5D3DD3@mattwynne.net>
Message-ID: <1126d7ae0903150055n6358ef47n8aa681b601776c9e@mail.gmail.com>

I like that heuristic Matt.

Actually coupling via the database is quite different to instance
variables. The database state would exist if you followed through the
scenario without cucumber e.g. manually.

It occurred to me you could avoid the table like this too:

Given a policy with a PCF practice state, secondary risk and something else

Given /^a policy with (.+)$/ do | attributes |
  # create policy
  attributes.split(/(?:(?:,|\sand)\s)/).each do | attribute |
    # apply attributes "a PCF practice state", "secondary risk",
"something else"
  end
end

Josh

On Sun, Mar 15, 2009 at 1:18 AM, Matt Wynne <matt at mattwynne.net> wrote:
>
> On 15 Mar 2009, at 00:30, Josh Chisholm wrote:
>
>>> That sounds like a great way to avoid the instance variable.
>>
>> Why is a named record preferable to an instance variable? It seems
>> like the coupling between steps is the same, but the coupled state is
>> stored differently. Maybe that's the point - stored differently.
>
> I guess my view is that having the state out front in the scenario is
> preferable whenever possible (without cluttering up the feature with noise)
> because it's clear, and there's less risk of a gap opening up between what
> the step appears to do given its name, and what it actually does when it
> runs. I take this gap seriously because I put a great deal of trust our
> features.
>
>> I've been tempted to start scenario lines with "With" as well, to get
>> away from the combinatorial explosion of setup steps for complex
>> entities (think decorator pattern). I've used tables too, but mine
>> looked more like this:
>>
>> Given a policy with:
>> ?| PCF practice state | secondary risk |
>> ?| yes ? ? ? ? ? ? ? ? ? ? ? ? | yes ? ? ? ? ? ? ? ? ? |
>>
>> Is that nasty? It means we can use one step to set all possible
>> boolean attributes of a policy, but it doesn't read so well.
>
> I don't think that's nasty, it seems entirely appropriate for that type of
> problem. It sounds like the type of acceptance tests I hear people like
> Keith Braithwaite talking about putting together for traders using Excel and
> Fit, and they seem to work really well.
>
> Thinking about this some more though, maybe there's an argument for breaking
> the feature up into multiple features, and using Background to set up the
> common state of the objects, then have a few scenarios that build on this
> with different steps to tweak the objects. Just another idea - it's really
> hard to judge without seeing more of the specific features.
>
>> "With ..." would mean steps that were coupled to the "last mentioned
>> thing". That seems like a different kind of coupling - there is only
>> one piece of state involved (the last thing) rather than a map of
>> named things. But it's less explicit and implies that the "last thing"
>> needs to be updated by each step that mentions things.
>
> I know what you mean, and it would certainly make for nice readable
> scenarios. My worry is how maintainable the steps would be in the long run.
> I'm used to seeing steps like this:
>
> Given /the Policy has a secondary risk/ do
> ?Policy.count.should == 1
> ?policy = Policy.first
> ?policy.secondary_risk = true
> ?policy.save
> end
>
> Which are pretty explicit and leave no room for accidental abuse. What the
> OP suggested would give you something more like this:
>
> Given /a Policy/ do
> ?@it = Factory(:policy)
> end
>
> With /a secondary risk/ do
> ?@it.secondary_risk = true
> ?@it.save
> end
>
> I dunno actually. Now I type it out it doesn't seem so bad :)
>
>
>> Matt, going back to Mark's example, it sounds like you lean towards
>> the latter (i.e. repeat 'Reach from the Stars for 'Halo 3' throughout
>> the scenario). Is that correct?
>
> I guess my heuristic is something like this:
>
> 1. If I can simply refer to "the Widget" then I do, wherever possible.
>
> 2. If some attribute of the Widget is important in the scenario, I'll
> explicitly set that attribute, and mention it again later in the assertions.
> e.g.
> ?Given a Widget named "Foo"
> ?When I delete the Widget
> ?Then I should see the text "bye bye Foo"
>
> 3. If I have to refer to multiple objects of the same class in one scenario,
> then I use names to differentiate between them. e.g.
> ?Given some Widgets named "Foo, Bar"
> ?When I delete the Widget "Foo"
> ?Then I should see 1 Widget
> ?And I should see the text "Bar"
>
>
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From apremdas at gmail.com  Sun Mar 15 08:38:16 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Sun, 15 Mar 2009 12:38:16 +0000
Subject: [rspec-users] How to use different mocking frameworks?
In-Reply-To: <57c63afe0903142201p895c417q4de2932bceaec98d@mail.gmail.com>
References: <a439235d-7e07-41f0-ad60-33e201da0f89@v18g2000pro.googlegroups.com>
	<57c63afe0903142201h47fccdcbsc9cf8f5e8c8a03c9@mail.gmail.com>
	<57c63afe0903142201p895c417q4de2932bceaec98d@mail.gmail.com>
Message-ID: <88fd8ddc0903150538j21e412a9hac8b23075f80b2c8@mail.gmail.com>

Would it be possible to split the tests into separate runs - a bit like
having two different run configurations with cucumber?

2009/3/15 David Chelimsky <dchelimsky at gmail.com>

> On Sun, Mar 15, 2009 at 12:01 AM, David Chelimsky <dchelimsky at gmail.com>
> wrote:
> > On Sat, Mar 14, 2009 at 8:37 PM, Val <vagostino at gmail.com> wrote:
> >> Hi,
> >>
> >> I'm pretty new to Rspec, so hope someone can help me out with this.
> >>
> >> I'm leveraging a couple pre-existing applications in my current
> >> project, both have fairly robust test suites in Rspec already.
> >> However, one is using Rspec's builit in mocking, and the other is
> >> using mocha.
> >>
> >> If I set config.mock_with mocha in spec_helper.rb, then all of the
> >> rspec mocks fail.  If I comment this out, all of the specs with mocha
> >> fail.
> >>
> >> Is there some way to set the mocking framework on a test and/or file
> >> basis?
> >
> > Nope. Gotta pick one or the other. Reason - diff mock frameworks
> > invade Object in diff ways - mixing and matching is dangerous to your
> > health.
>
> I mean within one project. Of course you can use rspec/mocks in one,
> mocha in another, flexmock and rr in others.
>
> >
> >> I've been all over Google, and can't seem to find a resolution
> >> to this.  I really don't want to have to back through and rewrite
> >> someone else's test suite that is already working.
> >>
> >> Thanks in advance for your help,
> >> Val
> >> _______________________________________________
> >> rspec-users mailing list
> >> rspec-users at rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/rspec-users
> >>
> >
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090315/c8259833/attachment-0001.html>

From dchelimsky at gmail.com  Sun Mar 15 09:09:02 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 15 Mar 2009 08:09:02 -0500
Subject: [rspec-users] How to use different mocking frameworks?
In-Reply-To: <88fd8ddc0903150538j21e412a9hac8b23075f80b2c8@mail.gmail.com>
References: <a439235d-7e07-41f0-ad60-33e201da0f89@v18g2000pro.googlegroups.com>
	<57c63afe0903142201h47fccdcbsc9cf8f5e8c8a03c9@mail.gmail.com>
	<57c63afe0903142201p895c417q4de2932bceaec98d@mail.gmail.com>
	<88fd8ddc0903150538j21e412a9hac8b23075f80b2c8@mail.gmail.com>
Message-ID: <57c63afe0903150609k3c552710h35e1896204680bef@mail.gmail.com>

On Sun, Mar 15, 2009 at 7:38 AM, Andrew Premdas <apremdas at gmail.com> wrote:
> Would it be possible to split the tests into separate runs - a bit like
> having two different run configurations with cucumber?

If you split the specs w/ rspec-mocks and those w/ mocha in separate
dirs, you could run them each manually. Or you could create rake tasks
to do it.

>
> 2009/3/15 David Chelimsky <dchelimsky at gmail.com>
>>
>> On Sun, Mar 15, 2009 at 12:01 AM, David Chelimsky <dchelimsky at gmail.com>
>> wrote:
>> > On Sat, Mar 14, 2009 at 8:37 PM, Val <vagostino at gmail.com> wrote:
>> >> Hi,
>> >>
>> >> I'm pretty new to Rspec, so hope someone can help me out with this.
>> >>
>> >> I'm leveraging a couple pre-existing applications in my current
>> >> project, both have fairly robust test suites in Rspec already.
>> >> However, one is using Rspec's builit in mocking, and the other is
>> >> using mocha.
>> >>
>> >> If I set config.mock_with mocha in spec_helper.rb, then all of the
>> >> rspec mocks fail. ?If I comment this out, all of the specs with mocha
>> >> fail.
>> >>
>> >> Is there some way to set the mocking framework on a test and/or file
>> >> basis?
>> >
>> > Nope. Gotta pick one or the other. Reason - diff mock frameworks
>> > invade Object in diff ways - mixing and matching is dangerous to your
>> > health.
>>
>> I mean within one project. Of course you can use rspec/mocks in one,
>> mocha in another, flexmock and rr in others.
>>
>> >
>> >> I've been all over Google, and can't seem to find a resolution
>> >> to this. ?I really don't want to have to back through and rewrite
>> >> someone else's test suite that is already working.
>> >>
>> >> Thanks in advance for your help,
>> >> Val
>> >> _______________________________________________
>> >> rspec-users mailing list
>> >> rspec-users at rubyforge.org
>> >> http://rubyforge.org/mailman/listinfo/rspec-users
>> >>
>> >
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From steven at stevenrbaker.com  Sun Mar 15 11:26:14 2009
From: steven at stevenrbaker.com (Steven Baker)
Date: Sun, 15 Mar 2009 11:26:14 -0400
Subject: [rspec-users] Rspec and EventMachine
In-Reply-To: <d7ee19d1-2476-4587-818b-b96df6b7f2b9@40g2000prx.googlegroups.com>
References: <d7ee19d1-2476-4587-818b-b96df6b7f2b9@40g2000prx.googlegroups.com>
Message-ID: <DBE44D06-DD80-4678-9337-8D2EAF4C8347@stevenrbaker.com>

> I am trying to create a app that makes use of EventMachine.
> As I recently fell in love with Rspec, I was trying to use it with our
> EM. However, I have no idea how to do this. Also, I want to remove
> network connections from the tests (as I might not be connected when
> running them), so I think I should mock them up, but again... I don't
> know how to do this!

We use a lot of eventmachine at work, and have some experience doing  
this.  I haven't written anything up, though.  If you'd like to hop on  
IRC Monday between 9-5 EST and ping me, I'll help you out with it.

-Steven


From ben at benmabey.com  Sun Mar 15 12:52:27 2009
From: ben at benmabey.com (Ben Mabey)
Date: Sun, 15 Mar 2009 10:52:27 -0600
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <4DCC2C10-05CF-48D3-BC0B-5CF38B5D3DD3@mattwynne.net>
References: <C5E03A45.DAC5%THart@picagroup.com>	<88fd8ddc0903141310s19a4e187gdafc62e9aef1d016@mail.gmail.com>	<3115A6E6-F971-4754-9EB3-0255B1C6CBB1@picagroup.com>	<5F583F21-B5D3-438C-A702-1410E40B40EF@mattwynne.net>	<1126d7ae0903141730w636417e8y438385391ab5f0cc@mail.gmail.com>
	<4DCC2C10-05CF-48D3-BC0B-5CF38B5D3DD3@mattwynne.net>
Message-ID: <49BD324B.7060002@benmabey.com>


> I know what you mean, and it would certainly make for nice readable 
> scenarios. My worry is how maintainable the steps would be in the long 
> run. I'm used to seeing steps like this:
>
> Given /the Policy has a secondary risk/ do
>   Policy.count.should == 1
>   policy = Policy.first
>   policy.secondary_risk = true
>   policy.save
> end
>
> Which are pretty explicit and leave no room for accidental abuse. What 
> the OP suggested would give you something more like this:
>
> Given /a Policy/ do
>   @it = Factory(:policy)
> end
>
> With /a secondary risk/ do
>   @it.secondary_risk = true
>   @it.save
> end
>
> I dunno actually. Now I type it out it doesn't seem so bad :)
>

As previously mentioned in the thread another way to phrase this is with 
step tables.  Here is the code I use:

http://gist.github.com/59007 
(related blog post: 
http://www.benmabey.com/2009/02/05/leveraging-test-data-builders-in-cucumber-steps/)

I have been using instance variables in my steps (but naming them after 
the model, i.e. @policy) but Matt's DB solution is nice in some 
respects.  Both ways fall apart when you have multiple polices, but in 
that case you should probably be passing in the name or some other 
identifying aspect of the model.  Anyways, it seems like a pattern is 
emerging on how to carry state to other steps when you have to.  I was 
bored so I combined both approaches:

module ObjectLocators

  def the_policy
    if @policy
      @policy
    else
      case Policy.count
      when 0
        raise "There is no @policy variable defined and no policy in the 
DB! Establish state in previous step or create a new policy."
      when 1
        Policy.first
      else
        raise "There are multiple policies in DB and no @policy variable 
set!  Please disambiguate the state in previous step."
      end
    end
  end

end


World { |world| world.extend(ObjectLocators) }

(this code is here: http://gist.github.com/79470)

Like I said, I was bored and haven't really tried this.  I don't know if 
I even like it, but I thought extracting out the patterns would be 
useful.  You could leverage factories just as I do in my previous gist 
to provide locator (locater?) for all of your models.


Great thread BTW.

-Ben



From phlip2005 at gmail.com  Sun Mar 15 13:05:03 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 15 Mar 2009 10:05:03 -0700
Subject: [rspec-users] custom, nested HTML matchers in RSpec
In-Reply-To: <57c63afe0903091704u3f1a9777u6d8af0f1fa470f2e@mail.gmail.com>
References: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>	<gp488o$3i8$1@ger.gmane.org>	<97ae2db00903091649u1e464c9n5658d4c41841d345@mail.gmail.com>
	<57c63afe0903091704u3f1a9777u6d8af0f1fa470f2e@mail.gmail.com>
Message-ID: <gpjcg2$47m$1@ger.gmane.org>

>>    response.body.should be_html_with{
>>      form :action => '/users' do
>>        fieldset do
>>          legend 'Personal Information'
>>          label 'First name'
>>          input :type => 'text', :name => 'user[first_name]'
>>        end
>>      end
>>    }

> Has anyone tried this? is it useful?

That assertion sucks! The actual sample HTML sez:

   <fieldset>
     <legend>Personal Information</legend>
     <ol>
       <li id="control_user_first_name">
         <label for="user_first_name">First name</label>
         <input type="text" name="user[first_name]" id="user_first_name" />
       </li>
     </ol>
   </fieldset>

The <legend> and <label> live in different containers, so they are not peers of 
each other. But the assertion specifies they are!

I think the assertion should fault until you specify at least this:

     response.body.should be_html_with{
       form :action => '/users' do
         fieldset do
           legend 'Personal Information'
           li do
             label 'First name'
             input :type => 'text', :name => 'user[first_name]'
           end
         end
       end
     }

Notice we have some conflicting requirements:

  - you can skip any tag
  - the reference should "look like" the sample (except it's in Ruby)

But you should not be able to skip a tag if its absence makes the reference 
"look different" from the sample. Hence, the test should require at least one of 
the <ol><li> tags that separate the two contexts...

(BTW the common verbiage for chemical tests of analytes here is "sample" for the 
substance submitted for analysis, and "reference" for the known sample used to 
calibrate the test.)

-- 
   Phlip


From evgeny.zislis at gmail.com  Sun Mar 15 13:13:14 2009
From: evgeny.zislis at gmail.com (evgeny.zislis at gmail.com)
Date: Sun, 15 Mar 2009 17:13:14 +0000
Subject: [rspec-users] evgeny.zislis has invited you to Spokeo
Message-ID: <49bd372a3be44_345033a64b413bb846711@mongrel10.tmail>

Hi rspec-users,<br/><br/> 

evgeny.zislis at gmail.com has invited you to try Spokeo,
which finds your friends' updates across the Web.

Your friends are already using Spokeo to follow you on Web Results.
Try Spokeo today to find what your friends are doing across 30 different social networks!

Click http://www.spokeo.com/public/join?c=4aa12a7f5dea606e8cc415534a44394bd67304c5 to accept your invitation.



-----
This invitation was sent with evgeny.zislis's approval.
If you wish to opt out of all future emails, go to http://www.spokeo.com/optout?c=r495251494854525749

Copyright (c) 2009 Spokeo, Inc. All rights reserved.
1685 Plymouth Street #200, Mountain View, CA 94043
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090315/bf81c44a/attachment.html>

From zach.dennis at gmail.com  Sun Mar 15 13:33:13 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Sun, 15 Mar 2009 13:33:13 -0400
Subject: [rspec-users] custom, nested HTML matchers in RSpec
In-Reply-To: <gpjcg2$47m$1@ger.gmane.org>
References: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>
	<gp488o$3i8$1@ger.gmane.org>
	<97ae2db00903091649u1e464c9n5658d4c41841d345@mail.gmail.com>
	<57c63afe0903091704u3f1a9777u6d8af0f1fa470f2e@mail.gmail.com>
	<gpjcg2$47m$1@ger.gmane.org>
Message-ID: <85d99afe0903151033h3809e8adqdc49ad9565005e4f@mail.gmail.com>

On Sun, Mar 15, 2009 at 1:05 PM, Phlip <phlip2005 at gmail.com> wrote:
>>> ? response.body.should be_html_with{
>>> ? ? form :action => '/users' do
>>> ? ? ? fieldset do
>>> ? ? ? ? legend 'Personal Information'
>>> ? ? ? ? label 'First name'
>>> ? ? ? ? input :type => 'text', :name => 'user[first_name]'
>>> ? ? ? end
>>> ? ? end
>>> ? }
>
>> Has anyone tried this? is it useful?
>
> That assertion sucks! The actual sample HTML sez:
>
> ?<fieldset>
> ? ?<legend>Personal Information</legend>
> ? ?<ol>
> ? ? ?<li id="control_user_first_name">
> ? ? ? ?<label for="user_first_name">First name</label>
> ? ? ? ?<input type="text" name="user[first_name]" id="user_first_name" />
> ? ? ?</li>
> ? ?</ol>
> ?</fieldset>
>
> The <legend> and <label> live in different containers, so they are not peers
> of each other. But the assertion specifies they are!

I didn't have the expectation that they were peers of each other, just
that they both existed somewhere in a fieldset tag. Any helper or
matchers used for spec'ing views should be as liberal as possible
while still communicating enough about the semantics of the page for
the example to be meaningful.

I would not expect nor want a matcher to default to verifying direct
descendant, sibling, or adjacent nodes. Those are best verified by a
person looking at the page. What I do care about is that fields in are
within a fieldset (but not necessarily immediately next to each
other).

>
> I think the assertion should fault until you specify at least this:
>
> ? ?response.body.should be_html_with{
> ? ? ?form :action => '/users' do
> ? ? ? ?fieldset do
> ? ? ? ? ?legend 'Personal Information'
> ? ? ? ? ?li do
> ? ? ? ? ? ?label 'First name'
> ? ? ? ? ? ?input :type => 'text', :name => 'user[first_name]'
> ? ? ? ? ?end
> ? ? ? ?end
> ? ? ?end
> ? ?}
>

I don't like this, we are specifying the "li" but that provides no
meaning of the page, it's strictly markup for presentation.

> Notice we have some conflicting requirements:
>
> ?- you can skip any tag
> ?- the reference should "look like" the sample (except it's in Ruby)
>
> But you should not be able to skip a tag if its absence makes the reference
> "look different" from the sample. Hence, the test should require at least
> one of the <ol><li> tags that separate the two contexts...
>
> (BTW the common verbiage for chemical tests of analytes here is "sample" for
> the substance submitted for analysis, and "reference" for the known sample
> used to calibrate the test.)
>
> --
> ?Phlip
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From matt at mattwynne.net  Sun Mar 15 14:37:01 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Sun, 15 Mar 2009 18:37:01 +0000
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <49BD324B.7060002@benmabey.com>
References: <C5E03A45.DAC5%THart@picagroup.com>	<88fd8ddc0903141310s19a4e187gdafc62e9aef1d016@mail.gmail.com>	<3115A6E6-F971-4754-9EB3-0255B1C6CBB1@picagroup.com>	<5F583F21-B5D3-438C-A702-1410E40B40EF@mattwynne.net>	<1126d7ae0903141730w636417e8y438385391ab5f0cc@mail.gmail.com>
	<4DCC2C10-05CF-48D3-BC0B-5CF38B5D3DD3@mattwynne.net>
	<49BD324B.7060002@benmabey.com>
Message-ID: <A8D344D7-F753-4BEF-B7DF-83EB0CBD9B4A@mattwynne.net>


On 15 Mar 2009, at 16:52, Ben Mabey wrote:

>
>> I know what you mean, and it would certainly make for nice readable  
>> scenarios. My worry is how maintainable the steps would be in the  
>> long run. I'm used to seeing steps like this:
>>
>> Given /the Policy has a secondary risk/ do
>>  Policy.count.should == 1
>>  policy = Policy.first
>>  policy.secondary_risk = true
>>  policy.save
>> end
>>
>> Which are pretty explicit and leave no room for accidental abuse.  
>> What the OP suggested would give you something more like this:
>>
>> Given /a Policy/ do
>>  @it = Factory(:policy)
>> end
>>
>> With /a secondary risk/ do
>>  @it.secondary_risk = true
>>  @it.save
>> end
>>
>> I dunno actually. Now I type it out it doesn't seem so bad :)
>>
>
> As previously mentioned in the thread another way to phrase this is  
> with step tables.  Here is the code I use:
>
> http://gist.github.com/59007 (related blog post: http://www.benmabey.com/2009/02/05/leveraging-test-data-builders-in-cucumber-steps/)
>
> I have been using instance variables in my steps (but naming them  
> after the model, i.e. @policy) but Matt's DB solution is nice in  
> some respects.  Both ways fall apart when you have multiple polices,  
> but in that case you should probably be passing in the name or some  
> other identifying aspect of the model.  Anyways, it seems like a  
> pattern is emerging on how to carry state to other steps when you  
> have to.  I was bored so I combined both approaches:
>
> module ObjectLocators
>
> def the_policy
>   if @policy
>     @policy
>   else
>     case Policy.count
>     when 0
>       raise "There is no @policy variable defined and no policy in  
> the DB! Establish state in previous step or create a new policy."
>     when 1
>       Policy.first
>     else
>       raise "There are multiple policies in DB and no @policy  
> variable set!  Please disambiguate the state in previous step."
>     end
>   end
> end
>
> end
>
>
> World { |world| world.extend(ObjectLocators) }
>
> (this code is here: http://gist.github.com/79470)
>
> Like I said, I was bored and haven't really tried this.  I don't  
> know if I even like it, but I thought extracting out the patterns  
> would be useful.  You could leverage factories just as I do in my  
> previous gist to provide locator (locater?) for all of your models.

We have some very similar code deep in the bowels of Songkick's  
features folder that is a little scrappy, but does help us solve this  
problem quite nicely.

Basically there's a regular expression that matches on phrases of the  
following form:

   the Widget
   the Widget "Foo"
   "Foo"

So you can use that in your step matchers like this:

   When /I delete (#{THE_THING})/ |identifier|
     thing_to_delete = identified_model(identifier)
   end

If you want to remember something just by the "Foo" label, you have to  
throw it into a collection, imaginatively named 'stuff', as you do so:

   stuff["Foo"] = Factory(:widget, :name => "Foo")

As I say it's a little scrappy as it's something we threw together  
ages ago and haven't really felt the need to revisit, but hopefully it  
will give someone some ideas:
http://gist.github.com/79496

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From phlip2005 at gmail.com  Sun Mar 15 14:47:39 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 15 Mar 2009 11:47:39 -0700
Subject: [rspec-users] custom, nested HTML matchers in RSpec
In-Reply-To: <85d99afe0903151033h3809e8adqdc49ad9565005e4f@mail.gmail.com>
References: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>	<gp488o$3i8$1@ger.gmane.org>	<97ae2db00903091649u1e464c9n5658d4c41841d345@mail.gmail.com>	<57c63afe0903091704u3f1a9777u6d8af0f1fa470f2e@mail.gmail.com>	<gpjcg2$47m$1@ger.gmane.org>
	<85d99afe0903151033h3809e8adqdc49ad9565005e4f@mail.gmail.com>
Message-ID: <gpjigd$kdt$1@ger.gmane.org>

Zach Dennis wrote:

> I didn't have the expectation that they were peers of each other, just
> that they both existed somewhere in a fieldset tag. Any helper or
> matchers used for spec'ing views should be as liberal as possible
> while still communicating enough about the semantics of the page for
> the example to be meaningful.
> 
> I would not expect nor want a matcher to default to verifying direct
> descendant, sibling, or adjacent nodes. Those are best verified by a
> person looking at the page. What I do care about is that fields in are
> within a fieldset (but not necessarily immediately next to each
> other).

However, I constantly must write extra test code just to check things are in the 
right order. Specifically, I could not use my original assert_xhtml to replace 
tests that checked some <option> values appeared in collating order. (Yes, tests 
on the model also checked those fields appeared in collating order, AND tests on 
the controller checked thru the "assigns" that those fields were in collating 
order...)

I am not going to target strict relationships, just the general order. But I 
have to draw the line somewhere!



From dchelimsky at gmail.com  Sun Mar 15 15:25:39 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 15 Mar 2009 14:25:39 -0500
Subject: [rspec-users] [ANN] rspec 1.2.0 Released
Message-ID: <57c63afe0903151225v5047d9f8nf306db41a8169ad3@mail.gmail.com>

rspec version 1.2.0 has been released!

Behaviour Driven Development for Ruby.

Changes:

### Version 1.2.0

WARNINGS:

  * If you use the ruby command to run specs instead of the spec command, you'll
    need to require 'spec/autorun' or they won't run. This won't affect you if
    you use the spec command or the Spec::Rake::SpecTask that ships with RSpec.

  * require 'spec/test/unit' to invoke test/unit interop if you're using
    RSpec's core (this is handled implicitly with spec-rails)

  * setup and teardown are gone - use before and after instead

    * you can still use setup and teardown if you're using
      Test::Unit::TestCase as the base ExampleGroup class (which is implicit
      in rspec-rails)

  * The matcher protocol has been improved. The old protocol is still
    supported, so as long as you're not monkey patching rspec's built-in
    matchers, or using extension libraries that do, this should not affect
    you. If you run into trouble, you'll just need to change:

    * failure_message          => failure_message_for_should
    * negative_failure_message => failure_message_for_should_not

  * All references to rubygems have been removed from within rspec's code.

    * See http://gist.github.com/54177 for rationale and suggestions on
      alternative approaches to loading rubygems

* deprecations

  * BaseTextFormatter#colourize - use colorize_failure instead.
  * BaseTextFormatter#magenta - use red instead.

* enhancements

  * cleaner integration with with heckle-1.4.2
  * allow registering example groups with a path-like key (Pat Maddox)
  * start DRb service at "druby://localhost:0" (Hongli Lai) - See
http://redmine.ruby-lang.org/issues/show/496
  * consistent reporting of errors as failures
  * added spec/test/unit as more intuitive path to loading test/unit interop lib
  * added explicit autorun feature for running specs with ruby command
  * added handling for does_not_match? for matchers that want to know
the context in which they were called
  * lots of ruby 1.9.1 compatibility fixes from Chad Humprhies
  * improved feedback from
be_kind_of/be_a_kind_of/be_instance_of/be_an_instance_of (Jakub
????astn??)
  * added --format silent (l) option, which is now the default when
running --heckle (Bob Aman)
  * sexy new custom matcher creation (Corey Haines & David Chelimsky -
initial concept by Yehuda Katz)
  * improved matcher protocol - old one is still supported, but new
one is cleaner and prefered

* bug fixes

  * support delegating operator matchers to subject with should_not
  * all arguments are included if --drb is specified in spec.opts
(Neil Buckley). Closes #671.
  * added --autospec option hack (used internally) to get --color to
work when using --drb and autospec.
  * Fixed mock framework failure message bug in which similar calls
were excluded from the output
  * cryptic error message on change.rb when the from value is wrong
(Michael Murray). Closes #706.

From dchelimsky at gmail.com  Sun Mar 15 15:25:44 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 15 Mar 2009 14:25:44 -0500
Subject: [rspec-users] [ANN] rspec-rails 1.2.0 Released
Message-ID: <57c63afe0903151225x577636b1mc7dce1d7af939e8@mail.gmail.com>

rspec-rails version 1.2.0 has been released!

* <http://rspec.info/>
* <http://wiki.github.com/dchelimsky/rspec>
* <http://wiki.github.com/dchelimsky/rspec/rails>
* <http://wiki.github.com/dchelimsky/rspec/upgrades>

Behaviour Driven Development for Ruby on Rails.

Changes:

### Version 1.2.0

IMPORTANT INFORMATION: Due to changes in Rails-2.3, there are some changes
in rspec-rails-1.2.0 that might break some specs in your existing apps. Be
sure to see http://wiki.github.com/dchelimsky/rspec/rails and
http://wiki.github.com/dchelimsky/rspec/upgrades for information about
upgrading.

IMPORTANT: This release includes the following
backwards-compatibility-breaking changes.

* rspec-rails supports rails 2.0.5, 2.1.2 and 2.2.2, and 2.3.1

  * We are no longer supporting 1.x versions of rails.

* expect_render and stub_render have been removed.

  * Both of these methods were deprecated in rspec-rails-1.1.5,
released in Sept, 2008.

* { route_for(args).should == "/path" } now delegates to
assert_generates (in rails)

  * see Upgrade.markdown for more information

* deprecations

  * controller.use_rails_error_handling! is deprecated
    * use rescue_action_in_public! (from rails) instead

* enhancements

  * Adding status codes to redirect_to matcher (Damian Janowski). Closes #570.
  * Initialize current URL before executing any examples in a
ViewExampleGroup (Wilson Bilkovich). Closes #654.
  * Support query strings in params_from (Wilson Bilkovich). Closes #652.
  * delegate route_for to assert_recognizes (less brittle)
  * it { should be_valid } (Kakutani). Closes #665.
  * controller is implicit subject in controller specs (Joe Ferris). #686.
  * template is implicit subject in view specs (Joe Ferris). #686.
  * redirect_to and render_template matchers can accept controller or
response (Joe Ferris). Closes #686.
  * generated specs use declarative docstrings
  * rspec_scaffold generator generates layout and stylesheet (per Rails-2.3)
  * add bypass_rescue for controller specs
  * infer template path from the first arg passed to describe in view specs
  * separate routing specs (in spec/routing)

* bug fixes

  * you no longer *have* to load ActionMailer to get specs to run. Closes #650.
  * query_params are now parsed by Rack::Utils.parse_query in
redirect_to matcher. Closes #684.
  * cleaned up spec_server (there was a bunch of pre-rails 2.0
material). Closes #685.
  * rspec's rake tasks are not loaded when running "rake gems" or any
of its subtasks
  * only warn when rspec is not installed when trying to invoke an
rspec rake task
  * support 2 arg version of ActionController::Base#render (reported
by Nathan Wilmes)
  * rake spec:server:start doesn't choke if there is no tmp directory
  * force cache_classes = false when running with spec_server. Closes #287.
  * keep spec_server working against edge rails (Jonathan Tron). Closes #685.
  * create lib/tasks if not present when running script/generate
rspec. Closes #687.
  * fixed regression (and added spec so it won't regress again) where
    render => :inline didn't render unless integrate_views was set
  * fixed nil.with_output_buffer bug in helper specs. Closes #719.

From pat.maddox at gmail.com  Sun Mar 15 15:32:01 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Sun, 15 Mar 2009 12:32:01 -0700
Subject: [rspec-users] custom, nested HTML matchers in RSpec
In-Reply-To: <85d99afe0903151033h3809e8adqdc49ad9565005e4f@mail.gmail.com>
References: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>
	<gp488o$3i8$1@ger.gmane.org>
	<97ae2db00903091649u1e464c9n5658d4c41841d345@mail.gmail.com>
	<57c63afe0903091704u3f1a9777u6d8af0f1fa470f2e@mail.gmail.com>
	<gpjcg2$47m$1@ger.gmane.org>
	<85d99afe0903151033h3809e8adqdc49ad9565005e4f@mail.gmail.com>
Message-ID: <9D41AAF0-158C-43EB-A8E9-798817317203@gmail.com>


On Mar 15, 2009, at 10:33 AM, Zach Dennis wrote:

> On Sun, Mar 15, 2009 at 1:05 PM, Phlip <phlip2005 at gmail.com> wrote:
>>>>   response.body.should be_html_with{
>>>>     form :action => '/users' do
>>>>       fieldset do
>>>>         legend 'Personal Information'
>>>>         label 'First name'
>>>>         input :type => 'text', :name => 'user[first_name]'
>>>>       end
>>>>     end
>>>>   }
>>
>>> Has anyone tried this? is it useful?
>>
>> That assertion sucks! The actual sample HTML sez:
>>
>>  <fieldset>
>>    <legend>Personal Information</legend>
>>    <ol>
>>      <li id="control_user_first_name">
>>        <label for="user_first_name">First name</label>
>>        <input type="text" name="user[first_name]"  
>> id="user_first_name" />
>>      </li>
>>    </ol>
>>  </fieldset>
>>
>> The <legend> and <label> live in different containers, so they are  
>> not peers
>> of each other. But the assertion specifies they are!
>
> I didn't have the expectation that they were peers of each other, just
> that they both existed somewhere in a fieldset tag. Any helper or
> matchers used for spec'ing views should be as liberal as possible
> while still communicating enough about the semantics of the page for
> the example to be meaningful.
>
> I would not expect nor want a matcher to default to verifying direct
> descendant, sibling, or adjacent nodes. Those are best verified by a
> person looking at the page. What I do care about is that fields in are
> within a fieldset (but not necessarily immediately next to each
> other).

Both of those points make sense to me.  What about


  response.body.should be_html_with{
     form :action => '/users' do
       fieldset do
         legend 'Personal Information'

         anything do
           label 'First name'
           input :type => 'text', :name => 'user[first_name]'
	end
       end
     end
   }

I dunno.  Zach's original attempt hardly "sucks".  But maybe you want  
to make the structure a bit more explicit?  Personally I think that it  
becomes too coupled to the HTML, and "anything {}" is added noise, but  
maybe that gets you moving in the right direction.

Pat

From jgoodsen at radsoft.com  Sun Mar 15 17:57:26 2009
From: jgoodsen at radsoft.com (John Goodsen)
Date: Sun, 15 Mar 2009 17:57:26 -0400
Subject: [rspec-users] Cucumber - Adding a step definition
In-Reply-To: <4DCC2C10-05CF-48D3-BC0B-5CF38B5D3DD3@mattwynne.net>
References: <C5E03A45.DAC5%THart@picagroup.com>
	<88fd8ddc0903141310s19a4e187gdafc62e9aef1d016@mail.gmail.com>
	<3115A6E6-F971-4754-9EB3-0255B1C6CBB1@picagroup.com>
	<5F583F21-B5D3-438C-A702-1410E40B40EF@mattwynne.net>
	<1126d7ae0903141730w636417e8y438385391ab5f0cc@mail.gmail.com>
	<4DCC2C10-05CF-48D3-BC0B-5CF38B5D3DD3@mattwynne.net>
Message-ID: <71498093-E35E-4543-AA93-6A8BCC8165F1@radsoft.com>

It's SRP applied to cucumber steps - just do it - keep your steps  
small and composable

Sent from my iPhone

On Mar 14, 2009, at 9:18 PM, Matt Wynne <matt at mattwynne.net> wrote:

>
> On 15 Mar 2009, at 00:30, Josh Chisholm wrote:
>
>>> That sounds like a great way to avoid the instance variable.
>>
>> Why is a named record preferable to an instance variable? It seems
>> like the coupling between steps is the same, but the coupled state is
>> stored differently. Maybe that's the point - stored differently.
>
> I guess my view is that having the state out front in the scenario  
> is preferable whenever possible (without cluttering up the feature  
> with noise) because it's clear, and there's less risk of a gap  
> opening up between what the step appears to do given its name, and  
> what it actually does when it runs. I take this gap seriously  
> because I put a great deal of trust our features.
>
>> I've been tempted to start scenario lines with "With" as well, to get
>> away from the combinatorial explosion of setup steps for complex
>> entities (think decorator pattern). I've used tables too, but mine
>> looked more like this:
>>
>> Given a policy with:
>> | PCF practice state | secondary risk |
>> | yes                         | yes                   |
>>
>> Is that nasty? It means we can use one step to set all possible
>> boolean attributes of a policy, but it doesn't read so well.
>
> I don't think that's nasty, it seems entirely appropriate for that  
> type of problem. It sounds like the type of acceptance tests I hear  
> people like Keith Braithwaite talking about putting together for  
> traders using Excel and Fit, and they seem to work really well.
>
> Thinking about this some more though, maybe there's an argument for  
> breaking the feature up into multiple features, and using Background  
> to set up the common state of the objects, then have a few scenarios  
> that build on this with different steps to tweak the objects. Just  
> another idea - it's really hard to judge without seeing more of the  
> specific features.
>
>> "With ..." would mean steps that were coupled to the "last mentioned
>> thing". That seems like a different kind of coupling - there is only
>> one piece of state involved (the last thing) rather than a map of
>> named things. But it's less explicit and implies that the "last  
>> thing"
>> needs to be updated by each step that mentions things.
>
> I know what you mean, and it would certainly make for nice readable  
> scenarios. My worry is how maintainable the steps would be in the  
> long run. I'm used to seeing steps like this:
>
> Given /the Policy has a secondary risk/ do
>  Policy.count.should == 1
>  policy = Policy.first
>  policy.secondary_risk = true
>  policy.save
> end
>
> Which are pretty explicit and leave no room for accidental abuse.  
> What the OP suggested would give you something more like this:
>
> Given /a Policy/ do
>  @it = Factory(:policy)
> end
>
> With /a secondary risk/ do
>  @it.secondary_risk = true
>  @it.save
> end
>
> I dunno actually. Now I type it out it doesn't seem so bad :)
>
>
>> Matt, going back to Mark's example, it sounds like you lean towards
>> the latter (i.e. repeat 'Reach from the Stars for 'Halo 3' throughout
>> the scenario). Is that correct?
>
> I guess my heuristic is something like this:
>
> 1. If I can simply refer to "the Widget" then I do, wherever possible.
>
> 2. If some attribute of the Widget is important in the scenario,  
> I'll explicitly set that attribute, and mention it again later in  
> the assertions. e.g.
>  Given a Widget named "Foo"
>  When I delete the Widget
>  Then I should see the text "bye bye Foo"
>
> 3. If I have to refer to multiple objects of the same class in one  
> scenario, then I use names to differentiate between them. e.g.
>  Given some Widgets named "Foo, Bar"
>  When I delete the Widget "Foo"
>  Then I should see 1 Widget
>  And I should see the text "Bar"
>
>
> Matt Wynne
> http://blog.mattwynne.net
> http://www.songkick.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

From vagostino at gmail.com  Sun Mar 15 14:51:24 2009
From: vagostino at gmail.com (Val)
Date: Sun, 15 Mar 2009 11:51:24 -0700 (PDT)
Subject: [rspec-users] How to use different mocking frameworks?
In-Reply-To: <57c63afe0903150609k3c552710h35e1896204680bef@mail.gmail.com>
References: <a439235d-7e07-41f0-ad60-33e201da0f89@v18g2000pro.googlegroups.com>
	<57c63afe0903142201h47fccdcbsc9cf8f5e8c8a03c9@mail.gmail.com> 
	<57c63afe0903142201p895c417q4de2932bceaec98d@mail.gmail.com> 
	<88fd8ddc0903150538j21e412a9hac8b23075f80b2c8@mail.gmail.com> 
	<57c63afe0903150609k3c552710h35e1896204680bef@mail.gmail.com>
Message-ID: <21ed4613-389b-4687-8b7e-70344cc86bae@k36g2000pri.googlegroups.com>

Okay.  Thanks for your responses.

I guess I'll try splitting them into separate directories.  Will each
directory automatically include it's own spec_helper.rb?

On Mar 15, 6:09?am, David Chelimsky <dchelim... at gmail.com> wrote:
> On Sun, Mar 15, 2009 at 7:38 AM, Andrew Premdas <aprem... at gmail.com> wrote:
> > Would it be possible to split the tests into separate runs - a bit like
> > having two different run configurations with cucumber?
>
> If you split the specs w/ rspec-mocks and those w/ mocha in separate
> dirs, you could run them each manually. Or you could create rake tasks
> to do it.
>
>
>
>
>
> > 2009/3/15 David Chelimsky <dchelim... at gmail.com>
>
> >> On Sun, Mar 15, 2009 at 12:01 AM, David Chelimsky <dchelim... at gmail.com>
> >> wrote:
> >> > On Sat, Mar 14, 2009 at 8:37 PM, Val <vagost... at gmail.com> wrote:
> >> >> Hi,
>
> >> >> I'm pretty new to Rspec, so hope someone can help me out with this.
>
> >> >> I'm leveraging a couple pre-existing applications in my current
> >> >> project, both have fairly robust test suites in Rspec already.
> >> >> However, one is using Rspec's builit in mocking, and the other is
> >> >> using mocha.
>
> >> >> If I set config.mock_with mocha in spec_helper.rb, then all of the
> >> >> rspec mocks fail. ?If I comment this out, all of the specs with mocha
> >> >> fail.
>
> >> >> Is there some way to set the mocking framework on a test and/or file
> >> >> basis?
>
> >> > Nope. Gotta pick one or the other. Reason - diff mock frameworks
> >> > invade Object in diff ways - mixing and matching is dangerous to your
> >> > health.
>
> >> I mean within one project. Of course you can use rspec/mocks in one,
> >> mocha in another, flexmock and rr in others.
>
> >> >> I've been all over Google, and can't seem to find a resolution
> >> >> to this. ?I really don't want to have to back through and rewrite
> >> >> someone else's test suite that is already working.
>
> >> >> Thanks in advance for your help,
> >> >> Val
> >> >> _______________________________________________
> >> >> rspec-users mailing list
> >> >> rspec-us... at rubyforge.org
> >> >>http://rubyforge.org/mailman/listinfo/rspec-users
>
> >> _______________________________________________
> >> rspec-users mailing list
> >> rspec-us... at rubyforge.org
> >>http://rubyforge.org/mailman/listinfo/rspec-users
>
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From rick.denatale at gmail.com  Sun Mar 15 12:49:00 2009
From: rick.denatale at gmail.com (Rick DeNatale)
Date: Sun, 15 Mar 2009 12:49:00 -0400
Subject: [rspec-users] An Update for my "Fan"
Message-ID: <deb2337a0903150949x37a9d82bj7ec86334bd82c249@mail.gmail.com>

On the assumption that someone here might actually occasionally read my blog
often enough to notice.
It's been down since sometime last Wednesday.

I've been aware of it since Wednesday night, and I've been working on
bringing it back.

If you're not interested, move along, these aren't the droids you are
looking for.  I apologize if you see this multiple times, but I cross-posted
it to the ruby/rails related lists to which I subscribe.

The blog, (and a few other public websites) is hosted on a server in my
house.  Sometime on Wednesday March 11, 2009, that server suffered a
catastrophic failure.  It looks like the IDE controller went bad and took
out one of the drives. I've since acquired a replacement server box from a
very generous friend, and I'm considering how to proceed.

It'll probably take a few days, and I might not be able to recover the
latest articles and comments, but I wanted to let anyone who was interested,
if such a person exists, what was up.

-- 
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090315/8492d4fc/attachment.html>

From dchelimsky at gmail.com  Sun Mar 15 18:13:18 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 15 Mar 2009 17:13:18 -0500
Subject: [rspec-users] How to use different mocking frameworks?
In-Reply-To: <21ed4613-389b-4687-8b7e-70344cc86bae@k36g2000pri.googlegroups.com>
References: <a439235d-7e07-41f0-ad60-33e201da0f89@v18g2000pro.googlegroups.com>
	<57c63afe0903142201h47fccdcbsc9cf8f5e8c8a03c9@mail.gmail.com>
	<57c63afe0903142201p895c417q4de2932bceaec98d@mail.gmail.com>
	<88fd8ddc0903150538j21e412a9hac8b23075f80b2c8@mail.gmail.com>
	<57c63afe0903150609k3c552710h35e1896204680bef@mail.gmail.com>
	<21ed4613-389b-4687-8b7e-70344cc86bae@k36g2000pri.googlegroups.com>
Message-ID: <57c63afe0903151513v7adf444bwc3c941956e37e482@mail.gmail.com>

On Sun, Mar 15, 2009 at 1:51 PM, Val <vagostino at gmail.com> wrote:
> Okay. ?Thanks for your responses.
>
> I guess I'll try splitting them into separate directories. ?Will each
> directory automatically include it's own spec_helper.rb?

Not sure I understand that question. You're going to be manually
splitting things up, right?

>
> On Mar 15, 6:09?am, David Chelimsky <dchelim... at gmail.com> wrote:
>> On Sun, Mar 15, 2009 at 7:38 AM, Andrew Premdas <aprem... at gmail.com> wrote:
>> > Would it be possible to split the tests into separate runs - a bit like
>> > having two different run configurations with cucumber?
>>
>> If you split the specs w/ rspec-mocks and those w/ mocha in separate
>> dirs, you could run them each manually. Or you could create rake tasks
>> to do it.
>>
>>
>>
>>
>>
>> > 2009/3/15 David Chelimsky <dchelim... at gmail.com>
>>
>> >> On Sun, Mar 15, 2009 at 12:01 AM, David Chelimsky <dchelim... at gmail.com>
>> >> wrote:
>> >> > On Sat, Mar 14, 2009 at 8:37 PM, Val <vagost... at gmail.com> wrote:
>> >> >> Hi,
>>
>> >> >> I'm pretty new to Rspec, so hope someone can help me out with this.
>>
>> >> >> I'm leveraging a couple pre-existing applications in my current
>> >> >> project, both have fairly robust test suites in Rspec already.
>> >> >> However, one is using Rspec's builit in mocking, and the other is
>> >> >> using mocha.
>>
>> >> >> If I set config.mock_with mocha in spec_helper.rb, then all of the
>> >> >> rspec mocks fail. ?If I comment this out, all of the specs with mocha
>> >> >> fail.
>>
>> >> >> Is there some way to set the mocking framework on a test and/or file
>> >> >> basis?
>>
>> >> > Nope. Gotta pick one or the other. Reason - diff mock frameworks
>> >> > invade Object in diff ways - mixing and matching is dangerous to your
>> >> > health.
>>
>> >> I mean within one project. Of course you can use rspec/mocks in one,
>> >> mocha in another, flexmock and rr in others.
>>
>> >> >> I've been all over Google, and can't seem to find a resolution
>> >> >> to this. ?I really don't want to have to back through and rewrite
>> >> >> someone else's test suite that is already working.
>>
>> >> >> Thanks in advance for your help,
>> >> >> Val
>> >> >> _______________________________________________
>> >> >> rspec-users mailing list
>> >> >> rspec-us... at rubyforge.org
>> >> >>http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> >> _______________________________________________
>> >> rspec-users mailing list
>> >> rspec-us... at rubyforge.org
>> >>http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> > _______________________________________________
>> > rspec-users mailing list
>> > rspec-us... at rubyforge.org
>> >http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From scott at railsnewbie.com  Sun Mar 15 18:18:12 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Sun, 15 Mar 2009 18:18:12 -0400
Subject: [rspec-users] How to use different mocking frameworks?
In-Reply-To: <21ed4613-389b-4687-8b7e-70344cc86bae@k36g2000pri.googlegroups.com>
References: <a439235d-7e07-41f0-ad60-33e201da0f89@v18g2000pro.googlegroups.com>	<57c63afe0903142201h47fccdcbsc9cf8f5e8c8a03c9@mail.gmail.com>
	<57c63afe0903142201p895c417q4de2932bceaec98d@mail.gmail.com>
	<88fd8ddc0903150538j21e412a9hac8b23075f80b2c8@mail.gmail.com>
	<57c63afe0903150609k3c552710h35e1896204680bef@mail.gmail.com>
	<21ed4613-389b-4687-8b7e-70344cc86bae@k36g2000pri.googlegroups.com>
Message-ID: <49BD7EA4.1080803@railsnewbie.com>

Val wrote:
> Okay.  Thanks for your responses.
>
> I guess I'll try splitting them into separate directories.  Will each
> directory automatically include it's own spec_helper.rb?
>   
Are you using any features from one mock framework that aren't present 
in the other?  If not, potentially you could, with some regexp prowess, 
rewrite all the mocks of one mocking framework to conform to the syntax 
of another.

Scott

> On Mar 15, 6:09 am, David Chelimsky <dchelim... at gmail.com> wrote:
>   
>> On Sun, Mar 15, 2009 at 7:38 AM, Andrew Premdas <aprem... at gmail.com> wrote:
>>     
>>> Would it be possible to split the tests into separate runs - a bit like
>>> having two different run configurations with cucumber?
>>>       
>> If you split the specs w/ rspec-mocks and those w/ mocha in separate
>> dirs, you could run them each manually. Or you could create rake tasks
>> to do it.
>>
>>
>>
>>
>>
>>     
>>> 2009/3/15 David Chelimsky <dchelim... at gmail.com>
>>>       
>>>> On Sun, Mar 15, 2009 at 12:01 AM, David Chelimsky <dchelim... at gmail.com>
>>>> wrote:
>>>>         
>>>>> On Sat, Mar 14, 2009 at 8:37 PM, Val <vagost... at gmail.com> wrote:
>>>>>           
>>>>>> Hi,
>>>>>>             
>>>>>> I'm pretty new to Rspec, so hope someone can help me out with this.
>>>>>>             
>>>>>> I'm leveraging a couple pre-existing applications in my current
>>>>>> project, both have fairly robust test suites in Rspec already.
>>>>>> However, one is using Rspec's builit in mocking, and the other is
>>>>>> using mocha.
>>>>>>             
>>>>>> If I set config.mock_with mocha in spec_helper.rb, then all of the
>>>>>> rspec mocks fail.  If I comment this out, all of the specs with mocha
>>>>>> fail.
>>>>>>             
>>>>>> Is there some way to set the mocking framework on a test and/or file
>>>>>> basis?
>>>>>>             
>>>>> Nope. Gotta pick one or the other. Reason - diff mock frameworks
>>>>> invade Object in diff ways - mixing and matching is dangerous to your
>>>>> health.
>>>>>           
>>>> I mean within one project. Of course you can use rspec/mocks in one,
>>>> mocha in another, flexmock and rr in others.
>>>>         
>>>>>> I've been all over Google, and can't seem to find a resolution
>>>>>> to this.  I really don't want to have to back through and rewrite
>>>>>> someone else's test suite that is already working.
>>>>>>             
>>>>>> Thanks in advance for your help,
>>>>>> Val
>>>>>> _______________________________________________
>>>>>> rspec-users mailing list
>>>>>> rspec-us... at rubyforge.org
>>>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>>>>             
>>>> _______________________________________________
>>>> rspec-users mailing list
>>>> rspec-us... at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>>         
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-us... at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>       
>> _______________________________________________
>> rspec-users mailing list
>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
>>     
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>   


From phlip2005 at gmail.com  Sun Mar 15 19:42:17 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 15 Mar 2009 16:42:17 -0700
Subject: [rspec-users] custom, nested HTML matchers in RSpec
In-Reply-To: <9D41AAF0-158C-43EB-A8E9-798817317203@gmail.com>
References: <49B4BE42.1020109__18059.4487851069$1236582753$gmane$org@gmail.com>	<gp488o$3i8$1@ger.gmane.org>	<97ae2db00903091649u1e464c9n5658d4c41841d345@mail.gmail.com>	<57c63afe0903091704u3f1a9777u6d8af0f1fa470f2e@mail.gmail.com>	<gpjcg2$47m$1@ger.gmane.org>	<85d99afe0903151033h3809e8adqdc49ad9565005e4f@mail.gmail.com>
	<9D41AAF0-158C-43EB-A8E9-798817317203@gmail.com>
Message-ID: <gpk3op$2s6$1@ger.gmane.org>

Pat Maddox wrote:

> I dunno.  Zach's original attempt hardly "sucks".

That was David Chelimsky's attempt - Zach seconded it. But I was replying to myself.

More important, the tie-breaker here is very simple:

     When the assertion fails, can it
     tell you exactly how to fix things?

That means if you must make the assertion less strict, you should get a clue 
_how_ to make it less strict!

> maybe that gets you moving in the right direction.

Don't make me tell you under what circumstances I learned graph theory. (-:

-- 
   Phlip


From phlip2005 at gmail.com  Sun Mar 15 23:39:43 2009
From: phlip2005 at gmail.com (Phlip)
Date: Sun, 15 Mar 2009 20:39:43 -0700
Subject: [rspec-users] [ANN] assert2/xhtml specifies your HTML by example
Message-ID: <49BDC9FF.8070600@gmail.com>



Rubies:

assert_xhtml now works with RSpec. (Call it ".should be_html_with{}" !)

This is its Rails functional test aspect:

     get :edit_user, :id => users(:Moses).id
     scope = self

     assert_xhtml do
       form :action => '/users' do
         fieldset do
           legend 'Personal Information'
           label 'First name'
           input :type => 'text',
                 :name => 'user[first_name]'
                 :value => scope.users(:Moses).first_name
         end
       end
     end

The assertion tests your form "by example". Your page must contain a form with 
the given action, and it must contain at least the listed elements, attributes, 
and text. Anything you don't care about - anything your designers might change - 
you simply leave out of the example.

(The example is actually Nokogiri::HTML::Builder notation, so anything Nokogiri 
can do, the assertion can do. But that's why we needed that 'scope' variable, as 
a kind of "messenger rope", to call your test-side methods inside the block. 
Otherwise, Nokogiri would dutifully convert them into HTML!)

Here's a similar test, in RSpec:

   it 'should have a cute form' do
     render '/users/new'

     response.body.should be_html_with{
       form :action => '/users' do
         fieldset do
           legend 'Personal Information'
           label 'First nome'
           input :type => 'text', :name => 'user[first_name]'
         end
       end
     }
   end

Oh, except it has a bug in it! Here's the diagnostic:

'/users/new should have a cute form' FAILED

Could not find this reference...

<form action="/users">
   <fieldset>
   <legend>Personal Information</legend>
   <label>First nome</label>
   <input type="text" name="user[first_name]">
</fieldset></form>

...in these sample(s)...

<form action="/users">
   <fieldset>
     <legend>Personal Information</legend>
     <ol>
       <li id="control_user_first_name">
         <label for="user_first_name">First name</label>
         <input type="text" name="user[first_name]" id="user_first_name">
        </li>
     </ol>
   </fieldset>
</form>

Notice, as usual, the specification diagnostic only contained the start of the 
match. The example with <form action="/users"> worked.

That's all there is to it. Write anything you like inside the block, and if the 
assertion can't find it, it will explain why it can't. Install the gem like this:

   gem install nokogiri assert2  #  make sure the later is 0.3.9!

Then use require 'assert2/xhtml', in either the test/unit or RSpec environments.

This project is wide-open for suggestions - with < 200 lines of code there's 
plenty of room for more features!

-- 
   Phlip
   http://www.zeroplayer.com/


From yun at nomitor.com  Mon Mar 16 07:00:02 2009
From: yun at nomitor.com (Yun Huang Yong)
Date: Mon, 16 Mar 2009 22:00:02 +1100
Subject: [rspec-users] Testing return value of a block argument
Message-ID: <49BE3132.6060305@nomitor.com>

Hi,

I'm using Log4r and one of its neat features is its handling of blocks 
such that you can do:
   log.debug { "Something bad happened" + some_expensive_method() }
instead of:
   log.debug("Something bad happened" + some_expensive_method())

The benefit of the former is that some_expensive_method() is not 
executed until the debug() method executes so if your log level doesn't 
include DEBUG you don't suffer the performance hit of calling 
some_expensive_method() needlessly.

Is there any way to test what the resultant log message is from 
evaluating the block?

i.e. something like:
   log_mock.should_receive(:debug) { |log_block|
     # execute log_block, and check its return value
   }

I have a simple bit of code to tinker with: http://gist.github.com/79820

Thanks in advance,
yun

-- 
Yun Huang Yong
yun at nomitor.com                  ...nom nom nom
--

From chrismear at gmail.com  Mon Mar 16 09:21:09 2009
From: chrismear at gmail.com (Chris Mear)
Date: Mon, 16 Mar 2009 13:21:09 +0000
Subject: [rspec-users] 'Missing template' when using send_data to render
	response
Message-ID: <68af9cd10903160621q7a095088r63ae510dd7aea784@mail.gmail.com>

Hi there,
Just upgraded to Rails 2.3/RSpec 1.2.0, and I've got a controller that uses
send_data to render a response. In the controller spec, I have:

controller.should_receive(:send_data).with(...)

The send_data method calls 'render' internally, but obviously when I
stub/mock out the send_data method this doesn't get called. So, with the
changes to controller/template isolation in 1.2.0, I now get a 'missing
template' error on this example as the controller tries to render the
default template.

Any suggestions to the best way to resolve this? My hunch is that it'll need
an extension to RenderObserver in rspec-rails, but I'm struggling to do the
right thing in my first foray into the RSpec source. Or maybe I shouldn't be
mocking the send_data call at all, but rather then underlying render call?

Many thanks,
Chris Mear
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090316/275666e3/attachment-0001.html>

From dchelimsky at gmail.com  Mon Mar 16 09:28:23 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 16 Mar 2009 08:28:23 -0500
Subject: [rspec-users] 'Missing template' when using send_data to render
	response
In-Reply-To: <68af9cd10903160621q7a095088r63ae510dd7aea784@mail.gmail.com>
References: <68af9cd10903160621q7a095088r63ae510dd7aea784@mail.gmail.com>
Message-ID: <57c63afe0903160628k4ee25debt1519ef23ed41e443@mail.gmail.com>

2009/3/16 Chris Mear <chrismear at gmail.com>:
> Hi there,
> Just upgraded to Rails 2.3/RSpec 1.2.0, and I've got a controller that uses
> send_data to render a response. In the controller spec, I have:
> controller.should_receive(:send_data).with(...)
> The send_data method calls 'render' internally, but obviously when I
> stub/mock out the send_data method this doesn't get called. So, with the
> changes to controller/template isolation in 1.2.0, I now get a 'missing
> template' error on this example as the controller tries to render the
> default template.
> Any suggestions to the best way to resolve this? My hunch is that it'll need
> an extension to RenderObserver in rspec-rails, but I'm struggling to do the
> right thing in my first foray into the RSpec source. Or maybe I shouldn't be
> mocking the send_data call at all, but rather then underlying render call?

How about controller.stub!(:render) also? You want
should_receive(:send_data) because that's the spec, right?

> Many thanks,
> Chris Mear
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From chrismear at gmail.com  Mon Mar 16 10:23:11 2009
From: chrismear at gmail.com (Chris Mear)
Date: Mon, 16 Mar 2009 14:23:11 +0000
Subject: [rspec-users] 'Missing template' when using send_data to render
	response
In-Reply-To: <57c63afe0903160628k4ee25debt1519ef23ed41e443@mail.gmail.com>
References: <68af9cd10903160621q7a095088r63ae510dd7aea784@mail.gmail.com>
	<57c63afe0903160628k4ee25debt1519ef23ed41e443@mail.gmail.com>
Message-ID: <6B8FC84B-D93B-4483-BD92-A9F2244839AE@gmail.com>

On 16 Mar 2009, at 13:28, David Chelimsky wrote:

> 2009/3/16 Chris Mear <chrismear at gmail.com>:
>> Hi there,
>> Just upgraded to Rails 2.3/RSpec 1.2.0, and I've got a controller  
>> that uses
>> send_data to render a response. In the controller spec, I have:
>> controller.should_receive(:send_data).with(...)
>> The send_data method calls 'render' internally, but obviously when I
>> stub/mock out the send_data method this doesn't get called. So,  
>> with the
>> changes to controller/template isolation in 1.2.0, I now get a  
>> 'missing
>> template' error on this example as the controller tries to render the
>> default template.
>> Any suggestions to the best way to resolve this? My hunch is that  
>> it'll need
>> an extension to RenderObserver in rspec-rails, but I'm struggling  
>> to do the
>> right thing in my first foray into the RSpec source. Or maybe I  
>> shouldn't be
>> mocking the send_data call at all, but rather then underlying  
>> render call?
>
> How about controller.stub!(:render) also? You want
> should_receive(:send_data) because that's the spec, right?

Oh, of course! That works beautifully. Too much overthinking on my part.

Cheers,
Chris


From chris at feedmechocolate.com  Mon Mar 16 10:13:21 2009
From: chris at feedmechocolate.com (Chris Mear)
Date: Mon, 16 Mar 2009 14:13:21 +0000
Subject: [rspec-users] 'Missing template' when using send_data to render
	response
In-Reply-To: <57c63afe0903160628k4ee25debt1519ef23ed41e443@mail.gmail.com>
References: <68af9cd10903160621q7a095088r63ae510dd7aea784@mail.gmail.com>
	<57c63afe0903160628k4ee25debt1519ef23ed41e443@mail.gmail.com>
Message-ID: <68af9cd10903160713y3cb4c974jde772478dd7ba167@mail.gmail.com>

2009/3/16 David Chelimsky <dchelimsky at gmail.com>

> 2009/3/16 Chris Mear <chrismear at gmail.com>:
> > Hi there,
> > Just upgraded to Rails 2.3/RSpec 1.2.0, and I've got a controller that
> uses
> > send_data to render a response. In the controller spec, I have:
> > controller.should_receive(:send_data).with(...)
> > The send_data method calls 'render' internally, but obviously when I
> > stub/mock out the send_data method this doesn't get called. So, with the
> > changes to controller/template isolation in 1.2.0, I now get a 'missing
> > template' error on this example as the controller tries to render the
> > default template.
> > Any suggestions to the best way to resolve this? My hunch is that it'll
> need
> > an extension to RenderObserver in rspec-rails, but I'm struggling to do
> the
> > right thing in my first foray into the RSpec source. Or maybe I shouldn't
> be
> > mocking the send_data call at all, but rather then underlying render
> call?
>
> How about controller.stub!(:render) also? You want
> should_receive(:send_data) because that's the spec, right?


Oh, of course! That works beautifully. Too much overthinking on my part.

Cheers,
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090316/057944a7/attachment.html>

From nick at deadorange.com  Mon Mar 16 11:33:28 2009
From: nick at deadorange.com (Nick Hoffman)
Date: Mon, 16 Mar 2009 11:33:28 -0400
Subject: [rspec-users] Testing return value of a block argument
In-Reply-To: <49BE3132.6060305@nomitor.com>
References: <49BE3132.6060305@nomitor.com>
Message-ID: <16827fa20903160833m581b69ddqfc42d5d380588a2c@mail.gmail.com>

On Mon, Mar 16, 2009 at 7:00 AM, Yun Huang Yong <yun at nomitor.com> wrote:
> Hi,
>
> I'm using Log4r and one of its neat features is its handling of blocks such
> that you can do:
> ?log.debug { "Something bad happened" + some_expensive_method() }
> instead of:
> ?log.debug("Something bad happened" + some_expensive_method())
>
> The benefit of the former is that some_expensive_method() is not executed
> until the debug() method executes so if your log level doesn't include DEBUG
> you don't suffer the performance hit of calling some_expensive_method()
> needlessly.
>
> Is there any way to test what the resultant log message is from evaluating
> the block?
>
> i.e. something like:
> ?log_mock.should_receive(:debug) { |log_block|
> ? ?# execute log_block, and check its return value
> ?}
>
> I have a simple bit of code to tinker with: http://gist.github.com/79820
>
> Thanks in advance,
> yun

Hi Yun. Have a look at #and_yield , described at
http://rspec.info/documentation/mocks/message_expectations.html .

Cheers,
Nick

From mark at mwilden.com  Mon Mar 16 12:03:26 2009
From: mark at mwilden.com (Mark Wilden)
Date: Mon, 16 Mar 2009 09:03:26 -0700
Subject: [rspec-users] Testing return value of a block argument
In-Reply-To: <16827fa20903160833m581b69ddqfc42d5d380588a2c@mail.gmail.com>
References: <49BE3132.6060305@nomitor.com>
	<16827fa20903160833m581b69ddqfc42d5d380588a2c@mail.gmail.com>
Message-ID: <3c30da400903160903y4d610e91mcdb373cf0c77d6dd@mail.gmail.com>

On Mon, Mar 16, 2009 at 8:33 AM, Nick Hoffman <nick at deadorange.com> wrote:
>>
>> Is there any way to test what the resultant log message is from evaluating
>> the block?
>>
>> i.e. something like:
>> ?log_mock.should_receive(:debug) { |log_block|
>> ? ?# execute log_block, and check its return value
>> ?}
>
> Hi Yun. Have a look at #and_yield , described at
> http://rspec.info/documentation/mocks/message_expectations.html .

That was my first thought, but and_yield stubs what the method will
yield, not what it should yield. It's like and_return.

///ark

From lists at ruby-forum.com  Mon Mar 16 12:16:16 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 16 Mar 2009 17:16:16 +0100
Subject: [rspec-users] Rails 2.3.2 and Cucumber 0.1.16
Message-ID: <f29a8cdf223b073621046973ae2c39dd@ruby-forum.com>

I am encountering a problem relating to cucumber and Rails 2.3.2 which
has something to do with Rails 2.3.2 but I am unable, as of yet, to
determine exactly what is the cause.

Situation: environment.rb RAILS_GEM_VERSION = '2.3.2'

$ cucumber -r features \
    features/components/authentication/authentication.feature
...
      Page load was not successful (Code: 500):
      ...
      <title>Action Controller: Exception caught</title>
      ...
      <Missing template ../../public/hll_terms_and_conditions.html
         in view path app/views</code></pre>


      Extracted source (around line #18:
      15:               :id =>; 'link_new_user_session'
      16:   -%>
      17:   <br/>
      18:   <%= render :file =>
'../../public/hll_terms_and_conditions.html' ->
      19:
      20: <% else ->
      21:
      ...

3 scenarios
3 steps passed
3 steps failed
10 steps skipped

Situation: environment.rb RAILS_GEM_VERSION = '2.2.2'

$ cucumber -r features \
    features/components/authentication/authentication.feature
...
3 scenarios
16 steps passed

Now, when I start the script/server and go to the project root then I
get no errors from either R2.2.2 or R2.3.2.  I am guessing that
something in R2.3.2 is changing the pwd from RAILS_ROOT for the feature
steps/tests only, since the file specified in the render statement does
exist (and is correctly displayed by an actual running application).
But, that is only a guess.

Any ideas as to what is going on here?
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Mon Mar 16 12:28:15 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 16 Mar 2009 17:28:15 +0100
Subject: [rspec-users] Rails 2.3.2 and Cucumber 0.1.16
In-Reply-To: <f29a8cdf223b073621046973ae2c39dd@ruby-forum.com>
References: <f29a8cdf223b073621046973ae2c39dd@ruby-forum.com>
Message-ID: <770ef622a83ebb7990232382a6b5cd97@ruby-forum.com>

James Byrne wrote:

> 
> Now, when I start the script/server and go to the project root then I
> get no errors from either R2.2.2 or R2.3.2.  I am guessing that
> something in R2.3.2 is changing the pwd from RAILS_ROOT for the feature
> steps/tests only, since the file specified in the render statement does
> exist (and is correctly displayed by an actual running application).
> But, that is only a guess.
> 

And a wrong one.  In both versions RAILS_ROOT is nil and pwd is the 
application root directory.  So, it must be something else.
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Mon Mar 16 15:32:44 2009
From: lists at ruby-forum.com (James Byrne)
Date: Mon, 16 Mar 2009 20:32:44 +0100
Subject: [rspec-users] Rails 2.3.2 and Cucumber 0.1.16
In-Reply-To: <770ef622a83ebb7990232382a6b5cd97@ruby-forum.com>
References: <f29a8cdf223b073621046973ae2c39dd@ruby-forum.com>
	<770ef622a83ebb7990232382a6b5cd97@ruby-forum.com>
Message-ID: <9be195810b146eba04804d8f7f9e9f26@ruby-forum.com>

It is starting to look like this is a webrat problem.
-- 
Posted via http://www.ruby-forum.com/.

From matt at mattwynne.net  Mon Mar 16 15:33:20 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Mon, 16 Mar 2009 19:33:20 +0000
Subject: [rspec-users] Testing return value of a block argument
In-Reply-To: <49BE3132.6060305@nomitor.com>
References: <49BE3132.6060305@nomitor.com>
Message-ID: <FF03F805-AF31-4417-BE0D-1C361CB55A40@mattwynne.net>


On 16 Mar 2009, at 11:00, Yun Huang Yong wrote:

> I'm using Log4r

You might want to check out this library, which seems to be better  
maintained these days:

http://github.com/TwP/logging/tree/master

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From erikpukinskis at gmail.com  Mon Mar 16 19:35:36 2009
From: erikpukinskis at gmail.com (Erik Pukinskis)
Date: Mon, 16 Mar 2009 16:35:36 -0700
Subject: [rspec-users] Is there any way to use a second webrat session
	temporarily?
Message-ID: <bd07856f0903161635l3252900bldfde168095ad0b50@mail.gmail.com>

Dear Rspecucumberatubyists,

I have a Rails app that creates subdomains, and I'd like to verify
them in a cucumber feature like so:

  When I visit http://blingo.myapp.com
  Then I should see "Welcome to blingo!"

The trouble is, webrat's visit method strips the domain off, and keeps
only the path, so it ends up going to my site root instead of the
subdomain.

I tried creating a separate mechanize session that is used for full urls:

require 'webrat/mechanize'

Given /^I visit (.*)$/ do |url|
  if url.match(/^http:\/\//)
    session = Webrat::MechanizeSession.new
    session.visit(url)
    response = session.response.body
  else
    visit url
  end
end

And that seems to work, but then when my "Then" step goes to find the
response, it doesn't find anything.  The "response" variable becomes
nil somewhere along the way. The step that's matching there is the
default one that ships with cucumber:

Then /^I should see "([^"]*)"$/ do |text|
  response.should contain(text)
end

Why is my response getting erased?

Love,
Erik

From scott at railsnewbie.com  Mon Mar 16 23:26:24 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Mon, 16 Mar 2009 23:26:24 -0400
Subject: [rspec-users] respond_to matcher
Message-ID: <49BF1860.5080706@railsnewbie.com>


I noticed this strange behaviour in a spec, and was wondering if it was 
considered a bug (it certainly took me by surprise):

http://gist.github.com/80261

The respond_to matcher specs seem to show this behaviour as intended:

http://gist.github.com/80262

Scott



From Peer.Allan at canadadrugs.com  Mon Mar 16 22:22:51 2009
From: Peer.Allan at canadadrugs.com (Peer Allan)
Date: Mon, 16 Mar 2009 21:22:51 -0500
Subject: [rspec-users] Route failure with Rails2.3 and rspec1.2
Message-ID: <C5E473AB.126D8%Peer.Allan@canadadrugs.com>

Hello all,

I have a spec for a route that used to pass under Rails 2.2.2 and rspec
1.1.12, but can?t figure out what is wrong since I updated. Here is the
assertion:

route_for(
        {
          :controller         => 'purchase_orders',
          :action             => 'update',
          :company_id         => "32",
          :id                 => '1'
        }).should == "/companies/32/purchase_orders/1"

Which results in this failure

Test::Unit::AssertionFailedError in 'PurchaseOrdersController route
generation routes #update to /companies/32/purchase_orders/1'
The recognized options <{"action"=>"show",
 "id"=>"1",
 "controller"=>"vendor_purchase_orders",
 "company_id"=>"company-name"}> did not match <{"action"=>"update",
 "id"=>"1",
 "controller"=>"vendor_purchase_orders",
 "company_id"=>"company-name"}>, difference: <{"action"=>"update"}>

As you may have guessed the route is defined like so:

Map.resources :companies do |c|
  c.resources :purchase_orders
End

Any ideas?

Peer Allan


From dchelimsky at gmail.com  Tue Mar 17 00:20:53 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 16 Mar 2009 23:20:53 -0500
Subject: [rspec-users] Route failure with Rails2.3 and rspec1.2
In-Reply-To: <C5E473AB.126D8%Peer.Allan@canadadrugs.com>
References: <C5E473AB.126D8%Peer.Allan@canadadrugs.com>
Message-ID: <57c63afe0903162120y3c101447g2beb1cb025749153@mail.gmail.com>

On Mon, Mar 16, 2009 at 9:22 PM, Peer Allan <Peer.Allan at canadadrugs.com> wrote:
> Hello all,
>
> I have a spec for a route that used to pass under Rails 2.2.2 and rspec
> 1.1.12, but can?t figure out what is wrong since I updated. Here is the
> assertion:
>
> route_for(
> ? ? ? ?{
> ? ? ? ? ?:controller ? ? ? ? => 'purchase_orders',
> ? ? ? ? ?:action ? ? ? ? ? ? => 'update',
> ? ? ? ? ?:company_id ? ? ? ? => "32",
> ? ? ? ? ?:id ? ? ? ? ? ? ? ? => '1'
> ? ? ? ?}).should == "/companies/32/purchase_orders/1"

route_for changed in rspec-rails-1.2.0

Please see the upgrade notes for more info:
http://github.com/dchelimsky/rspec-rails/blob/master/Upgrade.markdown

Cheers,
David
>
> Which results in this failure
>
> Test::Unit::AssertionFailedError in 'PurchaseOrdersController route
> generation routes #update to /companies/32/purchase_orders/1'
> The recognized options <{"action"=>"show",
> ?"id"=>"1",
> ?"controller"=>"vendor_purchase_orders",
> ?"company_id"=>"company-name"}> did not match <{"action"=>"update",
> ?"id"=>"1",
> ?"controller"=>"vendor_purchase_orders",
> ?"company_id"=>"company-name"}>, difference: <{"action"=>"update"}>
>
> As you may have guessed the route is defined like so:
>
> Map.resources :companies do |c|
> ?c.resources :purchase_orders
> End
>
> Any ideas?
>
> Peer Allan
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From lists at ruby-forum.com  Tue Mar 17 01:56:39 2009
From: lists at ruby-forum.com (aa aa)
Date: Tue, 17 Mar 2009 06:56:39 +0100
Subject: [rspec-users] cucumber, watir and new window
Message-ID: <96d1329c74b1de84a181b63b67121647@ruby-forum.com>

Hi,
I'm using cucumber and watir and when I want to test i'm on the right
page, I use
 browser.url.should =~ "blah"
but how do i test that if the code opens a new window properly? The
browser.url is still, correctly, set to the original page url.
-- 
Posted via http://www.ruby-forum.com/.

From apremdas at gmail.com  Tue Mar 17 06:04:39 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Tue, 17 Mar 2009 10:04:39 +0000
Subject: [rspec-users] [Webrat][RSpec]
Message-ID: <88fd8ddc0903170304va8e7220hcdb9fe42ce3979c4@mail.gmail.com>

Hi All,
Since upgrading rspec to 1.2 I am seeing behavior that a web browser is
being opened when there is a problem in a page that a feature visits.

Is this behavior intentional and if so can I turn it off. Having thirty
browser windows open up when I introduce an error that breaks alot of
features is a real pain in the backside.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090317/1cec039f/attachment.html>

From apremdas at gmail.com  Tue Mar 17 06:07:09 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Tue, 17 Mar 2009 10:07:09 +0000
Subject: [rspec-users] [Webrat][RSpec] Features opening browser windows
Message-ID: <88fd8ddc0903170307n46d5ace0x337a32f5292bad89@mail.gmail.com>

Apologies for previous message without proper subject

Since upgrading rspec to 1.2 I am seeing behavior that a web browser is
being opened when there is a problem in a page that a feature visits.

Is this behavior intentional and if so can I turn it off. Having thirty
browser windows open up when I introduce an error that breaks alot of
features is a real pain in the backside.

TIA

Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090317/1c01e9a6/attachment.html>

From levy at levycarneiro.com  Tue Mar 17 07:21:57 2009
From: levy at levycarneiro.com (Levy Carneiro Jr.)
Date: Tue, 17 Mar 2009 08:21:57 -0300
Subject: [rspec-users] Spec'ing chained calls
In-Reply-To: <e3e91d130903130725ob1c450avb3fd5c35e1ba1ec0@mail.gmail.com>
References: <fca2ab280903130704h3733d6ecg9afcf6d78edfc52f@mail.gmail.com>
	<e3e91d130903130725ob1c450avb3fd5c35e1ba1ec0@mail.gmail.com>
Message-ID: <fca2ab280903170421nccccb9ej1d04a8df78ebadc0@mail.gmail.com>

Thanks for your examples, Chris!

regards,
Levy

On Fri, Mar 13, 2009 at 11:25 AM, Chris Flipse <cflipse at gmail.com> wrote:

> You might want to look into using a null object, and breaking that first
> spec up into several examples
> (a null object returns itself when sent a message it doesn't know how to
> handle)
>
>
> http://gist.github.com/78570
>
> I've built more than a few named_scope chains using this pattern, and it
> seems to work out okay.  This approach is somewhat less brittle, in that
> it's not going to explode horribly if you change the order of the chain in
> the main method (if something else reads better, say) ...
>
> Downside is that it _won't_ catch if you add new methods to the chain.  If
> that's a concern, you could complicate the setup a bit, to narrow the focus
> to _just_ the methods you want.
>
>      @new_search = mock(Twitter::Search)
>
>      new_search.stub!(:containing => new_search, :since => new_search, :not_retweeted => new_search, :fetch => new_search)
>
>
> On Fri, Mar 13, 2009 at 10:04 AM, Levy Carneiro Jr. <levy at levycarneiro.com
> > wrote:
>
>> Hello!
>>
>> I'm trying to spec a method, that has several chained calls.
>>
>> http://gist.github.com/78562 (spec)
>> http://gist.github.com/78563 (model)
>>
>> In the first spec, I'm trying to focus on the method calls that have to be
>> made, and the arguments they should receive.
>>
>> Is there a better way to spec the behaviour for these chained calls? It
>> just seems too many lines to me :)
>>
>>
>> Thanks a lot!
>> Levy
>> PS: I'm using my branch of the twitter gem, at
>> http://github.com/levycarneiro/twitter, which just adds this method
>> 'not_retweeted'.
>>
>>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
>
> --
> // anything worth taking seriously is worth making fun of
> // http://blog.devcaffeine.com/
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090317/c0a45071/attachment.html>

From zuperinfinite at gmail.com  Tue Mar 17 08:44:51 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Tue, 17 Mar 2009 13:44:51 +0100
Subject: [rspec-users] [Webrat][RSpec] Features opening browser windows
In-Reply-To: <88fd8ddc0903170307n46d5ace0x337a32f5292bad89@mail.gmail.com>
References: <88fd8ddc0903170307n46d5ace0x337a32f5292bad89@mail.gmail.com>
Message-ID: <600BF7CA-0C30-42CB-AC12-90DE627CBE5B@gmail.com>


On 17-mrt-2009, at 11:07, Andrew Premdas wrote:

> Apologies for previous message without proper subject
>
> Since upgrading rspec to 1.2 I am seeing behavior that a web  
> browser is being opened when there is a problem in a page that a  
> feature visits.
>
> Is this behavior intentional and if so can I turn it off. Having  
> thirty browser windows open up when I introduce an error that  
> breaks alot of features is a real pain in the backside.

It's a config option in Webrat. Somehow it's default set to true,  
used to be false.

Put

Webrat.configure do |config|
   config.mode = :rails
   config.open_error_files = false
end

in cucumbers env.rb

cheers,
bartz

From matt at mattwynne.net  Tue Mar 17 09:53:10 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Tue, 17 Mar 2009 13:53:10 +0000
Subject: [rspec-users] Is there any way to use a second webrat session
	temporarily?
In-Reply-To: <bd07856f0903161635l3252900bldfde168095ad0b50@mail.gmail.com>
References: <bd07856f0903161635l3252900bldfde168095ad0b50@mail.gmail.com>
Message-ID: <76F4D443-3EFD-4BB2-A4FF-C7D5A7B37299@mattwynne.net>


On 16 Mar 2009, at 23:35, Erik Pukinskis wrote:

> Dear Rspecucumberatubyists,
>
> I have a Rails app that creates subdomains, and I'd like to verify
> them in a cucumber feature like so:
>
>  When I visit http://blingo.myapp.com
>  Then I should see "Welcome to blingo!"
>
> The trouble is, webrat's visit method strips the domain off, and keeps
> only the path, so it ends up going to my site root instead of the
> subdomain.
>
> I tried creating a separate mechanize session that is used for full  
> urls:
>
> require 'webrat/mechanize'
>
> Given /^I visit (.*)$/ do |url|
>  if url.match(/^http:\/\//)
>    session = Webrat::MechanizeSession.new
>    session.visit(url)
>    response = session.response.body
>  else
>    visit url
>  end
> end
>
> And that seems to work, but then when my "Then" step goes to find the
> response, it doesn't find anything.  The "response" variable becomes
> nil somewhere along the way. The step that's matching there is the
> default one that ships with cucumber:
>
> Then /^I should see "([^"]*)"$/ do |text|
>  response.should contain(text)
> end
>
> Why is my response getting erased?
>
> Love,
> Erik

I think response is a method or read-only property, set by webrat when  
you call #visit, so it's not something you can just set like that. I  
would have a look in the webrat source code and see if you can figure  
out why the subdomain is being stripped out of the request. I have a  
feeling I remember someone asking about this before.

Also note that webrat has its own mailing list on google groups which  
might be a better place to find answers.

HTH,

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From aslak.hellesoy at gmail.com  Tue Mar 17 14:29:46 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Tue, 17 Mar 2009 14:29:46 -0400
Subject: [rspec-users] HTML output truncated in Cucumber
In-Reply-To: <1237311807.v2.mailanyonewebmail-122159@fuse113>
References: <1237311807.v2.mailanyonewebmail-122159@fuse113>
Message-ID: <8d961d900903171129m4b12b27emaaae8b07c067e1b3@mail.gmail.com>

On Tue, Mar 17, 2009 at 1:43 PM, Bob Payne <bob at electroglide.biz> wrote:

> Aslak,
>

Hi Bob,
please use the mailing list:
http://wiki.github.com/aslakhellesoy/cucumber/get-in-touch


> I am using the
>
> --format html --out results.html --no_color
>
> directive in rake when running my cucumber tests.
>
> The last bit of output seems to be truncated.  Same is true for Pretty and
> Profile.
>

Ok


>
> We are using version 0.1.16.  We have not upgraded because we are running
> (unfortunately) in windows and the output of the pretty is much more
> usable without the ANSI codes.
>

You can get ANSI colors on windows - just gem install win32console.


>
> Is this just an older version problem or is there some solution we should
> look at?
>

Try upgrading to aslakhellesoy-cucumber (on GitHub).
If you run into problems with it, please describe in detail what the
problems are.

Cheers,
Aslak


>
> -bob payne
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090317/0566ee6c/attachment.html>

From apremdas at gmail.com  Tue Mar 17 17:07:58 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Tue, 17 Mar 2009 21:07:58 +0000
Subject: [rspec-users] [Webrat][RSpec] Features opening browser windows
In-Reply-To: <600BF7CA-0C30-42CB-AC12-90DE627CBE5B@gmail.com>
References: <88fd8ddc0903170307n46d5ace0x337a32f5292bad89@mail.gmail.com>
	<600BF7CA-0C30-42CB-AC12-90DE627CBE5B@gmail.com>
Message-ID: <88fd8ddc0903171407k39738f0bpfa260254c7516fea@mail.gmail.com>

Thanks Bart, spot on :)

2009/3/17 Bart Zonneveld <zuperinfinite at gmail.com>

>
> On 17-mrt-2009, at 11:07, Andrew Premdas wrote:
>
>  Apologies for previous message without proper subject
>>
>> Since upgrading rspec to 1.2 I am seeing behavior that a web browser is
>> being opened when there is a problem in a page that a feature visits.
>>
>> Is this behavior intentional and if so can I turn it off. Having thirty
>> browser windows open up when I introduce an error that breaks alot of
>> features is a real pain in the backside.
>>
>
> It's a config option in Webrat. Somehow it's default set to true, used to
> be false.
>
> Put
>
> Webrat.configure do |config|
>  config.mode = :rails
>  config.open_error_files = false
> end
>
> in cucumbers env.rb
>
> cheers,
> bartz
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090317/3959a800/attachment.html>

From sfeley at gmail.com  Wed Mar 18 00:04:22 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Wed, 18 Mar 2009 00:04:22 -0400
Subject: [rspec-users] [Webrat][RSpec]
In-Reply-To: <88fd8ddc0903170304va8e7220hcdb9fe42ce3979c4@mail.gmail.com>
References: <88fd8ddc0903170304va8e7220hcdb9fe42ce3979c4@mail.gmail.com>
Message-ID: <1fb4df0903172104r2133884fg219f706006f0e4be@mail.gmail.com>

2009/3/17 Andrew Premdas <apremdas at gmail.com>:
> Hi All,
> Since upgrading rspec to 1.2 I am seeing?behavior?that a web browser is
> being opened when there is a problem in a page that a feature visits.
> Is this?behavior?intentional and if so can I turn it off. Having thirty
> browser windows open up when I introduce an error that breaks alot of
> features is a real pain in the backside.

Agreed.  It's especially annoying because I run Cucumber in autospec,
and have a few scenarios that deliberately test for some exceptions to
be caught and 404s to be thrown.  These pop the browser page every
time they come up in the background, stealing focus and disrupting my
workflow.

This is not the principle of least surprise.  Magic should not happen
when it wasn't specifically asked for.


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From tom at zudio.com.au  Wed Mar 18 01:00:23 2009
From: tom at zudio.com.au (Tom Meier)
Date: Wed, 18 Mar 2009 16:00:23 +1100
Subject: [rspec-users] mock_model with Rspec/Rspec-rails 1.2 and Rails 2.3
Message-ID: <04328BE7-CA92-474B-8742-0EE815A3C715@zudio.com.au>

Hi,

Not sure if anyone has faced this problem yet and managed to resolve  
it... I understand Rspec 'decoupled' the mock frameworks, however it  
works fine with Rails 2.2 but fails in 2.3...


Can anyone give me any pointers as to what changes are required in  
spec_helper.rb to ensure mock_model methods are available?


Within console I can mock an object with the following:

require 'spec'
require 'spec/mocks'
require 'spec/mocks/mock.rb'
require 'spec/rails/mocks.rb'


include Spec
include Spec::Mocks
include Spec::Mocks::Methods
include Spec::Mocks::ExampleMethods
include Spec::Rails::Mocks

mock_model(User)
=> #<User:0x1c04c10 @name="User_1001">


However, within spec_helper.rb


require "erb"
ENV["RAILS_ENV"] = "test"
require File.expand_path(File.dirname(__FILE__) + "/../config/ 
environment")

require 'spec/autorun'
require 'spec/rails'
require 'spec/mocks'
require 'spec/mocks/mock.rb'
require 'spec/rails/mocks.rb'

Spec::Runner.configure do |config|
    config.include Spec::Mocks
    config.include Spec::Mocks::Methods
    config.include Spec::Mocks::ExampleMethods
    config.include Spec::Rails::Mocks


end




---

With the above settings when our specs run (while on rails 2.3 and  
rspec 1.2), the following error occurs :

undefined method `mock_model=' for #<User:0x2d5887c>



Any pointers in the right direction would be much appreciated...





Best regards,

Tom






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090318/272afa21/attachment.html>

From dchelimsky at gmail.com  Wed Mar 18 02:37:20 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 18 Mar 2009 01:37:20 -0500
Subject: [rspec-users] mock_model with Rspec/Rspec-rails 1.2 and Rails
	2.3
In-Reply-To: <04328BE7-CA92-474B-8742-0EE815A3C715@zudio.com.au>
References: <04328BE7-CA92-474B-8742-0EE815A3C715@zudio.com.au>
Message-ID: <57c63afe0903172337pc0b76dav90921048095159c0@mail.gmail.com>

2009/3/18 Tom Meier <tom at zudio.com.au>:
> Hi,
> Not sure if anyone has faced this problem yet and managed to resolve it... I
> understand Rspec 'decoupled' the mock frameworks, however it works fine with
> Rails 2.2 but fails in 2.3...

Why do you put decoupled in quotes? Are you mocking decoupling of mocking?

> Can anyone give me any pointers as to what changes are required in
> spec_helper.rb to ensure mock_model methods are available?
>
> Within console I can mock an object with the following:
> require 'spec'
> require 'spec/mocks'
> require 'spec/mocks/mock.rb'
> require 'spec/rails/mocks.rb'
>
> include Spec
> include Spec::Mocks
> include Spec::Mocks::Methods
> include Spec::Mocks::ExampleMethods
> include Spec::Rails::Mocks
> mock_model(User)
> => #<User:0x1c04c10 @name="User_1001">
>
> However, within spec_helper.rb
>
> require "erb"
> ENV["RAILS_ENV"] = "test"
> require File.expand_path(File.dirname(__FILE__) + "/../config/environment")
> require 'spec/autorun'
> require 'spec/rails'
> require 'spec/mocks'
> require 'spec/mocks/mock.rb'
> require 'spec/rails/mocks.rb'
> Spec::Runner.configure do |config|
> ?? config.include Spec::Mocks
> ?? config.include Spec::Mocks::Methods
> ?? config.include Spec::Mocks::ExampleMethods
> ?? config.include Spec::Rails::Mocks
>
> end
>
>
>
> ---
> With the above settings when our specs run (while on rails 2.3 and rspec
> 1.2), the following error occurs :
> undefined method `mock_model=' for #<User:0x2d5887c>

The error says "mock_model=", which indicates that you're trying to
set it somewhere in your code. Please show us the spec that is failing
with a reference to the line that is raising that error.

Thx

>
>
> Any pointers in the right direction would be much appreciated...
>
>
>
>
> Best regards,
> Tom
>
>
>
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From evgeny.bogdanov at gmail.com  Wed Mar 18 06:18:23 2009
From: evgeny.bogdanov at gmail.com (Evgeny Bogdanov)
Date: Wed, 18 Mar 2009 03:18:23 -0700 (PDT)
Subject: [rspec-users] [rspec] Stubbing partials in view specs
In-Reply-To: <6E3760F3-15A0-4E25-9E70-7DF948A4C8B2@gmail.com>
References: <71C878F7-574B-4287-8D5B-FAD56FD8AFB5@gmail.com> 
	<57c63afe0901200629y1bb6b1e8vf0acaf2f2c7d5a2@mail.gmail.com> 
	<6E3760F3-15A0-4E25-9E70-7DF948A4C8B2@gmail.com>
Message-ID: <6391f308-2ce8-4727-8049-be56e6ed242a@l16g2000yqo.googlegroups.com>

Hello,
I have a problem similar to one mentioned in this post.
I call a partial inside another partial.
_mother.haml contains:
render :partial => "children/child"

In mother_spec.rb file I am trying to stub the render call.
Here is a working version:
=============
    template.should_receive(:render)
    template.stub!(:render)

    render :partial => 'mother'
============
I would prefer to specify that the partial I am stubbing is "children/
child",
however the following code doesn't work for me:
===========
    template.stub!(:render).with(hash_including(:partial => 'children/
child'))
    template.expect_render(:partial => 'children/child')

    render :partial => 'mother'

: Mock 'render_proxy' expected :render with ({:partial=>"children/
child"}) once, but received it 0 times
===========
Is it possible to stub the render call with specific partial name?

Thank you in advance,
Evgeny

On Jan 20, 5:35?pm, Bart Zonneveld <zuperinfin... at gmail.com> wrote:
> On 20-jan-2009, at 15:29, David Chelimsky wrote:
>
> > On Tue, Jan 20, 2009 at 7:44 AM, Bart Zonneveld ?
> > <zuperinfin... at gmail.com> wrote:
> >> Hey list,
>
> >> As a good BDDer I want to test my views in isolation.
>
> > Sort of. A *good* BDDer wants to *specify* views in isolation. Testing
> > is for testers :)
>
> You're right! I tend to talk a lot to non-programmers, and they get ?
> that glaze-in-the-distance look in their eyes, whenever I mention ?
> specifiy, spec'ing, or what have you :).
>
> >> And as a good rails
> >> programmer, I separate views into partials when needed. So, when ?
> >> testing my
> >> views, I want tostubout rendering of partials in my views. I'm ?
> >> working on
> >> upgrading an app from rails 2.1.2 to 2.2.2, using the latest rspec ?
> >> and
> >> rspec-rails.
>
> >> I used to throw template.stub!(:render) in a before(:each) block ?
> >> and be done
> >> with it
>
> > That sounds kinda risky because you could be ignoring partials that
> > get rendered that you don't want to be rendered.
>
> It is, most definately.
>
> >> , but that doesn't work anymore. I can understand why, but now I have
> >> to do something like template.stub!(:render).with(hash_including
> >> (:partial =>
> >> anything)). Except for when I'm testing a partial, then I need to ?
> >> replace
> >> the anything with every partial I'm rendering in my partial.
>
> >> Is this the correct way,
>
> > Seems like the only way at the moment. Wouldn't call it correct or ?
> > incorrect.
>
> I would call it ugly :). Not only do I have to remember the ?
> hash_including part, but also the anything (and not :anything).
> Conceptually, I like the template.stub!(:render). Irendera ?
> template, on which Istuball the renders. Whether that's risky or ?
> not is a different discussion.
>
> >> or is there perhaps something like
> >> template.stub_partials :only => [], :except => [] ?
>
> > Nothing like this exists. Seems like a reasonable idea. Feel free to
> > submit a feature request, or better yet, a patch to
> >http://rspec.lighthouseapp.com
>
> Will do!
>
> cheers,
> bartz
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From harmaarts at gmail.com  Wed Mar 18 08:03:55 2009
From: harmaarts at gmail.com (Harm)
Date: Wed, 18 Mar 2009 05:03:55 -0700 (PDT)
Subject: [rspec-users] Speccing module which should be included in controller
Message-ID: <603a0375-a3a7-4f29-919e-7a74565c6df2@g38g2000yqd.googlegroups.com>

Dear all,

I have a module ApiAccessControl which is included in all controllers
which deal with the API. It sees if the users is valid, logs etc etc.

I want to see if this module does what it is supposed to but I dont
want to test that in every single controller dealing with the API. So
I created a file api_access_control_spec.rb with this content:

require File.dirname(__FILE__) + '/../spec_helper'

class ApiAccessControlTestController < ApplicationController
  include ApiAccessControl
end

describe ApiAccessControlTestController do
  describe "without valid credentials" do
    it "should respond with a 401 Unauthorized on the GET 'index'" do
      get "index"
      response.response_code.should == 401
    end
  end
end

This works by the grace that my routes file has a fallback map.connect
':controller/:action/:id'. I never use that fallback only for this
particular test. Is there anyway to get rid of this entry in my
routes.rb?

I tried something like this is a before block:
ActionController::Routing::RouteSet.new.add_route("index", :controller
=> "api_access_control_test", :action => "index")

But that doesn't seem to work. How do you guys test this sort of
stuff?

Harm

From matt at mattwynne.net  Wed Mar 18 12:16:14 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Wed, 18 Mar 2009 16:16:14 +0000
Subject: [rspec-users] Speccing module which should be included in
	controller
In-Reply-To: <603a0375-a3a7-4f29-919e-7a74565c6df2@g38g2000yqd.googlegroups.com>
References: <603a0375-a3a7-4f29-919e-7a74565c6df2@g38g2000yqd.googlegroups.com>
Message-ID: <8482A755-D6CA-4EA6-A481-850381248A45@mattwynne.net>


On 18 Mar 2009, at 12:03, Harm wrote:

> Dear all,
>
> I have a module ApiAccessControl which is included in all controllers
> which deal with the API. It sees if the users is valid, logs etc etc.
>
> I want to see if this module does what it is supposed to but I dont
> want to test that in every single controller dealing with the API. So
> I created a file api_access_control_spec.rb with this content:
>
> require File.dirname(__FILE__) + '/../spec_helper'
>
> class ApiAccessControlTestController < ApplicationController
>  include ApiAccessControl
> end
>
> describe ApiAccessControlTestController do
>  describe "without valid credentials" do
>    it "should respond with a 401 Unauthorized on the GET 'index'" do
>      get "index"
>      response.response_code.should == 401
>    end
>  end
> end
>
> This works by the grace that my routes file has a fallback map.connect
> ':controller/:action/:id'. I never use that fallback only for this
> particular test. Is there anyway to get rid of this entry in my
> routes.rb?
>
> I tried something like this is a before block:
> ActionController::Routing::RouteSet.new.add_route("index", :controller
> => "api_access_control_test", :action => "index")
>
> But that doesn't seem to work. How do you guys test this sort of
> stuff?
>
> Harm

See this thread:
http://www.nabble.com/How-to-Spec-a-Module-to-be-used-in-a-Controller-td20128726.html

It's slow though.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From pat.maddox at gmail.com  Wed Mar 18 12:54:10 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Wed, 18 Mar 2009 09:54:10 -0700
Subject: [rspec-users] mock_model with Rspec/Rspec-rails 1.2 and Rails
	2.3
In-Reply-To: <57c63afe0903172337pc0b76dav90921048095159c0@mail.gmail.com>
References: <04328BE7-CA92-474B-8742-0EE815A3C715@zudio.com.au>
	<57c63afe0903172337pc0b76dav90921048095159c0@mail.gmail.com>
Message-ID: <DDEE99F3-B42D-4E55-A839-727ED0F3C08A@gmail.com>

On Mar 17, 2009, at 11:37 PM, David Chelimsky wrote:

> 2009/3/18 Tom Meier <tom at zudio.com.au>:
>>
>> With the above settings when our specs run (while on rails 2.3 and  
>> rspec
>> 1.2), the following error occurs :
>> undefined method `mock_model=' for #<User:0x2d5887c>
>
> The error says "mock_model=", which indicates that you're trying to
> set it somewhere in your code. Please show us the spec that is failing
> with a reference to the line that is raising that error.

I think this would require him to do
self.mock_model = blah
or
send("mock_model=", blah)

which seems really, really weird.  Oh well.  Some code ought to clear  
it up.

Pat


From pat.maddox at gmail.com  Wed Mar 18 12:57:56 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Wed, 18 Mar 2009 09:57:56 -0700
Subject: [rspec-users] Speccing module which should be included in
	controller
In-Reply-To: <603a0375-a3a7-4f29-919e-7a74565c6df2@g38g2000yqd.googlegroups.com>
References: <603a0375-a3a7-4f29-919e-7a74565c6df2@g38g2000yqd.googlegroups.com>
Message-ID: <2254632F-B414-4F34-A54A-F7BF28AB301E@gmail.com>

On Mar 18, 2009, at 5:03 AM, Harm wrote:

> This works by the grace that my routes file has a fallback map.connect
> ':controller/:action/:id'. I never use that fallback only for this
> particular test. Is there anyway to get rid of this entry in my
> routes.rb?

map.connect ':controller/:action/:id' if RAILS_ENV == 'test'

yahtzee

From aslak.hellesoy at gmail.com  Wed Mar 18 15:16:55 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Wed, 18 Mar 2009 15:16:55 -0400
Subject: [rspec-users] ANN Cucumber 0.2.0
Message-ID: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>

I'm happy to announce the release of Cucumber 0.2.0.

There are a some really exciting new features in this release. Some of the
ones I find most valuable are:
* tags
* better output
* autoformatting of features
* better i18n
* Ruby 1.9 support
* background
* guess mode

Full release notes are available at
http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt
With this release I expect the formatter API to remain fairly stable. Check
out the Cucumber::Ast::Visitor class for the full API.

Thanks a lot to everyone who has contributed so far. The big internal
refactoring has now stabilised, so it should be easier to contribute again!

Enjoy!

(As usual, wait an hour or two for the gem to rsync around the Rubyforge
mirror park)

(::) Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090318/9894e895/attachment.html>

From dchelimsky at gmail.com  Wed Mar 18 15:21:42 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 18 Mar 2009 14:21:42 -0500
Subject: [rspec-users] ANN Cucumber 0.2.0
In-Reply-To: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
References: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
Message-ID: <57c63afe0903181221h2c0d5638t5967ea448271b2f2@mail.gmail.com>

2009/3/18 aslak hellesoy <aslak.hellesoy at gmail.com>:
> I'm happy to announce the release of Cucumber 0.2.0.
>
> There are a some really exciting new features in this release. Some of the
> ones I find most valuable are:
> * tags
> * better output
> * autoformatting of features
> * better i18n
> * Ruby 1.9 support
> * background
> * guess mode
>
> Full release notes are available at
> http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt
> With this release I expect the formatter API to remain fairly stable. Check
> out the Cucumber::Ast::Visitor class for the full API.
>
> Thanks a lot to everyone who has contributed so far. The big internal
> refactoring has now stabilised, so it should be easier to contribute again!

Congrats!!!!!!!

>
> Enjoy!
>
> (As usual, wait an hour or two for the gem to rsync around the Rubyforge
> mirror park)
>
> (::) Aslak (::)

What's this, like a cucumber in each ear?

>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From seatmanu at gmail.com  Wed Mar 18 16:08:46 2009
From: seatmanu at gmail.com (Emmanuel Pinault)
Date: Wed, 18 Mar 2009 13:08:46 -0700
Subject: [rspec-users] ANN Cucumber 0.2.0
In-Reply-To: <57c63afe0903181221h2c0d5638t5967ea448271b2f2@mail.gmail.com>
References: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
	<57c63afe0903181221h2c0d5638t5967ea448271b2f2@mail.gmail.com>
Message-ID: <21798F7D-6CC7-4CF3-989A-0552033E5F02@gmail.com>

Great! Is there  section for the new hook on reporting? I used the old  
reporting to customized some of our HTML reports and wonder if you  
have the new hooks documented somewhere?

Also what is the rerun formatter?

Thanks

Emmanuel

On Mar 18, 2009, at 12:21 PM, David Chelimsky wrote:

> 2009/3/18 aslak hellesoy <aslak.hellesoy at gmail.com>:
>> I'm happy to announce the release of Cucumber 0.2.0.
>>
>> There are a some really exciting new features in this release. Some  
>> of the
>> ones I find most valuable are:
>> * tags
>> * better output
>> * autoformatting of features
>> * better i18n
>> * Ruby 1.9 support
>> * background
>> * guess mode
>>
>> Full release notes are available at
>> http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt
>> With this release I expect the formatter API to remain fairly  
>> stable. Check
>> out the Cucumber::Ast::Visitor class for the full API.
>>
>> Thanks a lot to everyone who has contributed so far. The big internal
>> refactoring has now stabilised, so it should be easier to  
>> contribute again!
>
> Congrats!!!!!!!
>
>>
>> Enjoy!
>>
>> (As usual, wait an hour or two for the gem to rsync around the  
>> Rubyforge
>> mirror park)
>>
>> (::) Aslak (::)
>
> What's this, like a cucumber in each ear?
>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From joe at josephwilk.net  Wed Mar 18 16:13:21 2009
From: joe at josephwilk.net (Joseph Wilk)
Date: Wed, 18 Mar 2009 20:13:21 +0000
Subject: [rspec-users] ANN Cucumber 0.2.0
In-Reply-To: <57c63afe0903181221h2c0d5638t5967ea448271b2f2@mail.gmail.com>
References: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
	<57c63afe0903181221h2c0d5638t5967ea448271b2f2@mail.gmail.com>
Message-ID: <49C155E1.3050203@josephwilk.net>

David Chelimsky wrote:
> 2009/3/18 aslak hellesoy <aslak.hellesoy at gmail.com>:
>   
>> I'm happy to announce the release of Cucumber 0.2.0.
>>
>> There are a some really exciting new features in this release. Some of the
>> ones I find most valuable are:
>> * tags
>> * better output
>> * autoformatting of features
>> * better i18n
>> * Ruby 1.9 support
>> * background
>> * guess mode
>>
>> Full release notes are available at
>> http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt
>> With this release I expect the formatter API to remain fairly stable. Check
>> out the Cucumber::Ast::Visitor class for the full API.
>>
>> Thanks a lot to everyone who has contributed so far. The big internal
>> refactoring has now stabilised, so it should be easier to contribute again!
>>     
>
> Congrats!!!!!!!
>
>   
>> Enjoy!
>>
>> (As usual, wait an hour or two for the gem to rsync around the Rubyforge
>> mirror park)
>>
>> (::) Aslak (::)
>>     
>
> What's this, like a cucumber in each ear?
>   
Cucumber earrings are clearly in this year :)

http://en.dawanda.com/product/2413009-Cucumber-NonAllergic-Stud-Earrings-Polymer-Clay

-- 
Joseph Wilk
http://blog.josephwilk.net


>   
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>>     
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
>   



From joahking at gmail.com  Wed Mar 18 16:13:40 2009
From: joahking at gmail.com (Joaquin Rivera Padron)
Date: Wed, 18 Mar 2009 21:13:40 +0100
Subject: [rspec-users] ANN Cucumber 0.2.0
In-Reply-To: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
References: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
Message-ID: <8277b7f40903181313s6084c57dm9720bbef8afa114f@mail.gmail.com>

>
> Full release notes are available at
> http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt
>
> (::) Aslak (::)


wow! amazing how much the cukes have accomplished,

keep on the good work

cheers,
joaquin

-- 
www.least-significant-bit.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090318/49c6edbc/attachment.html>

From rick.denatale at gmail.com  Wed Mar 18 16:28:28 2009
From: rick.denatale at gmail.com (Rick DeNatale)
Date: Wed, 18 Mar 2009 16:28:28 -0400
Subject: [rspec-users] Problem spec'ing ActionMailer with attachment,
	body not getting 	rendered.
Message-ID: <deb2337a0903181328u284e7e6ep168867b50ce000c2@mail.gmail.com>

I've got a simple ActionMailer::Base subclass:
class InfoMailer < ActionMailer::Base

    def info(user, zip_name)
    recipients user.email
    subject "Requested Info"
    attachment(:content_type => "application/zip",
                :filename => zip_name,
                :body => File.read(zip_name))
    body(:message => "Here is the Info that you Requested")
  end
end

I'm trying to spec this following
http://www.rubytutorials.net/2008/02/26/small-rspec-revelations-actionmailer/

describe AssetsInfoMailer do
  before(:each) do
    @user = mock_model(User,
        :email => @user_email = "somewhere at over.the.rainbow",
        :full_name => "The Wicked Witch of the West"
        )
    ActionMailer::Base.delivery_method = :test
    ActionMailer::Base.perform_deliveries = true
    ActionMailer::Base.deliveries = []
  end

  describe ".info" do
    before(:each) do
      @path = 'xyz.zip'
      @attachment_body = 'zip_file_contents'
      File.stub!(:read).and_return(@attachment_body)
      @the_mail = AssetsInfoMailer.deliver_info(@user, at path)
      @attachments = @the_mail.attachments
    end

    it "should have the right body" do
      @the_mail.body.should == ""
    end
  end

The expectation of an empty string is just to see what's actually getting
returned, the result is:

1)
'AssetsInfoMailer.info should have the right body' FAILED
expected: "",
     got: "Attachment: xyz.zip\n" (using ==)

It's looking like the mail template never got rendered, and body is giving
me the attachment since it's the only part.

I've got one other mailer method in that mailer which doesn't contain an
attachement, and it's body comes out fine.

I'm not sure what's going on here, and I'd appreciate any
help/insight/condolences...



-- 
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090318/0522d691/attachment.html>

From seatmanu at gmail.com  Wed Mar 18 16:31:36 2009
From: seatmanu at gmail.com (Emmanuel Pinault)
Date: Wed, 18 Mar 2009 13:31:36 -0700
Subject: [rspec-users] Printing scenario count,
	pass and fail rather than steps
Message-ID: <7A36B327-95D0-4E41-8726-CFAA6D9AF14A@gmail.com>

Is there a way to do that using some options? I had to override the  
default reporting in 0.1.16 and prior.. But now with 0.2 the formatter  
look different and was wondering if this is something already possilbe  
or if I need to still create my custom report

Thanks

Emmanuel

From rick.denatale at gmail.com  Wed Mar 18 16:33:01 2009
From: rick.denatale at gmail.com (Rick DeNatale)
Date: Wed, 18 Mar 2009 16:33:01 -0400
Subject: [rspec-users] Problem spec'ing ActionMailer with attachment,
	body not getting 	rendered.
In-Reply-To: <deb2337a0903181328u284e7e6ep168867b50ce000c2@mail.gmail.com>
References: <deb2337a0903181328u284e7e6ep168867b50ce000c2@mail.gmail.com>
Message-ID: <deb2337a0903181333x517430c6xf12153fa33d43d90@mail.gmail.com>

On Wed, Mar 18, 2009 at 4:28 PM, Rick DeNatale <rick.denatale at gmail.com>wrote:

> I've got a simple ActionMailer::Base subclass:
> class InfoMailer < ActionMailer::Base
>
>     def info(user, zip_name)
>     recipients user.email
>     subject "Requested Info"
>     attachment(:content_type => "application/zip",
>                 :filename => zip_name,
>                 :body => File.read(zip_name))
>     body(:message => "Here is the Info that you Requested")
>   end
> end
>
> I'm trying to spec this following
> http://www.rubytutorials.net/2008/02/26/small-rspec-revelations-actionmailer/
>
> describe AssetsInfoMailer do
>   before(:each) do
>     @user = mock_model(User,
>         :email => @user_email = "somewhere at over.the.rainbow",
>         :full_name => "The Wicked Witch of the West"
>         )
>     ActionMailer::Base.delivery_method = :test
>     ActionMailer::Base.perform_deliveries = true
>     ActionMailer::Base.deliveries = []
>   end
>
>   describe ".info" do
>     before(:each) do
>       @path = 'xyz.zip'
>       @attachment_body = 'zip_file_contents'
>       File.stub!(:read).and_return(@attachment_body)
>       @the_mail = AssetsInfoMailer.deliver_info(@user, at path)
>       @attachments = @the_mail.attachments
>     end
>
>     it "should have the right body" do
>       @the_mail.body.should == ""
>     end
>   end
>
> The expectation of an empty string is just to see what's actually getting
> returned, the result is:
>
> 1)
> 'AssetsInfoMailer.info should have the right body' FAILED
> expected: "",
>      got: "Attachment: xyz.zip\n" (using ==)
>
> It's looking like the mail template never got rendered, and body is giving
> me the attachment since it's the only part.
>
> I've got one other mailer method in that mailer which doesn't contain an
> attachement, and it's body comes out fine.
>
> I'm not sure what's going on here, and I'd appreciate any
> help/insight/condolences...
>
Note that I screwed up in sanitizing the code, the mailer really is
AssetsInfoManager, and that's what's in the spec consistently.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090318/881b66e4/attachment.html>

From nick at deadorange.com  Wed Mar 18 16:35:02 2009
From: nick at deadorange.com (Nick Hoffman)
Date: Wed, 18 Mar 2009 16:35:02 -0400
Subject: [rspec-users] [rspec] Stubbing partials in view specs
In-Reply-To: <6391f308-2ce8-4727-8049-be56e6ed242a@l16g2000yqo.googlegroups.com>
References: <71C878F7-574B-4287-8D5B-FAD56FD8AFB5@gmail.com>
	<57c63afe0901200629y1bb6b1e8vf0acaf2f2c7d5a2@mail.gmail.com>
	<6E3760F3-15A0-4E25-9E70-7DF948A4C8B2@gmail.com>
	<6391f308-2ce8-4727-8049-be56e6ed242a@l16g2000yqo.googlegroups.com>
Message-ID: <16827fa20903181335p7cd4a3b2u857acb8e008558a9@mail.gmail.com>

Hey there Evgeny. My response is inline.

> I call a partial inside another partial.
> _mother.haml contains:
> render :partial => "children/child"

> In mother_spec.rb file I am trying to stub the render call.
> Here is a working version:
> =============
> ? ?template.should_receive(:render)
> ? ?template.stub!(:render)
>
> ? ?render :partial => 'mother'
> ============

If you set a method expectation on an object (IE:
template.should_receive(:render) ), you don't need to stub the method
(IE: template.stub!(:render) isn't needed).

> I would prefer to specify that the partial I am stubbing is "children/
> child",
> however the following code doesn't work for me:
> ===========
> ? ?template.stub!(:render).with(hash_including(:partial => 'children/
> child'))
> ? ?template.expect_render(:partial => 'children/child')
>
> ? ?render :partial => 'mother'
>
> : Mock 'render_proxy' expected :render with ({:partial=>"children/
> child"}) once, but received it 0 times
> ===========
> Is it possible to stub the render call with specific partial name?

What I said above about method expectations and method stubs also
applies here. You should remove the call to #stub! .

However, I'd be inclined to use #should_receive rather than #expect_render :

template.should_receive(:render).with :partial => 'children/child'
render :partial => 'mother'

I haven't written many view specs though, so maybe we're supposed to
use #expect_render .

I hope that helps. Cheers,
Nick

From hayafirst at gmail.com  Wed Mar 18 16:46:06 2009
From: hayafirst at gmail.com (Yi)
Date: Wed, 18 Mar 2009 15:46:06 -0500
Subject: [rspec-users] extra spec
Message-ID: <ee6f48c00903181346t2ec4c20bq8005c71e4016aa45@mail.gmail.com>

Hi,

If I do something like this:

  before(:each) do
    @test_class = Class.new do
          blahblah
    end
  end

I will get one extra test shown:
MyTest
 - test_class

Where did I go wrong for this?

Thanks

Yi
-- 
http://yiwenandsoftware.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090318/cfc2708d/attachment.html>

From matt-lists at reprocessed.org  Wed Mar 18 16:54:44 2009
From: matt-lists at reprocessed.org (Matt Patterson)
Date: Wed, 18 Mar 2009 20:54:44 +0000
Subject: [rspec-users] Cucumber failing with 'uninitialized constant
	Spec::Ruby'
Message-ID: <454DE225-861E-4D14-911F-4473340DB47A@reprocessed.org>

I've just upgraded RSpec to 1.2 on a Rails 2.2.2 app.

rake features fails with the following error:

/Library/Ruby/Gems/1.8/gems/activesupport-2.2.2/lib/active_support/ 
dependencies.rb:442:in `load_missing_constant': uninitialized constant  
Spec::Ruby (NameError)
	from /Library/Ruby/Gems/1.8/gems/activesupport-2.2.2/lib/ 
active_support/dependencies.rb:77:in `const_missing'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.0/lib/spec/interop/test.rb:1
	from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in  
`gem_original_require'
	from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in  
`polyglot_original_require'
	from /Library/Ruby/Gems/1.8/gems/polyglot-0.2.5/lib/polyglot.rb:54:in  
`require'
	from /Library/Ruby/Gems/1.8/gems/activesupport-2.2.2/lib/ 
active_support/dependencies.rb:155:in `require'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.0/lib/spec/test/unit.rb:1
	from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in  
`gem_original_require'
	 ... 25 levels...
	from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.0/bin/../lib/cucumber/ 
cli/main.rb:68:in `require_files'
	from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.0/bin/../lib/cucumber/ 
cli/main.rb:34:in `execute!'
	from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.0/bin/../lib/cucumber/ 
cli/main.rb:20:in `execute'
	from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.0/bin/cucumber:6

Bummer.

I've tried with Cucumber 0.1.16 and 0.2, has anyone else seen this?  
I'll start poking later, but if anyone's seen it and has a super-easy  
diagnosis/fix that would be awesome.

Matt

-- 
   Matt Patterson | Design & Code
   <matt at reprocessed org> | http://www.reprocessed.org/




From dchelimsky at gmail.com  Wed Mar 18 17:07:26 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 18 Mar 2009 16:07:26 -0500
Subject: [rspec-users] Cucumber failing with 'uninitialized constant
	Spec::Ruby'
In-Reply-To: <454DE225-861E-4D14-911F-4473340DB47A@reprocessed.org>
References: <454DE225-861E-4D14-911F-4473340DB47A@reprocessed.org>
Message-ID: <57c63afe0903181407q43a4f402x1bf67aeab77debf0@mail.gmail.com>

On Wed, Mar 18, 2009 at 3:54 PM, Matt Patterson
<matt-lists at reprocessed.org> wrote:
> I've just upgraded RSpec to 1.2 on a Rails 2.2.2 app.
>
> rake features fails with the following error:
>
> /Library/Ruby/Gems/1.8/gems/activesupport-2.2.2/lib/active_support/dependencies.rb:442:in
> `load_missing_constant': uninitialized constant Spec::Ruby (NameError)
> ? ? ? ?from
> /Library/Ruby/Gems/1.8/gems/activesupport-2.2.2/lib/active_support/dependencies.rb:77:in
> `const_missing'
> ? ? ? ?from
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.0/lib/spec/interop/test.rb:1
> ? ? ? ?from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require'
> ? ? ? ?from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in
> `polyglot_original_require'
> ? ? ? ?from /Library/Ruby/Gems/1.8/gems/polyglot-0.2.5/lib/polyglot.rb:54:in
> `require'
> ? ? ? ?from
> /Library/Ruby/Gems/1.8/gems/activesupport-2.2.2/lib/active_support/dependencies.rb:155:in
> `require'
> ? ? ? ?from /Library/Ruby/Gems/1.8/gems/rspec-1.2.0/lib/spec/test/unit.rb:1
> ? ? ? ?from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require'
> ? ? ? ? ... 25 levels...
> ? ? ? ?from
> /Library/Ruby/Gems/1.8/gems/cucumber-0.2.0/bin/../lib/cucumber/cli/main.rb:68:in
> `require_files'
> ? ? ? ?from
> /Library/Ruby/Gems/1.8/gems/cucumber-0.2.0/bin/../lib/cucumber/cli/main.rb:34:in
> `execute!'
> ? ? ? ?from
> /Library/Ruby/Gems/1.8/gems/cucumber-0.2.0/bin/../lib/cucumber/cli/main.rb:20:in
> `execute'
> ? ? ? ?from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.0/bin/cucumber:6
>
> Bummer.

Did you run 'ruby script/generate rspec'?

>
> I've tried with Cucumber 0.1.16 and 0.2, has anyone else seen this? I'll
> start poking later, but if anyone's seen it and has a super-easy
> diagnosis/fix that would be awesome.
>
> Matt
>
> --
> ?Matt Patterson | Design & Code
> ?<matt at reprocessed org> | http://www.reprocessed.org/
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From zach.dennis at gmail.com  Wed Mar 18 18:17:21 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Wed, 18 Mar 2009 18:17:21 -0400
Subject: [rspec-users] [rspec] Stubbing partials in view specs
In-Reply-To: <16827fa20903181335p7cd4a3b2u857acb8e008558a9@mail.gmail.com>
References: <71C878F7-574B-4287-8D5B-FAD56FD8AFB5@gmail.com>
	<57c63afe0901200629y1bb6b1e8vf0acaf2f2c7d5a2@mail.gmail.com>
	<6E3760F3-15A0-4E25-9E70-7DF948A4C8B2@gmail.com>
	<6391f308-2ce8-4727-8049-be56e6ed242a@l16g2000yqo.googlegroups.com>
	<16827fa20903181335p7cd4a3b2u857acb8e008558a9@mail.gmail.com>
Message-ID: <85d99afe0903181517j55af747aye152f59bd857361a@mail.gmail.com>

On Wed, Mar 18, 2009 at 4:35 PM, Nick Hoffman <nick at deadorange.com> wrote:
> Hey there Evgeny. My response is inline.
>
>> I call a partial inside another partial.
>> _mother.haml contains:
>> render :partial => "children/child"
>
>> In mother_spec.rb file I am trying to stub the render call.
>> Here is a working version:
>> =============
>> ? ?template.should_receive(:render)
>> ? ?template.stub!(:render)
>>
>> ? ?render :partial => 'mother'
>> ============
>
> If you set a method expectation on an object (IE:
> template.should_receive(:render) ), you don't need to stub the method
> (IE: template.stub!(:render) isn't needed).
>
>> I would prefer to specify that the partial I am stubbing is "children/
>> child",
>> however the following code doesn't work for me:
>> ===========
>> ? ?template.stub!(:render).with(hash_including(:partial => 'children/
>> child'))
>> ? ?template.expect_render(:partial => 'children/child')
>>
>> ? ?render :partial => 'mother'
>>
>> : Mock 'render_proxy' expected :render with ({:partial=>"children/
>> child"}) once, but received it 0 times
>> ===========
>> Is it possible to stub the render call with specific partial name?
>
> What I said above about method expectations and method stubs also
> applies here. You should remove the call to #stub! .
>
> However, I'd be inclined to use #should_receive rather than #expect_render :
>
> template.should_receive(:render).with :partial => 'children/child'
> render :partial => 'mother'
>
> I haven't written many view specs though, so maybe we're supposed to
> use #expect_render .

#expect_render is deprecated prior to 1.2 and it has been removed 1.2.
You don't want to use that. :)

>
> I hope that helps. Cheers,
> Nick
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From aslak.hellesoy at gmail.com  Wed Mar 18 18:17:59 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Wed, 18 Mar 2009 18:17:59 -0400
Subject: [rspec-users] ANN Cucumber 0.2.0
In-Reply-To: <49C155E1.3050203@josephwilk.net>
References: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
	<57c63afe0903181221h2c0d5638t5967ea448271b2f2@mail.gmail.com>
	<49C155E1.3050203@josephwilk.net>
Message-ID: <8d961d900903181517l75c20038l9e65e8c714285c5a@mail.gmail.com>

On Wed, Mar 18, 2009 at 4:13 PM, Joseph Wilk <joe at josephwilk.net> wrote:

> David Chelimsky wrote:
>
>> 2009/3/18 aslak hellesoy <aslak.hellesoy at gmail.com>:
>>
>>
>>> I'm happy to announce the release of Cucumber 0.2.0.
>>>
>>> There are a some really exciting new features in this release. Some of
>>> the
>>> ones I find most valuable are:
>>> * tags
>>> * better output
>>> * autoformatting of features
>>> * better i18n
>>> * Ruby 1.9 support
>>> * background
>>> * guess mode
>>>
>>> Full release notes are available at
>>>
>>> http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt
>>> With this release I expect the formatter API to remain fairly stable.
>>> Check
>>> out the Cucumber::Ast::Visitor class for the full API.
>>>
>>> Thanks a lot to everyone who has contributed so far. The big internal
>>> refactoring has now stabilised, so it should be easier to contribute
>>> again!
>>>
>>>
>>
>> Congrats!!!!!!!
>>
>>
>>
>>> Enjoy!
>>>
>>> (As usual, wait an hour or two for the gem to rsync around the Rubyforge
>>> mirror park)
>>>
>>> (::) Aslak (::)
>>>
>>>
>>
>> What's this, like a cucumber in each ear?
>>
>>
> Cucumber earrings are clearly in this year :)
>
>
> http://en.dawanda.com/product/2413009-Cucumber-NonAllergic-Stud-Earrings-Polymer-Clay
>

I'll consider those when I get my ears pierced, Joseph.

Until then - this is more me:

http://www.1stchoicecufflinks.com/ecommerce/Scripts/prodView2~idproduct~11689~Cool~Cucumber~Cufflinks.htm

Aslak


> --
> Joseph Wilk
> http://blog.josephwilk.net
>
>
>
>
>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>>
>>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>>
>>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090318/d616db49/attachment.html>

From zach.dennis at gmail.com  Wed Mar 18 18:23:28 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Wed, 18 Mar 2009 18:23:28 -0400
Subject: [rspec-users] [rspec] Stubbing partials in view specs
In-Reply-To: <6391f308-2ce8-4727-8049-be56e6ed242a@l16g2000yqo.googlegroups.com>
References: <71C878F7-574B-4287-8D5B-FAD56FD8AFB5@gmail.com>
	<57c63afe0901200629y1bb6b1e8vf0acaf2f2c7d5a2@mail.gmail.com>
	<6E3760F3-15A0-4E25-9E70-7DF948A4C8B2@gmail.com>
	<6391f308-2ce8-4727-8049-be56e6ed242a@l16g2000yqo.googlegroups.com>
Message-ID: <85d99afe0903181523q15756ff4u824248801ad7113a@mail.gmail.com>

On Wed, Mar 18, 2009 at 6:18 AM, Evgeny Bogdanov
<evgeny.bogdanov at gmail.com> wrote:
> Hello,
> I have a problem similar to one mentioned in this post.
> I call a partial inside another partial.
> _mother.haml contains:
> render :partial => "children/child"
>
> In mother_spec.rb file I am trying to stub the render call.
> Here is a working version:
> =============
> ? ?template.should_receive(:render)
> ? ?template.stub!(:render)
>
> ? ?render :partial => 'mother'
> ============
> I would prefer to specify that the partial I am stubbing is "children/
> child",
> however the following code doesn't work for me:
> ===========
> ? ?template.stub!(:render).with(hash_including(:partial => 'children/
> child'))
> ? ?template.expect_render(:partial => 'children/child')

What version of rspec are you using? #expect_render has been removed
in rspec 1.2 and has been deprecated for a while before that so you
won't want to rely on that unless you're using an old version of
rspec.

>
> ? ?render :partial => 'mother'
>
> : Mock 'render_proxy' expected :render with ({:partial=>"children/
> child"}) once, but received it 0 times
> ===========
> Is it possible to stub the render call with specific partial name?

You had it right, hash including should work:
   template.stub!(:render).with(hash_including(:partial => "children/child"))

To stub all partials being rendered:
   template.stub!(:render).with(hash_including(:partial => anything))

HTH,


>
> Thank you in advance,
> Evgeny
>
> On Jan 20, 5:35?pm, Bart Zonneveld <zuperinfin... at gmail.com> wrote:
>> On 20-jan-2009, at 15:29, David Chelimsky wrote:
>>
>> > On Tue, Jan 20, 2009 at 7:44 AM, Bart Zonneveld
>> > <zuperinfin... at gmail.com> wrote:
>> >> Hey list,
>>
>> >> As a good BDDer I want to test my views in isolation.
>>
>> > Sort of. A *good* BDDer wants to *specify* views in isolation. Testing
>> > is for testers :)
>>
>> You're right! I tend to talk a lot to non-programmers, and they get
>> that glaze-in-the-distance look in their eyes, whenever I mention
>> specifiy, spec'ing, or what have you :).
>>
>> >> And as a good rails
>> >> programmer, I separate views into partials when needed. So, when
>> >> testing my
>> >> views, I want tostubout rendering of partials in my views. I'm
>> >> working on
>> >> upgrading an app from rails 2.1.2 to 2.2.2, using the latest rspec
>> >> and
>> >> rspec-rails.
>>
>> >> I used to throw template.stub!(:render) in a before(:each) block
>> >> and be done
>> >> with it
>>
>> > That sounds kinda risky because you could be ignoring partials that
>> > get rendered that you don't want to be rendered.
>>
>> It is, most definately.
>>
>> >> , but that doesn't work anymore. I can understand why, but now I have
>> >> to do something like template.stub!(:render).with(hash_including
>> >> (:partial =>
>> >> anything)). Except for when I'm testing a partial, then I need to
>> >> replace
>> >> the anything with every partial I'm rendering in my partial.
>>
>> >> Is this the correct way,
>>
>> > Seems like the only way at the moment. Wouldn't call it correct or
>> > incorrect.
>>
>> I would call it ugly :). Not only do I have to remember the
>> hash_including part, but also the anything (and not :anything).
>> Conceptually, I like the template.stub!(:render). Irendera
>> template, on which Istuball the renders. Whether that's risky or
>> not is a different discussion.
>>
>> >> or is there perhaps something like
>> >> template.stub_partials :only => [], :except => [] ?
>>
>> > Nothing like this exists. Seems like a reasonable idea. Feel free to
>> > submit a feature request, or better yet, a patch to
>> >http://rspec.lighthouseapp.com
>>
>> Will do!
>>
>> cheers,
>> bartz
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From tom at zudio.com.au  Wed Mar 18 18:49:55 2009
From: tom at zudio.com.au (Tom Meier)
Date: Thu, 19 Mar 2009 09:49:55 +1100
Subject: [rspec-users] mock_model with Rspec/Rspec-rails 1.2 and
	Rails	2.3 [re : Pat & David)
In-Reply-To: <mailman.232.1237406941.12000.rspec-users@rubyforge.org>
References: <mailman.232.1237406941.12000.rspec-users@rubyforge.org>
Message-ID: <7C38F4CC-C8C5-4B29-8361-E81D905EE7DF@zudio.com.au>


Hi,

	Thanks for the assistance, I overlooked the obvious with the '=' in  
the error... After reviewing the error i started a new project and  
tried to replicate to show you the steps, but everything works as it  
should (sorry - i should have completed that already before contacting  
you). After narrowing it down with Pats' suggestion, it turns out it  
was referring back to itself, I was using a blueprint with the plugin  
'Machinist', and a method was of the same name as a field name  
('login') so it was pointing back to itself trying to make a mock of a  
mock...

So thanks for your assistance, much appreciated... Just overlooked  
something...


Best regards,

Tom



Thomas Meier
Lead Developer
Zudio Pty. Ltd.
Level 1 / 151 Park Road, Cheltenham,
Victoria 3192
Phone +61 3 9585 2077 Fax +61 3 9585 2079
zudio.com.au
Design | Web | Video | Music


> From: Pat Maddox <pat.maddox at gmail.com>
> Date: 19 March 2009 3:54:10 AM
> To: rspec-users <rspec-users at rubyforge.org>
> Subject: Re: [rspec-users] mock_model with Rspec/Rspec-rails 1.2 and  
> Rails 2.3
> Reply-To: rspec-users <rspec-users at rubyforge.org>
>
>
> On Mar 17, 2009, at 11:37 PM, David Chelimsky wrote:
>
>> 2009/3/18 Tom Meier <tom at zudio.com.au>:
>>>
>>> With the above settings when our specs run (while on rails 2.3 and  
>>> rspec
>>> 1.2), the following error occurs :
>>> undefined method `mock_model=' for #<User:0x2d5887c>
>>
>> The error says "mock_model=", which indicates that you're trying to
>> set it somewhere in your code. Please show us the spec that is  
>> failing
>> with a reference to the line that is raising that error.
>
> I think this would require him to do
> self.mock_model = blah
> or
> send("mock_model=", blah)
>
> which seems really, really weird.  Oh well.  Some code ought to  
> clear it up.
>
> Pat
>
>
> From: Pat Maddox <pat.maddox at gmail.com>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/e5b2ccd1/attachment.html>

From matt-lists at reprocessed.org  Wed Mar 18 19:17:02 2009
From: matt-lists at reprocessed.org (Matt Patterson)
Date: Wed, 18 Mar 2009 23:17:02 +0000
Subject: [rspec-users] Cucumber failing with 'uninitialized constant
	Spec::Ruby'
In-Reply-To: <57c63afe0903181407q43a4f402x1bf67aeab77debf0@mail.gmail.com>
References: <454DE225-861E-4D14-911F-4473340DB47A@reprocessed.org>
	<57c63afe0903181407q43a4f402x1bf67aeab77debf0@mail.gmail.com>
Message-ID: <8D48072A-4217-40E7-97AD-DDA329130C93@reprocessed.org>

On 18 Mar 2009, at 21:07, David Chelimsky wrote:

> On Wed, Mar 18, 2009 at 3:54 PM, Matt Patterson
> <matt-lists at reprocessed.org> wrote:
>> I've just upgraded RSpec to 1.2 on a Rails 2.2.2 app.
>>
>> rake features fails with the following error:
>>
>> /Library/Ruby/Gems/1.8/gems/activesupport-2.2.2/lib/active_support/ 
>> dependencies.rb:442:in
>> `load_missing_constant': uninitialized constant Spec::Ruby  
>> (NameError)
>>         ... 25 levels...
>>        from
>> /Library/Ruby/Gems/1.8/gems/cucumber-0.2.0/bin/../lib/cucumber/cli/ 
>> main.rb:68:in
>> `require_files'
>>        from
>
> Did you run 'ruby script/generate rspec'?

Yes, both ./script/generate rspec and ./script/generate cucumber

I just went back and checked on my environments/test.rb. With the line:

config.gem "rspec-rails", :lib =>'spec/rails'

Cucumber blows up. I switched to use the new suggestion from http://wiki.github.com/dchelimsky/rspec/configgem-for-rails 
:

config.gem "rspec", :lib => false, :version => ">= 1.2.0"
config.gem "rspec-rails", :lib => false, :version => ">= 1.2.0"

And it runs! Phew. Maybe put that, or a link to the wiki page, into  
rspec-rails/Upgrade.markdown?

Matt


-- 
   Matt Patterson | Design & Code
   <matt at reprocessed org> | http://www.reprocessed.org/




From aslak.hellesoy at gmail.com  Thu Mar 19 02:22:29 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Thu, 19 Mar 2009 02:22:29 -0400
Subject: [rspec-users] ANN Cucumber 0.2.0
In-Reply-To: <21798F7D-6CC7-4CF3-989A-0552033E5F02@gmail.com>
References: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
	<57c63afe0903181221h2c0d5638t5967ea448271b2f2@mail.gmail.com>
	<21798F7D-6CC7-4CF3-989A-0552033E5F02@gmail.com>
Message-ID: <8d961d900903182322x769fbefei94b0c1b8b1ed419e@mail.gmail.com>

On Wed, Mar 18, 2009 at 4:08 PM, Emmanuel Pinault <seatmanu at gmail.com>wrote:

> Great! Is there  section for the new hook on reporting? I used the old
> reporting to customized some of our HTML reports and wonder if you have the
> new hooks documented somewhere?
>

The public API for formatters is all the methods in  Cucumber::Ast::Visitor.
Override as you see fit.
I have updated
http://wiki.github.com/aslakhellesoy/cucumber/custom-formatters to reflect
the changes in 0.2.


>
> Also what is the rerun formatter?
>

A formatter that prints the location of all failed scenarios. Used by
Cucumber's Autotest plugin.


>
> Thanks
>
> Emmanuel
>
>
> On Mar 18, 2009, at 12:21 PM, David Chelimsky wrote:
>
>  2009/3/18 aslak hellesoy <aslak.hellesoy at gmail.com>:
>>
>>> I'm happy to announce the release of Cucumber 0.2.0.
>>>
>>> There are a some really exciting new features in this release. Some of
>>> the
>>> ones I find most valuable are:
>>> * tags
>>> * better output
>>> * autoformatting of features
>>> * better i18n
>>> * Ruby 1.9 support
>>> * background
>>> * guess mode
>>>
>>> Full release notes are available at
>>>
>>> http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt
>>> With this release I expect the formatter API to remain fairly stable.
>>> Check
>>> out the Cucumber::Ast::Visitor class for the full API.
>>>
>>> Thanks a lot to everyone who has contributed so far. The big internal
>>> refactoring has now stabilised, so it should be easier to contribute
>>> again!
>>>
>>
>> Congrats!!!!!!!
>>
>>
>>> Enjoy!
>>>
>>> (As usual, wait an hour or two for the gem to rsync around the Rubyforge
>>> mirror park)
>>>
>>> (::) Aslak (::)
>>>
>>
>> What's this, like a cucumber in each ear?
>>
>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>>  _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/0c310347/attachment.html>

From lists at ruby-forum.com  Thu Mar 19 05:28:42 2009
From: lists at ruby-forum.com (jazzez ravi)
Date: Thu, 19 Mar 2009 10:28:42 +0100
Subject: [rspec-users] Basic help
Message-ID: <85e02fd87dcbe97b37352667d1b2b4f3@ruby-forum.com>

Hi All,

1. Just now I installed rspec1.2.0 and dependencies

2. Tried the 2 programs mentioned in http://rspec.info/.

# bowling_spec.rb
require 'bowling'

describe Bowling do
  before(:each) do
    @bowling = Bowling.new
  end

  it "should score 0 for gutter game" do
    20.times { @bowling.hit(0) }
    @bowling.score.should == 0
  end
end

# bowling.rb
class Bowling
  def hit(pins)
  end

  def score
    0
  end
end


3. Run the bowling_spec.rb file

>ruby bowling_spec.rb --format specdoc

4. getting error like

bowling_spec.rb:6: undefined method `describe' for main:Object
(NoMethodError)

5. So i tried to add these lines,

require 'rspec' --> no Such file to Load
require 'spec' -->  No Error But also no output mentioned as per that
website.

Please anyone help to continue that program.

Regards,
P.Raveendran
http://raveendran.wordpress.com
-- 
Posted via http://www.ruby-forum.com/.

From dchelimsky at gmail.com  Thu Mar 19 08:36:29 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 19 Mar 2009 07:36:29 -0500
Subject: [rspec-users] Basic help
In-Reply-To: <85e02fd87dcbe97b37352667d1b2b4f3@ruby-forum.com>
References: <85e02fd87dcbe97b37352667d1b2b4f3@ruby-forum.com>
Message-ID: <57c63afe0903190536n614c5f7fs5ef46d373389f712@mail.gmail.com>

On Thu, Mar 19, 2009 at 4:28 AM, jazzez ravi <lists at ruby-forum.com> wrote:
> Hi All,
>
> 1. Just now I installed rspec1.2.0 and dependencies
>
> 2. Tried the 2 programs mentioned in http://rspec.info/.
>
> # bowling_spec.rb
> require 'bowling'
>
> describe Bowling do
> ?before(:each) do
> ? ?@bowling = Bowling.new
> ?end
>
> ?it "should score 0 for gutter game" do
> ? ?20.times { @bowling.hit(0) }
> ? ?@bowling.score.should == 0
> ?end
> end
>
> # bowling.rb
> class Bowling
> ?def hit(pins)
> ?end
>
> ?def score
> ? ?0
> ?end
> end
>
>
> 3. Run the bowling_spec.rb file
>
>>ruby bowling_spec.rb --format specdoc

Use the spec command (that's what's there on http://rspec.info):

spec bowling_spec.rb --format specdoc

Cheers,
David

>
> 4. getting error like
>
> bowling_spec.rb:6: undefined method `describe' for main:Object
> (NoMethodError)
>
> 5. So i tried to add these lines,
>
> require 'rspec' --> no Such file to Load
> require 'spec' --> ?No Error But also no output mentioned as per that
> website.
>
> Please anyone help to continue that program.
>
> Regards,
> P.Raveendran
> http://raveendran.wordpress.com
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From zach.dennis at gmail.com  Thu Mar 19 08:36:55 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Thu, 19 Mar 2009 08:36:55 -0400
Subject: [rspec-users] Basic help
In-Reply-To: <85e02fd87dcbe97b37352667d1b2b4f3@ruby-forum.com>
References: <85e02fd87dcbe97b37352667d1b2b4f3@ruby-forum.com>
Message-ID: <85d99afe0903190536w7f8212e2mb3a769b60ba82ad4@mail.gmail.com>

On Thu, Mar 19, 2009 at 5:28 AM, jazzez ravi <lists at ruby-forum.com> wrote:
> Hi All,
>
> 1. Just now I installed rspec1.2.0 and dependencies
>
> 2. Tried the 2 programs mentioned in http://rspec.info/.
>
> # bowling_spec.rb
> require 'bowling'
>
> describe Bowling do
> ?before(:each) do
> ? ?@bowling = Bowling.new
> ?end
>
> ?it "should score 0 for gutter game" do
> ? ?20.times { @bowling.hit(0) }
> ? ?@bowling.score.should == 0
> ?end
> end
>
> # bowling.rb
> class Bowling
> ?def hit(pins)
> ?end
>
> ?def score
> ? ?0
> ?end
> end
>
>
> 3. Run the bowling_spec.rb file
>
>>ruby bowling_spec.rb --format specdoc
>
> 4. getting error like
>
> bowling_spec.rb:6: undefined method `describe' for main:Object
> (NoMethodError)
>
> 5. So i tried to add these lines,
>
> require 'rspec' --> no Such file to Load
> require 'spec' --> ?No Error But also no output mentioned as per that
> website.
>
> Please anyone help to continue that program.

Try to put this at the top:

require 'rubygems'
require 'spec'

I have an environment variable set to always load rubygems on my
system so I can omit the require of it explicitly in code:

RUBYOPTS=-rubygems



>
> Regards,
> P.Raveendran
> http://raveendran.wordpress.com
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From lists at ruby-forum.com  Thu Mar 19 08:46:27 2009
From: lists at ruby-forum.com (Zhenning Guan)
Date: Thu, 19 Mar 2009 13:46:27 +0100
Subject: [rspec-users] what's the meaning of to_param?
Message-ID: <d15f2adf9048133faabf07ea633190db@ruby-forum.com>

usually, I just use this way.

=====
@weather = mock_model(Weather)
=====

but recently I saw this. so what's the :to_param and :save options
meaning?

======
@weather = mock_model(Weather, :to_param => "1", :save => true)
======
-- 
Posted via http://www.ruby-forum.com/.

From evgeny.bogdanov at gmail.com  Thu Mar 19 08:59:52 2009
From: evgeny.bogdanov at gmail.com (Evgeny Bogdanov)
Date: Thu, 19 Mar 2009 05:59:52 -0700 (PDT)
Subject: [rspec-users] [rspec] Stubbing partials in view specs
In-Reply-To: <85d99afe0903181523q15756ff4u824248801ad7113a@mail.gmail.com>
References: <71C878F7-574B-4287-8D5B-FAD56FD8AFB5@gmail.com> 
	<57c63afe0901200629y1bb6b1e8vf0acaf2f2c7d5a2@mail.gmail.com> 
	<6E3760F3-15A0-4E25-9E70-7DF948A4C8B2@gmail.com>
	<6391f308-2ce8-4727-8049-be56e6ed242a@l16g2000yqo.googlegroups.com>
	<85d99afe0903181523q15756ff4u824248801ad7113a@mail.gmail.com>
Message-ID: <2b516195-4fea-499d-af26-8077b2792586@o11g2000yql.googlegroups.com>

just upgraded to 1.2.0
the following code works now:

    template.stub!(:render).with(hash_including(:partial => "children/
child"))
    template.should_receive(:render).with(hash_including(:partial =>
"children/child"))

The only question that is left for me is about Nick's words:
"If you set a method expectation on an object (IE:
template.should_receive(:render) ), you don't need to stub the method
(IE: template.stub!(:render) isn't needed)."

Basically, there are two situation.
1) I want to check if a function was called and I want to execute the
function code
2) I want to check if a function was called and I don't want to
execute the function code so I used stubbing.

I thought that for the first scenario the solution would be:
template.should_receive(:render) #only checks if render function was
called

and for the second scenario
template.stub!(:render) #stub render function
template.should_receive(:render) #check if render function was called

Am I right?

Thanks,
Evgeny

On Mar 18, 11:23?pm, Zach Dennis <zach.den... at gmail.com> wrote:
> On Wed, Mar 18, 2009 at 6:18 AM, Evgeny Bogdanov
>
>
>
> <evgeny.bogda... at gmail.com> wrote:
> > Hello,
> > I have a problem similar to one mentioned in this post.
> > I call a partial inside another partial.
> > _mother.haml contains:
> > render :partial => "children/child"
>
> > In mother_spec.rb file I am trying to stub the render call.
> > Here is a working version:
> > =============
> > ? ?template.should_receive(:render)
> > ? ?template.stub!(:render)
>
> > ? ?render :partial => 'mother'
> > ============
> > I would prefer to specify that the partial I am stubbing is "children/
> > child",
> > however the following code doesn't work for me:
> > ===========
> > ? ?template.stub!(:render).with(hash_including(:partial => 'children/
> > child'))
> > ? ?template.expect_render(:partial => 'children/child')
>
> What version of rspec are you using? #expect_render has been removed
> in rspec 1.2 and has been deprecated for a while before that so you
> won't want to rely on that unless you're using an old version of
> rspec.
>
>
>
> > ? ?render :partial => 'mother'
>
> > : Mock 'render_proxy' expected :render with ({:partial=>"children/
> > child"}) once, but received it 0 times
> > ===========
> > Is it possible to stub the render call with specific partial name?
>
> You had it right, hash including should work:
> ? ?template.stub!(:render).with(hash_including(:partial => "children/child"))
>
> To stub all partials being rendered:
> ? ?template.stub!(:render).with(hash_including(:partial => anything))
>
> HTH,
>
>
>
>
>
> > Thank you in advance,
> > Evgeny
>
> > On Jan 20, 5:35?pm, Bart Zonneveld <zuperinfin... at gmail.com> wrote:
> >> On 20-jan-2009, at 15:29, David Chelimsky wrote:
>
> >> > On Tue, Jan 20, 2009 at 7:44 AM, Bart Zonneveld
> >> > <zuperinfin... at gmail.com> wrote:
> >> >> Hey list,
>
> >> >> As a good BDDer I want to test my views in isolation.
>
> >> > Sort of. A *good* BDDer wants to *specify* views in isolation. Testing
> >> > is for testers :)
>
> >> You're right! I tend to talk a lot to non-programmers, and they get
> >> that glaze-in-the-distance look in their eyes, whenever I mention
> >> specifiy, spec'ing, or what have you :).
>
> >> >> And as a good rails
> >> >> programmer, I separate views into partials when needed. So, when
> >> >> testing my
> >> >> views, I want tostubout rendering of partials in my views. I'm
> >> >> working on
> >> >> upgrading an app from rails 2.1.2 to 2.2.2, using the latest rspec
> >> >> and
> >> >> rspec-rails.
>
> >> >> I used to throw template.stub!(:render) in a before(:each) block
> >> >> and be done
> >> >> with it
>
> >> > That sounds kinda risky because you could be ignoring partials that
> >> > get rendered that you don't want to be rendered.
>
> >> It is, most definately.
>
> >> >> , but that doesn't work anymore. I can understand why, but now I have
> >> >> to do something like template.stub!(:render).with(hash_including
> >> >> (:partial =>
> >> >> anything)). Except for when I'm testing a partial, then I need to
> >> >> replace
> >> >> the anything with every partial I'm rendering in my partial.
>
> >> >> Is this the correct way,
>
> >> > Seems like the only way at the moment. Wouldn't call it correct or
> >> > incorrect.
>
> >> I would call it ugly :). Not only do I have to remember the
> >> hash_including part, but also the anything (and not :anything).
> >> Conceptually, I like the template.stub!(:render). Irendera
> >> template, on which Istuball the renders. Whether that's risky or
> >> not is a different discussion.
>
> >> >> or is there perhaps something like
> >> >> template.stub_partials :only => [], :except => [] ?
>
> >> > Nothing like this exists. Seems like a reasonable idea. Feel free to
> >> > submit a feature request, or better yet, a patch to
> >> >http://rspec.lighthouseapp.com
>
> >> Will do!
>
> >> cheers,
> >> bartz
>
> >> _______________________________________________
> >> rspec-users mailing list
> >> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
> --
> Zach Dennishttp://www.continuousthinking.comhttp://www.mutuallyhuman.com
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From zach.dennis at gmail.com  Thu Mar 19 09:15:53 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Thu, 19 Mar 2009 09:15:53 -0400
Subject: [rspec-users] what's the meaning of to_param?
In-Reply-To: <d15f2adf9048133faabf07ea633190db@ruby-forum.com>
References: <d15f2adf9048133faabf07ea633190db@ruby-forum.com>
Message-ID: <85d99afe0903190615w403fd1aw59c10695ad698445@mail.gmail.com>

On Thu, Mar 19, 2009 at 8:46 AM, Zhenning Guan <lists at ruby-forum.com> wrote:
> usually, I just use this way.
>
> =====
> @weather = mock_model(Weather)
> =====
>
> but recently I saw this. so what's the :to_param and :save options
> meaning?
>
> ======
> @weather = mock_model(Weather, :to_param => "1", :save => true)
> ======

http://www.railsbrain.com/api/rails-2.2.2/doc/index.html?a=M001952&name=to_param

It's a Rails thing, used when converting an object to a URL representation.


> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From zach.dennis at gmail.com  Thu Mar 19 09:20:16 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Thu, 19 Mar 2009 09:20:16 -0400
Subject: [rspec-users] what's the meaning of to_param?
In-Reply-To: <85d99afe0903190615w403fd1aw59c10695ad698445@mail.gmail.com>
References: <d15f2adf9048133faabf07ea633190db@ruby-forum.com>
	<85d99afe0903190615w403fd1aw59c10695ad698445@mail.gmail.com>
Message-ID: <85d99afe0903190620r1e1a7e64hd3556129e2cea5ea@mail.gmail.com>

On Thu, Mar 19, 2009 at 9:15 AM, Zach Dennis <zach.dennis at gmail.com> wrote:
> On Thu, Mar 19, 2009 at 8:46 AM, Zhenning Guan <lists at ruby-forum.com> wrote:
>> usually, I just use this way.
>>
>> =====
>> @weather = mock_model(Weather)
>> =====
>>
>> but recently I saw this. so what's the :to_param and :save options
>> meaning?
>>
>> ======
>> @weather = mock_model(Weather, :to_param => "1", :save => true)
>> ======
>
> http://www.railsbrain.com/api/rails-2.2.2/doc/index.html?a=M001952&name=to_param
>
> It's a Rails thing, used when converting an object to a URL representation.
>

Oops, sorry, I misread your question.

mock_model will provide you with #to_param so the only thing I can
think w/o knowing more is if whoever wrote the spec wanted to
specifically expect, look for, or somehow use the "1" that came from
to_param. They wanted to know that specific the result of
@weater.to_param was being used (which will be used be number of Rails
helpers).

My best guess on the save call is that the implementation is going to
call save, and the author of the spec by default wants it to be
successful for any subsequent examples.

>
>> --
>> Posted via http://www.ruby-forum.com/.
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
>
> --
> Zach Dennis
> http://www.continuousthinking.com
> http://www.mutuallyhuman.com
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From hayafirst at gmail.com  Thu Mar 19 10:25:04 2009
From: hayafirst at gmail.com (Yi)
Date: Thu, 19 Mar 2009 09:25:04 -0500
Subject: [rspec-users] [Cucumber 0.2] Failure to use should
Message-ID: <ee6f48c00903190725i532b21c5l5c09b8234ea8b88a@mail.gmail.com>

I have a step definition like this:

Then "the account should be created" do
  account = Account.find_by_name("my shiny new account")
  p account.class
  account.should_not be_blank
end

When running this step, I got the error message:

Account(id: integer, name: string, state: string, next_renewal_at: date,
created_at: datetime, updated_at: datetime, full_domain: string, deleted_at:
datetime, subscription_discount_id: integer, subscription_plan_id: integer)

    And the account should be created              #
features/step_definitions/create_account_steps.rb:31
      undefined method `be_blank' for
#<ActionController::Integration::Session:0x349994c> (NoMethodError)
      features/create_account.feature:10:in `And the account should be
created'

I print out the account class, which is a AR::B. Why cucumber tells me it is
a ActionController::Integration::Session?

I use cucumber 0.2 and rspec 1.2 with Rails 2.3.2

Thanks

Yi
-- 
http://yiwenandsoftware.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/855b95ce/attachment.html>

From dchelimsky at gmail.com  Thu Mar 19 10:30:15 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 19 Mar 2009 09:30:15 -0500
Subject: [rspec-users] [rspec] Stubbing partials in view specs
In-Reply-To: <2b516195-4fea-499d-af26-8077b2792586@o11g2000yql.googlegroups.com>
References: <71C878F7-574B-4287-8D5B-FAD56FD8AFB5@gmail.com>
	<57c63afe0901200629y1bb6b1e8vf0acaf2f2c7d5a2@mail.gmail.com>
	<6E3760F3-15A0-4E25-9E70-7DF948A4C8B2@gmail.com>
	<6391f308-2ce8-4727-8049-be56e6ed242a@l16g2000yqo.googlegroups.com>
	<85d99afe0903181523q15756ff4u824248801ad7113a@mail.gmail.com>
	<2b516195-4fea-499d-af26-8077b2792586@o11g2000yql.googlegroups.com>
Message-ID: <C9E28BA4-4873-4DCB-BA42-D2EA93C6C540@gmail.com>

On Mar 19, 2009, at 7:59 AM, Evgeny Bogdanov  
<evgeny.bogdanov at gmail.com> wrote:

> just upgraded to 1.2.0
> the following code works now:
>
>    template.stub!(:render).with(hash_including(:partial => "children/
> child"))
>    template.should_receive(:render).with(hash_including(:partial =>
> "children/child"))
>
> The only question that is left for me is about Nick's words:
> "If you set a method expectation on an object (IE:
> template.should_receive(:render) ), you don't need to stub the method
> (IE: template.stub!(:render) isn't needed)."
>
> Basically, there are two situation.
> 1) I want to check if a function was called and I want to execute the
> function code
> 2) I want to check if a function was called and I don't want to
> execute the function code so I used stubbing.
>
> I thought that for the first scenario the solution would be:
> template.should_receive(:render) #only checks if render function was
> called
>
> and for the second scenario
> template.stub!(:render) #stub render function
> template.should_receive(:render) #check if render function was called
>
> Am I right?

No. What I think you're describing is called a test spy: a means of  
monitoring interactions without changing the behavior. RSpec's mocks  
don't provide this. The only ruby framework I'm aware of that does is  
RR. There may be others.

A stub (stubs!) overrides an existing method (if one exists) and  
returns either self or any value you define with and_returns.

A message expectation, or mocked method (should_receive) does the same  
thing *plus* it verifies that the message was called.

HTH,
David

>
>
> Thanks,
> Evgeny
>
> On Mar 18, 11:23 pm, Zach Dennis <zach.den... at gmail.com> wrote:
>> On Wed, Mar 18, 2009 at 6:18 AM, Evgeny Bogdanov
>>
>>
>>
>> <evgeny.bogda... at gmail.com> wrote:
>>> Hello,
>>> I have a problem similar to one mentioned in this post.
>>> I call a partial inside another partial.
>>> _mother.haml contains:
>>> render :partial => "children/child"
>>
>>> In mother_spec.rb file I am trying to stub the render call.
>>> Here is a working version:
>>> =============
>>>    template.should_receive(:render)
>>>    template.stub!(:render)
>>
>>>    render :partial => 'mother'
>>> ============
>>> I would prefer to specify that the partial I am stubbing is  
>>> "children/
>>> child",
>>> however the following code doesn't work for me:
>>> ===========
>>>    template.stub!(:render).with(hash_including(:partial =>  
>>> 'children/
>>> child'))
>>>    template.expect_render(:partial => 'children/child')
>>
>> What version of rspec are you using? #expect_render has been removed
>> in rspec 1.2 and has been deprecated for a while before that so you
>> won't want to rely on that unless you're using an old version of
>> rspec.
>>
>>
>>
>>>    render :partial => 'mother'
>>
>>> : Mock 'render_proxy' expected :render with ({:partial=>"children/
>>> child"}) once, but received it 0 times
>>> ===========
>>> Is it possible to stub the render call with specific partial name?
>>
>> You had it right, hash including should work:
>>    template.stub!(:render).with(hash_including(:partial =>  
>> "children/child"))
>>
>> To stub all partials being rendered:
>>    template.stub!(:render).with(hash_including(:partial => anything))
>>
>> HTH,
>>
>>
>>
>>
>>
>>> Thank you in advance,
>>> Evgeny
>>
>>> On Jan 20, 5:35 pm, Bart Zonneveld <zuperinfin... at gmail.com> wrote:
>>>> On 20-jan-2009, at 15:29, David Chelimsky wrote:
>>
>>>>> On Tue, Jan 20, 2009 at 7:44 AM, Bart Zonneveld
>>>>> <zuperinfin... at gmail.com> wrote:
>>>>>> Hey list,
>>
>>>>>> As a good BDDer I want to test my views in isolation.
>>
>>>>> Sort of. A *good* BDDer wants to *specify* views in isolation.  
>>>>> Testing
>>>>> is for testers :)
>>
>>>> You're right! I tend to talk a lot to non-programmers, and they get
>>>> that glaze-in-the-distance look in their eyes, whenever I mention
>>>> specifiy, spec'ing, or what have you :).
>>
>>>>>> And as a good rails
>>>>>> programmer, I separate views into partials when needed. So, when
>>>>>> testing my
>>>>>> views, I want tostubout rendering of partials in my views. I'm
>>>>>> working on
>>>>>> upgrading an app from rails 2.1.2 to 2.2.2, using the latest  
>>>>>> rspec
>>>>>> and
>>>>>> rspec-rails.
>>
>>>>>> I used to throw template.stub!(:render) in a before(:each) block
>>>>>> and be done
>>>>>> with it
>>
>>>>> That sounds kinda risky because you could be ignoring partials  
>>>>> that
>>>>> get rendered that you don't want to be rendered.
>>
>>>> It is, most definately.
>>
>>>>>> , but that doesn't work anymore. I can understand why, but now  
>>>>>> I have
>>>>>> to do something like template.stub!(:render).with(hash_including
>>>>>> (:partial =>
>>>>>> anything)). Except for when I'm testing a partial, then I need to
>>>>>> replace
>>>>>> the anything with every partial I'm rendering in my partial.
>>
>>>>>> Is this the correct way,
>>
>>>>> Seems like the only way at the moment. Wouldn't call it correct or
>>>>> incorrect.
>>
>>>> I would call it ugly :). Not only do I have to remember the
>>>> hash_including part, but also the anything (and not :anything).
>>>> Conceptually, I like the template.stub!(:render). Irendera
>>>> template, on which Istuball the renders. Whether that's risky or
>>>> not is a different discussion.
>>
>>>>>> or is there perhaps something like
>>>>>> template.stub_partials :only => [], :except => [] ?
>>
>>>>> Nothing like this exists. Seems like a reasonable idea. Feel  
>>>>> free to
>>>>> submit a feature request, or better yet, a patch to
>>>>> http://rspec.lighthouseapp.com
>>
>>>> Will do!
>>
>>>> cheers,
>>>> bartz
>>
>>>> _______________________________________________
>>>> rspec-users mailing list
>>>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/ 
>>>> rspec-users
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-us... at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> --
>> Zach Dennishttp://www.continuousthinking.comhttp://www.mutuallyhuman.com
>> _______________________________________________
>> rspec-users mailing list
>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/ 
>> rspec-users
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

From nick at deadorange.com  Thu Mar 19 10:55:28 2009
From: nick at deadorange.com (Nick Hoffman)
Date: Thu, 19 Mar 2009 10:55:28 -0400
Subject: [rspec-users] [rspec] Stubbing partials in view specs
In-Reply-To: <2b516195-4fea-499d-af26-8077b2792586@o11g2000yql.googlegroups.com>
References: <71C878F7-574B-4287-8D5B-FAD56FD8AFB5@gmail.com>
	<57c63afe0901200629y1bb6b1e8vf0acaf2f2c7d5a2@mail.gmail.com>
	<6E3760F3-15A0-4E25-9E70-7DF948A4C8B2@gmail.com>
	<6391f308-2ce8-4727-8049-be56e6ed242a@l16g2000yqo.googlegroups.com>
	<85d99afe0903181523q15756ff4u824248801ad7113a@mail.gmail.com>
	<2b516195-4fea-499d-af26-8077b2792586@o11g2000yql.googlegroups.com>
Message-ID: <16827fa20903190755j2dd1cc51seca601246929aba2@mail.gmail.com>

> Basically, there are two situation.
> 1) I want to check if a function was called and I want to execute the
> function code

I don't think that's possible. Setting a method expectation (Eg:
template.should_receive(:render)) automatically stubs #render.

> 2) I want to check if a function was called and I don't want to
> execute the function code so I used stubbing.

That's how #should_receive works.

> I thought that for the first scenario the solution would be:
> template.should_receive(:render) #only checks if render function was
> called

You're correct that the only thing that's checked is whether or not
#render was called on the "template" object. However, creating that
expectation causes RSpec to stub #render . If you want to confirm
this, call #render , and you'll see that it returns nil. nil is the
default return value for a stubbed method.

> and for the second scenario
> template.stub!(:render) #stub render function
> template.should_receive(:render) #check if render function was called

Mostly! All you need is the call to #should_receive . The call to
#stub! doesn't do anything bad...it just doesn't do anything at all.

Cheers,
Nick

From aslak.hellesoy at gmail.com  Thu Mar 19 11:13:19 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Thu, 19 Mar 2009 11:13:19 -0400
Subject: [rspec-users] [Cucumber 0.2] Failure to use should
In-Reply-To: <ee6f48c00903190725i532b21c5l5c09b8234ea8b88a@mail.gmail.com>
References: <ee6f48c00903190725i532b21c5l5c09b8234ea8b88a@mail.gmail.com>
Message-ID: <8d961d900903190813p6fcb51a3o754db54a6317c125@mail.gmail.com>

2009/3/19 Yi <hayafirst at gmail.com>

> I have a step definition like this:
>
> Then "the account should be created" do
>   account = Account.find_by_name("my shiny new account")
>   p account.class
>   account.should_not be_blank
> end
>
> When running this step, I got the error message:
>
> Account(id: integer, name: string, state: string, next_renewal_at: date,
> created_at: datetime, updated_at: datetime, full_domain: string, deleted_at:
> datetime, subscription_discount_id: integer, subscription_plan_id: integer)
>
>     And the account should be created              #
> features/step_definitions/create_account_steps.rb:31
>       undefined method `be_blank' for
> #<ActionController::Integration::Session:0x349994c> (NoMethodError)
>       features/create_account.feature:10:in `And the account should be
> created'
>

The #be_blank method is defined by a module under 'rspec/matchers'. This
module is automatically included in ActionController::Integration::Session
if you have the following in your env.rb:

require 'spec/expectations'

Do you? If you just upgraded to Cucumber 0.2 you should probably rebootstrap
Cucumber with:

script/generate cucumber

Aslak


> I print out the account class, which is a AR::B. Why cucumber tells me it
> is a ActionController::Integration::Session?
>
> I use cucumber 0.2 and rspec 1.2 with Rails 2.3.2
>
> Thanks
>
> Yi
> --
> http://yiwenandsoftware.wordpress.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/fb2d378f/attachment.html>

From hayafirst at gmail.com  Thu Mar 19 11:39:16 2009
From: hayafirst at gmail.com (Yi)
Date: Thu, 19 Mar 2009 10:39:16 -0500
Subject: [rspec-users] [Cucumber 0.2] Failure to use should
In-Reply-To: <8d961d900903190813p6fcb51a3o754db54a6317c125@mail.gmail.com>
References: <ee6f48c00903190725i532b21c5l5c09b8234ea8b88a@mail.gmail.com>
	<8d961d900903190813p6fcb51a3o754db54a6317c125@mail.gmail.com>
Message-ID: <ee6f48c00903190839h102da972v56446562f9abefb0@mail.gmail.com>

This is my env.rb

# Sets up the Rails environment for Cucumber
ENV["RAILS_ENV"] ||= "test"
require File.expand_path(File.dirname(__FILE__) +
'/../../config/environment')
require 'cucumber/rails/world'
require 'cucumber/formatters/unicode' # Comment out this line if you don't
want Cucumber Unicode support
Cucumber::Rails.use_transactional_fixtures

require 'webrat'

Webrat.configure do |config|
  config.mode = :rails
  config.application_address= "myapp.local"
end

require 'cucumber/rails/rspec'
require 'webrat/core/matchers'


The only thing different is:
  config.application_address= "myapp.local"

I tried to comment out this line and it didn't help anyway.

I did script/generate cucumber and it didn't help. :(

Yi

2009/3/19 aslak hellesoy <aslak.hellesoy at gmail.com>

>
>
> 2009/3/19 Yi <hayafirst at gmail.com>
>
>> I have a step definition like this:
>>
>> Then "the account should be created" do
>>   account = Account.find_by_name("my shiny new account")
>>   p account.class
>>   account.should_not be_blank
>> end
>>
>> When running this step, I got the error message:
>>
>> Account(id: integer, name: string, state: string, next_renewal_at: date,
>> created_at: datetime, updated_at: datetime, full_domain: string, deleted_at:
>> datetime, subscription_discount_id: integer, subscription_plan_id: integer)
>>
>>     And the account should be created              #
>> features/step_definitions/create_account_steps.rb:31
>>       undefined method `be_blank' for
>> #<ActionController::Integration::Session:0x349994c> (NoMethodError)
>>       features/create_account.feature:10:in `And the account should be
>> created'
>>
>
> The #be_blank method is defined by a module under 'rspec/matchers'. This
> module is automatically included in ActionController::Integration::Session
> if you have the following in your env.rb:
>
> require 'spec/expectations'
>
> Do you? If you just upgraded to Cucumber 0.2 you should probably
> rebootstrap Cucumber with:
>
> script/generate cucumber
>
> Aslak
>
>
>> I print out the account class, which is a AR::B. Why cucumber tells me it
>> is a ActionController::Integration::Session?
>>
>> I use cucumber 0.2 and rspec 1.2 with Rails 2.3.2
>>
>> Thanks
>>
>> Yi
>> --
>> http://yiwenandsoftware.wordpress.com
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
>
> --
> Aslak (::)
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
http://yiwenandsoftware.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/2c5212c2/attachment.html>

From scott at railsnewbie.com  Thu Mar 19 11:39:23 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Thu, 19 Mar 2009 11:39:23 -0400
Subject: [rspec-users] [rspec] Stubbing partials in view specs / Test Spy
In-Reply-To: <C9E28BA4-4873-4DCB-BA42-D2EA93C6C540@gmail.com>
References: <71C878F7-574B-4287-8D5B-FAD56FD8AFB5@gmail.com>
	<57c63afe0901200629y1bb6b1e8vf0acaf2f2c7d5a2@mail.gmail.com>
	<6E3760F3-15A0-4E25-9E70-7DF948A4C8B2@gmail.com>
	<6391f308-2ce8-4727-8049-be56e6ed242a@l16g2000yqo.googlegroups.com>
	<85d99afe0903181523q15756ff4u824248801ad7113a@mail.gmail.com>
	<2b516195-4fea-499d-af26-8077b2792586@o11g2000yql.googlegroups.com>
	<C9E28BA4-4873-4DCB-BA42-D2EA93C6C540@gmail.com>
Message-ID: <004E1AFA-2CF1-445F-86C9-85B3D8BA5A73@railsnewbie.com>


On Mar 19, 2009, at 10:30 AM, David Chelimsky wrote:

> On Mar 19, 2009, at 7:59 AM, Evgeny Bogdanov <evgeny.bogdanov at gmail.com 
> > wrote:
>
>> just upgraded to 1.2.0
>> the following code works now:
>>
>>   template.stub!(:render).with(hash_including(:partial => "children/
>> child"))
>>   template.should_receive(:render).with(hash_including(:partial =>
>> "children/child"))
>>
>> The only question that is left for me is about Nick's words:
>> "If you set a method expectation on an object (IE:
>> template.should_receive(:render) ), you don't need to stub the method
>> (IE: template.stub!(:render) isn't needed)."
>>
>> Basically, there are two situation.
>> 1) I want to check if a function was called and I want to execute the
>> function code
>> 2) I want to check if a function was called and I don't want to
>> execute the function code so I used stubbing.
>>
>> I thought that for the first scenario the solution would be:
>> template.should_receive(:render) #only checks if render function was
>> called
>>
>> and for the second scenario
>> template.stub!(:render) #stub render function
>> template.should_receive(:render) #check if render function was called
>>
>> Am I right?
>
> No. What I think you're describing is called a test spy: a means of  
> monitoring interactions without changing the behavior. RSpec's mocks  
> don't provide this. The only ruby framework I'm aware of that does  
> is RR. There may be others.
>

"Before we exercise the SUT, we install a Test Spy as a stand-in for  
depended-on component (DOC) used by the SUT. The Test Spy is designed  
to act as an observation point by recording the method calls made to  
it by the SUT as it is exercised. During the result verification  
phase, the test compares the actual values passed to the Test Spy by  
the SUT with the values expected by the test. "

http://xunitpatterns.com/Test%20Spy.html

Actually, the "Not A Mock" framework also supports the test spy pattern:

http://github.com/notahat/not_a_mock/tree/master

Scott


> A stub (stubs!) overrides an existing method (if one exists) and  
> returns either self or any value you define with and_returns.
>
> A message expectation, or mocked method (should_receive) does the  
> same thing *plus* it verifies that the message was called.
>
>
> HTH,
> David
>
>>
>>
>> Thanks,
>> Evgeny
>>
>> On Mar 18, 11:23 pm, Zach Dennis <zach.den... at gmail.com> wrote:
>>> On Wed, Mar 18, 2009 at 6:18 AM, Evgeny Bogdanov
>>>
>>>
>>>
>>> <evgeny.bogda... at gmail.com> wrote:
>>>> Hello,
>>>> I have a problem similar to one mentioned in this post.
>>>> I call a partial inside another partial.
>>>> _mother.haml contains:
>>>> render :partial => "children/child"
>>>
>>>> In mother_spec.rb file I am trying to stub the render call.
>>>> Here is a working version:
>>>> =============
>>>>   template.should_receive(:render)
>>>>   template.stub!(:render)
>>>
>>>>   render :partial => 'mother'
>>>> ============
>>>> I would prefer to specify that the partial I am stubbing is  
>>>> "children/
>>>> child",
>>>> however the following code doesn't work for me:
>>>> ===========
>>>>   template.stub!(:render).with(hash_including(:partial =>  
>>>> 'children/
>>>> child'))
>>>>   template.expect_render(:partial => 'children/child')
>>>
>>> What version of rspec are you using? #expect_render has been removed
>>> in rspec 1.2 and has been deprecated for a while before that so you
>>> won't want to rely on that unless you're using an old version of
>>> rspec.
>>>
>>>
>>>
>>>>   render :partial => 'mother'
>>>
>>>> : Mock 'render_proxy' expected :render with ({:partial=>"children/
>>>> child"}) once, but received it 0 times
>>>> ===========
>>>> Is it possible to stub the render call with specific partial name?
>>>
>>> You had it right, hash including should work:
>>>   template.stub!(:render).with(hash_including(:partial =>  
>>> "children/child"))
>>>
>>> To stub all partials being rendered:
>>>   template.stub!(:render).with(hash_including(:partial => anything))
>>>
>>> HTH,
>>>
>>>
>>>
>>>
>>>
>>>> Thank you in advance,
>>>> Evgeny
>>>
>>>> On Jan 20, 5:35 pm, Bart Zonneveld <zuperinfin... at gmail.com> wrote:
>>>>> On 20-jan-2009, at 15:29, David Chelimsky wrote:
>>>
>>>>>> On Tue, Jan 20, 2009 at 7:44 AM, Bart Zonneveld
>>>>>> <zuperinfin... at gmail.com> wrote:
>>>>>>> Hey list,
>>>
>>>>>>> As a good BDDer I want to test my views in isolation.
>>>
>>>>>> Sort of. A *good* BDDer wants to *specify* views in isolation.  
>>>>>> Testing
>>>>>> is for testers :)
>>>
>>>>> You're right! I tend to talk a lot to non-programmers, and they  
>>>>> get
>>>>> that glaze-in-the-distance look in their eyes, whenever I mention
>>>>> specifiy, spec'ing, or what have you :).
>>>
>>>>>>> And as a good rails
>>>>>>> programmer, I separate views into partials when needed. So, when
>>>>>>> testing my
>>>>>>> views, I want tostubout rendering of partials in my views. I'm
>>>>>>> working on
>>>>>>> upgrading an app from rails 2.1.2 to 2.2.2, using the latest  
>>>>>>> rspec
>>>>>>> and
>>>>>>> rspec-rails.
>>>
>>>>>>> I used to throw template.stub!(:render) in a before(:each) block
>>>>>>> and be done
>>>>>>> with it
>>>
>>>>>> That sounds kinda risky because you could be ignoring partials  
>>>>>> that
>>>>>> get rendered that you don't want to be rendered.
>>>
>>>>> It is, most definately.
>>>
>>>>>>> , but that doesn't work anymore. I can understand why, but now  
>>>>>>> I have
>>>>>>> to do something like template.stub!(:render).with(hash_including
>>>>>>> (:partial =>
>>>>>>> anything)). Except for when I'm testing a partial, then I need  
>>>>>>> to
>>>>>>> replace
>>>>>>> the anything with every partial I'm rendering in my partial.
>>>
>>>>>>> Is this the correct way,
>>>
>>>>>> Seems like the only way at the moment. Wouldn't call it correct  
>>>>>> or
>>>>>> incorrect.
>>>
>>>>> I would call it ugly :). Not only do I have to remember the
>>>>> hash_including part, but also the anything (and not :anything).
>>>>> Conceptually, I like the template.stub!(:render). Irendera
>>>>> template, on which Istuball the renders. Whether that's risky or
>>>>> not is a different discussion.
>>>
>>>>>>> or is there perhaps something like
>>>>>>> template.stub_partials :only => [], :except => [] ?
>>>
>>>>>> Nothing like this exists. Seems like a reasonable idea. Feel  
>>>>>> free to
>>>>>> submit a feature request, or better yet, a patch to
>>>>>> http://rspec.lighthouseapp.com
>>>
>>>>> Will do!
>>>
>>>>> cheers,
>>>>> bartz
>>>
>>>>> _______________________________________________
>>>>> rspec-users mailing list
>>>>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
>>>> _______________________________________________
>>>> rspec-users mailing list
>>>> rspec-us... at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>> --
>>> Zach Dennishttp://www.continuousthinking.comhttp://www.mutuallyhuman.com
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From pat.maddox at gmail.com  Thu Mar 19 11:59:46 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Thu, 19 Mar 2009 08:59:46 -0700
Subject: [rspec-users] [Cucumber 0.2] Failure to use should
In-Reply-To: <ee6f48c00903190839h102da972v56446562f9abefb0@mail.gmail.com>
References: <ee6f48c00903190725i532b21c5l5c09b8234ea8b88a@mail.gmail.com>
	<8d961d900903190813p6fcb51a3o754db54a6317c125@mail.gmail.com>
	<ee6f48c00903190839h102da972v56446562f9abefb0@mail.gmail.com>
Message-ID: <2c7e61990903190859g4aca06bbk3d3009b2ddd08f37@mail.gmail.com>

Right, you need to add
require 'spec/expectations'

because Cucumber doesn't know about RSpec's matchers by default.

Pat

2009/3/19 Yi <hayafirst at gmail.com>:
> This is my env.rb
>
> # Sets up the Rails environment for Cucumber
> ENV["RAILS_ENV"] ||= "test"
> require File.expand_path(File.dirname(__FILE__) +
> '/../../config/environment')
> require 'cucumber/rails/world'
> require 'cucumber/formatters/unicode' # Comment out this line if you don't
> want Cucumber Unicode support
> Cucumber::Rails.use_transactional_fixtures
>
> require 'webrat'
>
> Webrat.configure do |config|
> ? config.mode = :rails
> ? config.application_address= "myapp.local"
> end
>
> require 'cucumber/rails/rspec'
> require 'webrat/core/matchers'
>
>
> The only thing different is:
> ? config.application_address= "myapp.local"
>
> I tried to comment out this line and it didn't help anyway.
>
> I did script/generate cucumber and it didn't help. :(
>
> Yi
>
> 2009/3/19 aslak hellesoy <aslak.hellesoy at gmail.com>
>>
>>
>> 2009/3/19 Yi <hayafirst at gmail.com>
>>>
>>> I have a step definition like this:
>>>
>>> Then "the account should be created" do
>>> ? account = Account.find_by_name("my shiny new account")
>>> ? p account.class
>>> ? account.should_not be_blank
>>> end
>>>
>>> When running this step, I got the error message:
>>>
>>> Account(id: integer, name: string, state: string, next_renewal_at: date,
>>> created_at: datetime, updated_at: datetime, full_domain: string, deleted_at:
>>> datetime, subscription_discount_id: integer, subscription_plan_id: integer)
>>>
>>> ??? And the account should be created????????????? #
>>> features/step_definitions/create_account_steps.rb:31
>>> ????? undefined method `be_blank' for
>>> #<ActionController::Integration::Session:0x349994c> (NoMethodError)
>>> ????? features/create_account.feature:10:in `And the account should be
>>> created'
>>
>> The #be_blank method is defined by a module under 'rspec/matchers'. This
>> module is automatically included in ActionController::Integration::Session
>> if you have the following in your env.rb:
>>
>> require 'spec/expectations'
>>
>> Do you? If you just upgraded to Cucumber 0.2 you should probably
>> rebootstrap Cucumber with:
>>
>> script/generate cucumber
>>
>> Aslak
>>
>>>
>>> I print out the account class, which is a AR::B. Why cucumber tells me it
>>> is a ActionController::Integration::Session?
>>>
>>> I use cucumber 0.2 and rspec 1.2 with Rails 2.3.2
>>>
>>> Thanks
>>>
>>> Yi
>>> --
>>> http://yiwenandsoftware.wordpress.com
>>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>>
>>
>> --
>> Aslak (::)
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
>
> --
> http://yiwenandsoftware.wordpress.com
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From jari.bakken at finn.no  Thu Mar 19 08:57:01 2009
From: jari.bakken at finn.no (jari.bakken at finn.no)
Date: Thu, 19 Mar 2009 13:57:01 +0100
Subject: [rspec-users] [ANN] celerity 0.0.6 Released
Message-ID: <C5E7FFAD.D66F%jari.bakken@finn.no>

celerity version 0.0.6 has been released!

* http://github.com/jarib/celerity/tree
* http://celerity.rubyforge.org

Celerity is a JRuby wrapper around HtmlUnit - a headless Java browser with JavaScript support. It provides a simple API for programmatic navigation through web applications. Celerity aims at being API compatible with Watir.

Changes:

## 0.0.6 2009-03-19
* Support for meta, strong, dl, dt, dd, and em HTML elements.
* Update to HtmlUnit 2.5-SNAPSHOT.
* New options for Browser#new: :proxy, :charset, :render, :log_level
* Methods added:
  - Browser#add_cookie
  - Browser#asynchronized
  - Browser#add_listener
  - Browser#content_type
  - Browser#cookies
  - Browser#debug_web_connection
  - Browser#focused_element
  - Browser#io
  - Browser#remove_cookie
  - Browser#response_headers
  - Browser#wait
  - Browser#xml
  - Browser#{element,elements}_by_xpath
  - ClickableElement#{double,right}_click
  - ElementCollection#{first,last}
* Methods removed:
  - Browser#show_*
* Methods renamed:
  - SelectList#get_all_contents   => SelectList#options
  - SelectList#get_selected_items => SelectList#selected_options
  - SelectList#clear_selection    => SelectList#clear
* Add support for finding elements by their corresponding <label>.
* Recognize buttons of type image, reset, submit.
* Proxy support (see Browser.new)
* Lots of refactorings, bug fixes and minor enhancements.

Thanks to Hirobumi Hama, Kamal Fariz Mahyuddin and Thomas Marek for contributions in this release.



From jeroentjevandijk at gmail.com  Thu Mar 19 12:35:16 2009
From: jeroentjevandijk at gmail.com (Jeroen van Dijk)
Date: Thu, 19 Mar 2009 17:35:16 +0100
Subject: [rspec-users] Mocking base class methods
In-Reply-To: <49A070F6.2060107@e-tobi.net>
References: <499FE5F9.3050905@e-tobi.net>
	<85d99afe0902211148p585d5e5cx283232b250f2e8b4@mail.gmail.com>
	<49A070F6.2060107@e-tobi.net>
Message-ID: <ecbf28ec0903190935x7073c98cpe652d71cbaa8593d@mail.gmail.com>

Hi all,

I'm having the same problem as Tobi and I wanted to try Tobi mock solution
but unfortunately it does not work for me.

Here is a trivial example I want to test:

module ActiveRecord
  class Base
      def self.count_by_params(params = {}, options = {})
          scoped_by_params(params).count
      end
  end
end

And my spec:
module ActiveRecord
  class Base
    include BaseClassMock
  end
end

class DummyUser < ActiveRecord::Base
end

it "should pass all the params and options to #scope_by_params" do
   params  = { :foo => 1, :bar => 2 }
    options = { :foo => 3, :bar => 4 }
    @dummy = DummyUser
    @dummy.base_class.should_receive(:scope_by_params).with(params, options)
    DummyUser.count_by_params(params, options)
end

With the above example and Tobi's BaseClassMock module I'm getting
"undefined method `should_receive' for #<Object:0x188c164>". Btw, I also get
this when I do not use Tobi be it for for #<Class:0x188cdf8> instead of
Object.

Any suggestions on what I'm doing wrong or a different approach?

Cheers,
Jeroen



On Sat, Feb 21, 2009 at 10:24 PM, Tobi <listaccount at e-tobi.net> wrote:

> Zach Dennis wrote:
>
> > +1 to composition over inheritance here. Mocking at different layers
> > of an inheritance hierarchy sounds like trouble and screams to pull
> > that thing apart.
>
> Good point! I've already tried the composition approach. It solves the
> testabilitiy problems, but it doesn't feel right in this case.
>
> Inheritance seems to be the more natural approach. The C++ application
> will call virtual methods on the base class which should be overriden in a
> derived class. So it seems to make sense to have the same inheritance tree
> in the Ruby counter parts.
>
> If I would use composition, I would at least need to dynamically extend
> the referenced base class so I can override some of the methods that are
> the counter parts of the virtual C++ methods. And I would need to expose
> the referenced class to the C++ code.
>
> I've finally found a way to kinda mock the base class in some way:
>
> module BaseClassMock
>  attr_accessor :base
>
>  def self.included(klass)
>    class << klass
>      @@base_class = Object.new
>
>      def base_class
>        return @@base_class
>      end
>    end
>  end
>
>  def initialize(*args)
>    @@base_class.new(*args) if @@base_class.respond_to?(:new)
>    @base = Object.new
>  end
>
>  def method_missing(symbol, *args)
>    @base.send(symbol, *args)
>  end
> end
>
> Any base class (Swig classes in my case) should then be declared for RSpec
> like:
>
> module Swig
>  class Base; include BaseClassMock; end
> end
>
> And in the specs I can then do:
>
>    Derived.base_class.should_receive(:new).with('something')
>    d = Derived.new('something')
>
> or:
>
>    d = Derived.new
>    d.base.should_receive(:do_something)
>    d.do_something
>
> Tobias
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/b5cb74c3/attachment.html>

From seatmanu at gmail.com  Thu Mar 19 12:40:47 2009
From: seatmanu at gmail.com (Emmanuel Pinault)
Date: Thu, 19 Mar 2009 09:40:47 -0700
Subject: [rspec-users] ANN Cucumber 0.2.0
In-Reply-To: <8d961d900903182322x769fbefei94b0c1b8b1ed419e@mail.gmail.com>
References: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
	<57c63afe0903181221h2c0d5638t5967ea448271b2f2@mail.gmail.com>
	<21798F7D-6CC7-4CF3-989A-0552033E5F02@gmail.com>
	<8d961d900903182322x769fbefei94b0c1b8b1ed419e@mail.gmail.com>
Message-ID: <EF77913A-E5C4-4229-A75C-E049FE77E096@gmail.com>


On Mar 18, 2009, at 11:22 PM, aslak hellesoy wrote:

>
>
> On Wed, Mar 18, 2009 at 4:08 PM, Emmanuel Pinault  
> <seatmanu at gmail.com> wrote:
> Great! Is there  section for the new hook on reporting? I used the  
> old reporting to customized some of our HTML reports and wonder if  
> you have the new hooks documented somewhere?
>
> The public API for formatters is all the methods in   
> Cucumber::Ast::Visitor. Override as you see fit.
> I have updated http://wiki.github.com/aslakhellesoy/cucumber/custom-formatters 
>  to reflect the changes in 0.2.

Thanks ! I started to digg last night into it. Saw one thing wrong in  
the HTML reported where the Span gets escaped ;)

Really like the refactoring you did by the  way. Much cleaner than  
before .

Emmanuel
>
>
>
> Also what is the rerun formatter?
>
> A formatter that prints the location of all failed scenarios. Used  
> by Cucumber's Autotest plugin.


>
>
>
> Thanks
>
> Emmanuel
>
>
> On Mar 18, 2009, at 12:21 PM, David Chelimsky wrote:
>
> 2009/3/18 aslak hellesoy <aslak.hellesoy at gmail.com>:
> I'm happy to announce the release of Cucumber 0.2.0.
>
> There are a some really exciting new features in this release. Some  
> of the
> ones I find most valuable are:
> * tags
> * better output
> * autoformatting of features
> * better i18n
> * Ruby 1.9 support
> * background
> * guess mode
>
> Full release notes are available at
> http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt
> With this release I expect the formatter API to remain fairly  
> stable. Check
> out the Cucumber::Ast::Visitor class for the full API.
>
> Thanks a lot to everyone who has contributed so far. The big internal
> refactoring has now stabilised, so it should be easier to contribute  
> again!
>
> Congrats!!!!!!!
>
>
> Enjoy!
>
> (As usual, wait an hour or two for the gem to rsync around the  
> Rubyforge
> mirror park)
>
> (::) Aslak (::)
>
> What's this, like a cucumber in each ear?
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
>
> -- 
> Aslak (::)
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/8f88d6ab/attachment.html>

From lenny at aps.org  Thu Mar 19 12:44:04 2009
From: lenny at aps.org (Lenny Marks)
Date: Thu, 19 Mar 2009 12:44:04 -0400
Subject: [rspec-users] [Cucumber] Feature vs. Scenario
Message-ID: <44597298-EDF1-4C87-AC2E-D99F41A17945@aps.org>

I'm curious what other people's thoughts are about when to use  
Features vs. Scenarios and how much it matters. I'm getting the sense  
that the line is a thin one, and has more to do with complexity/time  
to develop than anything else. I had originally enforced a fairly  
rigid definition of 'Scenario' to represent a particular  
variation(e.g. sufficient funds, insufficient funds), but lately I've  
been seeing a lot of examples where the scenario is more like a mini- 
feature.

ex. Mini-feature style

Feature: Create a new correspondence to an author

Scenario: Caution users about sending 'questionable' types of  
correspondence

Scenario: Lock manuscript before creating correspondence

These scenarios are each distinct things so to me are 'features' in a  
way but they may also be trivial to implement, so using any kind of   
'a feature should generally take n days/weeks to implement' guideline  
would make that smell. Also, just because it might be trivial to  
implement doesn't mean that I don't want to attach some context/ 
justification for documentation purposes....

ex.

Feature: Create Correspondence /  Caution before creating  
'questionable' types of correspondence
   In order to help avoid sending embarrassing letters
   Users should be forced to confirm they want to proceed
   before being able to create a correspondence deemed 'Questionable'  
by nature of its type
...
Feature: Create Correspondence / Check for locks
	In order to prevent invalid information from being sent out
	I should not be able to create a new correspondence
	when a lock has been placed on the manuscript

It used to be possible to have multiple features per file so feature  
vs. scenario could boil down to: Use feature if you want to annotate.  
This is no longer the case and I'm not convinced that was a good idea  
anyway. I guess that could still be accomplished by organizing  
features via directories  or maybe tags.

create_correspondence/
      caution_questionable.feature
      check_locks.feature

Another style related thing I can't decide on is what my scenarios  
should ideally represent.

One style is to use the scenario title as the 'what' and the Given/ 
When/Thens as the proof(acceptance test)

Scenario: Reject when account has insufficient funds
Given I have an account with $10
And I attempt to withdraw $20
Then I should have $10 in my checking account
And I should see 'Insufficient funds'

Another style is to use the Given/When/Then as the 'what'

Scenario: Insufficient funds
Given I have an account with $10
And I attempt to withdraw $20
Then I should have $10 in my checking account
And I should see 'Insufficient funds'

I find myself leaning toward the former most of the time. This was a  
bad example(too simple), but I find the latter style tends to blur the  
goal a bit.

Thanks
-lenny

From aslak.hellesoy at gmail.com  Thu Mar 19 12:59:35 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Thu, 19 Mar 2009 12:59:35 -0400
Subject: [rspec-users] ANN Cucumber 0.2.0
In-Reply-To: <EF77913A-E5C4-4229-A75C-E049FE77E096@gmail.com>
References: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
	<57c63afe0903181221h2c0d5638t5967ea448271b2f2@mail.gmail.com>
	<21798F7D-6CC7-4CF3-989A-0552033E5F02@gmail.com>
	<8d961d900903182322x769fbefei94b0c1b8b1ed419e@mail.gmail.com>
	<EF77913A-E5C4-4229-A75C-E049FE77E096@gmail.com>
Message-ID: <8d961d900903190959o74762740sef16ce0c459d2e78@mail.gmail.com>

2009/3/19 Emmanuel Pinault <seatmanu at gmail.com>

>
> On Mar 18, 2009, at 11:22 PM, aslak hellesoy wrote:
>
>
>
> On Wed, Mar 18, 2009 at 4:08 PM, Emmanuel Pinault <seatmanu at gmail.com>wrote:
>
>> Great! Is there  section for the new hook on reporting? I used the old
>> reporting to customized some of our HTML reports and wonder if you have the
>> new hooks documented somewhere?
>>
>
> The public API for formatters is all the methods in
> Cucumber::Ast::Visitor. Override as you see fit.
> I have updated
> http://wiki.github.com/aslakhellesoy/cucumber/custom-formatters to reflect
> the changes in 0.2.
>
>
> Thanks ! I started to digg last night into it. Saw one thing wrong in the
> HTML reported where the Span gets escaped ;)
>

Yep I have noticed that too - would be great if you could figure out how to
not have it escaped!


>
> Really like the refactoring you did by the  way. Much cleaner than before .
>
>


Thanks that's encouraging to hear :-)

Aslak


>
> Emmanuel
>
>
>
>
>>
>> Also what is the rerun formatter?
>>
>
> A formatter that prints the location of all failed scenarios. Used by
> Cucumber's Autotest plugin.
>
>
>
>
>
>
>>
>> Thanks
>>
>> Emmanuel
>>
>>
>> On Mar 18, 2009, at 12:21 PM, David Chelimsky wrote:
>>
>>  2009/3/18 aslak hellesoy <aslak.hellesoy at gmail.com>:
>>>
>>>> I'm happy to announce the release of Cucumber 0.2.0.
>>>>
>>>> There are a some really exciting new features in this release. Some of
>>>> the
>>>> ones I find most valuable are:
>>>> * tags
>>>> * better output
>>>> * autoformatting of features
>>>> * better i18n
>>>> * Ruby 1.9 support
>>>> * background
>>>> * guess mode
>>>>
>>>> Full release notes are available at
>>>>
>>>> http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt
>>>> With this release I expect the formatter API to remain fairly stable.
>>>> Check
>>>> out the Cucumber::Ast::Visitor class for the full API.
>>>>
>>>> Thanks a lot to everyone who has contributed so far. The big internal
>>>> refactoring has now stabilised, so it should be easier to contribute
>>>> again!
>>>>
>>>
>>> Congrats!!!!!!!
>>>
>>>
>>>> Enjoy!
>>>>
>>>> (As usual, wait an hour or two for the gem to rsync around the Rubyforge
>>>> mirror park)
>>>>
>>>> (::) Aslak (::)
>>>>
>>>
>>> What's this, like a cucumber in each ear?
>>>
>>>
>>>> _______________________________________________
>>>> rspec-users mailing list
>>>> rspec-users at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>>
>>>>  _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
>
> --
> Aslak (::)
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/568ac3a0/attachment-0001.html>

From seatmanu at gmail.com  Thu Mar 19 13:10:06 2009
From: seatmanu at gmail.com (Emmanuel Pinault)
Date: Thu, 19 Mar 2009 10:10:06 -0700
Subject: [rspec-users] ANN Cucumber 0.2.0
In-Reply-To: <8d961d900903190959o74762740sef16ce0c459d2e78@mail.gmail.com>
References: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
	<57c63afe0903181221h2c0d5638t5967ea448271b2f2@mail.gmail.com>
	<21798F7D-6CC7-4CF3-989A-0552033E5F02@gmail.com>
	<8d961d900903182322x769fbefei94b0c1b8b1ed419e@mail.gmail.com>
	<EF77913A-E5C4-4229-A75C-E049FE77E096@gmail.com>
	<8d961d900903190959o74762740sef16ce0c459d2e78@mail.gmail.com>
Message-ID: <FCA779AD-41BA-4A64-AF93-FF2C697F5382@gmail.com>


On Mar 19, 2009, at 9:59 AM, aslak hellesoy wrote:
>
> Thanks ! I started to digg last night into it. Saw one thing wrong  
> in the HTML reported where the Span gets escaped ;)
>
> Yep I have noticed that too - would be great if you could figure out  
> how to not have it escaped!
>

Working on it and actually an even better looking template :) should  
be done soon :)

Emmanuel
>

From seatmanu at gmail.com  Thu Mar 19 14:13:06 2009
From: seatmanu at gmail.com (Emmanuel Pinault)
Date: Thu, 19 Mar 2009 11:13:06 -0700
Subject: [rspec-users] ANN Cucumber 0.2.0
In-Reply-To: <8d961d900903190959o74762740sef16ce0c459d2e78@mail.gmail.com>
References: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
	<57c63afe0903181221h2c0d5638t5967ea448271b2f2@mail.gmail.com>
	<21798F7D-6CC7-4CF3-989A-0552033E5F02@gmail.com>
	<8d961d900903182322x769fbefei94b0c1b8b1ed419e@mail.gmail.com>
	<EF77913A-E5C4-4229-A75C-E049FE77E096@gmail.com>
	<8d961d900903190959o74762740sef16ce0c459d2e78@mail.gmail.com>
Message-ID: <4B752382-F8B6-4CFD-9BF6-22733108F9BF@gmail.com>


On Mar 19, 2009, at 9:59 AM, aslak hellesoy wrote
>
> Thanks ! I started to digg last night into it. Saw one thing wrong  
> in the HTML reported where the Span gets escaped ;)
>
> Yep I have noticed that too - would be great if you could figure out  
> how to not have it escaped!

Not sure it is the best way but it works:

       def visit_step_name(keyword, step_match, status, source_indent,  
background)
         #step_name is not exposed for some reason... maybe it should?  
That would simplify it even more
         step_name = step_match.format_args(lambda{|param| "#{param}"})

         step_parts = step_match.step_name.split(/ 
#{step_match.args.join("|")}/)

         @builder.li(:class => status) do
           @builder.text!("#{keyword}")
            step_parts.each_with_index do |part, index|
              @builder.text!("#{part}")
              @builder.span("#{step_match.args[index]}") if  
step_match.args[index]
            end
         end
       end

Few comments :

1) Maybe you could expose step_name are read only? I added the  
following in the formatter file on top as it would simplify the first  
line in visit_step_name

module Cucumber
    class Step
      attr_reader :step_name
    end
end

2 ) Also, I notice that now it is harder to attached a table to step  
(maybe it is due to the changes on how table can be used ...) and  
error as well. So I cannot easily add the error in the li than the  
step as the sequential logic in Step#accept won t allow it..  Not a  
bit deal it was nice to be able to have the error as part of the same LI

I can send you the final change I made to my template (That will look  
like close to Rspec in a way)  if you are interested in. Would be  
better than the default for now :)

Emmanuel
	
>
>
>
> Really like the refactoring you did by the  way. Much cleaner than  
> before .
>
>
> Thanks that's encouraging to hear :-)
>
> Aslak
>
>
> Emmanuel
>
>>
>>
>>
>> Also what is the rerun formatter?
>>
>> A formatter that prints the location of all failed scenarios. Used  
>> by Cucumber's Autotest plugin.
>
>
>>
>>
>>
>> Thanks
>>
>> Emmanuel
>>
>>
>> On Mar 18, 2009, at 12:21 PM, David Chelimsky wrote:
>>
>> 2009/3/18 aslak hellesoy <aslak.hellesoy at gmail.com>:
>> I'm happy to announce the release of Cucumber 0.2.0.
>>
>> There are a some really exciting new features in this release. Some  
>> of the
>> ones I find most valuable are:
>> * tags
>> * better output
>> * autoformatting of features
>> * better i18n
>> * Ruby 1.9 support
>> * background
>> * guess mode
>>
>> Full release notes are available at
>> http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt
>> With this release I expect the formatter API to remain fairly  
>> stable. Check
>> out the Cucumber::Ast::Visitor class for the full API.
>>
>> Thanks a lot to everyone who has contributed so far. The big internal
>> refactoring has now stabilised, so it should be easier to  
>> contribute again!
>>
>> Congrats!!!!!!!
>>
>>
>> Enjoy!
>>
>> (As usual, wait an hour or two for the gem to rsync around the  
>> Rubyforge
>> mirror park)
>>
>> (::) Aslak (::)
>>
>> What's this, like a cucumber in each ear?
>>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>>
>>
>> -- 
>> Aslak (::)
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
>
> -- 
> Aslak (::)
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/5e5d98ef/attachment.html>

From mark at mwilden.com  Thu Mar 19 15:58:30 2009
From: mark at mwilden.com (Mark Wilden)
Date: Thu, 19 Mar 2009 12:58:30 -0700
Subject: [rspec-users] [Cucumber] Feature vs. Scenario
In-Reply-To: <44597298-EDF1-4C87-AC2E-D99F41A17945@aps.org>
References: <44597298-EDF1-4C87-AC2E-D99F41A17945@aps.org>
Message-ID: <3c30da400903191258g2380d8e9k29dbb766c7952e0c@mail.gmail.com>

On Thu, Mar 19, 2009 at 9:44 AM, Lenny Marks <lenny at aps.org> wrote:

> These scenarios are each distinct things so to me are 'features' in a way
> but they may also be trivial to implement, so using any kind of ?'a feature
> should generally take n days/weeks to implement' guideline would make that
> smell.

I don't think there is a correspondence between a feature and its
implementation time. A feature defines a unit of user value. A very
useful feature could be trivial to implement. A minor feature could
take weeks. This is why developers should cost features, not business.

///ark

From apremdas at gmail.com  Thu Mar 19 17:52:47 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Thu, 19 Mar 2009 21:52:47 +0000
Subject: [rspec-users] [Cucumber] Feature vs. Scenario
In-Reply-To: <44597298-EDF1-4C87-AC2E-D99F41A17945@aps.org>
References: <44597298-EDF1-4C87-AC2E-D99F41A17945@aps.org>
Message-ID: <88fd8ddc0903191452r7a2763f9va73f588f3349e235@mail.gmail.com>

I think writing features is a new art form and as such we just don't know
answers to questions like this yet. After a while we might be able to move
towards a consensus given certain criteria, and people might be able to come
up with rules of thumb that help (i.e. if its got more than 7 scenarios
create another feature). But ultimately the judgement will be very
subjective and very dependent on context.

As features develop and more scenarios are implemented alot of refactoring
should be done to

1. Make sure scenarios are in the 'right' feature
2. To create new features when a feature gets overladen with scenarios
3. To change the location of a feature in your feature hierarchy so its in
the obvious place

In a similar way step definitions will need refactoring and adjusting.

I can see that a projects features can easily turn into a chaotic mess if
you don't keep on top of this.

There is a great advantage in viewing your features as a whole, and ensuring
this whole is beautiful and describes you application with precision and
clarity. Whilst this will inevitably lenghthen the task of writing features
when you begin, it will greatly reduce the burden of writing features when
your project is more mature.

HTH

Andrew


On a related point I think your examples would read better with a when

Scenario: Reject a withdrawl when account has insufficient funds
Given I have an account with $10
 When I attempt to withdraw $20
Then I should have $10 in my checking account
And I should see 'Insufficient funds'




2009/3/19 Lenny Marks <lenny at aps.org>

> I'm curious what other people's thoughts are about when to use Features vs.
> Scenarios and how much it matters. I'm getting the sense that the line is a
> thin one, and has more to do with complexity/time to develop than anything
> else. I had originally enforced a fairly rigid definition of 'Scenario' to
> represent a particular variation(e.g. sufficient funds, insufficient funds),
> but lately I've been seeing a lot of examples where the scenario is more
> like a mini-feature.
>
> ex. Mini-feature style
>
> Feature: Create a new correspondence to an author
>
> Scenario: Caution users about sending 'questionable' types of
> correspondence
>
> Scenario: Lock manuscript before creating correspondence
>
> These scenarios are each distinct things so to me are 'features' in a way
> but they may also be trivial to implement, so using any kind of  'a feature
> should generally take n days/weeks to implement' guideline would make that
> smell. Also, just because it might be trivial to implement doesn't mean that
> I don't want to attach some context/justification for documentation
> purposes....
>
> ex.
>
> Feature: Create Correspondence /  Caution before creating 'questionable'
> types of correspondence
>  In order to help avoid sending embarrassing letters
>  Users should be forced to confirm they want to proceed
>  before being able to create a correspondence deemed 'Questionable' by
> nature of its type
> ...
> Feature: Create Correspondence / Check for locks
>        In order to prevent invalid information from being sent out
>        I should not be able to create a new correspondence
>        when a lock has been placed on the manuscript
>
> It used to be possible to have multiple features per file so feature vs.
> scenario could boil down to: Use feature if you want to annotate. This is no
> longer the case and I'm not convinced that was a good idea anyway. I guess
> that could still be accomplished by organizing features via directories  or
> maybe tags.
>
> create_correspondence/
>     caution_questionable.feature
>     check_locks.feature
>
> Another style related thing I can't decide on is what my scenarios should
> ideally represent.
>
> One style is to use the scenario title as the 'what' and the
> Given/When/Thens as the proof(acceptance test)
>
> Scenario: Reject when account has insufficient funds
> Given I have an account with $10
> And I attempt to withdraw $20
> Then I should have $10 in my checking account
> And I should see 'Insufficient funds'
>
> Another style is to use the Given/When/Then as the 'what'
>
> Scenario: Insufficient funds
> Given I have an account with $10
> And I attempt to withdraw $20
> Then I should have $10 in my checking account
> And I should see 'Insufficient funds'
>
> I find myself leaning toward the former most of the time. This was a bad
> example(too simple), but I find the latter style tends to blur the goal a
> bit.
>
> Thanks
> -lenny
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/78aba063/attachment-0001.html>

From hayafirst at gmail.com  Thu Mar 19 18:03:39 2009
From: hayafirst at gmail.com (Yi)
Date: Thu, 19 Mar 2009 17:03:39 -0500
Subject: [rspec-users] [Cucumber 0.2] Failure to use should
In-Reply-To: <2c7e61990903190859g4aca06bbk3d3009b2ddd08f37@mail.gmail.com>
References: <ee6f48c00903190725i532b21c5l5c09b8234ea8b88a@mail.gmail.com>
	<8d961d900903190813p6fcb51a3o754db54a6317c125@mail.gmail.com>
	<ee6f48c00903190839h102da972v56446562f9abefb0@mail.gmail.com>
	<2c7e61990903190859g4aca06bbk3d3009b2ddd08f37@mail.gmail.com>
Message-ID: <ee6f48c00903191503v5f99a48dj58c111116243a100@mail.gmail.com>

I thought be_something is actually handled by rspec class Be. be_blank
essentially asks the object blank? predicate. Not that there is a "be_blank"
method declared anywhere.

Anyway, require 'spec/expectations' doesn't solve the problem. I will look
into this. Thanks

Yi

On Thu, Mar 19, 2009 at 10:59 AM, Pat Maddox <pat.maddox at gmail.com> wrote:

> Right, you need to add
> require 'spec/expectations'
>
> because Cucumber doesn't know about RSpec's matchers by default.
>
> Pat
>
> 2009/3/19 Yi <hayafirst at gmail.com>:
> > This is my env.rb
> >
> > # Sets up the Rails environment for Cucumber
> > ENV["RAILS_ENV"] ||= "test"
> > require File.expand_path(File.dirname(__FILE__) +
> > '/../../config/environment')
> > require 'cucumber/rails/world'
> > require 'cucumber/formatters/unicode' # Comment out this line if you
> don't
> > want Cucumber Unicode support
> > Cucumber::Rails.use_transactional_fixtures
> >
> > require 'webrat'
> >
> > Webrat.configure do |config|
> >   config.mode = :rails
> >   config.application_address= "myapp.local"
> > end
> >
> > require 'cucumber/rails/rspec'
> > require 'webrat/core/matchers'
> >
> >
> > The only thing different is:
> >   config.application_address= "myapp.local"
> >
> > I tried to comment out this line and it didn't help anyway.
> >
> > I did script/generate cucumber and it didn't help. :(
> >
> > Yi
> >
> > 2009/3/19 aslak hellesoy <aslak.hellesoy at gmail.com>
> >>
> >>
> >> 2009/3/19 Yi <hayafirst at gmail.com>
> >>>
> >>> I have a step definition like this:
> >>>
> >>> Then "the account should be created" do
> >>>   account = Account.find_by_name("my shiny new account")
> >>>   p account.class
> >>>   account.should_not be_blank
> >>> end
> >>>
> >>> When running this step, I got the error message:
> >>>
> >>> Account(id: integer, name: string, state: string, next_renewal_at:
> date,
> >>> created_at: datetime, updated_at: datetime, full_domain: string,
> deleted_at:
> >>> datetime, subscription_discount_id: integer, subscription_plan_id:
> integer)
> >>>
> >>>     And the account should be created              #
> >>> features/step_definitions/create_account_steps.rb:31
> >>>       undefined method `be_blank' for
> >>> #<ActionController::Integration::Session:0x349994c> (NoMethodError)
> >>>       features/create_account.feature:10:in `And the account should be
> >>> created'
> >>
> >> The #be_blank method is defined by a module under 'rspec/matchers'. This
> >> module is automatically included in
> ActionController::Integration::Session
> >> if you have the following in your env.rb:
> >>
> >> require 'spec/expectations'
> >>
> >> Do you? If you just upgraded to Cucumber 0.2 you should probably
> >> rebootstrap Cucumber with:
> >>
> >> script/generate cucumber
> >>
> >> Aslak
> >>
> >>>
> >>> I print out the account class, which is a AR::B. Why cucumber tells me
> it
> >>> is a ActionController::Integration::Session?
> >>>
> >>> I use cucumber 0.2 and rspec 1.2 with Rails 2.3.2
> >>>
> >>> Thanks
> >>>
> >>> Yi
> >>> --
> >>> http://yiwenandsoftware.wordpress.com
> >>>
> >>> _______________________________________________
> >>> rspec-users mailing list
> >>> rspec-users at rubyforge.org
> >>> http://rubyforge.org/mailman/listinfo/rspec-users
> >>
> >>
> >>
> >> --
> >> Aslak (::)
> >>
> >> _______________________________________________
> >> rspec-users mailing list
> >> rspec-users at rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/rspec-users
> >
> >
> >
> > --
> > http://yiwenandsoftware.wordpress.com
> >
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
http://yiwenandsoftware.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/a36f9ca0/attachment.html>

From ashley.moran at patchspace.co.uk  Thu Mar 19 18:11:00 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Thu, 19 Mar 2009 22:11:00 +0000
Subject: [rspec-users] ANN Cucumber 0.2.0
In-Reply-To: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
References: <8d961d900903181216u343610efu473ebaa2c9f91f9f@mail.gmail.com>
Message-ID: <3E0C8396-AB35-4206-B486-286C8BE42414@patchspace.co.uk>


On 18 Mar 2009, at 19:16, aslak hellesoy wrote:

> I'm happy to announce the release of Cucumber 0.2.0.


Thanks!  I just can't exaggerate how much of a difference Cucumber  
(and RSpec) makes to me.

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From rick.denatale at gmail.com  Thu Mar 19 20:01:27 2009
From: rick.denatale at gmail.com (Rick DeNatale)
Date: Thu, 19 Mar 2009 20:01:27 -0400
Subject: [rspec-users] RSpec style and truthiness
Message-ID: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>

I like to avoid over-constraining specifications, so for example of methods
which return 'boolean' values, I prefer to test either truthiness (anything
but false or nil), or falsiness (either false or nil).
This isn't an issue true predicate methods which are of the right form to
use be_whatever (as in a whatever? method taking no arguments). But for a
method taking arguments this doesn't work (I think!), and even if it did I
wouldn't want to use it for some cases. For instance I'm working with some
code now (which I'm not really free to change) which has methods like
has_member?(user) which tells whether or not the object has user as a
member.  So I tend to write things like

   @it.has_member?(user).should be
when the response is expected to be truthy
or
   @it.has_member?(user).should_not be

Now I recently noticed that if the second expectation fails, I get a rather
snarky message like 'not only did it fail, but it's awkwardly expressed, try
to express it as a positive.'

While I agree that it isn't as elegant an expression as I like, I don't see
a way out of the box to check that a result should be a falsy (or should
that be non-truthy) value.

Even 'should be' is a bit grating.  I'm tempted to write a pair of matchers
like be_truthy and be_falsy, but I was wondering what other RSpec users have
to say.

-- 
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090319/8b3b595c/attachment.html>

From dchelimsky at gmail.com  Thu Mar 19 20:37:13 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 19 Mar 2009 19:37:13 -0500
Subject: [rspec-users] RSpec style and truthiness
In-Reply-To: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
References: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
Message-ID: <57c63afe0903191737q4947fdd2ia5e563b431f9fe56@mail.gmail.com>

2009/3/19 Rick DeNatale <rick.denatale at gmail.com>:
> I like to avoid?over-constraining?specifications, so for example of methods
> which return 'boolean' values, I prefer to test either truthiness (anything
> but false or nil), or falsiness (either false or nil).
> This isn't an issue true predicate methods which are of the right form to
> use be_whatever (as in a whatever? method taking no arguments). But for a
> method taking arguments this doesn't work (I think!), and even if it did I
> wouldn't want to use it for some cases. For instance I'm working with some
> code now (which I'm not really free to change) which has methods like
> has_member?(user) which tells whether or not the object has user as a
> member. ?So I tend to write things like
> ?? @it.has_member?(user).should be

You *can* actually say @it.should have_member(user) :)

> when the response is expected to be truthy
> or
> ?? @it.has_member?(user).should_not be
> Now I recently noticed that if the second expectation fails, I get a rather
> snarky message like 'not only did it fail, but it's awkwardly expressed, try
> to express it as a positive.'

Pardon the snarkiness (I wrote that) - that was intended for a
different situation (should_not be < 5, instead of should be >= 5),
and the fact that you're seeing it for just 'be' is a bug.

> While I agree that it isn't as elegant an expression as I like, I don't see
> a way out of the box to check that a result should be a falsy (or should
> that be non-truthy) value.
> Even 'should be' is a bit grating. ?I'm tempted to write a pair of matchers
> like be_truthy and be_falsy, but I was wondering what other RSpec users have
> to say.

I can't tell you why, but be_truthy sounds fine to me, but be_falsy
sounds awful.

How about "should be_truthy" or "should_not be_truthy"?

>
> --
> Rick DeNatale
>
> Blog: http://talklikeaduck.denhaven2.com/
> Twitter: http://twitter.com/RickDeNatale
> WWR: http://www.workingwithrails.com/person/9021-rick-denatale
> LinkedIn: http://www.linkedin.com/in/rickdenatale
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From pat.maddox at gmail.com  Thu Mar 19 20:38:28 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Thu, 19 Mar 2009 17:38:28 -0700
Subject: [rspec-users] RSpec style and truthiness
In-Reply-To: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
References: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
Message-ID: <2c7e61990903191738w210d203ke765b028cf7a3aa3@mail.gmail.com>

I hate should/should_not be and so if I really *have* to do it then I
just throw a !! in the method and get back a real boolean.  Not ideal,
but it works.

HOWEVER

Predicate matchers *do* accept args, and in the specific example you
gave, the have matcher comes to the rescue.  Check out these examples:
 http://gist.github.com/82148

The first one shows the typical be_blah form taking an arg, and the
second one shows some magic provided by the have matcher.

Pat


2009/3/19 Rick DeNatale <rick.denatale at gmail.com>:
> I like to avoid?over-constraining?specifications, so for example of methods
> which return 'boolean' values, I prefer to test either truthiness (anything
> but false or nil), or falsiness (either false or nil).
> This isn't an issue true predicate methods which are of the right form to
> use be_whatever (as in a whatever? method taking no arguments). But for a
> method taking arguments this doesn't work (I think!), and even if it did I
> wouldn't want to use it for some cases. For instance I'm working with some
> code now (which I'm not really free to change) which has methods like
> has_member?(user) which tells whether or not the object has user as a
> member. ?So I tend to write things like
> ?? @it.has_member?(user).should be
> when the response is expected to be truthy
> or
> ?? @it.has_member?(user).should_not be
> Now I recently noticed that if the second expectation fails, I get a rather
> snarky message like 'not only did it fail, but it's awkwardly expressed, try
> to express it as a positive.'
> While I agree that it isn't as elegant an expression as I like, I don't see
> a way out of the box to check that a result should be a falsy (or should
> that be non-truthy) value.
> Even 'should be' is a bit grating. ?I'm tempted to write a pair of matchers
> like be_truthy and be_falsy, but I was wondering what other RSpec users have
> to say.
>
> --
> Rick DeNatale
>
> Blog: http://talklikeaduck.denhaven2.com/
> Twitter: http://twitter.com/RickDeNatale
> WWR: http://www.workingwithrails.com/person/9021-rick-denatale
> LinkedIn: http://www.linkedin.com/in/rickdenatale
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From sfeley at gmail.com  Thu Mar 19 23:20:07 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Thu, 19 Mar 2009 23:20:07 -0400
Subject: [rspec-users] RSpec style and truthiness
In-Reply-To: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
References: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
Message-ID: <1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>

2009/3/19 Rick DeNatale <rick.denatale at gmail.com>:
> Even 'should be' is a bit grating. ?I'm tempted to write a pair of matchers
> like be_truthy and be_falsy, but I was wondering what other RSpec users have
> to say.

should be || should_not be: that is the expectation:
Whether 'tis nobler in the parser to interpret
The outputs and side effects of outrageous duck typing,
Or to inherit against a sea of matchers
And by declaration extend them?  To fail: to raise;
No more; and by a raise to say we throw
The exception and the thousand natural returns
The code is heir to, 'tis a specification
Devoutly to be wished.  To fail: to raise;
To raise, perchance to rescue: ay, there's the rub,
For in that state of exception what tests may fail
When we have injected in this matcher code
Must give us pause: there's the RSpec
That makes calamity of such long backtraces;
For who would bear the Flogs and Heckles,
The oppressor's Reek, the proud man's Cucumber,
The pangs of despised Rcov, the spec_server's Drb,
The insolence of Autotest and the spurns
That patient merit of the occasional Rakes,
When he himself might his validation make
With a bare assertion?  .....


(...And so forth.  All of which is to say, before my Muse molested me,
that I rather _like_ the sparse "should be" and "should_not be" specs.
 Simple is good, and there's a poetry about them.  Keep 'em!)



-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From rspec at nigelthorne.com  Thu Mar 19 23:39:14 2009
From: rspec at nigelthorne.com (Nigel Thorne)
Date: Thu, 19 Mar 2009 20:39:14 -0700 (PDT)
Subject: [rspec-users] [cucumber] getting scenario name in hook
In-Reply-To: <1ebf5a4d0903111712j354a23f0hc82c2e2e55acb39e@mail.gmail.com>
References: <1ebf5a4d0903110812i6291ec87i58541e1a94812574@mail.gmail.com>
	<8d961d900903110921h79d8134cv42df0804affbef5d@mail.gmail.com>
	<1ebf5a4d0903111712j354a23f0hc82c2e2e55acb39e@mail.gmail.com>
Message-ID: <22613814.post@talk.nabble.com>


Where in the scenario object is the name stored? 

Cheers. 
Nigel


walketim wrote:
> 
> That did the trick. Thanks Aslak! Took a little while to figure out
> where it was in the Scenario object but it was pretty straight forward
> from there.
> 
> T
> 
> On Wed, Mar 11, 2009 at 10:21 AM, aslak hellesoy
> <aslak.hellesoy at gmail.com> wrote:
>>
>>
>> On Wed, Mar 11, 2009 at 4:12 PM, Tim Walker <walketim at gmail.com> wrote:
>>>
>>> Hi Guys,
>>>
>>> If I am generating diagnostics from a before do step can I get the
>>> name of the scenario?
>>
>> This is implemented in 0.1.99.x:
>> http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/44
>>
>> Aslak
>>
>>>
>>> Many thanks,
>>>
>>> Tim
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
> 
> 

-- 
View this message in context: http://www.nabble.com/-cucumber--getting-scenario-name-in-hook-tp22457271p22613814.html
Sent from the rspec-users mailing list archive at Nabble.com.


From dchelimsky at gmail.com  Thu Mar 19 23:42:01 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Thu, 19 Mar 2009 22:42:01 -0500
Subject: [rspec-users] RSpec style and truthiness
In-Reply-To: <1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>
References: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
	<1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>
Message-ID: <57c63afe0903192042j8f47dd8waceb55fa7211499c@mail.gmail.com>

On Thu, Mar 19, 2009 at 10:20 PM, Stephen Eley <sfeley at gmail.com> wrote:
> 2009/3/19 Rick DeNatale <rick.denatale at gmail.com>:
>> Even 'should be' is a bit grating. ?I'm tempted to write a pair of matchers
>> like be_truthy and be_falsy, but I was wondering what other RSpec users have
>> to say.
>

what_follows.should be_brilliant

> should be || should_not be: that is the expectation:
> Whether 'tis nobler in the parser to interpret
> The outputs and side effects of outrageous duck typing,
> Or to inherit against a sea of matchers
> And by declaration extend them? ?To fail: to raise;
> No more; and by a raise to say we throw
> The exception and the thousand natural returns
> The code is heir to, 'tis a specification
> Devoutly to be wished. ?To fail: to raise;
> To raise, perchance to rescue: ay, there's the rub,
> For in that state of exception what tests may fail
> When we have injected in this matcher code
> Must give us pause: there's the RSpec
> That makes calamity of such long backtraces;
> For who would bear the Flogs and Heckles,
> The oppressor's Reek, the proud man's Cucumber,
> The pangs of despised Rcov, the spec_server's Drb,
> The insolence of Autotest and the spurns
> That patient merit of the occasional Rakes,
> When he himself might his validation make
> With a bare assertion? ?.....
>
>
> (...And so forth. ?All of which is to say, before my Muse molested me,
> that I rather _like_ the sparse "should be" and "should_not be" specs.
> ?Simple is good, and there's a poetry about them. ?Keep 'em!)
>
>
>
> --
> Have Fun,
> ? Steve Eley (sfeley at gmail.com)
> ? ESCAPE POD - The Science Fiction Podcast Magazine
> ? http://www.escapepod.org
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From lists at ruby-forum.com  Thu Mar 19 23:42:04 2009
From: lists at ruby-forum.com (jazzez ravi)
Date: Fri, 20 Mar 2009 04:42:04 +0100
Subject: [rspec-users] Basic help
In-Reply-To: <57c63afe0903190536n614c5f7fs5ef46d373389f712@mail.gmail.com>
References: <85e02fd87dcbe97b37352667d1b2b4f3@ruby-forum.com>
	<57c63afe0903190536n614c5f7fs5ef46d373389f712@mail.gmail.com>
Message-ID: <3ef8f39d9ea4de1485d4b6d721c02357@ruby-forum.com>

David Chelimsky wrote:
> On Thu, Mar 19, 2009 at 4:28 AM, jazzez ravi <lists at ruby-forum.com> 
> wrote:
>> ?before(:each) do
>> class Bowling
>>
>>>ruby bowling_spec.rb --format specdoc
> 
> Use the spec command (that's what's there on http://rspec.info):
> 
> spec bowling_spec.rb --format specdoc
> 
> Cheers,
> David

Hi David,

spec bowling_spec.rb --format specdoc is working ..

Thank you

Regards,
P.Raveendran
http://raveendran.wordpress.com

-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Thu Mar 19 23:57:47 2009
From: lists at ruby-forum.com (jazzez ravi)
Date: Fri, 20 Mar 2009 04:57:47 +0100
Subject: [rspec-users] Basic help
In-Reply-To: <85d99afe0903190536w7f8212e2mb3a769b60ba82ad4@mail.gmail.com>
References: <85e02fd87dcbe97b37352667d1b2b4f3@ruby-forum.com>
	<85d99afe0903190536w7f8212e2mb3a769b60ba82ad4@mail.gmail.com>
Message-ID: <1f37f71bc729f320ec6d69bd430b4a61@ruby-forum.com>

Zach Dennis wrote:
> On Thu, Mar 19, 2009 at 5:28 AM, jazzez ravi <lists at ruby-forum.com> 
> wrote:
>> ?before(:each) do
>> class Bowling
>>
>> require 'spec' --> ?No Error But also no output mentioned as per that
>> website.
>>
>> Please anyone help to continue that program.
> 
> Try to put this at the top:
> 
> require 'rubygems'
> require 'spec'
> 
> I have an environment variable set to always load rubygems on my
> system so I can omit the require of it explicitly in code:
> 
> RUBYOPTS=-rubygems
> 
> 
> 
>>
> --
> Zach Dennis
> http://www.continuousthinking.com
> http://www.mutuallyhuman.com

Hi Zach,

I tried this one too. But the same error occurred.

spec bowling_spec.rb --format specdoc is working ..

Thank you


Regards,
P.Raveendran
http://raveendran.wordpress.com

-- 
Posted via http://www.ruby-forum.com/.

From matt-lists at reprocessed.org  Fri Mar 20 02:46:49 2009
From: matt-lists at reprocessed.org (Matt Patterson)
Date: Fri, 20 Mar 2009 06:46:49 +0000
Subject: [rspec-users] bypass_rescue and its inverse
Message-ID: <167B10B3-E924-4899-AE92-9B11FD7E7EEA@reprocessed.org>

Hey,

I've just started using rspec-rails 1.2 and the bypass rescue  
declaration is wonderful - by default I tend to write controller which  
raise exceptions (in exceptional circumstances), along with before- 
filters as guard clauses, so being able to switch off rescue from  
(which I properly spec separately) is a real boon.

Such a boon, in fact, that I immediately shoved it into a global  
before :each block so that my controller specs would do what I expect  
by default.

However, that makes my speccing of the rescue_from code a little  
trickier. Is there an easy way to do the inverse: to switch the  
default Rails behaviour back on, on command?

Thanks,

Matt

PS

I guess the other option is to figure out how to declaratively spec  
rescue from (which I, and judging by forks of the  
rspec_on_rails_matchers plugin, several others figured out for before  
filters)...

Bit unawake yet, may follow up with an answer to my own question when  
I've imbibed the caffeine.


-- 
   Matt Patterson | Design & Code
   <matt at reprocessed org> | http://www.reprocessed.org/




From pat.maddox at gmail.com  Fri Mar 20 02:49:50 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Thu, 19 Mar 2009 23:49:50 -0700
Subject: [rspec-users] RSpec style and truthiness
In-Reply-To: <57c63afe0903192042j8f47dd8waceb55fa7211499c@mail.gmail.com>
References: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
	<1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>
	<57c63afe0903192042j8f47dd8waceb55fa7211499c@mail.gmail.com>
Message-ID: <2c7e61990903192349x30a80e4el9b4d07e73a583f71@mail.gmail.com>

On Thu, Mar 19, 2009 at 8:42 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Thu, Mar 19, 2009 at 10:20 PM, Stephen Eley <sfeley at gmail.com> wrote:
>> 2009/3/19 Rick DeNatale <rick.denatale at gmail.com>:
>>> Even 'should be' is a bit grating. ?I'm tempted to write a pair of matchers
>>> like be_truthy and be_falsy, but I was wondering what other RSpec users have
>>> to say.
>>
>
> what_follows.should be_brilliant

ugh I think you've just reopened the debate over whether we ought to
use should/is/must/etc

:)

That was fantastic Stephen, thanks!

From joe at josephwilk.net  Fri Mar 20 05:56:51 2009
From: joe at josephwilk.net (Joseph Wilk)
Date: Fri, 20 Mar 2009 09:56:51 +0000
Subject: [rspec-users] RSpec style and truthiness
In-Reply-To: <1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>
References: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
	<1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>
Message-ID: <49C36863.4000909@josephwilk.net>

Stephen Eley wrote:
> 2009/3/19 Rick DeNatale <rick.denatale at gmail.com>:
>   
>> Even 'should be' is a bit grating.  I'm tempted to write a pair of matchers
>> like be_truthy and be_falsy, but I was wondering what other RSpec users have
>> to say.
>>     
>
> should be || should_not be: that is the expectation:
> Whether 'tis nobler in the parser to interpret
> The outputs and side effects of outrageous duck typing,
> Or to inherit against a sea of matchers
> And by declaration extend them?  To fail: to raise;
> No more; and by a raise to say we throw
> The exception and the thousand natural returns
> The code is heir to, 'tis a specification
> Devoutly to be wished.  To fail: to raise;
> To raise, perchance to rescue: ay, there's the rub,
> For in that state of exception what tests may fail
> When we have injected in this matcher code
> Must give us pause: there's the RSpec
> That makes calamity of such long backtraces;
> For who would bear the Flogs and Heckles,
> The oppressor's Reek, the proud man's Cucumber,
> The pangs of despised Rcov, the spec_server's Drb,
> The insolence of Autotest and the spurns
> That patient merit of the occasional Rakes,
> When he himself might his validation make
> With a bare assertion?  .....
>   
Please frame that and put it on a wall somewhere. Its Quite brilliant.

--
Joseph Wilk
http://blog.josephwilk.net

>
> (...And so forth.  All of which is to say, before my Muse molested me,
> that I rather _like_ the sparse "should be" and "should_not be" specs.
>  Simple is good, and there's a poetry about them.  Keep 'em!)
>
>
>
>   


From jeroentjevandijk at gmail.com  Fri Mar 20 06:30:54 2009
From: jeroentjevandijk at gmail.com (Jeroen van Dijk)
Date: Fri, 20 Mar 2009 11:30:54 +0100
Subject: [rspec-users] Mocking base class methods
In-Reply-To: <ecbf28ec0903190935x7073c98cpe652d71cbaa8593d@mail.gmail.com>
References: <499FE5F9.3050905@e-tobi.net>
	<85d99afe0902211148p585d5e5cx283232b250f2e8b4@mail.gmail.com>
	<49A070F6.2060107@e-tobi.net>
	<ecbf28ec0903190935x7073c98cpe652d71cbaa8593d@mail.gmail.com>
Message-ID: <ecbf28ec0903200330g655a59e1gc61522c95b9cc785@mail.gmail.com>

Huray, got it solved! Hopefully you'll agree with this solution (thanks to
mocha sorry)


  describe "count_by_params" do
    it "should pass all the params and options to #scope_by_params" do
      params  = { :foo => 1, :bar => 2 }
      options = { :foo => 3, :bar => 4 }

      @base = ActiveRecord::Base
      @result = mock("query results", :count => 1)
      @base.expects(:scoped_by_params).with(params,
options).returns(@result)
      @base.count_by_params(params, options)
    end



On Thu, Mar 19, 2009 at 5:35 PM, Jeroen van Dijk <jeroentjevandijk at gmail.com
> wrote:

> Hi all,
>
> I'm having the same problem as Tobi and I wanted to try Tobi mock solution
> but unfortunately it does not work for me.
>
> Here is a trivial example I want to test:
>
> module ActiveRecord
>   class Base
>       def self.count_by_params(params = {}, options = {})
>           scoped_by_params(params).count
>       end
>   end
> end
>
> And my spec:
> module ActiveRecord
>   class Base
>     include BaseClassMock
>   end
> end
>
> class DummyUser < ActiveRecord::Base
> end
>
> it "should pass all the params and options to #scope_by_params" do
>    params  = { :foo => 1, :bar => 2 }
>     options = { :foo => 3, :bar => 4 }
>     @dummy = DummyUser
>     @dummy.base_class.should_receive(:scope_by_params).with(params,
> options)
>     DummyUser.count_by_params(params, options)
> end
>
> With the above example and Tobi's BaseClassMock module I'm getting
> "undefined method `should_receive' for #<Object:0x188c164>". Btw, I also get
> this when I do not use Tobi be it for for #<Class:0x188cdf8> instead of
> Object.
>
> Any suggestions on what I'm doing wrong or a different approach?
>
> Cheers,
> Jeroen
>
>
>
>
> On Sat, Feb 21, 2009 at 10:24 PM, Tobi <listaccount at e-tobi.net> wrote:
>
>> Zach Dennis wrote:
>>
>> > +1 to composition over inheritance here. Mocking at different layers
>> > of an inheritance hierarchy sounds like trouble and screams to pull
>> > that thing apart.
>>
>> Good point! I've already tried the composition approach. It solves the
>> testabilitiy problems, but it doesn't feel right in this case.
>>
>> Inheritance seems to be the more natural approach. The C++ application
>> will call virtual methods on the base class which should be overriden in a
>> derived class. So it seems to make sense to have the same inheritance tree
>> in the Ruby counter parts.
>>
>> If I would use composition, I would at least need to dynamically extend
>> the referenced base class so I can override some of the methods that are
>> the counter parts of the virtual C++ methods. And I would need to expose
>> the referenced class to the C++ code.
>>
>> I've finally found a way to kinda mock the base class in some way:
>>
>> module BaseClassMock
>>  attr_accessor :base
>>
>>  def self.included(klass)
>>    class << klass
>>      @@base_class = Object.new
>>
>>      def base_class
>>        return @@base_class
>>      end
>>    end
>>  end
>>
>>  def initialize(*args)
>>    @@base_class.new(*args) if @@base_class.respond_to?(:new)
>>    @base = Object.new
>>  end
>>
>>  def method_missing(symbol, *args)
>>    @base.send(symbol, *args)
>>  end
>> end
>>
>> Any base class (Swig classes in my case) should then be declared for RSpec
>> like:
>>
>> module Swig
>>  class Base; include BaseClassMock; end
>> end
>>
>> And in the specs I can then do:
>>
>>    Derived.base_class.should_receive(:new).with('something')
>>    d = Derived.new('something')
>>
>> or:
>>
>>    d = Derived.new
>>    d.base.should_receive(:do_something)
>>    d.do_something
>>
>> Tobias
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090320/be5567e4/attachment-0001.html>

From lists at ruby-forum.com  Fri Mar 20 06:59:08 2009
From: lists at ruby-forum.com (Tom Ten Thij)
Date: Fri, 20 Mar 2009 11:59:08 +0100
Subject: [rspec-users] [cucumber] Creating an item without worrying about
	validity?
Message-ID: <b9725b4f18687f723a7ebbf5af320e22@ruby-forum.com>

In order to check at the cucumber level if permissions are working
correctly I am trying to write a cucumber scenario that tests if a
logged in user can create a certain model.

The step I am trying to implement is 'When I post valid attributes of a
frooble'. What I have been trying to do is build a frooble using a
factory and doing a post using it attributes. This makes me run into the
same issue as http://www.ruby-forum.com/topic/167579.

The alternative is to have to have to go through the steps of filling in
a valid form for a frooble, but I do not really care about that at this
stage, having to write them for each model will cost a lot of time and
it will cause brittleness in my tests.

Any suggestions? Should I give up trying to do this elegantly?

Tom.
-- 
Posted via http://www.ruby-forum.com/.

From matt-lists at reprocessed.org  Fri Mar 20 09:15:16 2009
From: matt-lists at reprocessed.org (Matt Patterson)
Date: Fri, 20 Mar 2009 13:15:16 +0000
Subject: [rspec-users] [cucumber] Creating an item without worrying
	about validity?
In-Reply-To: <b9725b4f18687f723a7ebbf5af320e22@ruby-forum.com>
References: <b9725b4f18687f723a7ebbf5af320e22@ruby-forum.com>
Message-ID: <38890DA2-13E9-4A61-A9E1-5CE4C63C0A89@reprocessed.org>

On 20 Mar 2009, at 10:59, Tom Ten Thij wrote:

> In order to check at the cucumber level if permissions are working
> correctly I am trying to write a cucumber scenario that tests if a
> logged in user can create a certain model.

Hey Tom

> The alternative is to have to have to go through the steps of  
> filling in
> a valid form for a frooble, but I do not really care about that at  
> this
> stage, having to write them for each model will cost a lot of time and
> it will cause brittleness in my tests.
>
> Any suggestions? Should I give up trying to do this elegantly?

I wonder, if you don't care about the actual filling in of the form,  
is this really a controller-level spec which has snuck into your  
integration-level scenarios?

My gut would be to exercise the permission system in isolation at  
controller level and then write features to work through the actual  
filling stuff when that became important to me again.

I.e. write 'X can create Y' scenarios for your 'creating a Y' feature  
when you need it. You could also pop in some 'X should not be able to  
create Y' scenarios to exercise the refusal side of permissions, and  
the user experience of being refused...

Matt


-- 
   Matt Patterson | Design & Code
   <matt at reprocessed org> | http://www.reprocessed.org/




From matt-lists at reprocessed.org  Fri Mar 20 09:18:12 2009
From: matt-lists at reprocessed.org (Matt Patterson)
Date: Fri, 20 Mar 2009 13:18:12 +0000
Subject: [rspec-users] bypass_rescue and its inverse
In-Reply-To: <167B10B3-E924-4899-AE92-9B11FD7E7EEA@reprocessed.org>
References: <167B10B3-E924-4899-AE92-9B11FD7E7EEA@reprocessed.org>
Message-ID: <77333640-DFC4-490F-834F-1F45C49CE614@reprocessed.org>

On 20 Mar 2009, at 06:46, Matt Patterson wrote:

> Such a boon, in fact, that I immediately shoved bypass_rescue into a  
> global before :each block so that my controller specs would do what  
> I expect by default.
>
> However, that makes my speccing of the rescue_from code a little  
> trickier. Is there an easy way to do the inverse: to switch the  
> default Rails behaviour back on, on command?
>
> I guess the other option is to figure out how to declaratively spec  
> rescue from (which I, and judging by forks of the  
> rspec_on_rails_matchers plugin, several others figured out for  
> before filters)...
>
> Bit unawake yet, may follow up with an answer to my own question  
> when I've imbibed the caffeine.


As predicted, I woke up and implemented a declarative matcher (will  
also work on anything which includes ActiveSupport::Rescuable). Up in  
rough form at http://github.com/fidothe/rspec-on-rails-matchers/tree/master 
. It won't work if you've used a block with rescue_from, but I decided  
I could live without that...

Matt


-- 
   Matt Patterson | Design & Code
   <matt at reprocessed org> | http://www.reprocessed.org/




From lists at ruby-forum.com  Fri Mar 20 09:45:23 2009
From: lists at ruby-forum.com (James Byrne)
Date: Fri, 20 Mar 2009 14:45:23 +0100
Subject: [rspec-users] Having a problem with new webrat matchers in cucumber
	2
Message-ID: <27586b327f7aaf3096fa2f5e397dd17c@ruby-forum.com>

I ran script/generate cucumber and since then I am having a few
difficulties.  For instance, take this case:


When /see (?:an|the) authori(?:s|z)ation required message/ do
  Then "I should see \"You are not authori(?:s|z)ed\""
end

Now gives:

    And they should see an authorization required message
           # features/app/step_definitions/authorization_steps.rb:1
      expected the following element's content to include
           "You are not authori(?:s|z)ed":
...
          You are not authorized to access the requested resource

This matcher worked perfectly well in cucumber up to and including  v
0.2.0, until after I ran script/generate cucumber.  The problem seems to
be the substitution in webrat_steps.rb of:

 response.should contain(text)
for
 response.body.should =~ /#{text}/m

I have reverted to the old style matcher which solves my immediate
problem.  My question is: Was subpattern matching deliberately removed
from this matcher or is this an error?

P.S. This is Canada and up here both 'ise' (UK) and 'ize' (US) endings
are commonly used. However, generally those who choose one despise those
who choose the other.  So as to have peace over a triviality I provide
for both.
-- 
Posted via http://www.ruby-forum.com/.

From zach.dennis at gmail.com  Fri Mar 20 10:18:51 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Fri, 20 Mar 2009 10:18:51 -0400
Subject: [rspec-users] Mocking base class methods
In-Reply-To: <ecbf28ec0903200330g655a59e1gc61522c95b9cc785@mail.gmail.com>
References: <499FE5F9.3050905@e-tobi.net>
	<85d99afe0902211148p585d5e5cx283232b250f2e8b4@mail.gmail.com>
	<49A070F6.2060107@e-tobi.net>
	<ecbf28ec0903190935x7073c98cpe652d71cbaa8593d@mail.gmail.com>
	<ecbf28ec0903200330g655a59e1gc61522c95b9cc785@mail.gmail.com>
Message-ID: <85d99afe0903200718w3c909e4asf39870b82b52dd51@mail.gmail.com>

2009/3/20 Jeroen van Dijk <jeroentjevandijk at gmail.com>:
> Huray, got it solved! Hopefully you'll agree with this solution (thanks to
> mocha sorry)
>
>
> ? describe "count_by_params" do
> ??? it "should pass all the params and options to #scope_by_params" do
> ????? params? = { :foo => 1, :bar => 2 }
> ????? options = { :foo => 3, :bar => 4 }
>
> ????? @base = ActiveRecord::Base
> ????? @result = mock("query results", :count => 1)
> ????? @base.expects(:scoped_by_params).with(params,
> options).returns(@result)
> ????? @base.count_by_params(params, options)
> ??? end
>

Is #scoped_by_params a public method that has its own examples? Down
at the model level I would want to know that count_by_params actually
was working as expected and not just collaborating with itself to call
an internal method. I don't know how crazy scoped_by_params is so
maybe there is a potential risk you're willing to accept given the
complexity of what it does, but this example raises my eyebrow as to
the behaviour your actually expecting and verifying.


>
> On Thu, Mar 19, 2009 at 5:35 PM, Jeroen van Dijk
> <jeroentjevandijk at gmail.com> wrote:
>>
>> Hi all,
>>
>> I'm having the same problem as Tobi and I wanted to try Tobi mock solution
>> but unfortunately it does not work for me.
>>
>> Here is a trivial example I want to test:
>>
>> module ActiveRecord
>> ? class Base
>> ????? def self.count_by_params(params = {}, options = {})
>> ??? ????? scoped_by_params(params).count
>> ??? ? end
>> ? end
>> end
>>
>> And my spec:
>> module ActiveRecord
>> ? class Base
>> ??? include BaseClassMock
>> ? end
>> end
>>
>> class DummyUser < ActiveRecord::Base
>> end
>>
>> it "should pass all the params and options to #scope_by_params" do
>> ?? params? = { :foo => 1, :bar => 2 }
>> ??? options = { :foo => 3, :bar => 4 }
>> ??? @dummy = DummyUser
>> ??? @dummy.base_class.should_receive(:scope_by_params).with(params,
>> options)
>> ??? DummyUser.count_by_params(params, options)
>> end
>>
>> With the above example and Tobi's BaseClassMock module I'm getting
>> "undefined method `should_receive' for #<Object:0x188c164>". Btw, I also get
>> this when I do not use Tobi be it for for #<Class:0x188cdf8> instead of
>> Object.
>>
>> Any suggestions on what I'm doing wrong or a different approach?
>>
>> Cheers,
>> Jeroen
>>
>>
>>
>> On Sat, Feb 21, 2009 at 10:24 PM, Tobi <listaccount at e-tobi.net> wrote:
>>>
>>> Zach Dennis wrote:
>>>
>>> > +1 to composition over inheritance here. Mocking at different layers
>>> > of an inheritance hierarchy sounds like trouble and screams to pull
>>> > that thing apart.
>>>
>>> Good point! I've already tried the composition approach. It solves the
>>> testabilitiy problems, but it doesn't feel right in this case.
>>>
>>> Inheritance seems to be the more natural approach. The C++ application
>>> will call virtual methods on the base class which should be overriden in
>>> a
>>> derived class. So it seems to make sense to have the same inheritance
>>> tree
>>> in the Ruby counter parts.
>>>
>>> If I would use composition, I would at least need to dynamically extend
>>> the referenced base class so I can override some of the methods that are
>>> the counter parts of the virtual C++ methods. And I would need to expose
>>> the referenced class to the C++ code.
>>>
>>> I've finally found a way to kinda mock the base class in some way:
>>>
>>> module BaseClassMock
>>> ?attr_accessor :base
>>>
>>> ?def self.included(klass)
>>> ? ?class << klass
>>> ? ? ?@@base_class = Object.new
>>>
>>> ? ? ?def base_class
>>> ? ? ? ?return @@base_class
>>> ? ? ?end
>>> ? ?end
>>> ?end
>>>
>>> ?def initialize(*args)
>>> ? ?@@base_class.new(*args) if @@base_class.respond_to?(:new)
>>> ? ?@base = Object.new
>>> ?end
>>>
>>> ?def method_missing(symbol, *args)
>>> ? ?@base.send(symbol, *args)
>>> ?end
>>> end
>>>
>>> Any base class (Swig classes in my case) should then be declared for
>>> RSpec
>>> like:
>>>
>>> module Swig
>>> ?class Base; include BaseClassMock; end
>>> end
>>>
>>> And in the specs I can then do:
>>>
>>> ? ?Derived.base_class.should_receive(:new).with('something')
>>> ? ?d = Derived.new('something')
>>>
>>> or:
>>>
>>> ? ?d = Derived.new
>>> ? ?d.base.should_receive(:do_something)
>>> ? ?d.do_something
>>>
>>> Tobias
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From aslak.hellesoy at gmail.com  Fri Mar 20 10:34:30 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Fri, 20 Mar 2009 10:34:30 -0400
Subject: [rspec-users] Having a problem with new webrat matchers in
	cucumber 2
In-Reply-To: <27586b327f7aaf3096fa2f5e397dd17c@ruby-forum.com>
References: <27586b327f7aaf3096fa2f5e397dd17c@ruby-forum.com>
Message-ID: <8d961d900903200734q9aa2febsbc3ac51ffd325c4c@mail.gmail.com>

On Fri, Mar 20, 2009 at 9:45 AM, James Byrne <lists at ruby-forum.com> wrote:

> I ran script/generate cucumber and since then I am having a few
> difficulties.  For instance, take this case:
>
>
> When /see (?:an|the) authori(?:s|z)ation required message/ do
>  Then "I should see \"You are not authori(?:s|z)ed\""
> end
>
> Now gives:
>
>    And they should see an authorization required message
>           # features/app/step_definitions/authorization_steps.rb:1
>      expected the following element's content to include
>           "You are not authori(?:s|z)ed":
> ...
>          You are not authorized to access the requested resource
>
> This matcher worked perfectly well in cucumber up to and including  v
> 0.2.0, until after I ran script/generate cucumber.  The problem seems to
> be the substitution in webrat_steps.rb of:
>
>  response.should contain(text)
> for
>  response.body.should =~ /#{text}/m
>

We switched to using response.should contain(text) a while back. This is
just a wrapper around Rails' assert_contain, the preferred (I think) way to
check for text on a page.

I'm not sure what Cucumber version you're on.

Aslak

>
> I have reverted to the old style matcher which solves my immediate
> problem.  My question is: Was subpattern matching deliberately removed
> from this matcher or is this an error?
>
> P.S. This is Canada and up here both 'ise' (UK) and 'ize' (US) endings
> are commonly used. However, generally those who choose one despise those
> who choose the other.  So as to have peace over a triviality I provide
> for both.
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090320/f6cc2a58/attachment.html>

From sfeley at gmail.com  Fri Mar 20 10:30:02 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Fri, 20 Mar 2009 10:30:02 -0400
Subject: [rspec-users] RSpec style and truthiness
In-Reply-To: <57c63afe0903192042j8f47dd8waceb55fa7211499c@mail.gmail.com>
References: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
	<1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>
	<57c63afe0903192042j8f47dd8waceb55fa7211499c@mail.gmail.com>
Message-ID: <1fb4df0903200730s591a4932od08e73ae78a24666@mail.gmail.com>

On Thu, Mar 19, 2009 at 11:42 PM, David Chelimsky <dchelimsky at gmail.com> wrote:
>
> what_follows.should be_brilliant

Thank you!  Glad I could provide a bit of entertainment.

(And hmmm.  Now I'm wondering why Ruby culture doesn't have a
phenomenon like that of Perl culture, where hackers have 'Perl Poetry'
competitions with poems that actually compile and run.  Wouldn't it be
easier to do in Ruby?  Or is it because putting 'def' in front of all
methods makes it hard to write anything except outdated hip-hop?)


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From rick.denatale at gmail.com  Fri Mar 20 10:39:52 2009
From: rick.denatale at gmail.com (Rick DeNatale)
Date: Fri, 20 Mar 2009 10:39:52 -0400
Subject: [rspec-users] RSpec style and truthiness
In-Reply-To: <1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>
References: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
	<1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>
Message-ID: <deb2337a0903200739s57474af2yf2037eed74fc9c73@mail.gmail.com>

On Thu, Mar 19, 2009 at 11:20 PM, Stephen Eley <sfeley at gmail.com> wrote:

> 2009/3/19 Rick DeNatale <rick.denatale at gmail.com>:
> > Even 'should be' is a bit grating.  I'm tempted to write a pair of
> matchers
> > like be_truthy and be_falsy, but I was wondering what other RSpec users
> have
> > to say.
>
> should be || should_not be: that is the expectation:
> Whether 'tis nobler in the parser to interpret



Alas, poor Eley!  I knew him Chelmsky.


-- 
Rick DeNatale

Blog: http://talklikeaduck.denhaven2.com/
Twitter: http://twitter.com/RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090320/2472d354/attachment-0001.html>

From ben at benmabey.com  Fri Mar 20 10:42:27 2009
From: ben at benmabey.com (Ben Mabey)
Date: Fri, 20 Mar 2009 08:42:27 -0600
Subject: [rspec-users] RSpec style and truthiness
In-Reply-To: <1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>
References: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
	<1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>
Message-ID: <49C3AB53.6010702@benmabey.com>

Stephen Eley wrote:
> 2009/3/19 Rick DeNatale <rick.denatale at gmail.com>:
>   
>> Even 'should be' is a bit grating.  I'm tempted to write a pair of matchers
>> like be_truthy and be_falsy, but I was wondering what other RSpec users have
>> to say.
>>     
>
> should be || should_not be: that is the expectation:
> Whether 'tis nobler in the parser to interpret
> The outputs and side effects of outrageous duck typing,
> Or to inherit against a sea of matchers
> And by declaration extend them?  To fail: to raise;
> No more; and by a raise to say we throw
> The exception and the thousand natural returns
> The code is heir to, 'tis a specification
> Devoutly to be wished.  To fail: to raise;
> To raise, perchance to rescue: ay, there's the rub,
> For in that state of exception what tests may fail
> When we have injected in this matcher code
> Must give us pause: there's the RSpec
> That makes calamity of such long backtraces;
> For who would bear the Flogs and Heckles,
> The oppressor's Reek, the proud man's Cucumber,
> The pangs of despised Rcov, the spec_server's Drb,
> The insolence of Autotest and the spurns
> That patient merit of the occasional Rakes,
> When he himself might his validation make
> With a bare assertion?  .....
>
>
> (...And so forth.  All of which is to say, before my Muse molested me,
> that I rather _like_ the sparse "should be" and "should_not be" specs.
>  Simple is good, and there's a poetry about them.  Keep 'em!)
>   

That is just great.  You have quite the talent.  On another mailing list 
we were talking about the standard story templates and it was suggested 
that we write the stories in prose to make them more interesting to 
read.  Alistair Cockburn came up with this funny little limerick after 
reading Liz Keogh's post about CAPTCHA[1]:

A spunky young buyer named Spry
   Went online to buy something fly
      But he found that a bot
      Had taken his spot
   Now he'll fill out a captcha and not cry



-Ben



1. 
http://lizkeogh.com/2008/09/10/feature-injection-and-handling-technical-stories/





From dchelimsky at gmail.com  Fri Mar 20 10:45:47 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 20 Mar 2009 09:45:47 -0500
Subject: [rspec-users] RSpec style and truthiness
In-Reply-To: <49C36863.4000909@josephwilk.net>
References: <deb2337a0903191701t662ba4eteb75fa3add4efee4@mail.gmail.com>
	<1fb4df0903192020q1eecebf4ue7a7f6be6a7ee4ae@mail.gmail.com>
	<49C36863.4000909@josephwilk.net>
Message-ID: <57c63afe0903200745v51a8c0c0yf2b0a376cadff893@mail.gmail.com>

On Fri, Mar 20, 2009 at 4:56 AM, Joseph Wilk <joe at josephwilk.net> wrote:
> Stephen Eley wrote:
>>
>> 2009/3/19 Rick DeNatale <rick.denatale at gmail.com>:
>>
>>>
>>> Even 'should be' is a bit grating. ?I'm tempted to write a pair of
>>> matchers
>>> like be_truthy and be_falsy, but I was wondering what other RSpec users
>>> have
>>> to say.
>>>
>>
>> should be || should_not be: that is the expectation:
>> Whether 'tis nobler in the parser to interpret
>> The outputs and side effects of outrageous duck typing,
>> Or to inherit against a sea of matchers
>> And by declaration extend them? ?To fail: to raise;
>> No more; and by a raise to say we throw
>> The exception and the thousand natural returns
>> The code is heir to, 'tis a specification
>> Devoutly to be wished. ?To fail: to raise;
>> To raise, perchance to rescue: ay, there's the rub,
>> For in that state of exception what tests may fail
>> When we have injected in this matcher code
>> Must give us pause: there's the RSpec
>> That makes calamity of such long backtraces;
>> For who would bear the Flogs and Heckles,
>> The oppressor's Reek, the proud man's Cucumber,
>> The pangs of despised Rcov, the spec_server's Drb,
>> The insolence of Autotest and the spurns
>> That patient merit of the occasional Rakes,
>> When he himself might his validation make
>> With a bare assertion? ?.....
>>
>
> Please frame that and put it on a wall somewhere. Its Quite brilliant.

Nay frame, nor wall, yet viewable by all:
http://wiki.github.com/dchelimsky/rspec/should-be-should_not-be

>
> --
> Joseph Wilk
> http://blog.josephwilk.net
>
>>
>> (...And so forth. ?All of which is to say, before my Muse molested me,
>> that I rather _like_ the sparse "should be" and "should_not be" specs.
>> ?Simple is good, and there's a poetry about them. ?Keep 'em!)
>>
>>
>>
>>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From zach.dennis at gmail.com  Fri Mar 20 11:11:52 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Fri, 20 Mar 2009 11:11:52 -0400
Subject: [rspec-users] Problem spec'ing ActionMailer with attachment,
	body 	not getting rendered.
In-Reply-To: <deb2337a0903181328u284e7e6ep168867b50ce000c2@mail.gmail.com>
References: <deb2337a0903181328u284e7e6ep168867b50ce000c2@mail.gmail.com>
Message-ID: <85d99afe0903200811l78db9cfal88aaf3cc4e211ce5@mail.gmail.com>

2009/3/18 Rick DeNatale <rick.denatale at gmail.com>:
> I've got a simple ActionMailer::Base subclass:
> class InfoMailer < ActionMailer::Base
>
> ????def info(user, zip_name)
> ?? ?recipients user.email
> ?? ?subject "Requested Info"
> ?? ?attachment(:content_type => "application/zip",
> ?? ? ? ? ? ? ? ?:filename => zip_name,
> ?? ? ? ? ? ? ? ?:body => File.read(zip_name))
> ?? ?body(:message => "Here is the Info that you Requested")
> ??end
> end
> I'm trying to spec this
> following?http://www.rubytutorials.net/2008/02/26/small-rspec-revelations-actionmailer/
> describe AssetsInfoMailer do
> ??before(:each) do
> ?? ?@user = mock_model(User,
> ?? ? ? ?:email => @user_email = "somewhere at over.the.rainbow",
> ?? ? ? ?:full_name => "The Wicked Witch of the West"
> ?? ? ? ?)
> ?? ?ActionMailer::Base.delivery_method = :test
> ?? ?ActionMailer::Base.perform_deliveries = true
> ?? ?ActionMailer::Base.deliveries = []
> ??end
> ??describe ".info" do
> ?? ?before(:each) do
> ?? ? ?@path = 'xyz.zip'
> ?? ? ?@attachment_body = 'zip_file_contents'
> ?? ? ?File.stub!(:read).and_return(@attachment_body)
> ?? ? ?@the_mail = AssetsInfoMailer.deliver_info(@user, at path)
> ?? ? ?@attachments = @the_mail.attachments
> ?? ?end
>
> ?? ?it "should have the right body" do
> ?? ? ?@the_mail.body.should == ""
> ?? ?end
> ??end
> The expectation of an empty string is just to see what's actually getting
> returned, the result is:
> 1)
> 'AssetsInfoMailer.info should have the right body' FAILED
> expected: "",
> ?? ? got: "Attachment: xyz.zip\n" (using ==)
> It's looking like the mail template never got rendered, and body is giving
> me the attachment since it's the only part.
> I've got one other mailer method in that mailer which doesn't contain an
> attachement, and it's body comes out fine.
> I'm not sure what's going on here, and I'd appreciate any
> help/insight/condolences...
>

When sending attachments emails are sent as multipart messages. The
only part being specified is the attachment. The other call to "body"
is being ignored. Try something like:

def info(user, zip_name)
  recipients user.email
  subject "Requested Info"
  attachment(:content_type => "application/zip",
              :filename => zip_name,
              :body => File.read(zip_name))
  part "text/plain" do |p|
    p.body(:message => "Here is the Info that you Requested")
  end
end

Also when you look at the email you'll have look at its #parts
otherwise @the_mail.body is going to returned the body representation
of each part concatenated.



> --
> Rick DeNatale
>
> Blog: http://talklikeaduck.denhaven2.com/
> Twitter: http://twitter.com/RickDeNatale
> WWR: http://www.workingwithrails.com/person/9021-rick-denatale
> LinkedIn: http://www.linkedin.com/in/rickdenatale
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From lists at ruby-forum.com  Fri Mar 20 11:42:34 2009
From: lists at ruby-forum.com (James Byrne)
Date: Fri, 20 Mar 2009 16:42:34 +0100
Subject: [rspec-users] Having a problem with new webrat matchers in
	cucumber 2
In-Reply-To: <8d961d900903200734q9aa2febsbc3ac51ffd325c4c@mail.gmail.com>
References: <27586b327f7aaf3096fa2f5e397dd17c@ruby-forum.com>
	<8d961d900903200734q9aa2febsbc3ac51ffd325c4c@mail.gmail.com>
Message-ID: <217bb29885cef303847b283adc071dd6@ruby-forum.com>

Aslak Helles?y wrote:
> 
> We switched to using response.should contain(text) a while back. This is
> just a wrapper around Rails' assert_contain, the preferred (I think) way 
> to check for text on a page.
> 
> I'm not sure what Cucumber version you're on.
> 
> Aslak

V 0.2.0
-- 
Posted via http://www.ruby-forum.com/.

From zach.dennis at gmail.com  Fri Mar 20 11:46:52 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Fri, 20 Mar 2009 11:46:52 -0400
Subject: [rspec-users] Problem spec'ing ActionMailer with attachment,
	body 	not getting rendered.
In-Reply-To: <85d99afe0903200811l78db9cfal88aaf3cc4e211ce5@mail.gmail.com>
References: <deb2337a0903181328u284e7e6ep168867b50ce000c2@mail.gmail.com>
	<85d99afe0903200811l78db9cfal88aaf3cc4e211ce5@mail.gmail.com>
Message-ID: <85d99afe0903200846p5fa8d460v4ea7d4aa8d8ed994@mail.gmail.com>

On Fri, Mar 20, 2009 at 11:11 AM, Zach Dennis <zach.dennis at gmail.com> wrote:
> 2009/3/18 Rick DeNatale <rick.denatale at gmail.com>:
>> I've got a simple ActionMailer::Base subclass:
>> class InfoMailer < ActionMailer::Base
>>
>> ????def info(user, zip_name)
>> ?? ?recipients user.email
>> ?? ?subject "Requested Info"
>> ?? ?attachment(:content_type => "application/zip",
>> ?? ? ? ? ? ? ? ?:filename => zip_name,
>> ?? ? ? ? ? ? ? ?:body => File.read(zip_name))
>> ?? ?body(:message => "Here is the Info that you Requested")
>> ??end
>> end
>> I'm trying to spec this
>> following?http://www.rubytutorials.net/2008/02/26/small-rspec-revelations-actionmailer/
>> describe AssetsInfoMailer do
>> ??before(:each) do
>> ?? ?@user = mock_model(User,
>> ?? ? ? ?:email => @user_email = "somewhere at over.the.rainbow",
>> ?? ? ? ?:full_name => "The Wicked Witch of the West"
>> ?? ? ? ?)
>> ?? ?ActionMailer::Base.delivery_method = :test
>> ?? ?ActionMailer::Base.perform_deliveries = true
>> ?? ?ActionMailer::Base.deliveries = []
>> ??end
>> ??describe ".info" do
>> ?? ?before(:each) do
>> ?? ? ?@path = 'xyz.zip'
>> ?? ? ?@attachment_body = 'zip_file_contents'
>> ?? ? ?File.stub!(:read).and_return(@attachment_body)
>> ?? ? ?@the_mail = AssetsInfoMailer.deliver_info(@user, at path)
>> ?? ? ?@attachments = @the_mail.attachments
>> ?? ?end
>>
>> ?? ?it "should have the right body" do
>> ?? ? ?@the_mail.body.should == ""
>> ?? ?end
>> ??end
>> The expectation of an empty string is just to see what's actually getting
>> returned, the result is:
>> 1)
>> 'AssetsInfoMailer.info should have the right body' FAILED
>> expected: "",
>> ?? ? got: "Attachment: xyz.zip\n" (using ==)
>> It's looking like the mail template never got rendered, and body is giving
>> me the attachment since it's the only part.
>> I've got one other mailer method in that mailer which doesn't contain an
>> attachement, and it's body comes out fine.
>> I'm not sure what's going on here, and I'd appreciate any
>> help/insight/condolences...
>>
>
> When sending attachments emails are sent as multipart messages. The
> only part being specified is the attachment. The other call to "body"
> is being ignored. Try something like:
>
> def info(user, zip_name)
> ?recipients user.email
> ?subject "Requested Info"
> ?attachment(:content_type => "application/zip",
> ? ? ? ? ? ? ?:filename => zip_name,
> ? ? ? ? ? ? ?:body => File.read(zip_name))
> ?part "text/plain" do |p|
> ? ?p.body(:message => "Here is the Info that you Requested")
> ?end
> end

I just tried my out, and while it does work because there are multiple
parts specified, also re-ordering of the initial #body to come before
the attachment doesn't seem to help with the original code either.

I'm curious now what you do find out and which route you decide to go,
keep us posted either way Rick.

>
> Also when you look at the email you'll have look at its #parts
> otherwise @the_mail.body is going to returned the body representation
> of each part concatenated.
>
>
>
>> --
>> Rick DeNatale
>>
>> Blog: http://talklikeaduck.denhaven2.com/
>> Twitter: http://twitter.com/RickDeNatale
>> WWR: http://www.workingwithrails.com/person/9021-rick-denatale
>> LinkedIn: http://www.linkedin.com/in/rickdenatale
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
>
> --
> Zach Dennis
> http://www.continuousthinking.com
> http://www.mutuallyhuman.com
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From lists at ruby-forum.com  Fri Mar 20 11:52:42 2009
From: lists at ruby-forum.com (James Byrne)
Date: Fri, 20 Mar 2009 16:52:42 +0100
Subject: [rspec-users] Having a problem with new webrat matchers in
	cucumber 2
In-Reply-To: <217bb29885cef303847b283adc071dd6@ruby-forum.com>
References: <27586b327f7aaf3096fa2f5e397dd17c@ruby-forum.com>
	<8d961d900903200734q9aa2febsbc3ac51ffd325c4c@mail.gmail.com>
	<217bb29885cef303847b283adc071dd6@ruby-forum.com>
Message-ID: <304dddff4b5fa8d019b89c2f218e385d@ruby-forum.com>

James Byrne wrote:
> Aslak Helles?y wrote:
>> 
>> We switched to using response.should contain(text) a while back. This is
>> just a wrapper around Rails' assert_contain, the preferred (I think) way 
>> to check for text on a page.

I am thinking that you are right.  This particular feature was written 
back when I was first starting out with cucumber, features and steps and 
BDD.  I have since taken to checking for specific css ids relating to 
messages and notices in steps rather than looking for the text itself. 
I likely will refactor this step to do the same.

I think, if it is not already on the wiki, that cucumber users might be 
encouraged to put any local additions to support/env.rb into a separate 
file like support/local_env.rb.  Running script/generate cucumber to 
upgrade an existing project leaves those with customized env.rb files 
with two equally unappealing alternatives; keep the old and forgo the 
new or replace it entirely.
-- 
Posted via http://www.ruby-forum.com/.

From pat.maddox at gmail.com  Fri Mar 20 12:23:39 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Fri, 20 Mar 2009 09:23:39 -0700
Subject: [rspec-users] Having a problem with new webrat matchers in
	cucumber 2
In-Reply-To: <304dddff4b5fa8d019b89c2f218e385d@ruby-forum.com>
References: <27586b327f7aaf3096fa2f5e397dd17c@ruby-forum.com>
	<8d961d900903200734q9aa2febsbc3ac51ffd325c4c@mail.gmail.com>
	<217bb29885cef303847b283adc071dd6@ruby-forum.com>
	<304dddff4b5fa8d019b89c2f218e385d@ruby-forum.com>
Message-ID: <2c7e61990903200923p7bae7b1dme56091df7bb2ec66@mail.gmail.com>

> I think, if it is not already on the wiki, that cucumber users might be
> encouraged to put any local additions to support/env.rb into a separate
> file like support/local_env.rb. ?Running script/generate cucumber to
> upgrade an existing project leaves those with customized env.rb files
> with two equally unappealing alternatives; keep the old and forgo the
> new or replace it entirely.

Or overwrite the file and use git diff to see what was removed, and
add it back in.

Pat

From walketim at gmail.com  Fri Mar 20 12:26:43 2009
From: walketim at gmail.com (Tim Walker)
Date: Fri, 20 Mar 2009 10:26:43 -0600
Subject: [rspec-users] [cucumber] getting scenario name in hook
In-Reply-To: <22613814.post@talk.nabble.com>
References: <1ebf5a4d0903110812i6291ec87i58541e1a94812574@mail.gmail.com>
	<8d961d900903110921h79d8134cv42df0804affbef5d@mail.gmail.com>
	<1ebf5a4d0903111712j354a23f0hc82c2e2e55acb39e@mail.gmail.com>
	<22613814.post@talk.nabble.com>
Message-ID: <1ebf5a4d0903200926x77b30967xbda7724613a48334@mail.gmail.com>

We're accessing it like this....

Before do |scenario|
  puts "Before Scenario: #{scenario.to_sexp[3]}"
  .
  .
  .
 end

HTH,

Tim

On Thu, Mar 19, 2009 at 9:39 PM, Nigel Thorne <rspec at nigelthorne.com> wrote:
>
> Where in the scenario object is the name stored?
>
> Cheers.
> Nigel
>
>
> walketim wrote:
>>
>> That did the trick. Thanks Aslak! Took a little while to figure out
>> where it was in the Scenario object but it was pretty straight forward
>> from there.
>>
>> T
>>
>> On Wed, Mar 11, 2009 at 10:21 AM, aslak hellesoy
>> <aslak.hellesoy at gmail.com> wrote:
>>>
>>>
>>> On Wed, Mar 11, 2009 at 4:12 PM, Tim Walker <walketim at gmail.com> wrote:
>>>>
>>>> Hi Guys,
>>>>
>>>> If I am generating diagnostics from a before do step can I get the
>>>> name of the scenario?
>>>
>>> This is implemented in 0.1.99.x:
>>> http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/44
>>>
>>> Aslak
>>>
>>>>
>>>> Many thanks,
>>>>
>>>> Tim
>>>> _______________________________________________
>>>> rspec-users mailing list
>>>> rspec-users at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>>
>
> --
> View this message in context: http://www.nabble.com/-cucumber--getting-scenario-name-in-hook-tp22457271p22613814.html
> Sent from the rspec-users mailing list archive at Nabble.com.
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Fri Mar 20 12:39:25 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 20 Mar 2009 11:39:25 -0500
Subject: [rspec-users] Having a problem with new webrat matchers in
	cucumber 2
In-Reply-To: <304dddff4b5fa8d019b89c2f218e385d@ruby-forum.com>
References: <27586b327f7aaf3096fa2f5e397dd17c@ruby-forum.com>
	<8d961d900903200734q9aa2febsbc3ac51ffd325c4c@mail.gmail.com>
	<217bb29885cef303847b283adc071dd6@ruby-forum.com>
	<304dddff4b5fa8d019b89c2f218e385d@ruby-forum.com>
Message-ID: <57c63afe0903200939tdd83551t7aca0c541755afde@mail.gmail.com>

On Fri, Mar 20, 2009 at 10:52 AM, James Byrne <lists at ruby-forum.com> wrote:
> James Byrne wrote:
>> Aslak Helles?y wrote:
>>>
>>> We switched to using response.should contain(text) a while back. This is
>>> just a wrapper around Rails' assert_contain, the preferred (I think) way
>>> to check for text on a page.
>
> I am thinking that you are right. ?This particular feature was written
> back when I was first starting out with cucumber, features and steps and
> BDD. ?I have since taken to checking for specific css ids relating to
> messages and notices in steps rather than looking for the text itself.
> I likely will refactor this step to do the same.
>
> I think, if it is not already on the wiki, that cucumber users might be
> encouraged to put any local additions to support/env.rb into a separate
> file like support/local_env.rb. ?Running script/generate cucumber to
> upgrade an existing project leaves those with customized env.rb files
> with two equally unappealing alternatives; keep the old and forgo the
> new or replace it entirely.

James - I think this is a good idea. Would you kindly post a ticket to
lighthouse:

http://rspec.lighthouseapp.com/projects/16211

Thanks!

> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

From dchelimsky at gmail.com  Fri Mar 20 12:53:17 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 20 Mar 2009 11:53:17 -0500
Subject: [rspec-users] Having a problem with new webrat matchers in
	cucumber 2
In-Reply-To: <2c7e61990903200923p7bae7b1dme56091df7bb2ec66@mail.gmail.com>
References: <27586b327f7aaf3096fa2f5e397dd17c@ruby-forum.com>
	<8d961d900903200734q9aa2febsbc3ac51ffd325c4c@mail.gmail.com>
	<217bb29885cef303847b283adc071dd6@ruby-forum.com>
	<304dddff4b5fa8d019b89c2f218e385d@ruby-forum.com>
	<2c7e61990903200923p7bae7b1dme56091df7bb2ec66@mail.gmail.com>
Message-ID: <57c63afe0903200953j4b12c1d0ibae7342c124b272b@mail.gmail.com>

On Fri, Mar 20, 2009 at 11:23 AM, Pat Maddox <pat.maddox at gmail.com> wrote:
>> I think, if it is not already on the wiki, that cucumber users might be
>> encouraged to put any local additions to support/env.rb into a separate
>> file like support/local_env.rb. ?Running script/generate cucumber to
>> upgrade an existing project leaves those with customized env.rb files
>> with two equally unappealing alternatives; keep the old and forgo the
>> new or replace it entirely.
>
> Or overwrite the file and use git diff to see what was removed, and
> add it back in.

Pat - this is a common problem w/ upgrading rspec-rails too - I asked
James to file the ticket so we could coordinate on approach w/ cuc and
rspec.

Make sense to you?

>
> Pat
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From pat.maddox at gmail.com  Fri Mar 20 13:10:53 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Fri, 20 Mar 2009 10:10:53 -0700
Subject: [rspec-users] Having a problem with new webrat matchers in
	cucumber 2
In-Reply-To: <57c63afe0903200953j4b12c1d0ibae7342c124b272b@mail.gmail.com>
References: <27586b327f7aaf3096fa2f5e397dd17c@ruby-forum.com>
	<8d961d900903200734q9aa2febsbc3ac51ffd325c4c@mail.gmail.com>
	<217bb29885cef303847b283adc071dd6@ruby-forum.com>
	<304dddff4b5fa8d019b89c2f218e385d@ruby-forum.com>
	<2c7e61990903200923p7bae7b1dme56091df7bb2ec66@mail.gmail.com>
	<57c63afe0903200953j4b12c1d0ibae7342c124b272b@mail.gmail.com>
Message-ID: <2c7e61990903201010s5e11735fk208f1c910e79e9de@mail.gmail.com>

On Fri, Mar 20, 2009 at 9:53 AM, David Chelimsky <dchelimsky at gmail.com> wrote:
> On Fri, Mar 20, 2009 at 11:23 AM, Pat Maddox <pat.maddox at gmail.com> wrote:
>>> I think, if it is not already on the wiki, that cucumber users might be
>>> encouraged to put any local additions to support/env.rb into a separate
>>> file like support/local_env.rb. ?Running script/generate cucumber to
>>> upgrade an existing project leaves those with customized env.rb files
>>> with two equally unappealing alternatives; keep the old and forgo the
>>> new or replace it entirely.
>>
>> Or overwrite the file and use git diff to see what was removed, and
>> add it back in.
>
> Pat - this is a common problem w/ upgrading rspec-rails too - I asked
> James to file the ticket so we could coordinate on approach w/ cuc and
> rspec.
>
> Make sense to you?

Generally I have some stuff that I have to require before the rspec
config block loads.  I *think* that splitting everything into two
files would cause problems with certain dependencies, but that may be
something I just have to work out.

Pat

From lists at ruby-forum.com  Fri Mar 20 14:49:30 2009
From: lists at ruby-forum.com (James Byrne)
Date: Fri, 20 Mar 2009 19:49:30 +0100
Subject: [rspec-users] Having a problem with new webrat matchers in
	cucumber 2
In-Reply-To: <57c63afe0903200939tdd83551t7aca0c541755afde@mail.gmail.com>
References: <27586b327f7aaf3096fa2f5e397dd17c@ruby-forum.com>
	<8d961d900903200734q9aa2febsbc3ac51ffd325c4c@mail.gmail.com>
	<217bb29885cef303847b283adc071dd6@ruby-forum.com>
	<304dddff4b5fa8d019b89c2f218e385d@ruby-forum.com>
	<57c63afe0903200939tdd83551t7aca0c541755afde@mail.gmail.com>
Message-ID: <3cb4d139148b46887dc32db6f045bf64@ruby-forum.com>

David Chelimsky wrote:

> 
> James - I think this is a good idea. Would you kindly post a ticket to
> lighthouse:
> 
> http://rspec.lighthouseapp.com/projects/16211
> 
> Thanks!

ticket #253
-- 
Posted via http://www.ruby-forum.com/.

From aslak.hellesoy at gmail.com  Fri Mar 20 16:15:43 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Fri, 20 Mar 2009 16:15:43 -0400
Subject: [rspec-users] [cucumber] getting scenario name in hook
In-Reply-To: <1ebf5a4d0903200926x77b30967xbda7724613a48334@mail.gmail.com>
References: <1ebf5a4d0903110812i6291ec87i58541e1a94812574@mail.gmail.com>
	<8d961d900903110921h79d8134cv42df0804affbef5d@mail.gmail.com>
	<1ebf5a4d0903111712j354a23f0hc82c2e2e55acb39e@mail.gmail.com>
	<22613814.post@talk.nabble.com>
	<1ebf5a4d0903200926x77b30967xbda7724613a48334@mail.gmail.com>
Message-ID: <8d961d900903201315g38f90cb9k668063dbed4a2616@mail.gmail.com>

On Fri, Mar 20, 2009 at 12:26 PM, Tim Walker <walketim at gmail.com> wrote:

> We're accessing it like this....
>
> Before do |scenario|
>  puts "Before Scenario: #{scenario.to_sexp[3]}"
>  .
>  .
>  .
>  end
>

I like that even if it's a little convoluted - I'm trying to avoid exposing
every single attribute.

Aslak


>
> HTH,
>
> Tim
>
> On Thu, Mar 19, 2009 at 9:39 PM, Nigel Thorne <rspec at nigelthorne.com>
> wrote:
> >
> > Where in the scenario object is the name stored?
> >
> > Cheers.
> > Nigel
> >
> >
> > walketim wrote:
> >>
> >> That did the trick. Thanks Aslak! Took a little while to figure out
> >> where it was in the Scenario object but it was pretty straight forward
> >> from there.
> >>
> >> T
> >>
> >> On Wed, Mar 11, 2009 at 10:21 AM, aslak hellesoy
> >> <aslak.hellesoy at gmail.com> wrote:
> >>>
> >>>
> >>> On Wed, Mar 11, 2009 at 4:12 PM, Tim Walker <walketim at gmail.com>
> wrote:
> >>>>
> >>>> Hi Guys,
> >>>>
> >>>> If I am generating diagnostics from a before do step can I get the
> >>>> name of the scenario?
> >>>
> >>> This is implemented in 0.1.99.x:
> >>> http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/44
> >>>
> >>> Aslak
> >>>
> >>>>
> >>>> Many thanks,
> >>>>
> >>>> Tim
> >>>> _______________________________________________
> >>>> rspec-users mailing list
> >>>> rspec-users at rubyforge.org
> >>>> http://rubyforge.org/mailman/listinfo/rspec-users
> >>>
> >>>
> >>> _______________________________________________
> >>> rspec-users mailing list
> >>> rspec-users at rubyforge.org
> >>> http://rubyforge.org/mailman/listinfo/rspec-users
> >>>
> >> _______________________________________________
> >> rspec-users mailing list
> >> rspec-users at rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/rspec-users
> >>
> >>
> >
> > --
> > View this message in context:
> http://www.nabble.com/-cucumber--getting-scenario-name-in-hook-tp22457271p22613814.html
> > Sent from the rspec-users mailing list archive at Nabble.com.
> >
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Aslak (::)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090320/77f37b78/attachment.html>

From lists at ruby-forum.com  Fri Mar 20 16:32:50 2009
From: lists at ruby-forum.com (James Byrne)
Date: Fri, 20 Mar 2009 21:32:50 +0100
Subject: [rspec-users] OT: SIT - how to turn it off
Message-ID: <abd044e446490fcc97c3bc35168ac0e7@ruby-forum.com>

Pardon the intrusion but if somebody knows how to turn off Rails special
treatment of attributes ending in _type and _value I would dearly like
to have this information.

Workarounds are accepted too.

I am trying to initialise an associated row that contains the columns
identifier_type and identifier_value.  The statement

  model.association.create!(:column_type => 'X', :column_value => 'Y')

leaves association.column_type and association.column_value attributes
with VALUES  NULL in the resulting generated SQL code.  I really need
Rails to accept the values that I provide.
-- 
Posted via http://www.ruby-forum.com/.

From bj at aboutus.org  Fri Mar 20 18:27:45 2009
From: bj at aboutus.org (BJ Clark)
Date: Fri, 20 Mar 2009 15:27:45 -0700
Subject: [rspec-users] have_tag and img's
Message-ID: <3B016902-BD3A-4508-949E-B9B448F7EBE0@aboutus.org>

I'm specing some xhtml (which I don't normally do, so forgive me if  
this is basic).

I've got the following spec:

       it "should build xhtml form pieces" do
         @captcha.should_receive(:request_image).and_return @image
         @captcha.vidoop_captcha().should have_tag "div.captcha" do
           with_tag "img[src=http://api.vidoop.com/vs/captchas/cpt123/image 
]"
           with_tag "input[type=hidden][name=captcha_id]"
           with_tag "input[name=captcha]"
         end
       end

@captcha.vidoop_captcha is returning the following html:
<div class="captcha"><input value="cpt123" name="captcha_id"/><image  
src="http://api.vidoop.com/vs/captchas/cpt123/image" alt="VidoopSecure  
Captcha Image"/><div class="instructions"><p>foo bar</p><input  
type="text" autocomplete="off" maxlength="2" name="captcha"  
id="captcha"/></div></div>

And my error is:
'Vidoop::Captcha::Helper rendering a catpcha should build xhtml form  
pieces' FAILED
Expected at least 1 element matching "img[src='http://api.vidoop.com/vs/captchas/cpt123/image' 
]", found 0.
<false> is not true.

I've tried with_tag as simple as "img" but even that isn't matching.  
The rest of the spec passes.

Any ideas?
Thanks,
BJ Clark

From phlip2005 at gmail.com  Fri Mar 20 21:34:03 2009
From: phlip2005 at gmail.com (Phlip)
Date: Fri, 20 Mar 2009 18:34:03 -0700
Subject: [rspec-users] have_tag and img's
In-Reply-To: <3B016902-BD3A-4508-949E-B9B448F7EBE0@aboutus.org>
References: <3B016902-BD3A-4508-949E-B9B448F7EBE0@aboutus.org>
Message-ID: <gq1g6d$8f9$1@ger.gmane.org>

BJ Clark wrote:

> I'm specing some xhtml (which I don't normally do, so forgive me if this 
> is basic).
> 
> I've got the following spec:
> 
>       it "should build xhtml form pieces" do
>         @captcha.should_receive(:request_image).and_return @image
>         @captcha.vidoop_captcha().should have_tag "div.captcha" do
>           with_tag 
> "img[src=http://api.vidoop.com/vs/captchas/cpt123/image]"
>           with_tag "input[type=hidden][name=captcha_id]"
>           with_tag "input[name=captcha]"
>         end
>       end

I suspect the XPath predicate should be [@name='captcha'], but I don't know 
with_tag shortcuts.

You might also try (>cough<) my assert_xhtml:

   @captcha.vidoop_captcha().should be_html_with{
     div :id => :captcha do
       img :src => 'http://api.vidoop.com/vs/captchas/cpt123/image'
       input :type => :hidden, :name => :captcha_id
       input :name => :captcha
     end
   end

I invented it specifically to solve the verbosity problem you encountered. gem 
install nokogiri assert2, and require 'assert2/xhtml'.

If it fails, it prints out the HTML pattern it sought, and the sample HTML from 
your production code.

-- 
   Phlip


From rspec at nigelthorne.com  Sat Mar 21 08:02:50 2009
From: rspec at nigelthorne.com (Nigel Thorne)
Date: Sat, 21 Mar 2009 23:02:50 +1100
Subject: [rspec-users] [cucumber] getting scenario name in hook
In-Reply-To: <1ebf5a4d0903200926x77b30967xbda7724613a48334@mail.gmail.com>
References: <1ebf5a4d0903110812i6291ec87i58541e1a94812574@mail.gmail.com>
	<8d961d900903110921h79d8134cv42df0804affbef5d@mail.gmail.com>
	<1ebf5a4d0903111712j354a23f0hc82c2e2e55acb39e@mail.gmail.com>
	<22613814.post@talk.nabble.com>
	<1ebf5a4d0903200926x77b30967xbda7724613a48334@mail.gmail.com>
Message-ID: <5d1f449a0903210502n493c3266l974ec7617502eb8c@mail.gmail.com>

That is exactly what I was looking for.. Thank you !




2009/3/21 Tim Walker <walketim at gmail.com>:
> We're accessing it like this....
>
> Before do |scenario|
> ?puts "Before Scenario: #{scenario.to_sexp[3]}"
> ?.
> ?.
> ?.
> ?end
>
> HTH,
>
> Tim
>
> On Thu, Mar 19, 2009 at 9:39 PM, Nigel Thorne <rspec at nigelthorne.com> wrote:
>>
>> Where in the scenario object is the name stored?
>>
>> Cheers.
>> Nigel
>>
>>
>> walketim wrote:
>>>
>>> That did the trick. Thanks Aslak! Took a little while to figure out
>>> where it was in the Scenario object but it was pretty straight forward
>>> from there.
>>>
>>> T
>>>
>>> On Wed, Mar 11, 2009 at 10:21 AM, aslak hellesoy
>>> <aslak.hellesoy at gmail.com> wrote:
>>>>
>>>>
>>>> On Wed, Mar 11, 2009 at 4:12 PM, Tim Walker <walketim at gmail.com> wrote:
>>>>>
>>>>> Hi Guys,
>>>>>
>>>>> If I am generating diagnostics from a before do step can I get the
>>>>> name of the scenario?
>>>>
>>>> This is implemented in 0.1.99.x:
>>>> http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/44
>>>>
>>>> Aslak
>>>>
>>>>>
>>>>> Many thanks,
>>>>>
>>>>> Tim
>>>>> _______________________________________________
>>>>> rspec-users mailing list
>>>>> rspec-users at rubyforge.org
>>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>>
>>>>
>>>> _______________________________________________
>>>> rspec-users mailing list
>>>> rspec-users at rubyforge.org
>>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>>
>>
>> --
>> View this message in context: http://www.nabble.com/-cucumber--getting-scenario-name-in-hook-tp22457271p22613814.html
>> Sent from the rspec-users mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Sat Mar 21 09:27:49 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sat, 21 Mar 2009 08:27:49 -0500
Subject: [rspec-users] OT: SIT - how to turn it off
In-Reply-To: <abd044e446490fcc97c3bc35168ac0e7@ruby-forum.com>
References: <abd044e446490fcc97c3bc35168ac0e7@ruby-forum.com>
Message-ID: <57c63afe0903210627t62d7db2bxba6819b40d3b47a5@mail.gmail.com>

On Fri, Mar 20, 2009 at 3:32 PM, James Byrne <lists at ruby-forum.com> wrote:
> Pardon the intrusion but if somebody knows how to turn off Rails special
> treatment of attributes ending in _type and _value I would dearly like
> to have this information.
>
> Workarounds are accepted too.
>
> I am trying to initialise an associated row that contains the columns
> identifier_type and identifier_value. ?The statement
>
> ?model.association.create!(:column_type => 'X', :column_value => 'Y')

What type of association? There are many and they are all handled
quite differently.

>
> leaves association.column_type and association.column_value attributes
> with VALUES ?NULL in the resulting generated SQL code. ?I really need
> Rails to accept the values that I provide.


> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From beenimble at gmail.com  Fri Mar 20 09:36:52 2009
From: beenimble at gmail.com (beenimble)
Date: Fri, 20 Mar 2009 06:36:52 -0700 (PDT)
Subject: [rspec-users] [cucumber] Sinatra "polyglot" app path error
Message-ID: <2d155cb4-0ca4-4271-8ab8-a319c9e4ac3d@h5g2000yqh.googlegroups.com>

In case of the following error when using Cucumber with Sinatra:

No such file or directory - /usr/local/lib/ruby/gems/1.8/gems/
polyglot-0.2.4/lib/views/index.erb

Implement env.rb as specified at the following link so your app and
its view path may be found (this supersedes prior examples):

http://github.com/aslakhellesoy/cucumber/blob/a478b71173a1ff92d6b5d1808e377a0a1b7aac2f/examples/sinatra/features/support/env.rb

[Note comment: "Force the application name because polyglot breaks the
auto-detection logic."]

From slabounty at gmail.com  Fri Mar 20 17:21:32 2009
From: slabounty at gmail.com (Scott LaBounty)
Date: Fri, 20 Mar 2009 14:21:32 -0700
Subject: [rspec-users] New User Issues
Message-ID: <7de47a040903201421r2e3f2978kf0ca9d4d42b30659@mail.gmail.com>

I just found RSpec and was trying to do the example on the main page for
RSpec (the bowling example). I'm using Ubuntu and did the normal "sudo gem
install rspec" and then tried to create the bowling_spec.rb file. When I ran
spec bowling_spec.rb, I was missing the cucumber gem, installed that, reran
and was missing the hoe gem, installed that, reran and it gave me the a
missing 'require' from the bowling_spec since I didn't have a bowling.rb
file. Is that expected? From the example, it didn't seem like it would be.
When I then added the bowling.rb file and reran everything looked correct
except that it wasn't in color (i.e. no green). Is that expected or do I
need to do something differnt to get this to work? I'm running ruby 1.8.6 if
it makes a difference.

Thanks,

-- 
Scott
http://steamcode.blogspot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090320/9522ef3d/attachment.html>

From dchelimsky at gmail.com  Sat Mar 21 10:54:50 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sat, 21 Mar 2009 09:54:50 -0500
Subject: [rspec-users] New User Issues
In-Reply-To: <7de47a040903201421r2e3f2978kf0ca9d4d42b30659@mail.gmail.com>
References: <7de47a040903201421r2e3f2978kf0ca9d4d42b30659@mail.gmail.com>
Message-ID: <57c63afe0903210754r78c83e63yb4084bb09965dd2b@mail.gmail.com>

2009/3/20 Scott LaBounty <slabounty at gmail.com>:
> I just found RSpec and was trying to do the example on the main page for
> RSpec (the bowling example). I'm using Ubuntu and did the normal "sudo gem
> install rspec" and then tried to create the bowling_spec.rb file. When I ran
> spec bowling_spec.rb, I was missing the cucumber gem, installed that, reran
> and was missing the hoe gem, installed that,

Cucumber and hoe are developer dependencies. You should probably
upgrade rubygems - sounds like you're using an old version that
doesn't know the difference between developer dependencies and
standard runtime dependencies.

I should probably make it so those dependencies don't exist at all
unless you have a new enough rubygems to make the distinction.

> reran and it gave me the a
> missing 'require' from the bowling_spec since I didn't have a bowling.rb
> file. Is that expected?

The example fails to point that out, but yes, it is the expected
behaviour if the file doesn't exist.

> From the example, it didn't seem like it would be.
> When I then added the bowling.rb file and reran everything looked correct
> except that it wasn't in color (i.e. no green). Is that expected or do I
> need to do something differnt to get this to work?

Add the --color option to the command line and you'll get color.

> I'm running ruby 1.8.6 if
> it makes a difference.

Nope - the example needs some fixing. I'm doing a bug-fix release in
the next few days, and I'll be sure to fix the example so it works as
a mini-tutorial when I do that release.

Thanks!

David



>
> Thanks,
>
> --
> Scott
> http://steamcode.blogspot.com/
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From lists at ruby-forum.com  Sat Mar 21 10:56:00 2009
From: lists at ruby-forum.com (James Byrne)
Date: Sat, 21 Mar 2009 15:56:00 +0100
Subject: [rspec-users] OT: SIT - how to turn it off
In-Reply-To: <57c63afe0903210627t62d7db2bxba6819b40d3b47a5@mail.gmail.com>
References: <abd044e446490fcc97c3bc35168ac0e7@ruby-forum.com>
	<57c63afe0903210627t62d7db2bxba6819b40d3b47a5@mail.gmail.com>
Message-ID: <2c13dd59c39dc755a752c737820816fb@ruby-forum.com>

David Chelimsky wrote:

> 
> What type of association? There are many and they are all handled
> quite differently.
> 

In this particular case this was a has_many / belongs_to pair and I was 
attempting a parent.child.create({}) call.  I discovered thereby that 
Rails, at least in version 2.3.2, evidently does not permit mass 
assignment of attributes ending in _type or _value; apparently 
regardless of their presence in an attr_accessible call.

However, this problem proved serendipitous.  In consequence I have 
discovered a great deal regarding problems with mass assignment. The 
result is that I have instead turned off mass assignment for the entire 
application.  This, needless to say, has broken a great deal of my tests 
and functioning code but I am mostly finished resolving those problems.

I found a good discussion of this problem and some solutions at:

  http://railspikes.com/2008/9/22/is-your-rails-application-safe-from-mass-assignment

-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Sat Mar 21 10:57:54 2009
From: lists at ruby-forum.com (James Byrne)
Date: Sat, 21 Mar 2009 15:57:54 +0100
Subject: [rspec-users] OT: SIT - how to turn it off
In-Reply-To: <2c13dd59c39dc755a752c737820816fb@ruby-forum.com>
References: <abd044e446490fcc97c3bc35168ac0e7@ruby-forum.com>
	<57c63afe0903210627t62d7db2bxba6819b40d3b47a5@mail.gmail.com>
	<2c13dd59c39dc755a752c737820816fb@ruby-forum.com>
Message-ID: <4ae9fcf2a54d999499e979347fa4f240@ruby-forum.com>

James Byrne wrote:
> In this particular case this was a has_many / belongs_to pair and I was 
> attempting a parent.child.create({}) call.  

S/B: parent.children.create({})
-- 
Posted via http://www.ruby-forum.com/.

From aslak.hellesoy at gmail.com  Sat Mar 21 11:53:23 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Sat, 21 Mar 2009 11:53:23 -0400
Subject: [rspec-users] [cucumber] Sinatra "polyglot" app path error
In-Reply-To: <2d155cb4-0ca4-4271-8ab8-a319c9e4ac3d@h5g2000yqh.googlegroups.com>
References: <2d155cb4-0ca4-4271-8ab8-a319c9e4ac3d@h5g2000yqh.googlegroups.com>
Message-ID: <8d961d900903210853x39fad692se1ec968edb0e2181@mail.gmail.com>

On Fri, Mar 20, 2009 at 9:36 AM, beenimble <beenimble at gmail.com> wrote:

> In case of the following error when using Cucumber with Sinatra:
>
> No such file or directory - /usr/local/lib/ruby/gems/1.8/gems/
> polyglot-0.2.4/lib/views/index.erb
>
> Implement env.rb as specified at the following link so your app and
> its view path may be found (this supersedes prior examples):
>
>
> http://github.com/aslakhellesoy/cucumber/blob/a478b71173a1ff92d6b5d1808e377a0a1b7aac2f/examples/sinatra/features/support/env.rb
>

Thanks - code and wiki updated:

http://github.com/aslakhellesoy/cucumber/commit/29d83d51907b8bfa455c1a2e365c72d77655e85c
http://wiki.github.com/aslakhellesoy/cucumber/sinatra

Thanks for helping Sinatra work well with Cucumber - feel free to update the
wiki and code with other tips and tricks.

Aslak


>
> [Note comment: "Force the application name because polyglot breaks the
> auto-detection logic."]
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090321/72a92770/attachment.html>

From cwdinfo at gmail.com  Sat Mar 21 12:53:57 2009
From: cwdinfo at gmail.com (s.ross)
Date: Sat, 21 Mar 2009 09:53:57 -0700
Subject: [rspec-users] [Cucumber] Rails Upgrade Notes
Message-ID: <1950D1EF-361F-48C5-A9C5-954075BE3953@gmail.com>

In the history.txt for 0.2 is an "important note" toward the bottom of  
the announcement. (http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt 
). This is really, *really* important for Rails users, but it can be  
more than a bit difficult to Google out.

Questions:

1. Can this be brought into a wiki page on github on cuke.info?
2. Is there a way to tell under what version of Cucumber one is  
running so the require can require either the old files for Cuke < 0.2  
or the ones now?

Thx

From aslak.hellesoy at gmail.com  Sat Mar 21 13:11:44 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Sat, 21 Mar 2009 13:11:44 -0400
Subject: [rspec-users] [Cucumber] Rails Upgrade Notes
In-Reply-To: <1950D1EF-361F-48C5-A9C5-954075BE3953@gmail.com>
References: <1950D1EF-361F-48C5-A9C5-954075BE3953@gmail.com>
Message-ID: <8d961d900903211011ue3d3881re664fc2b6e135434@mail.gmail.com>

On Sat, Mar 21, 2009 at 12:53 PM, s.ross <cwdinfo at gmail.com> wrote:

> In the history.txt for 0.2 is an "important note" toward the bottom of the
> announcement. (
> http://github.com/aslakhellesoy/cucumber/blob/d0555e4ca8a133f020efefd5a755da04bde3f57d/History.txt).
> This is really, *really* important for Rails users, but it can be more than
> a bit difficult to Google out.
>

The Important note dates back from 0.1.16.4, which is a couple of months
old.


>
> Questions:
>
> 1. Can this be brought into a wiki page on github on cuke.info?


Sure, feel free to edit the Rails page with relevant info. My general
recommendation is to always rerun script/generate cucumber after you upgrade
your Cucumber gem/plugin. Maybe you could add a note about that?


>
> 2. Is there a way to tell under what version of Cucumber one is running so
> the require can require either the old files for Cuke < 0.2 or the ones now?
>

cucumber --version

or from code:

Cucumber::VERSION::STRING

Aslak


> Thx
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090321/123ec13d/attachment.html>

From chris at stemcel.co.uk  Sat Mar 21 14:06:31 2009
From: chris at stemcel.co.uk (Chris Adams)
Date: Sat, 21 Mar 2009 18:06:31 +0000
Subject: [rspec-users] Are there any example specs for content importers to
	learn from
Message-ID: <02D96A7F-CEBA-4F88-9E03-0962AAF5E816@stemcel.co.uk>

Hi guys,

This is my first post to the mailing list, so apologies if this kind  
of question comes up alot already.

I've been working through the Peepcode screencasts on RSpec, and I'm  
trying to what I've been learning into practice to make an importer on  
a rails app that takes an xml feed, and imports each entry in the xml  
feed into the database, skipping imports if they already exist in the  
db.

The thing is, I don't know the best way to do this, as most examples  
I've seen only refer to handing objects one at a time.

Could someone point me to a couple of code examples of what importer  
specs should look like when written in rspec, or tell me roughly how I  
should be approaching this ?

I've put the generic version of the code in this gist, to give an idea  
of where I'm headed at the mo, but any feedback would be greatly  
appreciated.

https://gist.github.com/38859f947860d4fc45e2

Thanks and have a good weekend,

Chris

-- 
---
I'm currently only checking my email at 9am, midday and at 4pm.
If you need a response from me urgently, please call or text my  
mobile, or contact me via Skype (chris.d.adams).
---
Chris Adams
Stemcel Studios
The Hub
5 Torrens Street
London
EC1V 1NQ

email: chris at stemcel.co.uk
web:  www.stemcel.co.uk
twitter:chris_d_adams
skype: chris.d.adams
mob: 07974 368 229
tel: 0207 558 8971


From jeroentjevandijk at gmail.com  Sat Mar 21 14:12:20 2009
From: jeroentjevandijk at gmail.com (Jeroen van Dijk)
Date: Sat, 21 Mar 2009 19:12:20 +0100
Subject: [rspec-users] Mocking base class methods
In-Reply-To: <85d99afe0903200718w3c909e4asf39870b82b52dd51@mail.gmail.com>
References: <499FE5F9.3050905@e-tobi.net>
	<85d99afe0902211148p585d5e5cx283232b250f2e8b4@mail.gmail.com>
	<49A070F6.2060107@e-tobi.net>
	<ecbf28ec0903190935x7073c98cpe652d71cbaa8593d@mail.gmail.com>
	<ecbf28ec0903200330g655a59e1gc61522c95b9cc785@mail.gmail.com>
	<85d99afe0903200718w3c909e4asf39870b82b52dd51@mail.gmail.com>
Message-ID: <ecbf28ec0903211112n7448cd72ta140af39cdb4547b@mail.gmail.com>

> >   describe "count_by_params" do
> >     it "should pass all the params and options to #scope_by_params" do
> >       params  = { :foo => 1, :bar => 2 }
> >       options = { :foo => 3, :bar => 4 }
> >
> >       @base = ActiveRecord::Base
> >       @result = mock("query results", :count => 1)
> >       @base.expects(:scoped_by_params).with(params,
> > options).returns(@result)
> >       @base.count_by_params(params, options)
> >     end
> >
>
> Is #scoped_by_params a public method that has its own examples? Down
> at the model level I would want to know that count_by_params actually
> was working as expected and not just collaborating with itself to call
> an internal method. I don't know how crazy scoped_by_params is so
> maybe there is a potential risk you're willing to accept given the
> complexity of what it does, but this example raises my eyebrow as to
> the behaviour your actually expecting and verifying.
>


scoped_by_params is indeed a public method with its own examples. I agree
that this spec does not say much, it is not more than a verification of its
implementation i guess. In sum, I have three methods find_by_params,
count_by_params and scoped_by_params. The first two rely on
scoped_by_params, which in turn relies on dynamic scopes from
ActiveRecord::Base.

I see two possible ways of testing this; an integration test in which we
focus on the result of the queries. Another possibility, the one I use in
this example, is to check if other methods are called correctly.

My reasoning is that ActiveRecord::Base has an extensive test suite, so I
only need to test that it is called correctly. By mocking methods call I'm
having simpler and faster tests. The problem is that the test by itself will
not tell me when Rails internals are changed and my code has actually been
broken. I'm assuming that the end result should be tested by integration
tests, do you agree?

What would your test strategy be?

(The code is actually part of a small plugin I'm writing and can be found
here
http://github.com/jeroenvandijk/find_by_params/blob/5a97028c505d9254b2bcbe5e3aa5b801f7ca34ca/lib/find_by_params.rb
)


Jeroen

PS I'm a TDD beginner so feel free correct me :)




> >
> > On Thu, Mar 19, 2009 at 5:35 PM, Jeroen van Dijk
> > <jeroentjevandijk at gmail.com> wrote:
> >>
> >> Hi all,
> >>
> >> I'm having the same problem as Tobi and I wanted to try Tobi mock
> solution
> >> but unfortunately it does not work for me.
> >>
> >> Here is a trivial example I want to test:
> >>
> >> module ActiveRecord
> >>   class Base
> >>       def self.count_by_params(params = {}, options = {})
> >>           scoped_by_params(params).count
> >>       end
> >>   end
> >> end
> >>
> >> And my spec:
> >> module ActiveRecord
> >>   class Base
> >>     include BaseClassMock
> >>   end
> >> end
> >>
> >> class DummyUser < ActiveRecord::Base
> >> end
> >>
> >> it "should pass all the params and options to #scope_by_params" do
> >>    params  = { :foo => 1, :bar => 2 }
> >>     options = { :foo => 3, :bar => 4 }
> >>     @dummy = DummyUser
> >>     @dummy.base_class.should_receive(:scope_by_params).with(params,
> >> options)
> >>     DummyUser.count_by_params(params, options)
> >> end
> >>
> >> With the above example and Tobi's BaseClassMock module I'm getting
> >> "undefined method `should_receive' for #<Object:0x188c164>". Btw, I also
> get
> >> this when I do not use Tobi be it for for #<Class:0x188cdf8> instead of
> >> Object.
> >>
> >> Any suggestions on what I'm doing wrong or a different approach?
> >>
> >> Cheers,
> >> Jeroen
> >>
> >>
> >>
> >> On Sat, Feb 21, 2009 at 10:24 PM, Tobi <listaccount at e-tobi.net> wrote:
> >>>
> >>> Zach Dennis wrote:
> >>>
> >>> > +1 to composition over inheritance here. Mocking at different layers
> >>> > of an inheritance hierarchy sounds like trouble and screams to pull
> >>> > that thing apart.
> >>>
> >>> Good point! I've already tried the composition approach. It solves the
> >>> testabilitiy problems, but it doesn't feel right in this case.
> >>>
> >>> Inheritance seems to be the more natural approach. The C++ application
> >>> will call virtual methods on the base class which should be overriden
> in
> >>> a
> >>> derived class. So it seems to make sense to have the same inheritance
> >>> tree
> >>> in the Ruby counter parts.
> >>>
> >>> If I would use composition, I would at least need to dynamically extend
> >>> the referenced base class so I can override some of the methods that
> are
> >>> the counter parts of the virtual C++ methods. And I would need to
> expose
> >>> the referenced class to the C++ code.
> >>>
> >>> I've finally found a way to kinda mock the base class in some way:
> >>>
> >>> module BaseClassMock
> >>>  attr_accessor :base
> >>>
> >>>  def self.included(klass)
> >>>    class << klass
> >>>      @@base_class = Object.new
> >>>
> >>>      def base_class
> >>>        return @@base_class
> >>>      end
> >>>    end
> >>>  end
> >>>
> >>>  def initialize(*args)
> >>>    @@base_class.new(*args) if @@base_class.respond_to?(:new)
> >>>    @base = Object.new
> >>>  end
> >>>
> >>>  def method_missing(symbol, *args)
> >>>    @base.send(symbol, *args)
> >>>  end
> >>> end
> >>>
> >>> Any base class (Swig classes in my case) should then be declared for
> >>> RSpec
> >>> like:
> >>>
> >>> module Swig
> >>>  class Base; include BaseClassMock; end
> >>> end
> >>>
> >>> And in the specs I can then do:
> >>>
> >>>    Derived.base_class.should_receive(:new).with('something')
> >>>    d = Derived.new('something')
> >>>
> >>> or:
> >>>
> >>>    d = Derived.new
> >>>    d.base.should_receive(:do_something)
> >>>    d.do_something
> >>>
> >>> Tobias
> >>> _______________________________________________
> >>> rspec-users mailing list
> >>> rspec-users at rubyforge.org
> >>> http://rubyforge.org/mailman/listinfo/rspec-users
> >>
> >
> >
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
>
>
>
> --
> Zach Dennis
> http://www.continuousthinking.com
> http://www.mutuallyhuman.com
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090321/63af65ed/attachment.html>

From rick.denatale at gmail.com  Sat Mar 21 16:47:55 2009
From: rick.denatale at gmail.com (Rick DeNatale)
Date: Sat, 21 Mar 2009 16:47:55 -0400
Subject: [rspec-users] Problem spec'ing ActionMailer with attachment,
	body 	not getting rendered.
In-Reply-To: <85d99afe0903200846p5fa8d460v4ea7d4aa8d8ed994@mail.gmail.com>
References: <deb2337a0903181328u284e7e6ep168867b50ce000c2@mail.gmail.com>
	<85d99afe0903200811l78db9cfal88aaf3cc4e211ce5@mail.gmail.com>
	<85d99afe0903200846p5fa8d460v4ea7d4aa8d8ed994@mail.gmail.com>
Message-ID: <deb2337a0903211347wd60abc7o3ed6a30e96a3f2a4@mail.gmail.com>

On Fri, Mar 20, 2009 at 11:46 AM, Zach Dennis <zach.dennis at gmail.com> wrote:

> On Fri, Mar 20, 2009 at 11:11 AM, Zach Dennis <zach.dennis at gmail.com>
> wrote:
> > 2009/3/18 Rick DeNatale <rick.denatale at gmail.com>:
> >> I've got a simple ActionMailer::Base subclass:
> >> class InfoMailer < ActionMailer::Base
> >>
> >>     def info(user, zip_name)
> >>     recipients user.email
> >>     subject "Requested Info"
> >>     attachment(:content_type => "application/zip",
> >>                 :filename => zip_name,
> >>                 :body => File.read(zip_name))
> >>     body(:message => "Here is the Info that you Requested")
> >>   end
> >> end
> >> I'm trying to spec this
> >> following
> http://www.rubytutorials.net/2008/02/26/small-rspec-revelations-actionmailer/
> >> describe AssetsInfoMailer do
> >>   before(:each) do
> >>     @user = mock_model(User,
> >>         :email => @user_email = "somewhere at over.the.rainbow",
> >>         :full_name => "The Wicked Witch of the West"
> >>         )
> >>     ActionMailer::Base.delivery_method = :test
> >>     ActionMailer::Base.perform_deliveries = true
> >>     ActionMailer::Base.deliveries = []
> >>   end
> >>   describe ".info" do
> >>     before(:each) do
> >>       @path = 'xyz.zip'
> >>       @attachment_body = 'zip_file_contents'
> >>       File.stub!(:read).and_return(@attachment_body)
> >>       @the_mail = AssetsInfoMailer.deliver_info(@user, at path)
> >>       @attachments = @the_mail.attachments
> >>     end
> >>
> >>     it "should have the right body" do
> >>       @the_mail.body.should == ""
> >>     end
> >>   end
> >> The expectation of an empty string is just to see what's actually
> getting
> >> returned, the result is:
> >> 1)
> >> 'AssetsInfoMailer.info should have the right body' FAILED
> >> expected: "",
> >>      got: "Attachment: xyz.zip\n" (using ==)
> >> It's looking like the mail template never got rendered, and body is
> giving
> >> me the attachment since it's the only part.
> >> I've got one other mailer method in that mailer which doesn't contain an
> >> attachement, and it's body comes out fine.
> >> I'm not sure what's going on here, and I'd appreciate any
> >> help/insight/condolences...
> >>
> >
> > When sending attachments emails are sent as multipart messages. The
> > only part being specified is the attachment. The other call to "body"
> > is being ignored. Try something like:
> >
> > def info(user, zip_name)
> >  recipients user.email
> >  subject "Requested Info"
> >  attachment(:content_type => "application/zip",
> >              :filename => zip_name,
> >              :body => File.read(zip_name))
> >  part "text/plain" do |p|
> >    p.body(:message => "Here is the Info that you Requested")
> >  end
> > end
>
> I just tried my out, and while it does work because there are multiple
> parts specified, also re-ordering of the initial #body to come before
> the attachment doesn't seem to help with the original code either.
>
> I'm curious now what you do find out and which route you decide to go,
> keep us posted either way Rick.


I ende up with pretty much the above, but with

   p.body(render_message('info', :message =>...

since there was a template to render.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090321/30867f73/attachment-0001.html>

From pat.maddox at gmail.com  Sat Mar 21 17:07:40 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Sat, 21 Mar 2009 14:07:40 -0700
Subject: [rspec-users] Are there any example specs for content importers
	to learn from
In-Reply-To: <02D96A7F-CEBA-4F88-9E03-0962AAF5E816@stemcel.co.uk>
References: <02D96A7F-CEBA-4F88-9E03-0962AAF5E816@stemcel.co.uk>
Message-ID: <2c7e61990903211407o11f7f0acya09ee0269ddf7c0@mail.gmail.com>

That's basically what I do.  http://gist.github.com/82981 shows one I
wrote a couple days ago.  I yield each object because there are like
400k records and I can't keep them in memory.  Might be a little nicer
to yield the params hash and let the caller build the object, but I
don't need that flexibility at this point.

Pat


On Sat, Mar 21, 2009 at 11:06 AM, Chris Adams <chris at stemcel.co.uk> wrote:
> Hi guys,
>
> This is my first post to the mailing list, so apologies if this kind of
> question comes up alot already.
>
> I've been working through the Peepcode screencasts on RSpec, and I'm trying
> to what I've been learning into practice to make an importer on a rails app
> that takes an xml feed, and imports each entry in the xml feed into the
> database, skipping imports if they already exist in the db.
>
> The thing is, I don't know the best way to do this, as most examples I've
> seen only refer to handing objects one at a time.
>
> Could someone point me to a couple of code examples of what importer specs
> should look like when written in rspec, or tell me roughly how I should be
> approaching this ?
>
> I've put the generic version of the code in this gist, to give an idea of
> where I'm headed at the mo, but any feedback would be greatly appreciated.
>
> https://gist.github.com/38859f947860d4fc45e2
>
> Thanks and have a good weekend,
>
> Chris
>
> --
> ---
> I'm currently only checking my email at 9am, midday and at 4pm.
> If you need a response from me urgently, please call or text my mobile, or
> contact me via Skype (chris.d.adams).
> ---
> Chris Adams
> Stemcel Studios
> The Hub
> 5 Torrens Street
> London
> EC1V 1NQ
>
> email: chris at stemcel.co.uk
> web: ?www.stemcel.co.uk
> twitter:chris_d_adams
> skype: chris.d.adams
> mob: 07974 368 229
> tel: 0207 558 8971
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From gcirne at gmail.com  Sat Mar 21 19:20:59 2009
From: gcirne at gmail.com (Guilherme Machado Cirne)
Date: Sat, 21 Mar 2009 20:20:59 -0300
Subject: [rspec-users] Testing return value of a block argument
In-Reply-To: <49BE3132.6060305@nomitor.com>
References: <49BE3132.6060305@nomitor.com>
Message-ID: <21a1366d0903211620peea9ce6nd92b120572dcf4e8@mail.gmail.com>

I have this exact same problem. Anyone have a solution?

TIA,

-- 
Guilherme Machado Cirne
gcirne at gmail.com


On Mon, Mar 16, 2009 at 8:00 AM, Yun Huang Yong <yun at nomitor.com> wrote:

> Hi,
>
> I'm using Log4r and one of its neat features is its handling of blocks such
> that you can do:
>  log.debug { "Something bad happened" + some_expensive_method() }
> instead of:
>  log.debug("Something bad happened" + some_expensive_method())
>
> The benefit of the former is that some_expensive_method() is not executed
> until the debug() method executes so if your log level doesn't include DEBUG
> you don't suffer the performance hit of calling some_expensive_method()
> needlessly.
>
> Is there any way to test what the resultant log message is from evaluating
> the block?
>
> i.e. something like:
>  log_mock.should_receive(:debug) { |log_block|
>    # execute log_block, and check its return value
>  }
>
> I have a simple bit of code to tinker with: http://gist.github.com/79820
>
> Thanks in advance,
> yun
>
> --
> Yun Huang Yong
> yun at nomitor.com                  ...nom nom nom
> --
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090321/fac25f89/attachment.html>

From gcirne at gmail.com  Sat Mar 21 19:38:54 2009
From: gcirne at gmail.com (Guilherme Machado Cirne)
Date: Sat, 21 Mar 2009 20:38:54 -0300
Subject: [rspec-users] Expecting a block to return a specific value
Message-ID: <21a1366d0903211638q70811a08m10e0c85e2b9845c6@mail.gmail.com>

Hi,

I have the following method in a Rails view helper:

def title
  content_for(:title) do
    # some code which generates a title dynamically
  end
end

How can I spec that the code inside the block returns the correct title?

TIA,

-- 
Guilherme Machado Cirne
gcirne at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090321/61c61d02/attachment.html>

From slabounty at gmail.com  Sat Mar 21 19:54:59 2009
From: slabounty at gmail.com (Scott LaBounty)
Date: Sat, 21 Mar 2009 16:54:59 -0700
Subject: [rspec-users] New User Issues
In-Reply-To: <57c63afe0903210754r78c83e63yb4084bb09965dd2b@mail.gmail.com>
References: <7de47a040903201421r2e3f2978kf0ca9d4d42b30659@mail.gmail.com>
	<57c63afe0903210754r78c83e63yb4084bb09965dd2b@mail.gmail.com>
Message-ID: <7de47a040903211654l1a5b215fv84272583d9f6735f@mail.gmail.com>

David,

Thanks for the help. On the cucumber/hoe issue, I am running gem version
1.2.0 and when I did a "sudo gem update --system", I got a "Nothing to
update". That may not have been what I'm seeing. The --color makes things
look right.

Thanks again,

Scott

On Sat, Mar 21, 2009 at 7:54 AM, David Chelimsky <dchelimsky at gmail.com>wrote:

> 2009/3/20 Scott LaBounty <slabounty at gmail.com>:
> > I just found RSpec and was trying to do the example on the main page for
> > RSpec (the bowling example). I'm using Ubuntu and did the normal "sudo
> gem
> > install rspec" and then tried to create the bowling_spec.rb file. When I
> ran
> > spec bowling_spec.rb, I was missing the cucumber gem, installed that,
> reran
> > and was missing the hoe gem, installed that,
>
> Cucumber and hoe are developer dependencies. You should probably
> upgrade rubygems - sounds like you're using an old version that
> doesn't know the difference between developer dependencies and
> standard runtime dependencies.
>
> I should probably make it so those dependencies don't exist at all
> unless you have a new enough rubygems to make the distinction.
>
> > reran and it gave me the a
> > missing 'require' from the bowling_spec since I didn't have a bowling.rb
> > file. Is that expected?
>
> The example fails to point that out, but yes, it is the expected
> behaviour if the file doesn't exist.
>
> > From the example, it didn't seem like it would be.
> > When I then added the bowling.rb file and reran everything looked correct
> > except that it wasn't in color (i.e. no green). Is that expected or do I
> > need to do something differnt to get this to work?
>
> Add the --color option to the command line and you'll get color.
>
> > I'm running ruby 1.8.6 if
> > it makes a difference.
>
> Nope - the example needs some fixing. I'm doing a bug-fix release in
> the next few days, and I'll be sure to fix the example so it works as
> a mini-tutorial when I do that release.
>
> Thanks!
>
> David
>
>
>
> >
> > Thanks,
> >
> > --
> > Scott
> > http://steamcode.blogspot.com/
> >
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Scott
http://steamcode.blogspot.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090321/6b85f711/attachment.html>

From zach.dennis at gmail.com  Sat Mar 21 20:22:02 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Sat, 21 Mar 2009 20:22:02 -0400
Subject: [rspec-users] Expecting a block to return a specific value
In-Reply-To: <21a1366d0903211638q70811a08m10e0c85e2b9845c6@mail.gmail.com>
References: <21a1366d0903211638q70811a08m10e0c85e2b9845c6@mail.gmail.com>
Message-ID: <85d99afe0903211722r67627d63hc4c0b433d6fa70af@mail.gmail.com>

2009/3/21 Guilherme Machado Cirne <gcirne at gmail.com>:
> Hi,
>
> I have the following method in a Rails view helper:
>
> def title
> ? content_for(:title) do
> ??? # some code which generates a title dynamically
> ? end
> end
>
> How can I spec that the code inside the block returns the correct title?

My preference is to let my view helpers be rendered in my view specs,
and I move the logic that constructs the title onto a presenter. Then
I can say things like this in my view spec:

it "should render the title" do
  thing = mock "thing presenter", :title => "foo"
  assign[:thing] = thing
  render "some.template"
  response.should contain("foo")
end

And I can have a presenter spec which verifies the title is built correctly

describe ThingPresenter do
   describe '#title' do
      it "should return a concatenated title, user name, blah blah blah" do
         # ....
      end
   end
end

There are more ways to accomplish this I know, but I've grown to
become extremely fond of the clean separation between constructing
markup and producing presentation content. It makes things easier to
spec IMO, gives things a good home, and allows me to stop looking at
content for instance variables dynamically generated by Rails.

If interested...   http://wiki.github.com/mhs/caching_presenter


-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From mark at mwilden.com  Sat Mar 21 20:25:01 2009
From: mark at mwilden.com (Mark Wilden)
Date: Sat, 21 Mar 2009 17:25:01 -0700
Subject: [rspec-users] Testing return value of a block argument
In-Reply-To: <49BE3132.6060305@nomitor.com>
References: <49BE3132.6060305@nomitor.com>
Message-ID: <3c30da400903211725n49499683sa7230d5b67f70903@mail.gmail.com>

On Mon, Mar 16, 2009 at 4:00 AM, Yun Huang Yong <yun at nomitor.com> wrote:
>
> i.e. something like:
> ?log_mock.should_receive(:debug) { |log_block|
> ? ?# execute log_block, and check its return value
> ?}

I suppose you could always look at the source code for the debug
method, find out what it does with the result of the block and set an
expectation on that behavior.

///ark

From ashley.moran at patchspace.co.uk  Sat Mar 21 21:03:21 2009
From: ashley.moran at patchspace.co.uk (Ashley Moran)
Date: Sun, 22 Mar 2009 01:03:21 +0000
Subject: [rspec-users] [Cucumber] LinkedIn group & cocktail recipe
Message-ID: <8F4B4574-6E38-4DDC-8409-8189266A2C92@patchspace.co.uk>

Hi all

For no other good reason than I wanted the Cucumber logo on my  
LinkedIn profile - and I'm addicted to creating stuff on LinkedIn - I  
created a Cucumber group[1].

Well there is one good reason - more and more people I'm meeting are  
looking at Cucumber and using it without considering themselves "RSpec  
users".  So I think it'd be good to have a group for Cucumber-focused  
people.

In fact I'm starting to think I could expand the coaching I do to non- 
Ruby developers/teams who use Cucumber for BDD.  (Or rather -  
developers that don't, but *should*.)  Subversively getting them using  
Ruby would be a bonus =)

So anyway please join!

On a tangential note, this baryouth I know who works in a coffee-shop/ 
bar near me surprised me the other day when I asked for a new drink.   
He actually went out to a shop to get the magic ingredient, and  
produced... a cucumber martini[2]!  Think you need a really fine mesh  
to make a real one though.  As I don't have a sweet tooth, I got him  
to make it with no sugar.  Think the weather was a bit cold at the  
time, but it'd make a nice stiff summer drink.  Slightly bitter but  
very refreshing.  If anyone is planning a BDD conference in southern  
Italy, these should be on the menu* =)

Ashley

[1] http://www.linkedin.com/groups?gid=1858343
[2] http://www.drinknation.com/drink/Cucumber-Martini

* Since I'm pretty sure it's working in software development that  
turned me alcoholic, I think serving cucumber martinis would be  
*justification* for an RSpec/Cucumber conference...

-- 
http://www.patchspace.co.uk/
http://www.linkedin.com/in/ashleymoran
http://aviewfromafar.net/
http://twitter.com/ashleymoran







From bornboulder77 at gmail.com  Sun Mar 22 01:27:05 2009
From: bornboulder77 at gmail.com (Bjorn Boulder)
Date: Sat, 21 Mar 2009 22:27:05 -0700
Subject: [rspec-users] Problem running autotest in rails 2.3
Message-ID: <a6591d550903212227t72d6b670m8f6be58f518e4d03@mail.gmail.com>

People,

I'm trying to run autotest on rails 2.3

I get a NoMethodError.

Here is what I see:

Sat Mar 21 20:47 /b/tmp/myfc23 maco$
Sat Mar 21 20:47 /b/tmp/myfc23 maco$ autotest
loading autotest/rails_rspec
./vendor/plugins/rspec/lib/autotest/rspec.rb:24:in `initialize': undefined
method `failed_results_re=' for #<Autotest::RailsRspec:0x1205b88>
(NoMethodError)
        from
/pt/r1/lib/ruby/gems/1.8/gems/ZenTest-3.8.0/lib/autotest.rb:126:in `new'
        from
/pt/r1/lib/ruby/gems/1.8/gems/ZenTest-3.8.0/lib/autotest.rb:126:in `run'
        from /pt/r1/lib/ruby/gems/1.8/gems/ZenTest-3.8.0/bin/autotest:48
        from /pt/r1/bin/autotest:19:in `load'
        from /pt/r1/bin/autotest:19
Sat Mar 21 20:47 /b/tmp/myfc23 maco$
Sat Mar 21 20:47 /b/tmp/myfc23 maco$

Here is info about my rails:


Sat Mar 21 20:47 /b/tmp/myfc23 maco$
Sat Mar 21 20:47 /b/tmp/myfc23 maco$
Sat Mar 21 20:47 /b/tmp/myfc23 maco$ script/about
About your application's environment
Ruby version              1.8.7 (i686-darwin9.6.2)
RubyGems version          1.3.1
Rack version              1.0 bundled
Rails version             2.3.2
Active Record version     2.3.2
Action Pack version       2.3.2
Active Resource version   2.3.2
Action Mailer version     2.3.2
Active Support version    2.3.2
Application root          /b/tmp/myfc23
Environment               development
Database adapter          sqlite3
Database schema version   2
Sat Mar 21 20:51 /b/tmp/myfc23 maco$

Here is a list of my gems:

*** LOCAL GEMS ***

actionmailer (2.3.2, 2.2.2)
actionpack (2.3.2, 2.2.2)
activerecord (2.3.2, 2.2.2)
activeresource (2.3.2, 2.2.2)
activesupport (2.3.2, 2.2.2)
cgi_multipart_eof_fix (2.5.0)
chronic (0.2.3)
columnize (0.3.0)
daemons (1.0.10)
darkfish-rdoc (1.1.5)
diff-lcs (1.1.2)
extlib (0.9.10)
fastthread (1.0.1)
gem_plugin (0.2.3)
highline (1.5.0)
hoe (1.9.0)
hpricot (0.6.164)
libxml-ruby (0.9.8)
linecache (0.43)
mongrel (1.1.5)
mysql (2.7)
newgem (1.2.3)
rack (0.9.1)
rails (2.3.2, 2.2.2)
rake (0.8.4, 0.8.3)
rcov (0.8.1.2.0)
rdoc (2.4.1)
RedCloth (4.1.9)
rhodes (0.3.0)
rspec (1.2.0, 1.1.12)
rspec-rails (1.2.0, 1.1.12)
rubigen (1.5.2)
ruby-debug (0.10.3)
ruby-debug-base (0.10.3)
rubyforge (1.0.3)
sqlite3-ruby (1.2.4, 1.2.3)
syntax (1.0.0)
templater (0.5.0)
ZenTest (3.8.0)

Any tips on debugging this?

-b
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090321/a8e3c47f/attachment.html>

From dchelimsky at gmail.com  Sun Mar 22 11:20:35 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 22 Mar 2009 10:20:35 -0500
Subject: [rspec-users] Problem running autotest in rails 2.3
In-Reply-To: <a6591d550903212227t72d6b670m8f6be58f518e4d03@mail.gmail.com>
References: <a6591d550903212227t72d6b670m8f6be58f518e4d03@mail.gmail.com>
Message-ID: <57c63afe0903220820me0cc1a1wf3c93d4dbce29021@mail.gmail.com>

2009/3/22 Bjorn Boulder <bornboulder77 at gmail.com>:
> People,
> I'm trying to run autotest on rails 2.3
> I get a NoMethodError.
> Here is what I see:
> Sat Mar 21 20:47 /b/tmp/myfc23 maco$
> Sat Mar 21 20:47 /b/tmp/myfc23 maco$ autotest
> loading autotest/rails_rspec
> ./vendor/plugins/rspec/lib/autotest/rspec.rb:24:in `initialize': undefined
> method `failed_results_re=' for #<Autotest::RailsRspec:0x1205b88>
> (NoMethodError)
> ?? ? ? ?from
> /pt/r1/lib/ruby/gems/1.8/gems/ZenTest-3.8.0/lib/autotest.rb:126:in `new'
> ?? ? ? ?from
> /pt/r1/lib/ruby/gems/1.8/gems/ZenTest-3.8.0/lib/autotest.rb:126:in `run'
> ?? ? ? ?from /pt/r1/lib/ruby/gems/1.8/gems/ZenTest-3.8.0/bin/autotest:48
> ?? ? ? ?from /pt/r1/bin/autotest:19:in `load'
> ?? ? ? ?from /pt/r1/bin/autotest:19
> Sat Mar 21 20:47 /b/tmp/myfc23 maco$
> Sat Mar 21 20:47 /b/tmp/myfc23 maco$
> Here is info about my rails:
>
> Sat Mar 21 20:47 /b/tmp/myfc23 maco$
> Sat Mar 21 20:47 /b/tmp/myfc23 maco$
> Sat Mar 21 20:47 /b/tmp/myfc23 maco$ script/about
> About your application's environment
> Ruby version ? ? ? ? ? ? ?1.8.7 (i686-darwin9.6.2)
> RubyGems version ? ? ? ? ?1.3.1
> Rack version ? ? ? ? ? ? ?1.0 bundled
> Rails version ? ? ? ? ? ? 2.3.2
> Active Record version ? ? 2.3.2
> Action Pack version ? ? ? 2.3.2
> Active Resource version ? 2.3.2
> Action Mailer version ? ? 2.3.2
> Active Support version ? ?2.3.2
> Application root ? ? ? ? ?/b/tmp/myfc23
> Environment ? ? ? ? ? ? ? development
> Database adapter ? ? ? ? ?sqlite3
> Database schema version ? 2
> Sat Mar 21 20:51 /b/tmp/myfc23 maco$
> Here is a list of my gems:
> *** LOCAL GEMS ***
> actionmailer (2.3.2, 2.2.2)
> actionpack (2.3.2, 2.2.2)
> activerecord (2.3.2, 2.2.2)
> activeresource (2.3.2, 2.2.2)
> activesupport (2.3.2, 2.2.2)
> cgi_multipart_eof_fix (2.5.0)
> chronic (0.2.3)
> columnize (0.3.0)
> daemons (1.0.10)
> darkfish-rdoc (1.1.5)
> diff-lcs (1.1.2)
> extlib (0.9.10)
> fastthread (1.0.1)
> gem_plugin (0.2.3)
> highline (1.5.0)
> hoe (1.9.0)
> hpricot (0.6.164)
> libxml-ruby (0.9.8)
> linecache (0.43)
> mongrel (1.1.5)
> mysql (2.7)
> newgem (1.2.3)
> rack (0.9.1)
> rails (2.3.2, 2.2.2)
> rake (0.8.4, 0.8.3)
> rcov (0.8.1.2.0)
> rdoc (2.4.1)
> RedCloth (4.1.9)
> rhodes (0.3.0)
> rspec (1.2.0, 1.1.12)
> rspec-rails (1.2.0, 1.1.12)
> rubigen (1.5.2)
> ruby-debug (0.10.3)
> ruby-debug-base (0.10.3)
> rubyforge (1.0.3)
> sqlite3-ruby (1.2.4, 1.2.3)
> syntax (1.0.0)
> templater (0.5.0)
> ZenTest (3.8.0)

I think updating ZenTest will resolve this for you. ZenTest is up to 4.0 now.

> Any tips on debugging this?
> -b
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From peter.a.jaros at gmail.com  Sun Mar 22 11:33:00 2009
From: peter.a.jaros at gmail.com (Peter Jaros)
Date: Sun, 22 Mar 2009 11:33:00 -0400
Subject: [rspec-users] Testing return value of a block argument
In-Reply-To: <3c30da400903211725n49499683sa7230d5b67f70903@mail.gmail.com>
References: <49BE3132.6060305@nomitor.com>
	<3c30da400903211725n49499683sa7230d5b67f70903@mail.gmail.com>
Message-ID: <937d9d810903220833r3f3749adu1b02b3925058db4@mail.gmail.com>

Going forward, what do people think about being able to say

mock.should_receive(:debug).with_block  { |log_block|
  # execute log_block, and check its return value
 }

Thoughts?

Peter


On Sat, Mar 21, 2009 at 8:25 PM, Mark Wilden <mark at mwilden.com> wrote:
> On Mon, Mar 16, 2009 at 4:00 AM, Yun Huang Yong <yun at nomitor.com> wrote:
>>
>> i.e. something like:
>> ?log_mock.should_receive(:debug) { |log_block|
>> ? ?# execute log_block, and check its return value
>> ?}
>
> I suppose you could always look at the source code for the debug
> method, find out what it does with the result of the block and set an
> expectation on that behavior.
>
> ///ark
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Sun Mar 22 11:59:56 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 22 Mar 2009 10:59:56 -0500
Subject: [rspec-users] Testing return value of a block argument
In-Reply-To: <937d9d810903220833r3f3749adu1b02b3925058db4@mail.gmail.com>
References: <49BE3132.6060305@nomitor.com>
	<3c30da400903211725n49499683sa7230d5b67f70903@mail.gmail.com>
	<937d9d810903220833r3f3749adu1b02b3925058db4@mail.gmail.com>
Message-ID: <57c63afe0903220859qb6b4a1fjeb2d9a26ecfbf4c1@mail.gmail.com>

On Sun, Mar 22, 2009 at 10:33 AM, Peter Jaros <peter.a.jaros at gmail.com> wrote:
> Going forward, what do people think about being able to say
>
> mock.should_receive(:debug).with_block ?{ |log_block|
> ?# execute log_block, and check its return value
> ?}
>
> Thoughts?

I like the idea, but I don't know how well it will play with other
sorts of expectations. We'd probably need to alias it with and_block
so you could say:

mock.should_receive(:message).with(:these, "args").and_block {|block| .... }

Would you please file a feature request for this?

Thanks,
David

>
> Peter
>
>
> On Sat, Mar 21, 2009 at 8:25 PM, Mark Wilden <mark at mwilden.com> wrote:
>> On Mon, Mar 16, 2009 at 4:00 AM, Yun Huang Yong <yun at nomitor.com> wrote:
>>>
>>> i.e. something like:
>>> ?log_mock.should_receive(:debug) { |log_block|
>>> ? ?# execute log_block, and check its return value
>>> ?}
>>
>> I suppose you could always look at the source code for the debug
>> method, find out what it does with the result of the block and set an
>> expectation on that behavior.
>>
>> ///ark
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From mark at mwilden.com  Sun Mar 22 14:00:50 2009
From: mark at mwilden.com (Mark Wilden)
Date: Sun, 22 Mar 2009 11:00:50 -0700
Subject: [rspec-users] Testing return value of a block argument
In-Reply-To: <49BE3132.6060305@nomitor.com>
References: <49BE3132.6060305@nomitor.com>
Message-ID: <3c30da400903221100s65e61fc3m22972ac603ea69f7@mail.gmail.com>

On Mon, Mar 16, 2009 at 4:00 AM, Yun Huang Yong <yun at nomitor.com> wrote:
>
> Is there any way to test what the resultant log message is from evaluating
> the block?
>
> i.e. something like:
> ?log_mock.should_receive(:debug) { |log_block|
> ? ?# execute log_block, and check its return value
> ?}

Sorry - I don't quite understand. Do you want to test the logger debug
method's behavior when you pass it a certain block, or do you want to
test what the block itself does? If the former, it seems to me that
you wouldn't want to mock the logger object. If the latter, you can
just test the block directly.

///ark

From dchelimsky at gmail.com  Mon Mar 23 01:07:38 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 23 Mar 2009 00:07:38 -0500
Subject: [rspec-users] [ANN] rspec 1.2.1 Released
Message-ID: <57c63afe0903222207k1a5bb22g8714327a553017f8@mail.gmail.com>

rspec version 1.2.1 has been released!

* <http://rspec.info>
* <http://rubyforge.org/projects/rspec>
* <http://github.com/dchelimsky/rspec/wikis>
* <rspec-devel at rubyforge.org>

Behaviour Driven Development for Ruby.

Changes:

### Version 1.2.1 / 2009-03-22

This is a bug-fix release, recommended for anybody who has already upgraded to
rspec-1.2.0.

See Upgrade.rdoc for information about upgrading to rspec-1.2.1

* enhancments

  * matchers, including the new DSL, easily added to your test/unit tests
  * added support for 0 to n args in matcher DSL
  * restored loading rubygems when necessary
    * if you really don't want to use rubygems, you
      can set an NO_RUBYGEMS environment
      variable, and RSpec won't force it on you.
  * added -u/--debugger option (Rick DeNatale) #262.
    * just add "debugger" anywhere in your code and run spec
path/to/code --debugger
  * rename ExampleDescription to ExampleProxy
  * pass ExampleProxy to example_started(). Closes #738, #743
    * thanks to Tobias Grimm (Eclipse) fort the patch and Roman Chernyatchik
      (JetBrains, RubyMine) for the assist

* bug fixes

  * subject (implicit or explicit) is now properly inherited by nested
groups. Closes #744.

* <http://rspec.info>
* <http://rubyforge.org/projects/rspec>
* <http://github.com/dchelimsky/rspec/wikis>
* <rspec-devel at rubyforge.org>

From dchelimsky at gmail.com  Mon Mar 23 01:08:02 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 23 Mar 2009 00:08:02 -0500
Subject: [rspec-users] [ANN] rspec-rails 1.2.1 Released
Message-ID: <57c63afe0903222208y6384ee37qb77c5dfa21b9b62f@mail.gmail.com>

rspec-rails version 1.2.1 has been released!

* <http://rspec.info>
* <http://rubyforge.org/projects/rspec>
* <http://github.com/dchelimsky/rspec-rails>
* <http://wiki.github.com/dchelimsky/rspec/rails>
* <rspec-devel at rubyforge.org>

Behaviour Driven Development for Ruby on Rails.

Changes:

### Version 1.2.1 / 2009-03-22

This is a bug-fix release, recommended for anybody who has already upgraded to
rspec-rails-1.2.0 or is upgrading to rails-2.3.2

See Upgrade.rdoc for information about upgrading to rspec-rails-1.2.1

* enhancements

  * more cleanup of internals (reducing dependency on rspec-core)
  * don't require config/environments more than once
  * autotest includes spec/routing directory (Matt Peterson). Closes #739.
  * display helpful messages when installing rspec-rails running
script/generate rspec
    * thanks for Dr Nic for the pointers
  * restored require 'rubygems' where needed
    * export NO_RUBYGEMS=true if you don't use rubygems

* bug fixes

  * fix scoping issues in rspec-rails' own suite for ruby 1.9.1 (Matthias
    Hennemeyer). Closes #717.
  * rake stats no longer hides test directories. Closes #748.
  * fixed regression that was introduced in 1.2 in which controller_name
    failed to override the controller class passed to describe() (patches from
    Aaron Gibralter and Zach Dennis). Closes #732.

* <http://rspec.info>
* <http://rubyforge.org/projects/rspec>
* <http://github.com/dchelimsky/rspec-rails>
* <http://wiki.github.com/dchelimsky/rspec/rails>
* <rspec-devel at rubyforge.org>

From dchelimsky at gmail.com  Mon Mar 23 02:49:21 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 23 Mar 2009 01:49:21 -0500
Subject: [rspec-users] [ANN] rspec 1.2.2 Released
Message-ID: <57c63afe0903222349m583bb6c2qa2268af3ccb5a2a4@mail.gmail.com>

rspec version 1.2.2 has been released!

* <http://rspec.info>
* <http://rubyforge.org/projects/rspec>
* <http://github.com/dchelimsky/rspec/wikis>
* <rspec-devel at rubyforge.org>

Behaviour Driven Development for Ruby.

Changes:

### Version 1.2.2 / 2009-03-22

Bug-fix release (fixes regression introduced in 1.2.1)

* bug fixes

  * fixed bug in which spec_parser raised an error for custom example group
    base classes

* <http://rspec.info>
* <http://rubyforge.org/projects/rspec>
* <http://github.com/dchelimsky/rspec/wikis>
* <rspec-devel at rubyforge.org>

From dchelimsky at gmail.com  Mon Mar 23 02:49:27 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 23 Mar 2009 01:49:27 -0500
Subject: [rspec-users] [ANN] rspec-rails 1.2.2 Released
Message-ID: <57c63afe0903222349p13b26d4dq3126ff2cb2c67b0a@mail.gmail.com>

rspec-rails version 1.2.2 has been released!

* <http://rspec.info>
* <http://rubyforge.org/projects/rspec>
* <http://github.com/dchelimsky/rspec-rails>
* <http://wiki.github.com/dchelimsky/rspec/rails>
* <rspec-devel at rubyforge.org>

Behaviour Driven Development for Ruby on Rails.

Changes:

### Version 1.2.2 / 2009-03-22

No changes in this release, but aligns with the rspec-1.2.2 release.

* <http://rspec.info>
* <http://rubyforge.org/projects/rspec>
* <http://github.com/dchelimsky/rspec-rails>
* <http://wiki.github.com/dchelimsky/rspec/rails>
* <rspec-devel at rubyforge.org>

From longhiandrea at gmail.com  Mon Mar 23 05:41:43 2009
From: longhiandrea at gmail.com (andrea)
Date: Mon, 23 Mar 2009 02:41:43 -0700 (PDT)
Subject: [rspec-users] Rspec weird behaviour
Message-ID: <e9dda862-b9a1-4a87-85fa-1c4b9f5075cc@y9g2000yqg.googlegroups.com>

Hi,
I recently migrated from classic rails testing to Rspec, so I am
pretty new to the framework and still learning. I am getting weird
errors on an ActiveRecord model test, here is the basic class model
definition:

class Size < ActiveRecord::Base
  has_many :quantities, :dependent => :destroy
  validates_presence_of :name
  validates_uniqueness_of :name, :case_sensitive => false
end

and this is the faulty spec:
  it 'new size should have an error on name' do
    Size.new.should have(1).error_on(:name)
  end

the red response is:
 'new size should have an error on name' FAILED
 expected 1 error on :name, got 0

if I change the spec to read like this:
 Size.new.should have(:no).error_on(:name)

I still get a red response:
 'new size should have an error on name' FAILED
 expected 0 error on :name, got 1

Guess the problem is the model class name (Size) as I don't get such
weird stuff from other classes... can I fix this somehow?

Thanks

Andrea

From longhiandrea at gmail.com  Mon Mar 23 06:50:30 2009
From: longhiandrea at gmail.com (andrea)
Date: Mon, 23 Mar 2009 03:50:30 -0700 (PDT)
Subject: [rspec-users] Rspec weird behaviour
In-Reply-To: <e9dda862-b9a1-4a87-85fa-1c4b9f5075cc@y9g2000yqg.googlegroups.com>
References: <e9dda862-b9a1-4a87-85fa-1c4b9f5075cc@y9g2000yqg.googlegroups.com>
Message-ID: <d7cc68d8-a6a1-417a-bd2b-ff624e2697d3@s20g2000yqh.googlegroups.com>

On 23 Mar, 10:41, andrea <longhiand... at gmail.com> wrote:

[cut]

BTW I am using rails 2.3.2, rspec and rails-spec version 1.2.0

Andrea

From dchelimsky at gmail.com  Mon Mar 23 08:10:37 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 23 Mar 2009 07:10:37 -0500
Subject: [rspec-users] Rspec weird behaviour
In-Reply-To: <e9dda862-b9a1-4a87-85fa-1c4b9f5075cc@y9g2000yqg.googlegroups.com>
References: <e9dda862-b9a1-4a87-85fa-1c4b9f5075cc@y9g2000yqg.googlegroups.com>
Message-ID: <57c63afe0903230510u38839be9ied74427b69ac46e1@mail.gmail.com>

On Mon, Mar 23, 2009 at 4:41 AM, andrea <longhiandrea at gmail.com> wrote:
> Hi,
> I recently migrated from classic rails testing to Rspec, so I am
> pretty new to the framework and still learning. I am getting weird
> errors on an ActiveRecord model test, here is the basic class model
> definition:
>
> class Size < ActiveRecord::Base
> ?has_many :quantities, :dependent => :destroy
> ?validates_presence_of :name
> ?validates_uniqueness_of :name, :case_sensitive => false
> end
>
> and this is the faulty spec:
> ?it 'new size should have an error on name' do
> ? ?Size.new.should have(1).error_on(:name)
> ?end
>
> the red response is:
> ?'new size should have an error on name' FAILED
> ?expected 1 error on :name, got 0
>
> if I change the spec to read like this:
> ?Size.new.should have(:no).error_on(:name)
>
> I still get a red response:
> ?'new size should have an error on name' FAILED
> ?expected 0 error on :name, got 1
>
> Guess the problem is the model class name (Size) as I don't get such
> weird stuff from other classes... can I fix this somehow?

Hi Andrea,

I just tried this myself (because I wanted to see if the class name
was really the problem) and "Size.new.should have(1).error_on(:name)"
passed for me. I also tried "Size.new.should
have(:no).errors_on(:name)" and that failed correctly. So something
else is amiss in this case.

If this persists, please submit a bug report to
http://rspec.lighthouseapp.com and include a zipped up app that I can
run to see the problem.

Thanks,
David

>
> Thanks
>
> Andrea
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From chuck at chuckgrindel.com  Mon Mar 23 10:44:17 2009
From: chuck at chuckgrindel.com (Charles Grindel)
Date: Mon, 23 Mar 2009 10:44:17 -0400
Subject: [rspec-users] Installing RSpec 1.2.2 and RSpec-Rails 1.2.2 As
	Plugins for Rails 2.0.5
Message-ID: <c7d77dde0903230744g12ac05d7y9f7adf40a3a9c5ce@mail.gmail.com>

Hi,

I have read the Rspec-Rails page (
http://wiki.github.com/dchelimsky/rspec/rails) describing the different
installation procedures for RSpec and Rails.  Since I am running Rails
2.0.5, I followed the instructions under "Install an RSpec release >= 1.1.4
in Rails <= 2.1.0".  In these instructions, it has me clone the Rspec and
Rspec-Rails projects and then it says to checkout 1.1.8.  I assumed that
this should be 1.2.2.

cd rspec
git checkout 1.2.2

However, when I execute the checkout command, I receive the following
message:

Note: moving to "1.2.2" which isn't a local branch
If you want to create a new branch from this checkout, you may do so
(now or later) by using -b with the checkout command again. Example:
  git checkout -b <new_branch_name>
HEAD is now at fd09ebc... prep for 1.2.2 release

Being a git newbie, I am not sure if this is what I should expect to see.
Any feedback on whether this is correct or what I should do differently
would be greatly appreciated.

Thanks,
Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090323/10baecb7/attachment.html>

From scott at railsnewbie.com  Mon Mar 23 10:45:03 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Mon, 23 Mar 2009 10:45:03 -0400
Subject: [rspec-users] Rspec weird behaviour
In-Reply-To: <e9dda862-b9a1-4a87-85fa-1c4b9f5075cc@y9g2000yqg.googlegroups.com>
References: <e9dda862-b9a1-4a87-85fa-1c4b9f5075cc@y9g2000yqg.googlegroups.com>
Message-ID: <49C7A06F.4080003@railsnewbie.com>

andrea wrote:
> Hi,
> I recently migrated from classic rails testing to Rspec, so I am
> pretty new to the framework and still learning. I am getting weird
> errors on an ActiveRecord model test, here is the basic class model
> definition:
>
> class Size < ActiveRecord::Base
>   has_many :quantities, :dependent => :destroy
>   validates_presence_of :name
>   validates_uniqueness_of :name, :case_sensitive => false
> end
>
> and this is the faulty spec:
>   it 'new size should have an error on name' do
>     Size.new.should have(1).error_on(:name)
>   end
>
> the red response is:
>  'new size should have an error on name' FAILED
>  expected 1 error on :name, got 0
>
> if I change the spec to read like this:
>  Size.new.should have(:no).error_on(:name)
>   

It should be have(0).errors_on(:name), AFAIK

> I still get a red response:
>  'new size should have an error on name' FAILED
>  expected 0 error on :name, got 1
>
> Guess the problem is the model class name (Size) as I don't get such
> weird stuff from other classes... can I fix this somehow?
>
> Thanks
>
> Andrea
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>   


From dchelimsky at gmail.com  Mon Mar 23 11:09:56 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 23 Mar 2009 10:09:56 -0500
Subject: [rspec-users] Installing RSpec 1.2.2 and RSpec-Rails 1.2.2 As
	Plugins for Rails 2.0.5
In-Reply-To: <c7d77dde0903230744g12ac05d7y9f7adf40a3a9c5ce@mail.gmail.com>
References: <c7d77dde0903230744g12ac05d7y9f7adf40a3a9c5ce@mail.gmail.com>
Message-ID: <57c63afe0903230809u37abc841pea9be72a1006f98c@mail.gmail.com>

2009/3/23 Charles Grindel <chuck at chuckgrindel.com>:
> Hi,
>
> I have read the Rspec-Rails page
> (http://wiki.github.com/dchelimsky/rspec/rails) describing the different
> installation procedures for RSpec and Rails.? Since I am running Rails
> 2.0.5, I followed the instructions under "Install an RSpec release >= 1.1.4
> in Rails <= 2.1.0".? In these instructions, it has me clone the Rspec and
> Rspec-Rails projects and then it says to checkout 1.1.8.? I assumed that
> this should be 1.2.2.
>
> cd rspec
> git checkout 1.2.2
>
> However, when I execute the checkout command, I receive the following
> message:
>
> Note: moving to "1.2.2" which isn't a local branch
> If you want to create a new branch from this checkout, you may do so
> (now or later) by using -b with the checkout command again. Example:
> ? git checkout -b <new_branch_name>
> HEAD is now at fd09ebc... prep for 1.2.2 release
>
> Being a git newbie, I am not sure if this is what I should expect to see.
> Any feedback on whether this is correct or what I should do differently
> would be greatly appreciated.

I neglected to tag the release in git last night. It is now properly
tagged, so if you go into each plugin dir and "git pull", you should
be able to proceed.

Cheers,
David

>
> Thanks,
> Chuck
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From dchelimsky at gmail.com  Mon Mar 23 11:24:10 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 23 Mar 2009 10:24:10 -0500
Subject: [rspec-users] Rspec weird behaviour
In-Reply-To: <49C7A06F.4080003@railsnewbie.com>
References: <e9dda862-b9a1-4a87-85fa-1c4b9f5075cc@y9g2000yqg.googlegroups.com>
	<49C7A06F.4080003@railsnewbie.com>
Message-ID: <57c63afe0903230824t53dc5d02g12c9f9b6d29d5583@mail.gmail.com>

On Mon, Mar 23, 2009 at 9:45 AM, Scott Taylor <scott at railsnewbie.com> wrote:
> andrea wrote:
>>
>> Hi,
>> I recently migrated from classic rails testing to Rspec, so I am
>> pretty new to the framework and still learning. I am getting weird
>> errors on an ActiveRecord model test, here is the basic class model
>> definition:
>>
>> class Size < ActiveRecord::Base
>> ?has_many :quantities, :dependent => :destroy
>> ?validates_presence_of :name
>> ?validates_uniqueness_of :name, :case_sensitive => false
>> end
>>
>> and this is the faulty spec:
>> ?it 'new size should have an error on name' do
>> ? ?Size.new.should have(1).error_on(:name)
>> ?end
>>
>> the red response is:
>> ?'new size should have an error on name' FAILED
>> ?expected 1 error on :name, got 0
>>
>> if I change the spec to read like this:
>> ?Size.new.should have(:no).error_on(:name)
>>
>
> It should be have(0).errors_on(:name), AFAIK

have(:no).errors_on ... actually works as advertised (converts to 0).

>
>> I still get a red response:
>> ?'new size should have an error on name' FAILED
>> ?expected 0 error on :name, got 1
>>
>> Guess the problem is the model class name (Size) as I don't get such
>> weird stuff from other classes... can I fix this somehow?
>>
>> Thanks
>>
>> Andrea
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From apremdas at gmail.com  Mon Mar 23 12:58:42 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Mon, 23 Mar 2009 16:58:42 +0000
Subject: [rspec-users] Running two instances of autospec
Message-ID: <88fd8ddc0903230958x4bd01ed7ud1fd9603684b5afa@mail.gmail.com>

Hi all,
Got this silly idea that I'd like to run two instances of autospec -

  - one for features
  - the other for specs

However I can't work out how to run just the features on their own - can
anyone help?

TIA

Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090323/60260403/attachment-0001.html>

From chuck at chuckgrindel.com  Mon Mar 23 14:23:21 2009
From: chuck at chuckgrindel.com (Charles Grindel)
Date: Mon, 23 Mar 2009 14:23:21 -0400
Subject: [rspec-users] Spec Server Error on rake spec:server:start
Message-ID: <c7d77dde0903231123q2ba6b886v1cd3368943a68bb0@mail.gmail.com>

Hi,

I am following the directions for setting up autotest (
http://wiki.github.com/dchelimsky/rspec/spec_server-autospec-nearly-pure-bdd-joy)
and experienced an error when I run rake spec:server:start.

$ rake spec:server:start
(in /home/cgrindel/code/it/webapp)
Starting up spec_server ...
/home/cgrindel/code/it/webapp/vendor/plugins/rspec-rails/lib/spec/rails/spec_server.rb:1:
uninitialized constant Rails (NameError)
    from script/spec_server:21:in `require'
    from script/spec_server:21

I took a quick look at the code in script/spec_server.rb.  In short, it
appears that the script requires 'spec/rails/spec_server' before the Rails
environment is loaded which happens on line 26.  I moved the require of
'spec/rails/spec_server' after the Rails environment load.  This appears to
have fixed this issue.

So, my first question, has anyone else seen this problem?  If not, can
anyone explain how the Rails constant should be available before the Rails
environment is loaded?

Thanks,
Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090323/08e16a43/attachment.html>

From dchelimsky at gmail.com  Mon Mar 23 14:41:56 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 23 Mar 2009 13:41:56 -0500
Subject: [rspec-users] Spec Server Error on rake spec:server:start
In-Reply-To: <c7d77dde0903231123q2ba6b886v1cd3368943a68bb0@mail.gmail.com>
References: <c7d77dde0903231123q2ba6b886v1cd3368943a68bb0@mail.gmail.com>
Message-ID: <57c63afe0903231141v39484cefl6f89cba655e68bde@mail.gmail.com>

2009/3/23 Charles Grindel <chuck at chuckgrindel.com>:
> Hi,
>
> I am following the directions for setting up autotest
> (http://wiki.github.com/dchelimsky/rspec/spec_server-autospec-nearly-pure-bdd-joy)
> and experienced an error when I run rake spec:server:start.
>
> $ rake spec:server:start
> (in /home/cgrindel/code/it/webapp)
> Starting up spec_server ...
> /home/cgrindel/code/it/webapp/vendor/plugins/rspec-rails/lib/spec/rails/spec_server.rb:1:
> uninitialized constant Rails (NameError)
> ??? from script/spec_server:21:in `require'
> ??? from script/spec_server:21
>
> I took a quick look at the code in script/spec_server.rb.? In short, it
> appears that the script requires 'spec/rails/spec_server' before the Rails
> environment is loaded which happens on line 26.? I moved the require of
> 'spec/rails/spec_server' after the Rails environment load.? This appears to
> have fixed this issue.
>
> So, my first question, has anyone else seen this problem?? If not, can
> anyone explain how the Rails constant should be available before the Rails
> environment is loaded?

Did you run "script/generate rspec" when you upgraded the plugin? If
not, please do so now, and let it rewrite everything in script/ and
lib/tasks/rspec.rake.

>
> Thanks,
> Chuck
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From chuck at chuckgrindel.com  Mon Mar 23 15:16:43 2009
From: chuck at chuckgrindel.com (Charles Grindel)
Date: Mon, 23 Mar 2009 15:16:43 -0400
Subject: [rspec-users] Spec Server Error on rake spec:server:start
In-Reply-To: <57c63afe0903231141v39484cefl6f89cba655e68bde@mail.gmail.com>
References: <c7d77dde0903231123q2ba6b886v1cd3368943a68bb0@mail.gmail.com>
	<57c63afe0903231141v39484cefl6f89cba655e68bde@mail.gmail.com>
Message-ID: <c7d77dde0903231216m121d4beby45c85dea76f2a13e@mail.gmail.com>

Hi, David,

I forgot to generate rspec after the upgrade.  That fixed the problem.
Thanks for your help.

Thanks,
Chuck

On Mon, Mar 23, 2009 at 2:41 PM, David Chelimsky <dchelimsky at gmail.com>wrote:

> 2009/3/23 Charles Grindel <chuck at chuckgrindel.com>:
> > Hi,
> >
> > I am following the directions for setting up autotest
> > (
> http://wiki.github.com/dchelimsky/rspec/spec_server-autospec-nearly-pure-bdd-joy
> )
> > and experienced an error when I run rake spec:server:start.
> >
> > $ rake spec:server:start
> > (in /home/cgrindel/code/it/webapp)
> > Starting up spec_server ...
> >
> /home/cgrindel/code/it/webapp/vendor/plugins/rspec-rails/lib/spec/rails/spec_server.rb:1:
> > uninitialized constant Rails (NameError)
> >     from script/spec_server:21:in `require'
> >     from script/spec_server:21
> >
> > I took a quick look at the code in script/spec_server.rb.  In short, it
> > appears that the script requires 'spec/rails/spec_server' before the
> Rails
> > environment is loaded which happens on line 26.  I moved the require of
> > 'spec/rails/spec_server' after the Rails environment load.  This appears
> to
> > have fixed this issue.
> >
> > So, my first question, has anyone else seen this problem?  If not, can
> > anyone explain how the Rails constant should be available before the
> Rails
> > environment is loaded?
>
> Did you run "script/generate rspec" when you upgraded the plugin? If
> not, please do so now, and let it rewrite everything in script/ and
> lib/tasks/rspec.rake.
>
> >
> > Thanks,
> > Chuck
> >
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090323/1c5f6d77/attachment.html>

From dchelimsky at gmail.com  Mon Mar 23 15:34:01 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 23 Mar 2009 14:34:01 -0500
Subject: [rspec-users] Spec Server Error on rake spec:server:start
In-Reply-To: <c7d77dde0903231216m121d4beby45c85dea76f2a13e@mail.gmail.com>
References: <c7d77dde0903231123q2ba6b886v1cd3368943a68bb0@mail.gmail.com>
	<57c63afe0903231141v39484cefl6f89cba655e68bde@mail.gmail.com>
	<c7d77dde0903231216m121d4beby45c85dea76f2a13e@mail.gmail.com>
Message-ID: <57c63afe0903231234o15b0f577we44b3177f9f2cb7@mail.gmail.com>

2009/3/23 Charles Grindel <chuck at chuckgrindel.com>:
> Hi, David,
>
> I forgot to generate rspec after the upgrade.? That fixed the problem.
> Thanks for your help.

Glad you got it working.

Cheers,
David

>
> Thanks,
> Chuck
>
> On Mon, Mar 23, 2009 at 2:41 PM, David Chelimsky <dchelimsky at gmail.com>
> wrote:
>>
>> 2009/3/23 Charles Grindel <chuck at chuckgrindel.com>:
>> > Hi,
>> >
>> > I am following the directions for setting up autotest
>> >
>> > (http://wiki.github.com/dchelimsky/rspec/spec_server-autospec-nearly-pure-bdd-joy)
>> > and experienced an error when I run rake spec:server:start.
>> >
>> > $ rake spec:server:start
>> > (in /home/cgrindel/code/it/webapp)
>> > Starting up spec_server ...
>> >
>> > /home/cgrindel/code/it/webapp/vendor/plugins/rspec-rails/lib/spec/rails/spec_server.rb:1:
>> > uninitialized constant Rails (NameError)
>> > ??? from script/spec_server:21:in `require'
>> > ??? from script/spec_server:21
>> >
>> > I took a quick look at the code in script/spec_server.rb.? In short, it
>> > appears that the script requires 'spec/rails/spec_server' before the
>> > Rails
>> > environment is loaded which happens on line 26.? I moved the require of
>> > 'spec/rails/spec_server' after the Rails environment load.? This appears
>> > to
>> > have fixed this issue.
>> >
>> > So, my first question, has anyone else seen this problem?? If not, can
>> > anyone explain how the Rails constant should be available before the
>> > Rails
>> > environment is loaded?
>>
>> Did you run "script/generate rspec" when you upgraded the plugin? If
>> not, please do so now, and let it rewrite everything in script/ and
>> lib/tasks/rspec.rake.
>>
>> >
>> > Thanks,
>> > Chuck
>> >
>> > _______________________________________________
>> > rspec-users mailing list
>> > rspec-users at rubyforge.org
>> > http://rubyforge.org/mailman/listinfo/rspec-users
>> >
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From balint.erdi at gmail.com  Mon Mar 23 13:14:58 2009
From: balint.erdi at gmail.com (Balint Erdi)
Date: Mon, 23 Mar 2009 10:14:58 -0700 (PDT)
Subject: [rspec-users] [cucumber] webrat+selenium integration problem:
	record not saved to database?
Message-ID: <f2f9e79b-ecee-40b7-8df1-d202036eea71@j39g2000yqn.googlegroups.com>

Hey,

I am writing a simple cucumber feature for a Rails app to test if the
webrat+selenium integration was successful:

 Scenario: Successful log in
    Given the user "pepito" exists # (1)
    And the user "pepito" is active
    When I go to the login page
    And I fill in "login" with "pepito"
    And I fill in "password" with "secret"
    And I press "submit" # (2)
    Then I should see a confirmation message

Now I think I managed to set up the architecture all right (using sep.
setup files for plain and javascript -selenium- features as described
here: http://wiki.github.com/aslakhellesoy/cucumber/setting-up-selenium).
The problem is that the "Then I should see a confirmation message"
fails.

I put a breakpoint at (2) to investigate the problem. I've found that:

1. the user is succesfully created (User.first in a rails console
gives back pepito)
2. I can log in successfully from the console (User.authenticate
("pepito", "secret") gives back the user meaning successful
authentication.
3. The login and password fields are correctly filled with the values
(checking that in the launched FF browser)
4. If I manually submit the form at the breakpoint, it also fails to
log in, so it's not that the "And I press "submit" step does something
other than submitting the form.
5. the users table in the database that selenium uses is empty.
(mysql> select * from users;
Empty set (0.00 sec) ). That surprises me a bit since in theory
selenium does not use transactional fixtures so the record should
appear right away after (1) runs.

Here are my cucumber config file(s):
http://gist.github.com/83635

I run the feature like this:

cucumber -r features/support/env.rb -r features/support/enhanced.rb -r
features/step_definitions features/enhanced/login.feature

And these are the setup steps to create and activate the user:

Given /^the user "(.*)" exists$/ do |login_name|
  User.find_by_login(login_name) || Factory
(:user_with_password, :login => login_name)
end

Given /^the user "(.*)" is active$/ do |login_name|
  User.find_by_login(login_name).activate!
end

I also see in the log that the form is submitted with the correct
parameters.

Please let me know if you see what I am missing or what I should do
differently.

Thank you,
Balint

From bornboulder77 at gmail.com  Mon Mar 23 19:10:13 2009
From: bornboulder77 at gmail.com (Bjorn Boulder)
Date: Mon, 23 Mar 2009 16:10:13 -0700
Subject: [rspec-users] Spec::Rails,
	"model.should have(1).error_on(:attribute)" passes when?
Message-ID: <a6591d550903231610h2e3309feodc5b6c2e05974f93@mail.gmail.com>

Spec::Rails people,

I'm curious about:
  - model.should have(1).error_on(:attribute)

displayed in the URL below:
  http://rspec.rubyforge.org/rspec-rails/1.2.2/classes/Spec/Rails/Extensions/ActiveRecord/InstanceMethods.html

The Rspec peepcode screencast suggests that
model.should have(1).error_on(:attribute)
should pass if
model.send(:attribute)
returns nil

For me, I get an exception from the rspec script.

My work-around is simple.

Instead of:
  - model.should have(1).error_on(:attribute)
I Use:
  -model.send(:attribute).should be_nil

But now I have the question:
  - What kind of error causes:
    - model.should have(1).error_on(:attribute)
    - to pass ??

--b

From dchelimsky at gmail.com  Mon Mar 23 19:18:26 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 23 Mar 2009 18:18:26 -0500
Subject: [rspec-users] Spec::Rails,
	"model.should have(1).error_on(:attribute)" 	passes when?
In-Reply-To: <a6591d550903231610h2e3309feodc5b6c2e05974f93@mail.gmail.com>
References: <a6591d550903231610h2e3309feodc5b6c2e05974f93@mail.gmail.com>
Message-ID: <57c63afe0903231618o57b3d47au72d42989fc42f372@mail.gmail.com>

On Mon, Mar 23, 2009 at 6:10 PM, Bjorn Boulder <bornboulder77 at gmail.com> wrote:
> Spec::Rails people,
>
> I'm curious about:
> ?- model.should have(1).error_on(:attribute)
>
> displayed in the URL below:
> ?http://rspec.rubyforge.org/rspec-rails/1.2.2/classes/Spec/Rails/Extensions/ActiveRecord/InstanceMethods.html
>
> The Rspec peepcode screencast suggests that
> model.should have(1).error_on(:attribute)
> should pass if
> model.send(:attribute)
> returns nil
>
> For me, I get an exception from the rspec script.
>
> My work-around is simple.
>
> Instead of:
> ?- model.should have(1).error_on(:attribute)
> I Use:
> ?-model.send(:attribute).should be_nil
>
> But now I have the question:
> ?- What kind of error causes:
> ? ?- model.should have(1).error_on(:attribute)
> ? ?- to pass ??

If you add this to your model:

  validates_presence_of :attribute

Then this will pass

  Model.new(:attribute => nil).should have(1).error_on(:attribute)

Cheers,
David

>
> --b
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From andrew at avit.ca  Mon Mar 23 17:22:10 2009
From: andrew at avit.ca (Andrew Vit)
Date: Mon, 23 Mar 2009 14:22:10 -0700 (PDT)
Subject: [rspec-users] Problems with gem rdoc rspec
Message-ID: <050a3b70-bb67-42ca-87d4-57de54c7e06e@w35g2000prg.googlegroups.com>

My gems, e.g. rspec, gets installed in:
/Library/Ruby/Gems/1.8/gems/rspec-1.2.2

(Note the extra /gems/ subdirectory)

When I run "gem rdoc rspec" the output is empty and the Files section
has errors:

file not found -/Library/Ruby/Gems/1.8/rspec-1.2.2/rdoc/License.txt-
file not found -/Library/Ruby/Gems/1.8/rspec-1.2.2/rdoc/Manifest.txt-
file not found -/Library/Ruby/Gems/1.8/rspec-1.2.2/rdoc/examples/
failing/README.txt-
file not found -/Library/Ruby/Gems/1.8/rspec-1.2.2/rdoc/TODO.txt-

(Those are the only files in there. Note the lack of /gems/
subdirectory)

Do I need to add /gems/ to my GEM_PATH? I didn't think that's how it
works, and my other rubygems build their rdocs fine.

Or do I need to set a different path variable to set this up?
(GEM_HOME? I tried that and it didn't seem to help.)

Thanks for your help,
Andrew Vit


My environment:

$ echo $GEM_PATH
/Library/Ruby/Gems/1.8

$ more ~/.gemrc
---
verbose: true
update_sources: true
sources:
  - http://gems.rubyforge.org/
  - http://gems.github.com/
backtrace: false
bulk_threshold: 1000
benchmark: false
gem: --rdoc
rdoc:  --fmt ajax --charset utf8 --exclude .*generator.* --
exclude .*test.* --exclude .*spec.*

From ben at benmabey.com  Mon Mar 23 21:00:47 2009
From: ben at benmabey.com (Ben Mabey)
Date: Mon, 23 Mar 2009 19:00:47 -0600
Subject: [rspec-users] [cucumber] webrat+selenium integration problem:
 record not saved to database?
In-Reply-To: <f2f9e79b-ecee-40b7-8df1-d202036eea71@j39g2000yqn.googlegroups.com>
References: <f2f9e79b-ecee-40b7-8df1-d202036eea71@j39g2000yqn.googlegroups.com>
Message-ID: <49C830BF.1040401@benmabey.com>

Balint Erdi wrote:
> Hey,
>
> I am writing a simple cucumber feature for a Rails app to test if the
> webrat+selenium integration was successful:
>
>  Scenario: Successful log in
>     Given the user "pepito" exists # (1)
>     And the user "pepito" is active
>     When I go to the login page
>     And I fill in "login" with "pepito"
>     And I fill in "password" with "secret"
>     And I press "submit" # (2)
>     Then I should see a confirmation message
>
> Now I think I managed to set up the architecture all right (using sep.
> setup files for plain and javascript -selenium- features as described
> here: http://wiki.github.com/aslakhellesoy/cucumber/setting-up-selenium).
> The problem is that the "Then I should see a confirmation message"
> fails.
>
> I put a breakpoint at (2) to investigate the problem. I've found that:
>
> 1. the user is succesfully created (User.first in a rails console
> gives back pepito)
> 2. I can log in successfully from the console (User.authenticate
> ("pepito", "secret") gives back the user meaning successful
> authentication.
> 3. The login and password fields are correctly filled with the values
> (checking that in the launched FF browser)
> 4. If I manually submit the form at the breakpoint, it also fails to
> log in, so it's not that the "And I press "submit" step does something
> other than submitting the form.
> 5. the users table in the database that selenium uses is empty.
> (mysql> select * from users;
> Empty set (0.00 sec) ). That surprises me a bit since in theory
> selenium does not use transactional fixtures so the record should
> appear right away after (1) runs.
>   

Webrat's Selenium adapter will not change your DB settings.  On line 10 
on your env.rb file you actually have transactional support turned on.  
You need to comment that line out when using Selenium.  For more info 
please read about this problem on the wiki:

http://wiki.github.com/aslakhellesoy/cucumber/troubleshooting

HTH,
Ben

From longhiandrea at gmail.com  Tue Mar 24 08:50:30 2009
From: longhiandrea at gmail.com (andrea)
Date: Tue, 24 Mar 2009 05:50:30 -0700 (PDT)
Subject: [rspec-users] Rspec weird behaviour
In-Reply-To: <57c63afe0903230510u38839be9ied74427b69ac46e1@mail.gmail.com>
References: <e9dda862-b9a1-4a87-85fa-1c4b9f5075cc@y9g2000yqg.googlegroups.com>
	<57c63afe0903230510u38839be9ied74427b69ac46e1@mail.gmail.com>
Message-ID: <ed6265ca-21f8-4141-a958-829d40ad5114@w35g2000yqm.googlegroups.com>

On 23 Mar, 13:10, David Chelimsky <dchelim... at gmail.com> wrote:

> If this persists, please submit a bug report tohttp://rspec.lighthouseapp.comand include a zipped up app that I can
> run to see the problem.

Thanks Dave, now everything works as expected, but I still don't know
what was the problem.
First I duplicated the app, tested it and got the same bad results as
the original one. Then I started to remove stuff from the duplicated
app until I got the Size model specs pass. This happened when I
removed the Size controller specs file. Weird.
I went back to the original app, cut the code from the Size controller
specs file and run the specs.. this time everything passed. I pasted
back the content to the Size controller file, saved and again all
specs run as they should... I feel really confused :-)

Regards
Andrea

From stefan at soocial.com  Tue Mar 24 11:27:07 2009
From: stefan at soocial.com (Stefan Fountain)
Date: Tue, 24 Mar 2009 16:27:07 +0100
Subject: [rspec-users] Where do I find help about user roles?
Message-ID: <D2850286-C0C4-4923-9CAA-508AEB25662C@soocial.com>

I'm trying to create a scenario with a 'given I am logged in'. I'm  
struggling to find good documentation about this, the rspec/cucumber  
book doesn't have this chapter written yet.

Could you point me in the right direction? Currently I'm starting to  
use Factory_girl gem to do it but not sure if that is the correct way  
or how cucumber is designed to handle these kinds of 'given's.

Thanks in advance.




From mr.gaffo at gmail.com  Tue Mar 24 11:18:31 2009
From: mr.gaffo at gmail.com (Mike Gaffney)
Date: Tue, 24 Mar 2009 10:18:31 -0500
Subject: [rspec-users] [cucumber] webrat+selenium integration problem:
 record not saved to database?
In-Reply-To: <49C830BF.1040401@benmabey.com>
References: <f2f9e79b-ecee-40b7-8df1-d202036eea71@j39g2000yqn.googlegroups.com>
	<49C830BF.1040401@benmabey.com>
Message-ID: <49C8F9C7.2000409@gmail.com>

If you actually want to use transactional fixtures with selenium, try out
http://github.com/gaffo/mainline

Something I coded up that allows selenium to work with transactional 
fixtures.

Ben Mabey wrote:
> Balint Erdi wrote:
>> Hey,
>>
>> I am writing a simple cucumber feature for a Rails app to test if the
>> webrat+selenium integration was successful:
>>
>>  Scenario: Successful log in
>>     Given the user "pepito" exists # (1)
>>     And the user "pepito" is active
>>     When I go to the login page
>>     And I fill in "login" with "pepito"
>>     And I fill in "password" with "secret"
>>     And I press "submit" # (2)
>>     Then I should see a confirmation message
>>
>> Now I think I managed to set up the architecture all right (using sep.
>> setup files for plain and javascript -selenium- features as described
>> here: 
>> http://wiki.github.com/aslakhellesoy/cucumber/setting-up-selenium).
>> The problem is that the "Then I should see a confirmation message"
>> fails.
>>
>> I put a breakpoint at (2) to investigate the problem. I've found that:
>>
>> 1. the user is succesfully created (User.first in a rails console
>> gives back pepito)
>> 2. I can log in successfully from the console (User.authenticate
>> ("pepito", "secret") gives back the user meaning successful
>> authentication.
>> 3. The login and password fields are correctly filled with the values
>> (checking that in the launched FF browser)
>> 4. If I manually submit the form at the breakpoint, it also fails to
>> log in, so it's not that the "And I press "submit" step does something
>> other than submitting the form.
>> 5. the users table in the database that selenium uses is empty.
>> (mysql> select * from users;
>> Empty set (0.00 sec) ). That surprises me a bit since in theory
>> selenium does not use transactional fixtures so the record should
>> appear right away after (1) runs.
>>   
>
> Webrat's Selenium adapter will not change your DB settings.  On line 
> 10 on your env.rb file you actually have transactional support turned 
> on.  You need to comment that line out when using Selenium.  For more 
> info please read about this problem on the wiki:
>
> http://wiki.github.com/aslakhellesoy/cucumber/troubleshooting
>
> HTH,
> Ben
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

From Peer.Allan at canadadrugs.com  Tue Mar 24 14:02:31 2009
From: Peer.Allan at canadadrugs.com (Peer Allan)
Date: Tue, 24 Mar 2009 13:02:31 -0500
Subject: [rspec-users] (x)HTML Parsing Errors, Cuc 0.2.0 + Rspec 1.2
Message-ID: <C5EE8A67.1EF0B%Peer.Allan@canadadrugs.com>

Hello all,

I have some cucumber features that are making me scratch my head.  After
updating the Rspec 1.2 my features are now generating thousands of "ignoring
attempt to close tag with other tag" when I run them. The W3C validator
tells me that the XHTML is valid.  The good news is that the tests still
pass, but you the nice output is gone.

I experimented with some different combinations of gems to figure it out but
it all came down to Rspec 1.2.x.  If I remove it then the errors go away.
This happens under both Rails 2.2.2 and Rails 2.3.2

Has anyone else run into this?

Peer 


From lists at ruby-forum.com  Tue Mar 24 14:27:16 2009
From: lists at ruby-forum.com (James Byrne)
Date: Tue, 24 Mar 2009 19:27:16 +0100
Subject: [rspec-users] Where do I find help about user roles?
In-Reply-To: <D2850286-C0C4-4923-9CAA-508AEB25662C@soocial.com>
References: <D2850286-C0C4-4923-9CAA-508AEB25662C@soocial.com>
Message-ID: <eff6f41bf49c1416ec7a6b3a3797d34d@ruby-forum.com>

Stefan Fountain wrote:
> I'm trying to create a scenario with a 'given I am logged in'. I'm
> struggling to find good documentation about this, the rspec/cucumber
> book doesn't have this chapter written yet.
> 
> Could you point me in the right direction? Currently I'm starting to
> use Factory_girl gem to do it but not sure if that is the correct way
> or how cucumber is designed to handle these kinds of 'given's.
> 
> Thanks in advance.

Authentication is a very large topic.  There are a number of 
authentication plugins and gems available (logins).  I happen to use the 
AuthLogic gem at the moment.  There is a fairly good tutorial on 
Authlogic at 
http://www.binarylogic.com/2008/11/3/tutorial-authlogic-basic-setup.

Authorisation (Roles) is a separate matter altogether.  I have a minimal 
authorisation function that simply checks a flag attribute on the user 
model.  This suffices for testing but needs be replaced in production.

Note as well that at the moment I do not use mocks for this stuff.

One of my sample scenarios looks like this:

  Scenario: Add a new client
    Given I do have a user named "authuser"
      And the user named "authuser" authenticates
      And the user named "authuser" is authorized to "add" "clients"
 ...

The user steps look like this:

(note: some do not approve of instance @ variables in tests)

When /have an? user named "(.*)"/ do |name|
  Then "add an user named \"#{name}\""
end

When /(?:add|create) an?(?:new)? user named "(.*)"/ do |name|
  User.find_by_username(name).destroy
  Then "initialise a new user named \"#{name}\""
  Then "should save the new user"
end

When /initialise a new user named "(.*)"/ do |name|
  @my_new_user = nil
  my_user = User.new
  my_user.username = "#{name}"
  my_user.password = "#{name}-password"
  my_user.password_confirmation = "#{name}-password"
...
  @my_new_user = my_user
end

When /should save the new user/ do
  @my_new_user.save!
end

...

The authentication step looks like this:

When /user named "(.*)" authenticates/ do |name|
  visit new_user_session_path
  Then "see an authentication request message"
  Then "enter the username \"#{name}\""
  Then "enter the password \"#{name}-password\""
  Then "press the authenticate button"
  Then "see an authentication success message"
  visit root_path
  have_no_selector("#authentication_request")
end


And so on.  No doubt there are better ways to do it but this works for 
me.

HTH
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Tue Mar 24 14:37:31 2009
From: lists at ruby-forum.com (James Byrne)
Date: Tue, 24 Mar 2009 19:37:31 +0100
Subject: [rspec-users] Where do I find help about user roles?
In-Reply-To: <eff6f41bf49c1416ec7a6b3a3797d34d@ruby-forum.com>
References: <D2850286-C0C4-4923-9CAA-508AEB25662C@soocial.com>
	<eff6f41bf49c1416ec7a6b3a3797d34d@ruby-forum.com>
Message-ID: <770e5f68cd33361d333d68eeb1883d77@ruby-forum.com>

James Byrne wrote:

> When /(?:add|create) an?(?:new)? user named "(.*)"/ do |name|
>   User.find_by_username(name).destroy

s/b
  User.find_by_username(name).destroy if User.find_by_username(name)

Sorry about that.
-- 
Posted via http://www.ruby-forum.com/.

From apremdas at gmail.com  Tue Mar 24 14:50:11 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Tue, 24 Mar 2009 18:50:11 +0000
Subject: [rspec-users] Where do I find help about user roles?
In-Reply-To: <D2850286-C0C4-4923-9CAA-508AEB25662C@soocial.com>
References: <D2850286-C0C4-4923-9CAA-508AEB25662C@soocial.com>
Message-ID: <88fd8ddc0903241150l7b17047nd9049fe1d2c416d3@mail.gmail.com>

Have a look at fbrp http://github.com/diabolo/fbrp/tree/master , it has a
feature based rewrite of RestfulAuthentications tests, using Object_Daddy
and Cucumber. Lots of logging in without using features

HTH

Andrew

2009/3/24 Stefan Fountain <stefan at soocial.com>

> I'm trying to create a scenario with a 'given I am logged in'. I'm
> struggling to find good documentation about this, the rspec/cucumber book
> doesn't have this chapter written yet.
>
> Could you point me in the right direction? Currently I'm starting to use
> Factory_girl gem to do it but not sure if that is the correct way or how
> cucumber is designed to handle these kinds of 'given's.
>
> Thanks in advance.
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090324/f09c9e9e/attachment-0001.html>

From lists at ruby-forum.com  Tue Mar 24 17:48:52 2009
From: lists at ruby-forum.com (Balint Erdi)
Date: Tue, 24 Mar 2009 22:48:52 +0100
Subject: [rspec-users] [cucumber] webrat+selenium integration problem:
	record n
In-Reply-To: <49C830BF.1040401@benmabey.com>
References: <f2f9e79b-ecee-40b7-8df1-d202036eea71@j39g2000yqn.googlegroups.com>
	<49C830BF.1040401@benmabey.com>
Message-ID: <e7aee908ce1ecf1a5515395d87cc12fc@ruby-forum.com>

@Ben: Thank you, I fixed that and am using your database_cleaner to 
truncate the database.

Turns out the problem (or rather, another problem) was that I set up a 
separate environment (selenium) for the selenium tests but still some of 
the steps used the test environment and thus the database record was 
generated in the test database not in the selenium one where it should 
have been.

I struggled to get the record creation happen in the selenium database 
but finally I gave up and am now using the test for both selenium and 
"plain" cucumber features. So the database_cleaner serves me even 
better. It works! My current config is here: 
http://gist.github.com/83635. Once again, thank you for your help.

@Mike: I may check that out, thank you!

Balint

Ben Mabey wrote:
> Balint Erdi wrote:
>>     And I fill in "password" with "secret"
>>
>> 5. the users table in the database that selenium uses is empty.
>> (mysql> select * from users;
>> Empty set (0.00 sec) ). That surprises me a bit since in theory
>> selenium does not use transactional fixtures so the record should
>> appear right away after (1) runs.
>>   
> 
> Webrat's Selenium adapter will not change your DB settings.  On line 10
> on your env.rb file you actually have transactional support turned on.
> You need to comment that line out when using Selenium.  For more info
> please read about this problem on the wiki:
> 
> http://wiki.github.com/aslakhellesoy/cucumber/troubleshooting
> 
> HTH,
> Ben

-- 
Posted via http://www.ruby-forum.com/.

From likonar at gmail.com  Tue Mar 24 16:21:48 2009
From: likonar at gmail.com (max@gorbul.net)
Date: Tue, 24 Mar 2009 13:21:48 -0700 (PDT)
Subject: [rspec-users] stricter routing specs with conditional routes
Message-ID: <98f0d405-8840-4228-98b9-081f1acf5653@o36g2000yqh.googlegroups.com>

Hello,

could you please advise me how to test conditional routes with rspec
v1.2.0 ?
I have something like the following in my application.
------------
map.with_options(:namespace => "admin/",
                  :conditions => { :subdomain => /^admin$/i },
                  :name_prefix => "admin_") do |admin|
   admin.resources(:users)
   admin.resources(:messages)
end
------------
Before 1.2.0 all specs run without failures. After I upgraded to rails
2.3 with rspec 1.2.0 I got a ton of failed spec related to mismatched
routes:

route_for(:controller => "admin/users", :id=>"1", :action =>
"create").
   should == {:path => "/admin/users/1", :method => :post}

this spec is failed because :subdomain => nil

How to deal with such issue?

Thank you,
Max

From ben at benmabey.com  Tue Mar 24 18:55:47 2009
From: ben at benmabey.com (Ben Mabey)
Date: Tue, 24 Mar 2009 16:55:47 -0600
Subject: [rspec-users] [cucumber] webrat+selenium integration problem:
 record n
In-Reply-To: <e7aee908ce1ecf1a5515395d87cc12fc@ruby-forum.com>
References: <f2f9e79b-ecee-40b7-8df1-d202036eea71@j39g2000yqn.googlegroups.com>	<49C830BF.1040401@benmabey.com>
	<e7aee908ce1ecf1a5515395d87cc12fc@ruby-forum.com>
Message-ID: <49C964F3.9000600@benmabey.com>

Balint Erdi wrote:
> @Ben: Thank you, I fixed that and am using your database_cleaner to 
> truncate the database.
>
> Turns out the problem (or rather, another problem) was that I set up a 
> separate environment (selenium) for the selenium tests but still some of 
> the steps used the test environment and thus the database record was 
> generated in the test database not in the selenium one where it should 
> have been.
>
> I struggled to get the record creation happen in the selenium database 
> but finally I gave up and am now using the test for both selenium and 
> "plain" cucumber features. So the database_cleaner serves me even 
> better. It works! My current config is here: 
> http://gist.github.com/83635. Once again, thank you for your help.
>   

Couple things I'd like to point out.  In your enhanced.rb you don't need 
to do the Before hook yourself.  You can just require 
'database_cleaner/cucumber'.  I've updated your gist to use that. 
In your plain.rb it seems like you are trying to truncate your database 
just once upon startup.  If that is the case then the recommended way is 
to use the clean_with method like so:
DatabaseCleaner.clean_with :truncation

Again, I have updated the gist to reflect this.

-Ben
> @Mike: I may check that out, thank you!
>
> Balint
>
> Ben Mabey wrote:
>   
>> Balint Erdi wrote:
>>     
>>>     And I fill in "password" with "secret"
>>>
>>> 5. the users table in the database that selenium uses is empty.
>>> (mysql> select * from users;
>>> Empty set (0.00 sec) ). That surprises me a bit since in theory
>>> selenium does not use transactional fixtures so the record should
>>> appear right away after (1) runs.
>>>   
>>>       
>> Webrat's Selenium adapter will not change your DB settings.  On line 10
>> on your env.rb file you actually have transactional support turned on.
>> You need to comment that line out when using Selenium.  For more info
>> please read about this problem on the wiki:
>>
>> http://wiki.github.com/aslakhellesoy/cucumber/troubleshooting
>>
>> HTH,
>> Ben
>>     
>
>   


From anja-email1 at web.de  Wed Mar 25 10:32:50 2009
From: anja-email1 at web.de (Andrea Jahn)
Date: Wed, 25 Mar 2009 15:32:50 +0100
Subject: [rspec-users] spec for view with Searchlogic
Message-ID: <1316278356@web.de>



 

Hi,

I'm using the Searchlogic plugin. Since I have added the search form in the index template,
the view spec doesn't work anymore.

Controller
---------
 def index
 @search = PlPlanning.new_search(params[:search])
 @search.order_by = :id
 @pl_plannings, @count = @search.all, @search.count
 end


view
-----

<!-- search form -->
<div id='search_form_area' class="search_form" style="display:none" >
 <% remote_form_for [:planning, @search] do |f| %>
 <fieldset>
 <legend>Search <%= PlPlanning::DISPLAY_NAME.pluralize %></legend>
 <% f.fields_for @search.conditions do |pl_plannings| %> 
 <%= pl_plannings.label :id, PlPlanning::DISPLAY_NAME + " Id:", :class => "search_label" %>
 <%= pl_plannings.text_field :id %>
 <br />
 <%= f.submit "Search" %>
 <% end %>
 </fieldset> 
 <% end %>
</div>


spec
----

class Searchlogic::Cache::PlPlanningSearch; end
 ...


 before(:each) do
 @pl_plannings = []
 assigns[:pl_plannings] = @pl_plannings
 

 @search = Searchlogic::Cache::PlPlanningSearch.new ???
 assigns[:search] = @search

 render "/planning/pl_plannings/index"
 end

...


 => Error in the line containing the remote_form_for call
 undefined method `planning_searchlogic_cache_pl_planning_search_path' for #<ActionView::Base:0x6b6bf38>


Has anybody experience with Searchlogic + rspec ? Can I stub search_paths ?

Thanks
Andrea

 

 


	
Verschicken Sie SMS direkt vom Postfach aus - in alle deutschen und viele 
ausl?ndische Netze zum gleichen Preis! 
https://produkte.web.de/webde_sms/sms 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090325/91e374a6/attachment.html>

From aslak.hellesoy at gmail.com  Wed Mar 25 11:08:25 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Wed, 25 Mar 2009 16:08:25 +0100
Subject: [rspec-users] [Cucumber] ANN: Cucumber with pure Java
Message-ID: <8d961d900903250808p46a2ca82ke23e8c8975dd6ff3@mail.gmail.com>

Big news for all Java programmers out there.
Now you can use Cucumber with pure Java!

That's right, you don't have to write a single line of Ruby! (1)
All of your step definitions can be written as annotated methods in POJOs
(Plain Old Java Objects).

To get a taste of what this looks like, check out the simple example in the
cucumber_java project on GitHub:

* README for example:
http://github.com/aslakhellesoy/cucumber_java/tree/271160300da5bc9275dd67624f711c5ea6913187/examples/simple
* Some sample step defs:
http://github.com/aslakhellesoy/cucumber_java/blob/271160300da5bc9275dd67624f711c5ea6913187/examples/simple/src/main/java/simple/StuffSteps.java
* The main page: http://github.com/aslakhellesoy/cucumber_java/tree/master

By this I hope Cucumber will reach a bigger crowd. Much bigger crowd
actually :-) - this will work for Scala, Clojure, Jython and all the other
cool JVM languages too.
(I'll be doing something similar for .NET, which will bring Cucumber
goodness to C#, F# and whatever languages run on .NET. But IronRuby must
catch up on speed first).

I had the pleasure of going back to visit PicoContainer - a pioneering
lightweight dependency injection container I developed with Paul Hammant
back in 2003. It's still lightweight and a joy to use (relatively speaking -
Java in itself isn't joyful). Cucumber-java uses PicoContainer to
instantiate the POJOs that define the annotated step definition methods, so
if you're so inclined, these classes can depend on each other via
constructor DI, and PicoContainer just figures out how to instantiate the
objects).

So if you're working on a Java project, have been looking at Cucumber but
stayed away because of all the weird Ruby, this is your chance. Here is a
cuke for Duke!

(::) Aslak (::)

(1) You still need a tiny bit of Ruby to register step definitions:
http://github.com/aslakhellesoy/cucumber_java/blob/271160300da5bc9275dd67624f711c5ea6913187/examples/simple/features/support/env.rb
(This will hopefully go away in the future, with some better Ant and Maven
support).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090325/6bc22a11/attachment.html>

From ben at benmabey.com  Wed Mar 25 13:18:31 2009
From: ben at benmabey.com (Ben Mabey)
Date: Wed, 25 Mar 2009 11:18:31 -0600
Subject: [rspec-users] [Cucumber] ANN: Cucumber with pure Java
In-Reply-To: <8d961d900903250808p46a2ca82ke23e8c8975dd6ff3@mail.gmail.com>
References: <8d961d900903250808p46a2ca82ke23e8c8975dd6ff3@mail.gmail.com>
Message-ID: <3133DE2A-6697-4679-8BED-08B30C6B25F5@benmabey.com>


On Mar 25, 2009, at 9:08 AM, aslak hellesoy wrote:

> Big news for all Java programmers out there.
> Now you can use Cucumber with pure Java!
>
> That's right, you don't have to write a single line of Ruby! (1)
> All of your step definitions can be written as annotated methods in  
> POJOs (Plain Old Java Objects).
>
> To get a taste of what this looks like, check out the simple example  
> in the cucumber_java project on GitHub:
>
> * README for example: http://github.com/aslakhellesoy/cucumber_java/tree/271160300da5bc9275dd67624f711c5ea6913187/examples/simple
> * Some sample step defs: http://github.com/aslakhellesoy/cucumber_java/blob/271160300da5bc9275dd67624f711c5ea6913187/examples/simple/src/main/java/simple/StuffSteps.java
> * The main page: http://github.com/aslakhellesoy/cucumber_java/tree/master
>
> By this I hope Cucumber will reach a bigger crowd. Much bigger crowd  
> actually :-) - this will work for Scala, Clojure, Jython and all the  
> other cool JVM languages too.
> (I'll be doing something similar for .NET, which will bring Cucumber  
> goodness to C#, F# and whatever languages run on .NET. But IronRuby  
> must catch up on speed first).
>
> I had the pleasure of going back to visit PicoContainer - a  
> pioneering lightweight dependency injection container I developed  
> with Paul Hammant back in 2003. It's still lightweight and a joy to  
> use (relatively speaking - Java in itself isn't joyful). Cucumber- 
> java uses PicoContainer to instantiate the POJOs that define the  
> annotated step definition methods, so if you're so inclined, these  
> classes can depend on each other via constructor DI, and  
> PicoContainer just figures out how to instantiate the objects).
>
> So if you're working on a Java project, have been looking at  
> Cucumber but stayed away because of all the weird Ruby, this is your  
> chance. Here is a cuke for Duke!
>
> (::) Aslak (::)
>
> (1) You still need a tiny bit of Ruby to register step definitions: http://github.com/aslakhellesoy/cucumber_java/blob/271160300da5bc9275dd67624f711c5ea6913187/examples/simple/features/support/env.rb
> (This will hopefully go away in the future, with some better Ant and  
> Maven support).


Very cool stuff.  It would be an interesting and informative exercise  
to take a JBehave tutorial and use Cucumber to drive out the same  
feature and then have a side-by-side comparison of the required step  
definitions.  I found this JBehave tutorial which would make a good  
candidate for such a comparison:
http://www.ryangreenhall.com/articles/bdd-by-example.html

If someone doesn't get around to this in the next couple of weeks I  
may take a stab at it and make a blog post of it.

-Ben

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090325/212802a7/attachment-0001.html>

From lists at ruby-forum.com  Wed Mar 25 14:37:00 2009
From: lists at ruby-forum.com (Phor Gruber)
Date: Wed, 25 Mar 2009 19:37:00 +0100
Subject: [rspec-users] Spec::Rails,
	"model.should have(1).error_on(:attribute)"
In-Reply-To: <57c63afe0903231618o57b3d47au72d42989fc42f372@mail.gmail.com>
References: <a6591d550903231610h2e3309feodc5b6c2e05974f93@mail.gmail.com>
	<57c63afe0903231618o57b3d47au72d42989fc42f372@mail.gmail.com>
Message-ID: <a9f640d4615a666f4709fb87ce20087c@ruby-forum.com>

I added:
  - validates_presence_of :attribute

To my model.

The test now passes.

yay!!

Thanks David.

-- 
Posted via http://www.ruby-forum.com/.

From aslak.hellesoy at gmail.com  Wed Mar 25 14:49:29 2009
From: aslak.hellesoy at gmail.com (=?utf-8?Q?Aslak_Helles=C3=B8y?=)
Date: Wed, 25 Mar 2009 19:49:29 +0100
Subject: [rspec-users] [Cucumber] ANN: Cucumber with pure Java
In-Reply-To: <3133DE2A-6697-4679-8BED-08B30C6B25F5@benmabey.com>
References: <8d961d900903250808p46a2ca82ke23e8c8975dd6ff3@mail.gmail.com>
	<3133DE2A-6697-4679-8BED-08B30C6B25F5@benmabey.com>
Message-ID: <DC41CE17-2333-415A-A0C5-9795ED8769F7@gmail.com>



Den 25. mars. 2009 kl. 18.18 skrev Ben Mabey <ben at benmabey.com>:

>
> On Mar 25, 2009, at 9:08 AM, aslak hellesoy wrote:
>
>> Big news for all Java programmers out there.
>> Now you can use Cucumber with pure Java!
>>
>> That's right, you don't have to write a single line of Ruby! (1)
>> All of your step definitions can be written as annotated methods in  
>> POJOs (Plain Old Java Objects).
>>
>> To get a taste of what this looks like, check out the simple  
>> example in the cucumber_java project on GitHub:
>>
>> * README for example: http://github.com/aslakhellesoy/cucumber_java/tree/271160300da5bc9275dd67624f711c5ea6913187/examples/simple
>> * Some sample step defs: http://github.com/aslakhellesoy/cucumber_java/blob/271160300da5bc9275dd67624f711c5ea6913187/examples/simple/src/main/java/simple/StuffSteps.java
>> * The main page: http://github.com/aslakhellesoy/cucumber_java/tree/master
>>
>> By this I hope Cucumber will reach a bigger crowd. Much bigger  
>> crowd actually :-) - this will work for Scala, Clojure, Jython and  
>> all the other cool JVM languages too.
>> (I'll be doing something similar for .NET, which will bring  
>> Cucumber goodness to C#, F# and whatever languages run on .NET. But  
>> IronRuby must catch up on speed first).
>>
>> I had the pleasure of going back to visit PicoContainer - a  
>> pioneering lightweight dependency injection container I developed  
>> with Paul Hammant back in 2003. It's still lightweight and a joy to  
>> use (relatively speaking - Java in itself isn't joyful). Cucumber- 
>> java uses PicoContainer to instantiate the POJOs that define the  
>> annotated step definition methods, so if you're so inclined, these  
>> classes can depend on each other via constructor DI, and  
>> PicoContainer just figures out how to instantiate the objects).
>>
>> So if you're working on a Java project, have been looking at  
>> Cucumber but stayed away because of all the weird Ruby, this is  
>> your chance. Here is a cuke for Duke!
>>
>> (::) Aslak (::)
>>
>> (1) You still need a tiny bit of Ruby to register step definitions: http://github.com/aslakhellesoy/cucumber_java/blob/271160300da5bc9275dd67624f711c5ea6913187/examples/simple/features/support/env.rb
>> (This will hopefully go away in the future, with some better Ant  
>> and Maven support).
>
>
> Very cool stuff.  It would be an interesting and informative  
> exercise to take a JBehave tutorial and use Cucumber to drive out  
> the same feature and then have a side-by-side comparison of the  
> required step definitions.  I found this JBehave tutorial which  
> would make a good candidate for such a comparison:
> http://www.ryangreenhall.com/articles/bdd-by-example.html
>

I skimmed it, and it looks like a great tutorial. A comparison would  
be very interesting.

Aslak

> If someone doesn't get around to this in the next couple of weeks I  
> may take a stab at it and make a blog post of it.
>
> -Ben
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090325/1e14559b/attachment.html>

From hayafirst at gmail.com  Wed Mar 25 15:00:16 2009
From: hayafirst at gmail.com (Yi)
Date: Wed, 25 Mar 2009 14:00:16 -0500
Subject: [rspec-users] [Cucumber 0.2] Failure to use should
In-Reply-To: <ee6f48c00903191503v5f99a48dj58c111116243a100@mail.gmail.com>
References: <ee6f48c00903190725i532b21c5l5c09b8234ea8b88a@mail.gmail.com>
	<8d961d900903190813p6fcb51a3o754db54a6317c125@mail.gmail.com>
	<ee6f48c00903190839h102da972v56446562f9abefb0@mail.gmail.com>
	<2c7e61990903190859g4aca06bbk3d3009b2ddd08f37@mail.gmail.com>
	<ee6f48c00903191503v5f99a48dj58c111116243a100@mail.gmail.com>
Message-ID: <ee6f48c00903251200l45542781u1b5977738c229c1e@mail.gmail.com>

Just did a little bit exploration. Found out
http://github.com/carlosbrando/remarkable/tree/master plugin I use actually
cause the problem. This plugin also broke spec:server:start rake task as
well. :-(

On Thu, Mar 19, 2009 at 5:03 PM, Yi <hayafirst at gmail.com> wrote:

> I thought be_something is actually handled by rspec class Be. be_blank
> essentially asks the object blank? predicate. Not that there is a "be_blank"
> method declared anywhere.
>
> Anyway, require 'spec/expectations' doesn't solve the problem. I will look
> into this. Thanks
>
> Yi
>
>
> On Thu, Mar 19, 2009 at 10:59 AM, Pat Maddox <pat.maddox at gmail.com> wrote:
>
>> Right, you need to add
>> require 'spec/expectations'
>>
>> because Cucumber doesn't know about RSpec's matchers by default.
>>
>> Pat
>>
>> 2009/3/19 Yi <hayafirst at gmail.com>:
>> > This is my env.rb
>> >
>> > # Sets up the Rails environment for Cucumber
>> > ENV["RAILS_ENV"] ||= "test"
>> > require File.expand_path(File.dirname(__FILE__) +
>> > '/../../config/environment')
>> > require 'cucumber/rails/world'
>> > require 'cucumber/formatters/unicode' # Comment out this line if you
>> don't
>> > want Cucumber Unicode support
>> > Cucumber::Rails.use_transactional_fixtures
>> >
>> > require 'webrat'
>> >
>> > Webrat.configure do |config|
>> >   config.mode = :rails
>> >   config.application_address= "myapp.local"
>> > end
>> >
>> > require 'cucumber/rails/rspec'
>> > require 'webrat/core/matchers'
>> >
>> >
>> > The only thing different is:
>> >   config.application_address= "myapp.local"
>> >
>> > I tried to comment out this line and it didn't help anyway.
>> >
>> > I did script/generate cucumber and it didn't help. :(
>> >
>> > Yi
>> >
>> > 2009/3/19 aslak hellesoy <aslak.hellesoy at gmail.com>
>> >>
>> >>
>> >> 2009/3/19 Yi <hayafirst at gmail.com>
>> >>>
>> >>> I have a step definition like this:
>> >>>
>> >>> Then "the account should be created" do
>> >>>   account = Account.find_by_name("my shiny new account")
>> >>>   p account.class
>> >>>   account.should_not be_blank
>> >>> end
>> >>>
>> >>> When running this step, I got the error message:
>> >>>
>> >>> Account(id: integer, name: string, state: string, next_renewal_at:
>> date,
>> >>> created_at: datetime, updated_at: datetime, full_domain: string,
>> deleted_at:
>> >>> datetime, subscription_discount_id: integer, subscription_plan_id:
>> integer)
>> >>>
>> >>>     And the account should be created              #
>> >>> features/step_definitions/create_account_steps.rb:31
>> >>>       undefined method `be_blank' for
>> >>> #<ActionController::Integration::Session:0x349994c> (NoMethodError)
>> >>>       features/create_account.feature:10:in `And the account should be
>> >>> created'
>> >>
>> >> The #be_blank method is defined by a module under 'rspec/matchers'.
>> This
>> >> module is automatically included in
>> ActionController::Integration::Session
>> >> if you have the following in your env.rb:
>> >>
>> >> require 'spec/expectations'
>> >>
>> >> Do you? If you just upgraded to Cucumber 0.2 you should probably
>> >> rebootstrap Cucumber with:
>> >>
>> >> script/generate cucumber
>> >>
>> >> Aslak
>> >>
>> >>>
>> >>> I print out the account class, which is a AR::B. Why cucumber tells me
>> it
>> >>> is a ActionController::Integration::Session?
>> >>>
>> >>> I use cucumber 0.2 and rspec 1.2 with Rails 2.3.2
>> >>>
>> >>> Thanks
>> >>>
>> >>> Yi
>> >>> --
>> >>> http://yiwenandsoftware.wordpress.com
>> >>>
>> >>> _______________________________________________
>> >>> rspec-users mailing list
>> >>> rspec-users at rubyforge.org
>> >>> http://rubyforge.org/mailman/listinfo/rspec-users
>> >>
>> >>
>> >>
>> >> --
>> >> Aslak (::)
>> >>
>> >> _______________________________________________
>> >> rspec-users mailing list
>> >> rspec-users at rubyforge.org
>> >> http://rubyforge.org/mailman/listinfo/rspec-users
>> >
>> >
>> >
>> > --
>> > http://yiwenandsoftware.wordpress.com
>> >
>> > _______________________________________________
>> > rspec-users mailing list
>> > rspec-users at rubyforge.org
>> > http://rubyforge.org/mailman/listinfo/rspec-users
>> >
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
>
> --
> http://yiwenandsoftware.wordpress.com
>



-- 
http://yiwenandsoftware.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090325/001194d4/attachment.html>

From tadatoshi.mailinglist at gmail.com  Wed Mar 25 15:16:25 2009
From: tadatoshi.mailinglist at gmail.com (Tadatoshi Takahashi)
Date: Wed, 25 Mar 2009 15:16:25 -0400
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake spec"
	fails
Message-ID: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>

Hi,

I started to use RSpec and RSpec-rails 1.2.0 last week when I upgraded to
Ruby on Rails 2.3.2.
At that time, "ruby script/generate rspec" hang but autospec and "rake spec"
were successful.

Yesterday, I updated to RSpec and RSpec-rails 1.2.2.
This time, "ruby script/generate rspec" was successful with helpful
messages.
autospec is still successful.
But "rake spec" failed and it even overwritten the development database.
It appears that only the database tables with the fixtures that are being
used are overwritten.

I could stop using fixtures all together.
But I would rather like to know how to resolve this problem.

Please let me know what I should do to resolve the problem.

Thank you in advance.

Tadatoshi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090325/eabebe63/attachment-0001.html>

From lists at ruby-forum.com  Wed Mar 25 15:29:04 2009
From: lists at ruby-forum.com (Tadatoshi Takahashi)
Date: Wed, 25 Mar 2009 20:29:04 +0100
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
Message-ID: <0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>

Tadatoshi Takahashi wrote:
> Hi,
> 
> I started to use RSpec and RSpec-rails 1.2.0 last week when I upgraded 
> to
> Ruby on Rails 2.3.2.
> At that time, "ruby script/generate rspec" hang but autospec and "rake 
> spec"
> were successful.
> 
> Yesterday, I updated to RSpec and RSpec-rails 1.2.2.
> This time, "ruby script/generate rspec" was successful with helpful
> messages.
> autospec is still successful.
> But "rake spec" failed and it even overwritten the development database.
> It appears that only the database tables with the fixtures that are 
> being
> used are overwritten.
> 
> I could stop using fixtures all together.
> But I would rather like to know how to resolve this problem.
> 
> Please let me know what I should do to resolve the problem.
> 
> Thank you in advance.
> 
> Tadatoshi

P.S.
It seems that autospec is run against test database and that "rake spec" 
is run against development database.
How can I resolve this problem?
-- 
Posted via http://www.ruby-forum.com/.

From sfeley at gmail.com  Wed Mar 25 15:47:58 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Wed, 25 Mar 2009 15:47:58 -0400
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
Message-ID: <1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>

On Wed, Mar 25, 2009 at 3:29 PM, Tadatoshi Takahashi
<lists at ruby-forum.com> wrote:
>
> P.S.
> It seems that autospec is run against test database and that "rake spec"
> is run against development database.
> How can I resolve this problem?

The first thing I'd check would be whether you have RAILS_ENV defined
in your .profile or .bashrc or wherever.  RSpec used to always declare
the 'test' environment, but the latest version of spec_helper.rb
declares it conditionally:

ENV["RAILS_ENV"] ||= 'test'

It shouldn't be necessary to declare your environment as 'development'
in the shell, because it's usually the default.  So if you have that
environment variable set somewhere, take it out.



-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From afolgueras at gmail.com  Wed Mar 25 16:15:20 2009
From: afolgueras at gmail.com (Alex)
Date: Wed, 25 Mar 2009 13:15:20 -0700 (PDT)
Subject: [rspec-users] How to spec a around_filter
Message-ID: <ef8b06ee-0005-4030-b104-6152f0e14e5b@r36g2000vbr.googlegroups.com>

Hi all, any of you guys had success specking out a around_filter? I
tried a few things like controller.should_receive
(:around_filter_method), controller.stub!(:around_filter_method) but
without success. In fact, the method is always executed even though I
stubed it. What I find strange is that I also have a before_filter and
I do not have any problems specking it. Why should it be different for
an around_filter?

Thanks

From dchelimsky at gmail.com  Wed Mar 25 16:30:55 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 25 Mar 2009 15:30:55 -0500
Subject: [rspec-users] Spec::Rails,
	"model.should have(1).error_on(:attribute)"
In-Reply-To: <a9f640d4615a666f4709fb87ce20087c@ruby-forum.com>
References: <a6591d550903231610h2e3309feodc5b6c2e05974f93@mail.gmail.com>
	<57c63afe0903231618o57b3d47au72d42989fc42f372@mail.gmail.com>
	<a9f640d4615a666f4709fb87ce20087c@ruby-forum.com>
Message-ID: <10D2FBA4-5945-40DF-B119-293999EE09A2@gmail.com>

On Mar 25, 2009, at 1:37 PM, Phor Gruber <lists at ruby-forum.com> wrote:

> I added:
>  - validates_presence_of :attribute
>
> To my model.
>
> The test now passes.

Congrats! It took longer than it usually does, but you just  
experienced the red and green parts of the red/green/refactor cycle.

Cheers,
David

>
>
> yay!!
>
> Thanks David.
>
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

From lists at ruby-forum.com  Wed Mar 25 17:42:49 2009
From: lists at ruby-forum.com (Balint Erdi)
Date: Wed, 25 Mar 2009 22:42:49 +0100
Subject: [rspec-users] [cucumber] webrat+selenium integration problem:
	record n
In-Reply-To: <49C964F3.9000600@benmabey.com>
References: <f2f9e79b-ecee-40b7-8df1-d202036eea71@j39g2000yqn.googlegroups.com>
	<49C830BF.1040401@benmabey.com>
	<e7aee908ce1ecf1a5515395d87cc12fc@ruby-forum.com>
	<49C964F3.9000600@benmabey.com>
Message-ID: <8aa5aba65e3d4a53021bbbe32e211708@ruby-forum.com>

Ben Mabey wrote:

> Couple things I'd like to point out.  In your enhanced.rb you don't need
> to do the Before hook yourself.  You can just require
> 'database_cleaner/cucumber'.  I've updated your gist to use that.
> In your plain.rb it seems like you are trying to truncate your database
> just once upon startup.  If that is the case then the recommended way is
> to use the clean_with method like so:
> DatabaseCleaner.clean_with :truncation
> 
> Again, I have updated the gist to reflect this.
> 
> -Ben

Hey Ben, thanks a lot.

The problem I am experiencing now is that information stored in the 
session does not seem to be retained between steps (again, only in the 
case of selenium sessions, plain sesssion work fine). So the login 
function works fine now but when I go to another page afterwards it 
throws a big error because the action tries to render something based on 
the current user.

Is the session store I am using relevant? I used the default 
cookie-based storage and then tried to change to the active-record based 
one to no avail. My config is at http://gist.github.com/83635

Thank you,
Balint
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Wed Mar 25 17:49:39 2009
From: lists at ruby-forum.com (Tadatoshi Takahashi)
Date: Wed, 25 Mar 2009 22:49:39 +0100
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
Message-ID: <ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>

Stephen Eley wrote:
> On Wed, Mar 25, 2009 at 3:29 PM, Tadatoshi Takahashi
> <lists at ruby-forum.com> wrote:
>>
>> P.S.
>> It seems that autospec is run against test database and that "rake spec"
>> is run against development database.
>> How can I resolve this problem?
> 
> The first thing I'd check would be whether you have RAILS_ENV defined
> in your .profile or .bashrc or wherever.  RSpec used to always declare
> the 'test' environment, but the latest version of spec_helper.rb
> declares it conditionally:
> 
> ENV["RAILS_ENV"] ||= 'test'
> 
> It shouldn't be necessary to declare your environment as 'development'
> in the shell, because it's usually the default.  So if you have that
> environment variable set somewhere, take it out.
> 
> 
> 
> --
> Have Fun,
>    Steve Eley (sfeley at gmail.com)
>    ESCAPE POD - The Science Fiction Podcast Magazine
>    http://www.escapepod.org

Hi, Steve,

Thank you for your reply.

I have never set RAILS_ENV anywhere.
To make sure, I have looked at .profile but RAILS_ENV is not set there.

Is there any other place where that RAILS_ENV is getting set?

Thank you.

Tadatoshi

-- 
Posted via http://www.ruby-forum.com/.

From sfeley at gmail.com  Wed Mar 25 18:21:31 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Wed, 25 Mar 2009 18:21:31 -0400
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
Message-ID: <1fb4df0903251521v1beacfe4v1701634536405af4@mail.gmail.com>

On Wed, Mar 25, 2009 at 5:49 PM, Tadatoshi Takahashi
<lists at ruby-forum.com> wrote:
>
> I have never set RAILS_ENV anywhere.
> To make sure, I have looked at .profile but RAILS_ENV is not set there.
>
> Is there any other place where that RAILS_ENV is getting set?

I don't know.  But the way to test it from the command line would be:

echo $RAILS_ENV




-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From mark at mwilden.com  Wed Mar 25 18:58:40 2009
From: mark at mwilden.com (Mark Wilden)
Date: Wed, 25 Mar 2009 15:58:40 -0700
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
Message-ID: <3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>

On Wed, Mar 25, 2009 at 2:49 PM, Tadatoshi Takahashi
<lists at ruby-forum.com> wrote:
> Stephen Eley wrote:
>> On Wed, Mar 25, 2009 at 3:29 PM, Tadatoshi Takahashi
>> <lists at ruby-forum.com> wrote:
>>>
>>> P.S.
>>> It seems that autospec is run against test database and that "rake spec"
>>> is run against development database.
>
> Is there any other place where that RAILS_ENV is getting set?

Check the rakefiles? Could someone have "improved" one? It happened to me.

///ark

From seatmanu at gmail.com  Wed Mar 25 19:18:44 2009
From: seatmanu at gmail.com (Emmanuel Pinault)
Date: Wed, 25 Mar 2009 16:18:44 -0700
Subject: [rspec-users] Cucumber and matcher
Message-ID: <1721DF4C-3CBE-4769-A968-599545253AC2@gmail.com>

Hi,


Is there way to generate a better error messages when I have a matcher  
in my step like

1.should == 0  => would fail with expected 1, got 0

I would like to add more details to that error?  Especially , in my  
case ,I am using the include? matcher.


Thanks

Emmanuel



From ben at benmabey.com  Wed Mar 25 19:24:29 2009
From: ben at benmabey.com (Ben Mabey)
Date: Wed, 25 Mar 2009 17:24:29 -0600
Subject: [rspec-users] [cucumber] webrat+selenium integration problem:
 record n
In-Reply-To: <8aa5aba65e3d4a53021bbbe32e211708@ruby-forum.com>
References: <f2f9e79b-ecee-40b7-8df1-d202036eea71@j39g2000yqn.googlegroups.com>	<49C830BF.1040401@benmabey.com>	<e7aee908ce1ecf1a5515395d87cc12fc@ruby-forum.com>	<49C964F3.9000600@benmabey.com>
	<8aa5aba65e3d4a53021bbbe32e211708@ruby-forum.com>
Message-ID: <49CABD2D.5050200@benmabey.com>

Balint Erdi wrote:
> Ben Mabey wrote:
>
>   
>> Couple things I'd like to point out.  In your enhanced.rb you don't need
>> to do the Before hook yourself.  You can just require
>> 'database_cleaner/cucumber'.  I've updated your gist to use that.
>> In your plain.rb it seems like you are trying to truncate your database
>> just once upon startup.  If that is the case then the recommended way is
>> to use the clean_with method like so:
>> DatabaseCleaner.clean_with :truncation
>>
>> Again, I have updated the gist to reflect this.
>>
>> -Ben
>>     
>
> Hey Ben, thanks a lot.
>
> The problem I am experiencing now is that information stored in the 
> session does not seem to be retained between steps (again, only in the 
> case of selenium sessions, plain sesssion work fine). So the login 
> function works fine now but when I go to another page afterwards it 
> throws a big error because the action tries to render something based on 
> the current user.
>
> Is the session store I am using relevant? I used the default 
> cookie-based storage and then tried to change to the active-record based 
> one to no avail. My config is at http://gist.github.com/83635
>   

Hmm.. I've never had issues with sessions not persisting when using the 
selenium adapter.  Nothing in your config looks wrong.
What is your login method?  It is telling Selenium to go to the login 
page and submit the proper credentials?

Ben

From lists at ruby-forum.com  Wed Mar 25 19:25:14 2009
From: lists at ruby-forum.com (Balint Erdi)
Date: Thu, 26 Mar 2009 00:25:14 +0100
Subject: [rspec-users] [cucumber] webrat+selenium integration problem:
	record n
In-Reply-To: <8aa5aba65e3d4a53021bbbe32e211708@ruby-forum.com>
References: <f2f9e79b-ecee-40b7-8df1-d202036eea71@j39g2000yqn.googlegroups.com>
	<49C830BF.1040401@benmabey.com>
	<e7aee908ce1ecf1a5515395d87cc12fc@ruby-forum.com>
	<49C964F3.9000600@benmabey.com>
	<8aa5aba65e3d4a53021bbbe32e211708@ruby-forum.com>
Message-ID: <9a961e8387f98819712a97a6471642bc@ruby-forum.com>


> Hey Ben, thanks a lot.
> 
> The problem I am experiencing now is that information stored in the 
> session does not seem to be retained between steps (again, only in the 
> case of selenium sessions, plain sesssion work fine). So the login 
> function works fine now but when I go to another page afterwards it 
> throws a big error because the action tries to render something based on 
> the current user.
> 
> Is the session store I am using relevant? I used the default 
> cookie-based storage and then tried to change to the active-record based 
> one to no avail. My config is at http://gist.github.com/83635
> 
> Thank you,
> Balint

Ok, I think I have the problem and it has nothing to do with session 
storage. I intend to explain it below so others might benefit from it.

  Scenario: Successfully sharing album with group via the "Share with 
group" link
    Given I am logged in as "pepito"
    When I go to my photosets page

I used some existing step definitions I wrote for non-selenium features 
to log in the user like so:

  Given /^I log in as "(.*)"$/ do |login_name|
    @user = User.find_by_login(login_name)
    post "/session", :login => @user.login, :password => 'secret' # !!!
  end

  Given /^I am logged in as "(.*)"$/ do |login_name|
    Given %(the user "#{login_name}" exists)
    Given %(the user "#{login_name}" is active)
    Given %(I log in as "#{login_name}")
  end

When the feature gets to "When I go to my photosets page", the selenium 
browser is launched but there is no user logged in here, there is no 
session, so that step will fail miserably. That's because the line 
denoted by !!! does not log in the user in the selenium session but in 
the "test session" (I know this is not the proper definition but I 
cannot precisely name it).

So if I need a logged in user in a selenium feature I should go the 
"hard way" and start from scratch:

  Given the user "pepito" exists
  And the user "pepito" is active
  When I go to the login page
  And I fill in "login" with "pepito"
  And I fill in "password" with "secret"
  And I press "entrar"
  And I go to my photosets page
  ...

It takes some time to get one's head around realizing there is a test 
world and a selenium world and keep in mind which action modifies which 
world and learn how they can interact with each other (through the 
database I guess if they use the same environment).

Please correct me if I am wrong in anything I say above,
Balint

-- 
Posted via http://www.ruby-forum.com/.

From ben at benmabey.com  Wed Mar 25 19:43:49 2009
From: ben at benmabey.com (Ben Mabey)
Date: Wed, 25 Mar 2009 17:43:49 -0600
Subject: [rspec-users] [cucumber] webrat+selenium integration problem:
 record n
In-Reply-To: <9a961e8387f98819712a97a6471642bc@ruby-forum.com>
References: <f2f9e79b-ecee-40b7-8df1-d202036eea71@j39g2000yqn.googlegroups.com>	<49C830BF.1040401@benmabey.com>	<e7aee908ce1ecf1a5515395d87cc12fc@ruby-forum.com>	<49C964F3.9000600@benmabey.com>	<8aa5aba65e3d4a53021bbbe32e211708@ruby-forum.com>
	<9a961e8387f98819712a97a6471642bc@ruby-forum.com>
Message-ID: <49CAC1B5.7000704@benmabey.com>

Balint Erdi wrote:
>> Hey Ben, thanks a lot.
>>
>> The problem I am experiencing now is that information stored in the 
>> session does not seem to be retained between steps (again, only in the 
>> case of selenium sessions, plain sesssion work fine). So the login 
>> function works fine now but when I go to another page afterwards it 
>> throws a big error because the action tries to render something based on 
>> the current user.
>>
>> Is the session store I am using relevant? I used the default 
>> cookie-based storage and then tried to change to the active-record based 
>> one to no avail. My config is at http://gist.github.com/83635
>>
>> Thank you,
>> Balint
>>     
>
> Ok, I think I have the problem and it has nothing to do with session 
> storage. I intend to explain it below so others might benefit from it.
>
>   Scenario: Successfully sharing album with group via the "Share with 
> group" link
>     Given I am logged in as "pepito"
>     When I go to my photosets page
>
> I used some existing step definitions I wrote for non-selenium features 
> to log in the user like so:
>
>   Given /^I log in as "(.*)"$/ do |login_name|
>     @user = User.find_by_login(login_name)
>     post "/session", :login => @user.login, :password => 'secret' # !!!
>   end
>
>   Given /^I am logged in as "(.*)"$/ do |login_name|
>     Given %(the user "#{login_name}" exists)
>     Given %(the user "#{login_name}" is active)
>     Given %(I log in as "#{login_name}")
>   end
>
> When the feature gets to "When I go to my photosets page", the selenium 
> browser is launched but there is no user logged in here, there is no 
> session, so that step will fail miserably. That's because the line 
> denoted by !!! does not log in the user in the selenium session but in 
> the "test session" (I know this is not the proper definition but I 
> cannot precisely name it).
>
> So if I need a logged in user in a selenium feature I should go the 
> "hard way" and start from scratch:
>
>   Given the user "pepito" exists
>   And the user "pepito" is active
>   When I go to the login page
>   And I fill in "login" with "pepito"
>   And I fill in "password" with "secret"
>   And I press "entrar"
>   And I go to my photosets page
>   ...
>
> It takes some time to get one's head around realizing there is a test 
> world and a selenium world and keep in mind which action modifies which 
> world and learn how they can interact with each other (through the 
> database I guess if they use the same environment).
>
> Please correct me if I am wrong in anything I say above,
> Balint
>
>   
Yep.. that is what I thought was happening.  The "test session" is rails 
integration session that webrat uses.
I would still use your login step but just have it hit the form.   So 
something like:

  Given /^I log in as "(.*)"$/ do |login_name|
    @user = User.find_by_login(login_name)
    vist "/session"
    fill_in "login", :with => login_name
    fill_in "password", :with => 'secret'
    click_button "entrar" 
  end



With that step definition you don't need to pollute all of your features 
with the steps to login.  As it turns out you can have the best of both 
worlds.  Meaning, if you want webrat to use the faster post method only 
for non-selenium runs you can.  Like so:

  Given /^I log in as "(.*)"$/ do |login_name|
    @user = User.find_by_login(login_name)
    webrat.atutomate do 
      vist "/session"
      fill_in "login", :with => login_name
      fill_in "password", :with => 'secret'
      click_button "entrar" 
    end

    webrat.simulate do      
      post "/session", :login => @user.login, :password => 'secret'    
    end
  end



In short, the webrat#automate block is only executed with an adapter 
that is automating a real browser.  Likewise the webrat#simulate block 
is only executed when the adapter is simulating a browser, such as the 
rails adapter. Does that make sense?

-Ben



From zach.dennis at gmail.com  Wed Mar 25 20:24:15 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Wed, 25 Mar 2009 20:24:15 -0400
Subject: [rspec-users] [Cucumber] ANN: Cucumber with pure Java
In-Reply-To: <3133DE2A-6697-4679-8BED-08B30C6B25F5@benmabey.com>
References: <8d961d900903250808p46a2ca82ke23e8c8975dd6ff3@mail.gmail.com>
	<3133DE2A-6697-4679-8BED-08B30C6B25F5@benmabey.com>
Message-ID: <85d99afe0903251724h12695ac9pa341cc028232a8ab@mail.gmail.com>

2009/3/25 Ben Mabey <ben at benmabey.com>:
>
> On Mar 25, 2009, at 9:08 AM, aslak hellesoy wrote:
>
> Big news for all Java programmers out there.
> Now you can use Cucumber with pure Java!
>
> That's right, you don't have to write a single line of Ruby! (1)
> All of your step definitions can be written as annotated methods in POJOs
> (Plain Old Java Objects).
>
> To get a taste of what this looks like, check out the simple example in the
> cucumber_java project on GitHub:
>
> * README for example:
> http://github.com/aslakhellesoy/cucumber_java/tree/271160300da5bc9275dd67624f711c5ea6913187/examples/simple
> * Some sample step defs:
> http://github.com/aslakhellesoy/cucumber_java/blob/271160300da5bc9275dd67624f711c5ea6913187/examples/simple/src/main/java/simple/StuffSteps.java
> * The main page: http://github.com/aslakhellesoy/cucumber_java/tree/master
>
> By this I hope Cucumber will reach a bigger crowd. Much bigger crowd
> actually :-) - this will work for Scala, Clojure, Jython and all the other
> cool JVM languages too.
> (I'll be doing something similar for .NET, which will bring Cucumber
> goodness to C#, F# and whatever languages run on .NET. But IronRuby must
> catch up on speed first).
>
> I had the pleasure of going back to visit PicoContainer - a pioneering
> lightweight dependency injection container I developed with Paul Hammant
> back in 2003. It's still lightweight and a joy to use (relatively speaking -
> Java in itself isn't joyful). Cucumber-java uses PicoContainer to
> instantiate the POJOs that define the annotated step definition methods, so
> if you're so inclined, these classes can depend on each other via
> constructor DI, and PicoContainer just figures out how to instantiate the
> objects).
>
> So if you're working on a Java project, have been looking at Cucumber but
> stayed away because of all the weird Ruby, this is your chance. Here is a
> cuke for Duke!
>
> (::) Aslak (::)
>
> (1) You still need a tiny bit of Ruby to register step definitions:
> http://github.com/aslakhellesoy/cucumber_java/blob/271160300da5bc9275dd67624f711c5ea6913187/examples/simple/features/support/env.rb
> (This will hopefully go away in the future, with some better Ant and Maven
> support).
>
>
> Very cool stuff. ?It would be an interesting and informative?exercise to
> take a JBehave tutorial and use Cucumber to drive out the same?feature and
> then have a side-by-side comparison of the required step definitions.
> found this JBehave tutorial which would make a good candidate for such a
> comparison:
> http://www.ryangreenhall.com/articles/bdd-by-example.html
> If someone doesn't get around to this in the next couple of weeks I may take
> a stab at it and make a blog post of it.

I'm assuming you mean w/Java, but I'd like to encourage folks who are
learning BDD to walk through his example even with Ruby. I did that
tonight and it was quite pleasant. The tutorial is small and focused,
and it can be completed in not much time.  However, the tutorial does
leave out some implementation that you would need in order to actually
complete it, but I find those sorts of things fun to figure out.

Translating Ryan's tutorial to Ruby allows you to explore writing
rspec simple matchers (or full fledged matchers) if you want to go
that route, and overall I found it fun to go through it and practice
my own skills.

I know it's not the comparison Ben and Aslak are talking about, but
for those of you who are looking for a good little tutorial to walk
through and practice with, this one is pretty good if you are somewhat
familiar with Cucumber, RSpec, and Ruby,

-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From zach.dennis at gmail.com  Wed Mar 25 20:32:20 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Wed, 25 Mar 2009 20:32:20 -0400
Subject: [rspec-users] Cucumber and matcher
In-Reply-To: <1721DF4C-3CBE-4769-A968-599545253AC2@gmail.com>
References: <1721DF4C-3CBE-4769-A968-599545253AC2@gmail.com>
Message-ID: <85d99afe0903251732p47fe9fa0l4d1d962fe6282f08@mail.gmail.com>

On Wed, Mar 25, 2009 at 7:18 PM, Emmanuel Pinault <seatmanu at gmail.com> wrote:
> Hi,
>
>
> Is there way to generate a better error messages when I have a matcher in my
> step like
>
> 1.should == 0 ?=> would fail with expected 1, got 0
>
> I would like to add more details to that error? ?Especially , in my case ,I
> am using the include? matcher.

Check out rolling your own simple matcher:

http://apidock.com/rspec/Spec/Matchers/simple_matcher

It can be done in only a few lines!

>
>
> Thanks
>
> Emmanuel
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From lists at ruby-forum.com  Wed Mar 25 21:00:16 2009
From: lists at ruby-forum.com (Balint Erdi)
Date: Thu, 26 Mar 2009 02:00:16 +0100
Subject: [rspec-users] [cucumber] webrat+selenium integration problem:
	record n
In-Reply-To: <49CAC1B5.7000704@benmabey.com>
References: <f2f9e79b-ecee-40b7-8df1-d202036eea71@j39g2000yqn.googlegroups.com>
	<49C830BF.1040401@benmabey.com>
	<e7aee908ce1ecf1a5515395d87cc12fc@ruby-forum.com>
	<49C964F3.9000600@benmabey.com>
	<8aa5aba65e3d4a53021bbbe32e211708@ruby-forum.com>
	<9a961e8387f98819712a97a6471642bc@ruby-forum.com>
	<49CAC1B5.7000704@benmabey.com>
Message-ID: <3a5f0b6c4b238712e8ca8fda63a789e9@ruby-forum.com>

Ben Mabey wrote:

> 
> With that step definition you don't need to pollute all of your features
> with the steps to login.  As it turns out you can have the best of both
> worlds.  Meaning, if you want webrat to use the faster post method only
> for non-selenium runs you can.  Like so:
> 
>   Given /^I log in as "(.*)"$/ do |login_name|
>     @user = User.find_by_login(login_name)
>     webrat.atutomate do
>       vist "/session"
>       fill_in "login", :with => login_name
>       fill_in "password", :with => 'secret'
>       click_button "entrar"
>     end
> 
>     webrat.simulate do
>       post "/session", :login => @user.login, :password => 'secret'
>     end
>   end
> 

Excellent (and elegant), it works now!

Thank you for your help along the way,
Balint
-- 
Posted via http://www.ruby-forum.com/.

From dchelimsky at gmail.com  Wed Mar 25 21:00:20 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Wed, 25 Mar 2009 20:00:20 -0500
Subject: [rspec-users] Cucumber and matcher
In-Reply-To: <85d99afe0903251732p47fe9fa0l4d1d962fe6282f08@mail.gmail.com>
References: <1721DF4C-3CBE-4769-A968-599545253AC2@gmail.com>
	<85d99afe0903251732p47fe9fa0l4d1d962fe6282f08@mail.gmail.com>
Message-ID: <57c63afe0903251800u6bfc23f4g9afa866b72da52ba@mail.gmail.com>

On Wed, Mar 25, 2009 at 7:32 PM, Zach Dennis <zach.dennis at gmail.com> wrote:
> On Wed, Mar 25, 2009 at 7:18 PM, Emmanuel Pinault <seatmanu at gmail.com> wrote:
>> Hi,
>>
>>
>> Is there way to generate a better error messages when I have a matcher in my
>> step like
>>
>> 1.should == 0 ?=> would fail with expected 1, got 0
>>
>> I would like to add more details to that error? ?Especially , in my case ,I
>> am using the include? matcher.
>
> Check out rolling your own simple matcher:
>
> http://apidock.com/rspec/Spec/Matchers/simple_matcher
>
> It can be done in only a few lines!

Or the new Matcher DSL - simple matcher even simpler!

http://rspec.rubyforge.org/rspec/1.2.2/files/features/matchers/create_matcher_feature.html

>
>>
>>
>> Thanks
>>
>> Emmanuel
>>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
>
> --
> Zach Dennis
> http://www.continuousthinking.com
> http://www.mutuallyhuman.com
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From cflipse at gmail.com  Wed Mar 25 21:59:18 2009
From: cflipse at gmail.com (Chris Flipse)
Date: Wed, 25 Mar 2009 21:59:18 -0400
Subject: [rspec-users] How to spec a around_filter
In-Reply-To: <ef8b06ee-0005-4030-b104-6152f0e14e5b@r36g2000vbr.googlegroups.com>
References: <ef8b06ee-0005-4030-b104-6152f0e14e5b@r36g2000vbr.googlegroups.com>
Message-ID: <e3e91d130903251859of3afa10o7eca7de78512e95c@mail.gmail.com>

I havn't done this myself, but would
controller.stub!(:around_filter_method).and_yield  work?

On Wed, Mar 25, 2009 at 4:15 PM, Alex <afolgueras at gmail.com> wrote:

> Hi all, any of you guys had success specking out a around_filter? I
> tried a few things like controller.should_receive
> (:around_filter_method), controller.stub!(:around_filter_method) but
> without success. In fact, the method is always executed even though I
> stubed it. What I find strange is that I also have a before_filter and
> I do not have any problems specking it. Why should it be different for
> an around_filter?
>
> Thanks
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
// anything worth taking seriously is worth making fun of
// http://blog.devcaffeine.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090325/967261ba/attachment.html>

From seatmanu at gmail.com  Thu Mar 26 00:26:40 2009
From: seatmanu at gmail.com (Emmanuel Pinault)
Date: Wed, 25 Mar 2009 21:26:40 -0700
Subject: [rspec-users] Cucumber and matcher
In-Reply-To: <57c63afe0903251800u6bfc23f4g9afa866b72da52ba@mail.gmail.com>
References: <1721DF4C-3CBE-4769-A968-599545253AC2@gmail.com>
	<85d99afe0903251732p47fe9fa0l4d1d962fe6282f08@mail.gmail.com>
	<57c63afe0903251800u6bfc23f4g9afa866b72da52ba@mail.gmail.com>
Message-ID: <6D3DA16D-BCE3-4E61-B837-9D9A6F8E4E08@gmail.com>

Thanks David!

I will try the new matcher after I migrate to rspec 1.2.x  :)  But  
seems a lot easier to create . Really liking it!

Emmanuel

On Mar 25, 2009, at 6:00 PM, David Chelimsky wrote:

> On Wed, Mar 25, 2009 at 7:32 PM, Zach Dennis <zach.dennis at gmail.com>  
> wrote:
>> On Wed, Mar 25, 2009 at 7:18 PM, Emmanuel Pinault  
>> <seatmanu at gmail.com> wrote:
>>> Hi,
>>>
>>>
>>> Is there way to generate a better error messages when I have a  
>>> matcher in my
>>> step like
>>>
>>> 1.should == 0  => would fail with expected 1, got 0
>>>
>>> I would like to add more details to that error?  Especially , in  
>>> my case ,I
>>> am using the include? matcher.
>>
>> Check out rolling your own simple matcher:
>>
>> http://apidock.com/rspec/Spec/Matchers/simple_matcher
>>
>> It can be done in only a few lines!
>
> Or the new Matcher DSL - simple matcher even simpler!
>
> http://rspec.rubyforge.org/rspec/1.2.2/files/features/matchers/create_matcher_feature.html
>
>>
>>>
>>>
>>> Thanks
>>>
>>> Emmanuel
>>>
>>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>
>>
>>
>> --
>> Zach Dennis
>> http://www.continuousthinking.com
>> http://www.mutuallyhuman.com
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From lists at ruby-forum.com  Thu Mar 26 02:23:55 2009
From: lists at ruby-forum.com (Zhenning Guan)
Date: Thu, 26 Mar 2009 07:23:55 +0100
Subject: [rspec-users] what's the different between ([@weather]) and
	(@weather)?
Message-ID: <ff33d70f00fc0b46f037d23babcf95ca@ruby-forum.com>

before do
  @weather = mock_model(Weather)
  Weather.stub!(:find).and_return([@weather])
end

I saw this code on peepcode, but I'm a little confused the
and_return([@weather]).
mostly, we just and_return(@weather), don't we? so, what is the meaning
of  and_return([@weather]) ?
-- 
Posted via http://www.ruby-forum.com/.

From anja-email1 at web.de  Thu Mar 26 03:44:22 2009
From: anja-email1 at web.de (Andrea Jahn)
Date: Thu, 26 Mar 2009 08:44:22 +0100
Subject: [rspec-users]
 =?iso-8859-15?q?what=27s_the_different_between_=28?=
 =?iso-8859-15?q?=5B=40weather=5D=29_and_=28=40weather=29=3F?=
Message-ID: <1317360869@web.de>



 

Hi,

Weather.find(1) returns an object: @weather
Weather.find(:all) returns an array of objects : [@weather] 

look at the api of ActiveRecordBase. http://api.rubyonrails.org/classes/ActiveRecord/Base.html [http://api.rubyonrails.org/classes/ActiveRecord/Base.html]

You have not specified a parameter for the find method here, so you expect, that
the find methods you are using, will all return an array of objects.

In the spec you can also define the expected parameters:

Weather.stub!(:find).with(*:all*,* :order* => "title").and_return([@weather])



Andrea
*Von:* "Zhenning Guan" <lists at ruby-forum.com>
*Gesendet:* 26.03.09 07:54:56
*An:* rspec-users at rubyforge.org
*Betreff:* [rspec-users] what's the different between ([@weather]) and (@weather)?



before do
@weather = mock_model(Weather)
Weather.stub!(:find).and_return([@weather])
end

I saw this code on peepcode, but I'm a little confused the
and_return([@weather]).
mostly, we just and_return(@weather), don't we? so, what is the meaning
of and_return([@weather]) ?
-- 
Posted via http://www.ruby-forum.com/.
_______________________________________________
rspec-users mailing list
rspec-users at rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
	



	
Verschicken Sie SMS direkt vom Postfach aus - in alle deutschen und viele 
ausl?ndische Netze zum gleichen Preis! 
https://produkte.web.de/webde_sms/sms 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090326/a07090af/attachment.html>

From phlip2005 at gmail.com  Thu Mar 26 08:53:35 2009
From: phlip2005 at gmail.com (Phlip)
Date: Thu, 26 Mar 2009 05:53:35 -0700
Subject: [rspec-users] [ANN] assert2-0.4.6 provides assert_xhtml,
	an alternative to assert_select
Message-ID: <49CB7ACF.3030809@gmail.com>

Rubyists:

Consider the following monstrosity, coded using assert_select:

   assert_select "div#logo_box img[src=/0000/0001/logo.gif][alt=My Company]"

Now, behold it rewritten to use assert_xhtml:

   assert_xhtml do
     div.logo_box! do
       img :src => /logo.gif$/, :alt => 'My Company'
     end
   end

That sample contains more Ruby; it's not just one big string.

Still not convinced? Oh, I forgot the <a> around the <img>! Try this:

   assert_xhtml do
     div.logo_box! do
       a :href => '/' do
         img :src => /logo.gif$/, :alt => 'My Company'
       end
     end
   end

And we had an issue with the small logo sneaking into the logo_box once. Let's 
exclude it:

   assert_xhtml do
     div.logo_box do
       a :href => '/' do
         img :src => /logo.gif$/, :alt => 'My Company'
       end
       without!{ img :src => /mini_logo.gif/ }
     end
   end

Imagine adding all that to assert_select - it would get much harder to read, and 
more complex. assert_xhtml uses Nokogiri::HTML::Builder notation, so anything it 
can build, you can query.

Version 0.4.6 adds all the following features. To begin, enter:

   gem install nokogiri assert2

== require 'assert2/xhtml' ==

All assert{ 2.0 } dependencies are optional. If you have Nokogiri
(>=1.2.2), you can test Rails views like this:

      user = users(:Moses)
      get :edit_user, :id =>  user.id

      assert_xhtml do

        form :action =>  '/users' do
          fieldset do
            legend 'Personal Information'
            label 'First name'
            input :type =>  'text',
                  :name =>  'user[first_name]'
                  :value =>  user.first_name
          end
        end

      end

That's a Rails functional test on a form. The assertion expects the form
to target the given action, and contain a fieldset, a legend, a label, and
a populated text input field. The assertion forgives any other details,
such as intervening structural tags, excess spaces, or extra attributes;
and complains if any required detail is missing, out of order, or ill-formed.

The DSL inside that block is Nokogiri::HTML::Builder notation. Generally
speaking, anything Nokogiri can build, you can specify.

=== arguments ===

Call assert_xhtml(my_xml){} to interrogate your XML. When called without
an argument, the method reads @response.body.

=== without! ===

Every assert* has a matching deny* method. assert_xhtml recognizes the
special element without! as a request to fail if the given elements
do indeed appear in your output:

     get :info, :record_id => record.id
     assert_xhtml do
       div :class => :content do
         without!{ div :class => :download }
       end
     end

That assertion will fail if the outer <div class='content'> tag does not
exist, or if any inner <div class='download'> does exist.

The without! element respects your document layout. This assertion
passes...

     assert_xhtml SAMPLE_LIST do
       ul{ li{ ul{ li 'Sales report'
           without!{ li 'All Sales report criteria' } } } }
     end

...even though the target document contains an <li>All Sales report
criteria</li>:

     <ul style='font-size: 18'>
       <li>model
         <ul>
           <li>Billings report</li>
           <li>Sales report</li>
           <li>Billings criteria</li>
           <li>Common system</li>
         </ul>
       </li>
       <li>controller
         <ul>
           <li>All Sales report criteria</li>
           <li>All Billings reports</li>
         </ul>
       </li>
     </ul>

The two <li> elements appear in different <ul> lists, so the assertion
does not associate them.

The committee does not yet know what without!{ without!{} } does, so please
do not rely on its current behavior, whatever that is!

=== escapes ===

Certain elements, such as <select> and <id>, have the same names as internal
methods. If you experience a bizarre error message, such as "wrong argument
type Hash (expected Array)", add a ! to the end of the element, like this:

     assert_xhtml do
       h2 'Sites'

       select! :id => 'sites',
               :name => 'sites[]',
               :multiple => :multiple,
               :size => SaleController::LIST_SIZE
     end

=== text ===

An element such as h3{ 'text' } will match <h3> text </h3>, with leading or
trailing blanks, but it won't match <h3><span>text</span></h3>. This rule
prevents runaway matches between high- and low-level elements.

The example for the next section illustrates how to mix text and attribute
specifications on the same element.

A text specification may be a /regexp/.

=== :xpath!=> ===

assert_xhtml works by throwing away structural information. If you need
more control over your structure, use an :xpath! attribute to apply raw
XPath specifications to your target elements.

This assertion detect the rather pedestrian fact that your <title>
element remains inside your <html><head> block - and it did not
escape and rampage off to somewhere else:

     assert_xhtml do
       title :xpath! => 'parent::head/parent::html' do
         text 'Chamber of Commerce - Info - Hope Orphanage'
       end
     end

Note the XPath evaluates as a predicate of the target <title>, so its parent 
axis lists the familiar elements in reverse.

That code also shows the 'text' directive, inserting text contents directly
into the enclosing element. A future version of Nokogiri will allow the
element's first argument to specify its text.

An :xpath! of a number evaluates to the 1-based index of an item in its
parent. This assertion forces list items to appear in the correct order:

     assert_xhtml do
       ul :style => 'font-size: 18' do
         li 'model' do
           li(:xpath! => 1){ text 'Sales report'  }
           li(:xpath! => 2){ text 'Billings report' }
           li(:xpath! => 3){ text 'Billings criteria' }
         end
       end
     end

=== :verbose! => true ===

Sometimes when an assertion fails, you can't tell why. To see each
context the assertion considers, add :verbose! => true to the lowest
element you know works, and run the tests:

     assert_xhtml SAMPLE_FORM do
       fieldset do
         li :verbose! => true do
           label 'First name', :for => :user_first_name
         end
       end
     end

The verbose option works as "spew", not as a diagnostic, and it reports
each considered element's contents.

Because XPath evaluates the <label>, in our example, before the <li>, you
might need to comment the <label> out to see a successful spew on the <li>.

=== scope ===

assert_xhtml{} yields its block to Nokogiri::HTML::Builder, which turns
every method call into an HTML element. This freedom comes at a price -
you can't easily call your own methods!

Use this scope trick to pass your outer scope into the specification:

      get :edit_user, :id => users(:Moses).id
      scope = self

      assert_xhtml do
        form :action => '/users' do
          input :value => scope.users(:Moses).first_name
        end
      end

Notice we could improve that test by declaring a variable,
user = users(:Moses), in the outer scope, and simply passing
the user variable itself into the specification.

=== :class=> ===

The :class attribute is magic. This assertion passes...

     assert_xhtml SAMPLE_LIST do
       ul :class => :kalika do
         li 'Billings report'
       end
     end

...despite the actual HTML contains <ul class='kalika goddess'>. This feature
simulates the CSS Selector notation that matches classes by their cascading
effects.

=== class & ID shortcuts ===

Nokogiri expands div.rad.thing! to <div class='rad' id='thing'/>. That
means you don't need to write div :class => 'rad', :id => 'thing' (or
ul :class => :kalika). You can then put other arguments after the shortcut,
and the <div> in our example receives them, too.

=== diagnostic message ===

When this assertion fails, it attempts to print out...

  - your reference elements, rendered as HTML
  - each "near-miss" region of your sample HTML

The next version will feature much better diagnostics. Until they work, if these 
diagnostics are not sufficient, put :verbose! on the lowest element you think 
works, and comment out its contents...

=== RSpec ===

The matching "specification", in RSpec language, is be_html_with{}.
Its syntax and behavior are the same:

   it 'should have a cute form' do
     render '/users/new'

     response.body.should be_html_with{
       form :action => '/users' do
         fieldset do
           legend 'Personal Information'
           label 'First nome'
           input :type => 'text', :name => 'user[first_name]'
         end
       end
     }
   end

Good hunting!

-- 
   Phlip


From afolgueras at gmail.com  Thu Mar 26 14:21:04 2009
From: afolgueras at gmail.com (Alex)
Date: Thu, 26 Mar 2009 11:21:04 -0700 (PDT)
Subject: [rspec-users] How to spec a around_filter
In-Reply-To: <e3e91d130903251859of3afa10o7eca7de78512e95c@mail.gmail.com>
References: <ef8b06ee-0005-4030-b104-6152f0e14e5b@r36g2000vbr.googlegroups.com>
	<e3e91d130903251859of3afa10o7eca7de78512e95c@mail.gmail.com>
Message-ID: <3cf3430b-1ef8-4948-95e2-6e8a1677ca21@r28g2000vbp.googlegroups.com>

Works like a charm!

Thanks a lot.

On Mar 25, 9:59?pm, Chris Flipse <cfli... at gmail.com> wrote:
> I havn't done this myself, but would
> controller.stub!(:around_filter_method).and_yield ?work?
>
> On Wed, Mar 25, 2009 at 4:15 PM, Alex <afolgue... at gmail.com> wrote:
> > Hi all, any of you guys had success specking out a around_filter? I
> > tried a few things like controller.should_receive
> > (:around_filter_method), controller.stub!(:around_filter_method) but
> > without success. In fact, the method is always executed even though I
> > stubed it. What I find strange is that I also have a before_filter and
> > I do not have any problems specking it. Why should it be different for
> > an around_filter?
>
> > Thanks
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
> --
> // anything worth taking seriously is worth making fun of
> //http://blog.devcaffeine.com/
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From afolgueras at gmail.com  Thu Mar 26 14:22:25 2009
From: afolgueras at gmail.com (Alex)
Date: Thu, 26 Mar 2009 11:22:25 -0700 (PDT)
Subject: [rspec-users] How to spec a around_filter
In-Reply-To: <e3e91d130903251859of3afa10o7eca7de78512e95c@mail.gmail.com>
References: <ef8b06ee-0005-4030-b104-6152f0e14e5b@r36g2000vbr.googlegroups.com>
	<e3e91d130903251859of3afa10o7eca7de78512e95c@mail.gmail.com>
Message-ID: <b3db456b-3d55-4e6c-a960-836913426afc@n20g2000vba.googlegroups.com>

Works like a charm!

Thanks a lot.

On Mar 25, 9:59?pm, Chris Flipse <cfli... at gmail.com> wrote:
> I havn't done this myself, but would
> controller.stub!(:around_filter_method).and_yield ?work?
>
> On Wed, Mar 25, 2009 at 4:15 PM, Alex <afolgue... at gmail.com> wrote:
> > Hi all, any of you guys had success specking out a around_filter? I
> > tried a few things like controller.should_receive
> > (:around_filter_method), controller.stub!(:around_filter_method) but
> > without success. In fact, the method is always executed even though I
> > stubed it. What I find strange is that I also have a before_filter and
> > I do not have any problems specking it. Why should it be different for
> > an around_filter?
>
> > Thanks
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
> --
> // anything worth taking seriously is worth making fun of
> //http://blog.devcaffeine.com/
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From f.mischa at gmail.com  Fri Mar 27 03:31:19 2009
From: f.mischa at gmail.com (Mischa Fierer)
Date: Fri, 27 Mar 2009 02:31:19 -0500
Subject: [rspec-users] [Cucumber][email-spec] Testing Incoming Email with
	email-spec
Message-ID: <ae16b71e0903270031k19abeaa1p10523a34e6caf86@mail.gmail.com>

Hi,
I've done some work for email-spec that allows you to quickly test incoming
e-mail handling.

Does any body else receive e-mail? If so, I would love your input/feedback,
as I'm hoping this will eventually get merged into master so that everyone
can use.

The branch i'm working in is
here<http://github.com/mischa/email-spec/tree/incoming>.
It provides an IncomingEmail class which you can use to generate emails with
attachments, multipart emails, etc. Your app can then process this email as
if it is a normal one.

The rationale behind this is that while Rails Recipies and others advocate
testing e-mail with actual e-mail fixtures, this felt too brittle for what I
wanted to do.

So, email-spec will now hopefully help with testing things like:

1) Emailing attachments / notes to a backpack-like page
2) Replying to messages via email. E.g. how some websites allow you to
'reply above this line' to messages / comments via email.
3) A messaging system that hides users from each other (e.g. a dating site).

Ben also suggested that this could be used to testing things like how your
app handles bounced e-mail, etc.

I have included a sample list of steps below. If you are confused about how
receiving e-mail might work, please checkout my example app (not using
e-mail spec) here<http://github.com/mischa/receive_mail_example_app/tree/master>.
It uses the fetcher plugin.

Anyway, here are the features:

Feature: EmailSpec Example -- Quickly generate incoming e-mail


In order to keep track of my information

As a customer I want to send e-mail to an e-mail spec app

to keep the e-mail in the app so that it can be with other relavent info


    Scenario: An incoming email is delivered to a page
      Given an incoming email to "mischa at example.com"
      And the email is from "ahcsim at elpmaxe.com"
      And a "User" with the email "mischa at example.com"


      When the email is delivered

      And I go to the email page

      Then I should see the email



    Scenario: An incoming email with a header
      Given an incoming email to "mischa at example.com"
      And the email is from "ahcsim at elpmaxe.com"
      And a "User" with the email "mischa at example.com"
      And the "agent" header is "007"


      When the email is delivered

      And I go to the email page

      Then I should see the email



    Scenario: An incoming email with an attachment is delivered to a page
      Given an incoming email
      And the email is to "mischa at example.com"
      And a "User" with the email "mischa at example.com"
      And the email has the "image/png" file at
"features/support/rails.png" attached

      When the email is delivered
      And I go to the email page
      Then I should see the email
      And I should see the attachment



    Scenario: An incoming multipart email's text part goes to a page
      Given an incoming email to "mischa at example.com"
      And the email is from "ahcsim at elpmaxe.com"
      And the email has both an html part and a text part
      And a "User" with the email "mischa at example.com"


      When the email is delivered

      And I go to the email page

      Then I should see only the text part of the email


    Scenario: An incoming html only email goes to a page
      Given an incoming email to "mischa at example.com"
      And the email has only html
      And the email is from "ahcsim at elpmaxe.com"
      And a "User" with the email "mischa at example.com"


      When the email is delivered

      And I go to the email page

      Then I should see the html



Thanks,

Mischa Fierer
http://www.themomorohoax.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090327/34a04b76/attachment-0001.html>

From dchelimsky at gmail.com  Fri Mar 27 08:36:12 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Fri, 27 Mar 2009 08:36:12 -0400
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
	<3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>
Message-ID: <57c63afe0903270536r51e25c72v1e00616da3469fd@mail.gmail.com>

On Wed, Mar 25, 2009 at 6:58 PM, Mark Wilden <mark at mwilden.com> wrote:
> On Wed, Mar 25, 2009 at 2:49 PM, Tadatoshi Takahashi
> <lists at ruby-forum.com> wrote:
>> Stephen Eley wrote:
>>> On Wed, Mar 25, 2009 at 3:29 PM, Tadatoshi Takahashi
>>> <lists at ruby-forum.com> wrote:
>>>>
>>>> P.S.
>>>> It seems that autospec is run against test database and that "rake spec"
>>>> is run against development database.
>>
>> Is there any other place where that RAILS_ENV is getting set?
>
> Check the rakefiles? Could someone have "improved" one? It happened to me.

You can also change spec_helper.rb to force the test environment with:

  ENV["RAILS_ENV"] = 'test'

That's what it used to do but somebody complained that it shouldn't
force an environment :)

Cheers,
David

>
> ///ark
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From sfeley at gmail.com  Fri Mar 27 16:03:33 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Fri, 27 Mar 2009 16:03:33 -0400
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <57c63afe0903270536r51e25c72v1e00616da3469fd@mail.gmail.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
	<3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>
	<57c63afe0903270536r51e25c72v1e00616da3469fd@mail.gmail.com>
Message-ID: <1fb4df0903271303w78a544besf8bcf97642b2c808@mail.gmail.com>

On Fri, Mar 27, 2009 at 8:36 AM, David Chelimsky <dchelimsky at gmail.com> wrote:
>
> You can also change spec_helper.rb to force the test environment with:
> ?ENV["RAILS_ENV"] = 'test'
> That's what it used to do but somebody complained that it shouldn't
> force an environment :)

Yeah.  Running tests in the 'test' environment?  What were you
thinking?  That's almost as ridiculous as expecting the 'rails'
command to create a Rails app!  >%-\

It might be that your positive comment on my Lighthouse ticket
yesterday is going to my head, but it seems to me that the arrow of
work here is backwards.  The reason for having a generated skeleton,
including spec_helper.rb, is to give people sensible starter code with
defaults for sensible cases.  99% of Rails users are going to want to
run their Rspec behaviors in 'test' every time.  Setting the
environment to 'test' is therefore sensible.

People with edge cases are more likely to know what they're doing, and
should know that they can change that one line to add the '||=' or
comment it out completely.  The people who are most likely to be
impacted by the less forceful spec_helper are probably newer users who
don't understand shells and environments quite as well, and might be
running in 'one-click' Rails setups that set the environment for them
without them knowing about it.


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From lists at ruby-forum.com  Fri Mar 27 16:50:16 2009
From: lists at ruby-forum.com (Tadatoshi Takahashi)
Date: Fri, 27 Mar 2009 21:50:16 +0100
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <1fb4df0903271303w78a544besf8bcf97642b2c808@mail.gmail.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
	<3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>
	<57c63afe0903270536r51e25c72v1e00616da3469fd@mail.gmail.com>
	<1fb4df0903271303w78a544besf8bcf97642b2c808@mail.gmail.com>
Message-ID: <18ce164ba599159782b217d28de02237@ruby-forum.com>

Stephen Eley wrote:
> On Fri, Mar 27, 2009 at 8:36 AM, David Chelimsky <dchelimsky at gmail.com> 
> wrote:
>>
>> You can also change spec_helper.rb to force the test environment with:
>> ?ENV["RAILS_ENV"] = 'test'
>> That's what it used to do but somebody complained that it shouldn't
>> force an environment :)
> 
> Yeah.  Running tests in the 'test' environment?  What were you
> thinking?  That's almost as ridiculous as expecting the 'rails'
> command to create a Rails app!  >%-\
> 
> It might be that your positive comment on my Lighthouse ticket
> yesterday is going to my head, but it seems to me that the arrow of
> work here is backwards.  The reason for having a generated skeleton,
> including spec_helper.rb, is to give people sensible starter code with
> defaults for sensible cases.  99% of Rails users are going to want to
> run their Rspec behaviors in 'test' every time.  Setting the
> environment to 'test' is therefore sensible.
> 
> People with edge cases are more likely to know what they're doing, and
> should know that they can change that one line to add the '||=' or
> comment it out completely.  The people who are most likely to be
> impacted by the less forceful spec_helper are probably newer users who
> don't understand shells and environments quite as well, and might be
> running in 'one-click' Rails setups that set the environment for them
> without them knowing about it.
> 
> 
> --
> Have Fun,
>    Steve Eley (sfeley at gmail.com)
>    ESCAPE POD - The Science Fiction Podcast Magazine
>    http://www.escapepod.org


Thank you, David, Steve.

About Steve's comment,
I may not be familiar with everything in Ruby on Rails but I am willing 
to learn.
And I would like to know in which case it would be better to run RSpec 
in an environment other than test one.
To me, I like clear separation of development, test, and production 
environment in Ruby on Rails.
And I like to run Specs in test environment because for every run of a 
spec (example), database is cleaned up and doesn't affect the result of 
running the next spec (example). And I don't want the development 
database to be cleaned up by running RSpec against it.
But that's only my understanding.
If anybody could give me more insight about it, I would greatly 
appreciate it.

Thank you.

Tadatoshi
-- 
Posted via http://www.ruby-forum.com/.

From sfeley at gmail.com  Fri Mar 27 18:21:22 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Fri, 27 Mar 2009 18:21:22 -0400
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <18ce164ba599159782b217d28de02237@ruby-forum.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
	<3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>
	<57c63afe0903270536r51e25c72v1e00616da3469fd@mail.gmail.com>
	<1fb4df0903271303w78a544besf8bcf97642b2c808@mail.gmail.com>
	<18ce164ba599159782b217d28de02237@ruby-forum.com>
Message-ID: <1fb4df0903271521h139052f9t4ceb770deffb3986@mail.gmail.com>

On Fri, Mar 27, 2009 at 4:50 PM, Tadatoshi Takahashi
<lists at ruby-forum.com> wrote:
>
> About Steve's comment,
> I may not be familiar with everything in Ruby on Rails but I am willing
> to learn.

FWIW, I absolutely did not mean my comment as an insult, to you or
anybody else.  I was going a bit more general, and wasn't referring
specifically to you.  Anyway, in my own head "new user" is _never_ an
insult.  Everybody starts there.  It's like insulting someone for
having been born.


> And I would like to know in which case it would be better to run RSpec
> in an environment other than test one.

I can see cases where some specialized behaviors might run in specific
environments -- for instance, maybe you have a routine task in your
staging environment that copies data from the production environment,
etc.  If those behaviors are non-trivial, it makes sense to spec and
test them.  But if they're initialized in your environment config
files, you're then stuck either with doing backflips to try to fake
out Rails, or running your specs in that environment.

That's just one hypothetical case off the top of my head.  Doubtless
there are others that might be logical.  (And a whole lot more that
wouldn't be, but someone would surely try them anyway.)


> To me, I like clear separation of development, test, and production
> environment in Ruby on Rails.
> And I like to run Specs in test environment because for every run of a
> spec (example), database is cleaned up and doesn't affect the result of
> running the next spec (example). And I don't want the development
> database to be cleaned up by running RSpec against it.

And you're absolutely right.  On all of that.  Anything different
would be an exception, not the rule.  It sounds to me like you're
pretty grounded in the principles of Rails -- don't sell yourself
short.




-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From hayafirst at gmail.com  Sat Mar 28 00:17:23 2009
From: hayafirst at gmail.com (Yi)
Date: Fri, 27 Mar 2009 23:17:23 -0500
Subject: [rspec-users] flash.now
Message-ID: <ee6f48c00903272117x43f15659l9551715935c0cb4e@mail.gmail.com>

Hi,

How can I test flash.now[:key] is being set in a controller test? Both
flash[:key] and flash.now[:key].should == message didn't work

I can use response.session["flash"][:key].should == message . Just looks bad

Thanks

Yi

-- 
http://yiwenandsoftware.wordpress.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090327/e380216b/attachment.html>

From lists at ruby-forum.com  Sat Mar 28 00:19:49 2009
From: lists at ruby-forum.com (Tadatoshi Takahashi)
Date: Sat, 28 Mar 2009 05:19:49 +0100
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <1fb4df0903271521h139052f9t4ceb770deffb3986@mail.gmail.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
	<3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>
	<57c63afe0903270536r51e25c72v1e00616da3469fd@mail.gmail.com>
	<1fb4df0903271303w78a544besf8bcf97642b2c808@mail.gmail.com>
	<18ce164ba599159782b217d28de02237@ruby-forum.com>
	<1fb4df0903271521h139052f9t4ceb770deffb3986@mail.gmail.com>
Message-ID: <0418ecd203dc506fca4c2093f148421e@ruby-forum.com>

Stephen Eley wrote:
> On Fri, Mar 27, 2009 at 4:50 PM, Tadatoshi Takahashi
> <lists at ruby-forum.com> wrote:
>>
>> About Steve's comment,
>> I may not be familiar with everything in Ruby on Rails but I am willing
>> to learn.
> 
> FWIW, I absolutely did not mean my comment as an insult, to you or
> anybody else.  I was going a bit more general, and wasn't referring
> specifically to you.  Anyway, in my own head "new user" is _never_ an
> insult.  Everybody starts there.  It's like insulting someone for
> having been born.
> 
> 
>> And I would like to know in which case it would be better to run RSpec
>> in an environment other than test one.
> 
> I can see cases where some specialized behaviors might run in specific
> environments -- for instance, maybe you have a routine task in your
> staging environment that copies data from the production environment,
> etc.  If those behaviors are non-trivial, it makes sense to spec and
> test them.  But if they're initialized in your environment config
> files, you're then stuck either with doing backflips to try to fake
> out Rails, or running your specs in that environment.
> 
> That's just one hypothetical case off the top of my head.  Doubtless
> there are others that might be logical.  (And a whole lot more that
> wouldn't be, but someone would surely try them anyway.)
> 
> 
>> To me, I like clear separation of development, test, and production
>> environment in Ruby on Rails.
>> And I like to run Specs in test environment because for every run of a
>> spec (example), database is cleaned up and doesn't affect the result of
>> running the next spec (example). And I don't want the development
>> database to be cleaned up by running RSpec against it.
> 
> And you're absolutely right.  On all of that.  Anything different
> would be an exception, not the rule.  It sounds to me like you're
> pretty grounded in the principles of Rails -- don't sell yourself
> short.
> 
> 
> 
> 
> --
> Have Fun,
>    Steve Eley (sfeley at gmail.com)
>    ESCAPE POD - The Science Fiction Podcast Magazine
>    http://www.escapepod.org


Hi, Steve.

Thank you for your reply.
I am glad that I have learned a lot from your replies.

Sincerely,
Tadatoshi

-- 
Posted via http://www.ruby-forum.com/.

From programmer2188 at gmail.com  Sat Mar 28 09:49:46 2009
From: programmer2188 at gmail.com (Brandon Olivares)
Date: Sat, 28 Mar 2009 09:49:46 -0400
Subject: [rspec-users] Cucumber step definitions vs. RSpec examples
Message-ID: <000101c9afac$0fd828f0$2f887ad0$@com>

Hi,

So, I'm confused. I've been trying to use Cucumber and RSpec, but step
definitions and RSpec examples just seem to be overlapping. What should go
in either one of these?

For instance, let's say I'm testing if a form exists on a page. What goes in
Cucumber and what goes in RSpec?

What I did for now is put Webrat methods in the step definitions, like
fill_in, select, etc, without submitting since I'm not testing processing
yet; and then put selector matchers in the RSpec examples.

But I have no idea if that's right. How do you separate these and keep them
from duplicating one another?

Thanks,
Brandon


From zuperinfinite at gmail.com  Sat Mar 28 16:49:09 2009
From: zuperinfinite at gmail.com (Bart Zonneveld)
Date: Sat, 28 Mar 2009 21:49:09 +0100
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <1fb4df0903271303w78a544besf8bcf97642b2c808@mail.gmail.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
	<3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>
	<57c63afe0903270536r51e25c72v1e00616da3469fd@mail.gmail.com>
	<1fb4df0903271303w78a544besf8bcf97642b2c808@mail.gmail.com>
Message-ID: <FF4E42E9-8135-426C-94F4-FB3D762640FB@gmail.com>


On 27 mrt 2009, at 21:03, Stephen Eley wrote:

> On Fri, Mar 27, 2009 at 8:36 AM, David Chelimsky  
> <dchelimsky at gmail.com> wrote:
>>
>> You can also change spec_helper.rb to force the test environment  
>> with:
>>  ENV["RAILS_ENV"] = 'test'
>> That's what it used to do but somebody complained that it shouldn't
>> force an environment :)
>
> 99% of Rails users are going to want to
> run their Rspec behaviors in 'test' every time.  Setting the
> environment to 'test' is therefore sensible.

I very strongly disagree on this one. As it so happens, we've found a  
bug in Passenger regarding uploads, umasks and permissions, which was  
caused by Passenger overwriting the TMP_DIR environment variable. Took  
us quite a while to figure this one out.

Even more, rake RAILS_ENV=development spec wouldn't work as expected  
when the env gets explicitly set from within a spec helper.

my 2cts,
bartz


From andrew at avit.ca  Sun Mar 29 02:51:33 2009
From: andrew at avit.ca (Andrew Vit)
Date: Sat, 28 Mar 2009 23:51:33 -0700 (PDT)
Subject: [rspec-users] spec_server not reloading model classes
Message-ID: <1106da77-505a-4262-b9df-a67c9af6027b@w35g2000prg.googlegroups.com>

Hi,

I'm using the latest rspec-rails 1.2.2 with rails 2.3.2, and I'm
trying to get it to work with spec_server. This is on Mac/Leopard,
with the stock ruby, all gems installed in /Library/Ruby/. I have
configured:

# config/environments/test.rb
config.cache_classes = false

# spec/spec.opts
--drb

The tests run nice and fast, so I know they're running against the
spec_server, but when I make a change to my model which should toggle
the result of a test, it doesn't change until I restart the
spec:server. I have tried running it with combinations of:

rake spec:server:start
script/spec_server

script/autospec
autospec

The specs run, but no reloading makes it useless. Any ideas?

Thanks,
Andrew Vit

From scott at railsnewbie.com  Sun Mar 29 03:12:46 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Sun, 29 Mar 2009 03:12:46 -0400
Subject: [rspec-users] spec_server not reloading model classes
In-Reply-To: <1106da77-505a-4262-b9df-a67c9af6027b@w35g2000prg.googlegroups.com>
References: <1106da77-505a-4262-b9df-a67c9af6027b@w35g2000prg.googlegroups.com>
Message-ID: <49CF1F6E.7080905@railsnewbie.com>

Andrew Vit wrote:
> Hi,
>
> I'm using the latest rspec-rails 1.2.2 with rails 2.3.2, and I'm
> trying to get it to work with spec_server. This is on Mac/Leopard,
> with the stock ruby, all gems installed in /Library/Ruby/. I have
> configured:
>
> # config/environments/test.rb
> config.cache_classes = false
>
> # spec/spec.opts
> --drb
>
>   
Do you notice reloading occurring in dev mode (with cache-classes = 
false) with the same class?

Are you explicitly using require anywhere?

Scott



> The tests run nice and fast, so I know they're running against the
> spec_server, but when I make a change to my model which should toggle
> the result of a test, it doesn't change until I restart the
> spec:server. I have tried running it with combinations of:
>
> rake spec:server:start
> script/spec_server
>
> script/autospec
> autospec
>
> The specs run, but no reloading makes it useless. Any ideas?
>
> Thanks,
> Andrew Vit
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>   


From andrew at avit.ca  Sun Mar 29 04:05:42 2009
From: andrew at avit.ca (Andrew Vit)
Date: Sun, 29 Mar 2009 01:05:42 -0700 (PDT)
Subject: [rspec-users] spec_server not reloading model classes
In-Reply-To: <49CF1F6E.7080905@railsnewbie.com>
References: <1106da77-505a-4262-b9df-a67c9af6027b@w35g2000prg.googlegroups.com>
	<49CF1F6E.7080905@railsnewbie.com>
Message-ID: <7a9e7cb7-5bc3-499e-9986-36cb6e4a8e69@j9g2000prh.googlegroups.com>

I just tried it with:

$ rake RAILS_ENV=development spec:server:start
$ RAILS_ENV=development script/autospec

And it looks the same. (If I change the model file, the tests re-run
but it obviously doesn't get reloaded: even if I add a syntax error,
it still runs.)

Not sure where you mean about the explicit require. All my specs files
have require spec_helper at the top, which is how they come out of the
box...

Thanks for your help,
Andrew



On Mar 29, 12:12?am, Scott Taylor <sc... at railsnewbie.com> wrote:
> Andrew Vit wrote:
> > Hi,
>
> > I'm using the latest rspec-rails 1.2.2 with rails 2.3.2, and I'm
> > trying to get it to work with spec_server. This is on Mac/Leopard,
> > with the stock ruby, all gems installed in /Library/Ruby/. I have
> > configured:
>
> > # config/environments/test.rb
> > config.cache_classes = false
>
> > # spec/spec.opts
> > --drb
>
> Do you notice reloading occurring in dev mode (with cache-classes =
> false) with the same class?
>
> Are you explicitly using require anywhere?
>
> Scott
>
>
>
>
>
> > The tests run nice and fast, so I know they're running against the
> > spec_server, but when I make a change to my model which should toggle
> > the result of a test, it doesn't change until I restart the
> > spec:server. I have tried running it with combinations of:
>
> > rake spec:server:start
> > script/spec_server
>
> > script/autospec
> > autospec
>
> > The specs run, but no reloading makes it useless. Any ideas?
>
> > Thanks,
> > Andrew Vit
> > _______________________________________________
> > rspec-users mailing list
> > rspec-us... at rubyforge.org
> >http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From scott at railsnewbie.com  Sun Mar 29 04:40:49 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Sun, 29 Mar 2009 04:40:49 -0400
Subject: [rspec-users] spec_server not reloading model classes
In-Reply-To: <7a9e7cb7-5bc3-499e-9986-36cb6e4a8e69@j9g2000prh.googlegroups.com>
References: <1106da77-505a-4262-b9df-a67c9af6027b@w35g2000prg.googlegroups.com>	<49CF1F6E.7080905@railsnewbie.com>
	<7a9e7cb7-5bc3-499e-9986-36cb6e4a8e69@j9g2000prh.googlegroups.com>
Message-ID: <49CF3411.9040409@railsnewbie.com>

Andrew Vit wrote:
> I just tried it with:
>
> $ rake RAILS_ENV=development spec:server:start
> $ RAILS_ENV=development script/autospec
>   

Actually I meant poking around your app with a browser in dev mode ;)

I'm pretty sure that rails will still try to run the test environment, 
even with RAILS_ENV set to a different value, anyway.
> And it looks the same. (If I change the model file, the tests re-run
> but it obviously doesn't get reloaded: even if I add a syntax error,
> it still runs.)
>
> Not sure where you mean about the explicit require. All my specs files
> have require spec_helper at the top, which is how they come out of the
> box...
>   
I was thinking of any explicit requires which may occur in app/ and lib/.

AFAIK, this is more of a rails loading issue than an rspec one.

Scott


> Thanks for your help,
> Andrew
>
>
>
> On Mar 29, 12:12 am, Scott Taylor <sc... at railsnewbie.com> wrote:
>   
>> Andrew Vit wrote:
>>     
>>> Hi,
>>>       
>>> I'm using the latest rspec-rails 1.2.2 with rails 2.3.2, and I'm
>>> trying to get it to work with spec_server. This is on Mac/Leopard,
>>> with the stock ruby, all gems installed in /Library/Ruby/. I have
>>> configured:
>>>       
>>> # config/environments/test.rb
>>> config.cache_classes = false
>>>       
>>> # spec/spec.opts
>>> --drb
>>>       
>> Do you notice reloading occurring in dev mode (with cache-classes =
>> false) with the same class?
>>
>> Are you explicitly using require anywhere?
>>
>> Scott
>>
>>
>>
>>
>>
>>     
>>> The tests run nice and fast, so I know they're running against the
>>> spec_server, but when I make a change to my model which should toggle
>>> the result of a test, it doesn't change until I restart the
>>> spec:server. I have tried running it with combinations of:
>>>       


>>> rake spec:server:start
>>> script/spec_server
>>>       
>>> script/autospec
>>> autospec
>>>       
>>> The specs run, but no reloading makes it useless. Any ideas?
>>>       
>>> Thanks,
>>> Andrew Vit
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-us... at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>       
>> _______________________________________________
>> rspec-users mailing list
>> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users
>>     
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>   


From andrew at avit.ca  Sun Mar 29 06:15:48 2009
From: andrew at avit.ca (Andrew Vit)
Date: Sun, 29 Mar 2009 03:15:48 -0700 (PDT)
Subject: [rspec-users] spec_server not reloading model classes
In-Reply-To: <49CF3411.9040409@railsnewbie.com>
References: <1106da77-505a-4262-b9df-a67c9af6027b@w35g2000prg.googlegroups.com>
	<49CF1F6E.7080905@railsnewbie.com>
	<7a9e7cb7-5bc3-499e-9986-36cb6e4a8e69@j9g2000prh.googlegroups.com>
	<49CF3411.9040409@railsnewbie.com>
Message-ID: <4eab1d15-ce00-4992-a81a-9fdcc9d02eb0@z16g2000prd.googlegroups.com>


On Mar 29, 1:40?am, Scott Taylor <sc... at railsnewbie.com> wrote:
> Actually I meant poking around your app with a browser in dev mode ;)

Ok, I get it, I wasn't sure what you were driving at! ;-) Yes,
everything is reloading fine in the browser under development.


> I'm pretty sure that rails will still try to run the test environment,
> even with RAILS_ENV set to a different value, anyway.

The RAILS_ENV is being set conditionally in my script files, except
script/autospec where it isn't defined.
ENV["RAILS_ENV"] ||= 'test'


> I was thinking of any explicit requires which may occur in app/ and lib/.

Nothing out of the ordinary...


> AFAIK, this is more of a rails loading issue than an rspec one.

I just tried this on a clean new rails app, and the reloading still
doesn't work when running spec_server and autospec with --drb. It
works fine when I'm not using spec_server, but then it reloads all of
rails each time. Works fine, except when using spec_server.

The rspec site says:
[http://rspec.info/rails/runners.html]
> Note that there are some classes and modules that, by default, won?t get reloaded
> by Rails, which means they won?t be reloaded by spec_server. There are a number
> of strategies available for coercing Rails to reload files every time in a given
> environment. See the Rails documentation for more information.

Does that include my app/models? I wouldn't have thought so... Another
post on this mailing list seemed to suggest those don't need manual
reloading and "just work".

$ gem list rails
rails (2.3.2)
$ gem list rspec
rspec (1.2.2)
rspec-rails (1.2.2)
$ rails test_spec_server && cd test_spec_server
$ script/plugin install git://github.com/dchelimsky/rspec-rails.git
$ script/generate rspec
$ script/generate rspec_model car name:string
# edit config/environments/test.rb => config.cache_classes = false
# edit spec/spec.opts => --drb
$ rake spec:server:start
$ script/autospec
# 1 example, 0 failures
# edit app/models/car.rb => add invalid syntax!
# 1 example, 0 failures

Can anyone confirm/reproduce? (Or else tell me what I'm doing wrong?)

Thanks,
Andrew Vit

From peter.a.jaros at gmail.com  Sun Mar 29 11:37:26 2009
From: peter.a.jaros at gmail.com (Peter Jaros)
Date: Sun, 29 Mar 2009 11:37:26 -0400
Subject: [rspec-users] flash.now
In-Reply-To: <ee6f48c00903272117x43f15659l9551715935c0cb4e@mail.gmail.com>
References: <ee6f48c00903272117x43f15659l9551715935c0cb4e@mail.gmail.com>
Message-ID: <937d9d810903290837u25a1ca29k847df5f92d0184e8@mail.gmail.com>

2009/3/28 Yi <hayafirst at gmail.com>:

> How can I test flash.now[:key] is being set in a controller test? Both
> flash[:key] and flash.now[:key].should == message didn't work
>
> I can use response.session["flash"][:key].should == message . Just looks bad

That's odd.  In a controller example, you should have a #flash method
available to do exactly what you tried:

http://rspec.rubyforge.org/rspec-rails/1.2.2/classes/Spec/Rails/Example/FunctionalExampleGroup.html#M000051

Try this: where you would like to put the expectation, put "puts
self.class".  Then run it and see what class name it prints.  If it's
ControllerExampleGroup, then there's something weird going on.  If
it's not, then it hasn't figured out that you're spec'ing a
controller.  In that case, post the opening of the describe block and
we'll be able to see what's going on.

Peter

From ben at benmabey.com  Sun Mar 29 12:11:28 2009
From: ben at benmabey.com (Ben Mabey)
Date: Sun, 29 Mar 2009 10:11:28 -0600
Subject: [rspec-users] flash.now
In-Reply-To: <ee6f48c00903272117x43f15659l9551715935c0cb4e@mail.gmail.com>
References: <ee6f48c00903272117x43f15659l9551715935c0cb4e@mail.gmail.com>
Message-ID: <49CF9DB0.3090303@benmabey.com>

Yi wrote:
> Hi,
>
> How can I test flash.now[:key] is being set in a controller test? Both 
> flash[:key] and flash.now[:key].should == message didn't work
>
> I can use response.session["flash"][:key].should == message . Just 
> looks bad
>
> Thanks
>
> Yi
>
> -- 
> http://yiwenandsoftware.wordpress.com


In the past I have used this article to test flash.now in rspec:
http://www.kerrybuckley.org/2007/07/04/correct-use-of-the-flash-in-rails/

Note, that the post is pretty old and so rspec-rails may support this 
out of the box by now.. I don't know though.

-Ben

From brandtkurowski at gmail.com  Sat Mar 28 21:33:50 2009
From: brandtkurowski at gmail.com (Brandt Kurowski)
Date: Sat, 28 Mar 2009 18:33:50 -0700 (PDT)
Subject: [rspec-users] [Rails] specifying that a layout yields?
Message-ID: <0396dca8-75a3-4856-8918-ebd3f3fd8099@e18g2000yqo.googlegroups.com>

I recently had a bug in a layout due to the layout not calling "yield"
to display the actual content. I wanted to write a spec to describe
what was missing, but it wasn't obvious how, so I just fixed the
problem first and doubled back to spec it later.

Anyway, the most succinct thing I was able to come up with was the
following:

  # http://gist.github.com/87246
  describe "/layouts/application" do
    it "should show the content" do
      class << template
        attr_accessor :did_render_content
      end
      template.did_render_content = false
      render :inline => "<% self.did_render_content = true
%>", :layout => 'application'
      template.did_render_content.should be_true
    end
  end

But I'm not quite satisfied with this, as it's not as clear and
expressive as specs usually are. I thought I'd write a custom matcher
for it, but it's not obvious to me what I'd even want the spec to look
like.

Any ideas?

Thanks,

Brandt

From dotjake at gmail.com  Fri Mar 27 16:38:15 2009
From: dotjake at gmail.com (jakepaul)
Date: Fri, 27 Mar 2009 13:38:15 -0700 (PDT)
Subject: [rspec-users]  autospec fails but rake spec tasks pass
Message-ID: <22746792.post@talk.nabble.com>


I can't figure out what is causing this problem. I'm using the latest rspec
and rspec-rails gems on rails 2.3.2.

When I run autospec, the tests in the model spec that I am editing will all
fail. The error messages are like this: 

ActiveRecord::RecordInvalid in 'Job new record should create a new record
given valid attributes'
Validation failed: 

(Nothing after Validation Failed:, just blank). It doesn't matter what
attributes I pass to create the new model, and it doesn't matter if I do it
using a regular create! method or using Machinist, the same error happens.

Now, if I make a change, autospec will run the specs from that one model
spec again, and they will all pass. Then it runs all of my specs again and
that's when the specific spec I'm editing fails (only when it runs all the
specs). When I run rake spec:models or rake spec:controllers, everything
passes as it should. So I figured it might have something to do with the
controller specs, and if I remove those, autospec passes again. Then if I
put the controller specs back, autospec still passes. It only starts failing
if I again edit the model specs.

This is happening in multiple models, not just one. It's making it
impossible to work with, so I'd really appreciate any thoughts you might
have. Thank you!



-- 
View this message in context: http://www.nabble.com/autospec-fails-but-rake-spec-tasks-pass-tp22746792p22746792.html
Sent from the rspec-users mailing list archive at Nabble.com.


From dotjake at gmail.com  Sat Mar 28 23:05:53 2009
From: dotjake at gmail.com (jakepaul)
Date: Sat, 28 Mar 2009 20:05:53 -0700 (PDT)
Subject: [rspec-users] autospec fails but rake spec tasks pass (solution)
In-Reply-To: <22746792.post@talk.nabble.com>
References: <22746792.post@talk.nabble.com>
Message-ID: <22763942.post@talk.nabble.com>


I figured out what the problem was. Turns out that the controller specs used
Mocha's any_instance method to stub valid? and return false (I got this idea
from a Railscast). Due to the order in which autospec runs the specs,
editing the model spec was causing it to be run after the controller spec,
and the Mocha stubs were still being applied in the model specs. I'm not
sure if I was doing something wrong, if there is some way to 'clear' the
stubbed methods that would be great, or perhaps I just shouldn't use
any_instance.
-- 
View this message in context: http://www.nabble.com/autospec-fails-but-rake-spec-tasks-pass-tp22746792p22763942.html
Sent from the rspec-users mailing list archive at Nabble.com.


From dchelimsky at gmail.com  Sun Mar 29 12:38:10 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 29 Mar 2009 12:38:10 -0400
Subject: [rspec-users] autospec fails but rake spec tasks pass (solution)
In-Reply-To: <22763942.post@talk.nabble.com>
References: <22746792.post@talk.nabble.com> <22763942.post@talk.nabble.com>
Message-ID: <57c63afe0903290938h101afb0fpbdfff7064e3ee2f6@mail.gmail.com>

On Sat, Mar 28, 2009 at 11:05 PM, jakepaul <dotjake at gmail.com> wrote:
>
> I figured out what the problem was. Turns out that the controller specs used
> Mocha's any_instance method to stub valid? and return false (I got this idea
> from a Railscast). Due to the order in which autospec runs the specs,
> editing the model spec was causing it to be run after the controller spec,
> and the Mocha stubs were still being applied in the model specs. I'm not
> sure if I was doing something wrong, if there is some way to 'clear' the
> stubbed methods that would be great, or perhaps I just shouldn't use
> any_instance.

I haven't seen the railscast to which you refer, but if you're using
mocha instead of rspec's mock framework, be sure to configure that in
spec_helper.rb (or anywhere that gets loaded before the specs run):

Spec::Runner.configure do |config|
  config.mock_with :mocha
end

If you do that, then the mocha stubs and expectations should get
cleared out after each example runs, eliminating the ordering
dependency that is causing you trouble.

Cheers,
David

> --
> View this message in context: http://www.nabble.com/autospec-fails-but-rake-spec-tasks-pass-tp22746792p22763942.html
> Sent from the rspec-users mailing list archive at Nabble.com.
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From sfeley at gmail.com  Sun Mar 29 15:18:14 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Sun, 29 Mar 2009 15:18:14 -0400
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <FF4E42E9-8135-426C-94F4-FB3D762640FB@gmail.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
	<3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>
	<57c63afe0903270536r51e25c72v1e00616da3469fd@mail.gmail.com>
	<1fb4df0903271303w78a544besf8bcf97642b2c808@mail.gmail.com>
	<FF4E42E9-8135-426C-94F4-FB3D762640FB@gmail.com>
Message-ID: <1fb4df0903291218o78799aj6e0b91d3fad5f802@mail.gmail.com>

On Sat, Mar 28, 2009 at 4:49 PM, Bart Zonneveld <zuperinfinite at gmail.com> wrote:
>
> I very strongly disagree on this one. As it so happens, we've found a bug in
> Passenger regarding uploads, umasks and permissions, which was caused by
> Passenger overwriting the TMP_DIR environment variable. Took us quite a
> while to figure this one out.

Weird.  And a bit unfathomable to me why Passenger would have a need
to set a generic environment variable like that.  I seem to recall
those guys have run into trouble with namespacing before.  It seems
like a different case to me than Rails code setting RAILS_ENV.


> Even more, rake RAILS_ENV=development spec wouldn't work as expected when
> the env gets explicitly set from within a spec helper.

My first question would be, why do you want to do that?  What are you
doing in development mode that needs to be tested against separately
from other modes?

Second, assuming a good answer, why not just alter that line in
spec_helper.rb?  It's not like you have to go and fork the gem to
alter this behavior; configuration settings like this are what
spec_helper.rb is for.  If you're setting your environment on the
command line all the time then you must be clueful enough not to need
the same level of handholding.

But I'll moderate my smartassishness just slightly: while I'm still in
favor of leaving spec_helper.rb with an explicit assignment to 'test',
perhaps a comment may be in order on the lines of:

# This line ensures that RSpec will run in the 'test' environment
# regardless of defaults set by other tools.  If you have reasons to run
# specs in other environments, you can allow this value to be overridden
# by changing the line to:
#
# ENV['RAILS_ENV'] ||= 'test'

Then everybody who bothers to read spec_helper at least knows about
the issue and can make up their own minds.  And as a side bonus,
really new Rubyists can learn something about the ||= operator.  >8->
(Hey, everyone has a first time for seeing it.  I first noticed it in
the restful_authentication plugin, IIRC, and now I use it all the
time.)


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From sfeley at gmail.com  Sun Mar 29 15:47:05 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Sun, 29 Mar 2009 15:47:05 -0400
Subject: [rspec-users] Cucumber step definitions vs. RSpec examples
In-Reply-To: <000101c9afac$0fd828f0$2f887ad0$@com>
References: <000101c9afac$0fd828f0$2f887ad0$@com>
Message-ID: <1fb4df0903291247q47d0a851q9f66f4b77a2e153c@mail.gmail.com>

On Sat, Mar 28, 2009 at 9:49 AM, Brandon Olivares
<programmer2188 at gmail.com> wrote:
>
> So, I'm confused. I've been trying to use Cucumber and RSpec, but step
> definitions and RSpec examples just seem to be overlapping. What should go
> in either one of these?

This is a subjective judgment call that doesn't have an absolute
'right' answer.  Ask a dozen programmers how they test and you're
likely to get at least three dozen answers.

I believe the purists would say that the duplication is a feature.
The gist of this point of view is that RSpec's main strength is on the
unit testing level: you want to test that model code works separate
from your controller code, and your controller code separate from your
view code.  Then if one fails, you know exactly what class went wrong
and what to fix.

Cucumber's main strength is on the acceptance or integration level:
you want to make sure it all comes together correctly and creates the
right application behavior, which is very hard to prove with unit
testing alone.  But if you _only_ did Cucumber tests, your test to see
if a form exists on a page (to use your example) would be too broad.
If it failed, where do you look first?  Is the view broken?  The
controller code?  Do you even have a model for the view to operate on?
 Etc.

So you need to have bot levels.  You specify your overall behavior
with Cucumber, then you specify the isolated behaviors of the pieces
to make that work, and then you write your code.  That's the
full-round-trip, complete by-the-RSpec-book BDD answer.

My own view...  Well, my view is that I've tried that and been driven
nuts by it.  Writing specs for controllers and views can take me many
times longer than writing the code.  Mocking out the models for
controllers is frustrating and fragile to me, and view specs are just
obvious and tedious.  I don't have any _fun_ writing those specs.  And
if I'm not having fun, I find myself not motivated to program.

So I stopped writing those specs, and now I mostly just write model
specs and Cucumber features.  It usually doesn't take that long for me
to look at a failing Cucumber test and figure out what went wrong --
from the failure text, a stacktrace, or sometimes just manually
running the action and eyeballing it.  Sometimes, if the controller
action is unusual, I will write a spec for it, but only if my own
instincts tell me it's warranted.  (Or if something failed in an odd
way and I want to make sure that doesn't happen again.)

That's my current answer based on past experience.  Next month I might
have a different way of doing things.  I'm not going to make the case
here that I'm right and you should never write controller/view specs
for ordinary actions.  (If nothing else, doing it a bunch of times --
and getting some things wrong, then fixing them -- is a great way to
learn how controllers and views really work.)

I think the real answer is to try it a few different ways, decide what
works within your comfort level *and* leads to good code, and let
yourself experiment.  And then, if you develop an effective working
pattern down the road that you think makes good general sense, share
it with the community as one more way of doing things.   >8->

-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From pat.maddox at gmail.com  Sun Mar 29 15:50:52 2009
From: pat.maddox at gmail.com (Pat Maddox)
Date: Sun, 29 Mar 2009 19:50:52 +0000
Subject: [rspec-users] Cucumber step definitions vs. RSpec examples
In-Reply-To: <000101c9afac$0fd828f0$2f887ad0$@com>
References: <000101c9afac$0fd828f0$2f887ad0$@com>
Message-ID: <2c7e61990903291250q4e4526ebra27fb04c1694c747@mail.gmail.com>

On Sat, Mar 28, 2009 at 1:49 PM, Brandon Olivares
<programmer2188 at gmail.com> wrote:
> Hi,
>
> So, I'm confused. I've been trying to use Cucumber and RSpec, but step
> definitions and RSpec examples just seem to be overlapping. What should go
> in either one of these?
>
> For instance, let's say I'm testing if a form exists on a page. What goes in
> Cucumber and what goes in RSpec?
>
> What I did for now is put Webrat methods in the step definitions, like
> fill_in, select, etc, without submitting since I'm not testing processing
> yet; and then put selector matchers in the RSpec examples.
>
> But I have no idea if that's right. How do you separate these and keep them
> from duplicating one another?
>
> Thanks,
> Brandon
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

So far I've not found a situation where I want to just test a form's
existence at the acceptance level - I always just submit the form.
Then I might write a couple RSpec examples to verify the
presence/absence of that form in certain situations.

Occasionally there is duplication between your acceptance and unit
tests - I think that's okay.  Acceptance tests verify the behavior at
the application level, and unit tests generally do a better job of
defect localization.  I try to minimize that duplication though, and
frequently I will sacrifice the defect localization and only test that
behavior through Cucumber.  Then I go back and write the unit test the
first time I experience a problem and it takes me longer to track down
than it should have :)

Pat

From aidy.lewis at googlemail.com  Sun Mar 29 16:23:49 2009
From: aidy.lewis at googlemail.com (aidy lewis)
Date: Sun, 29 Mar 2009 21:23:49 +0100
Subject: [rspec-users] [Cucumber] Stack trace in HTML
Message-ID: <7ac2300c0903291323k3d8cacd9j443e509f7ff91a53@mail.gmail.com>

Hi,

Is the stack trace not in the HTML by design?

Aidy

From aslak.hellesoy at gmail.com  Sun Mar 29 16:58:26 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Sun, 29 Mar 2009 22:58:26 +0200
Subject: [rspec-users] [Cucumber] Stack trace in HTML
In-Reply-To: <7ac2300c0903291323k3d8cacd9j443e509f7ff91a53@mail.gmail.com>
References: <7ac2300c0903291323k3d8cacd9j443e509f7ff91a53@mail.gmail.com>
Message-ID: <8d961d900903291358k5b1e067ue3007309f3011b58@mail.gmail.com>

On Sun, Mar 29, 2009 at 10:23 PM, aidy lewis <aidy.lewis at googlemail.com>wrote:

> Hi,
>
> Is the stack trace not in the HTML by design?
>

Tried aslakhellesoy-cucumber 0.2.2.2?

Aslak


>
> Aidy
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090329/1fe8e4df/attachment.html>

From programmer2188 at gmail.com  Sun Mar 29 17:38:08 2009
From: programmer2188 at gmail.com (Brandon Olivares)
Date: Sun, 29 Mar 2009 17:38:08 -0400
Subject: [rspec-users] Cucumber step definitions vs. RSpec examples
In-Reply-To: <1fb4df0903291247q47d0a851q9f66f4b77a2e153c@mail.gmail.com>
References: <000101c9afac$0fd828f0$2f887ad0$@com>
	<1fb4df0903291247q47d0a851q9f66f4b77a2e153c@mail.gmail.com>
Message-ID: <000001c9b0b6$a8f6e8e0$fae4baa0$@com>



> -----Original Message-----
> From: rspec-users-bounces at rubyforge.org [mailto:rspec-users-
> bounces at rubyforge.org] On Behalf Of Stephen Eley
> Sent: Sunday, March 29, 2009 3:47 PM
> To: rspec-users
> Subject: Re: [rspec-users] Cucumber step definitions vs. RSpec examples
> 
> This is a subjective judgment call that doesn't have an absolute
> 'right' answer.  Ask a dozen programmers how they test and you're
> likely to get at least three dozen answers.
> 
> I believe the purists would say that the duplication is a feature.
> The gist of this point of view is that RSpec's main strength is on the
> unit testing level: you want to test that model code works separate
> from your controller code, and your controller code separate from your
> view code.  Then if one fails, you know exactly what class went wrong
> and what to fix.
> 
> Cucumber's main strength is on the acceptance or integration level:
> you want to make sure it all comes together correctly and creates the
> right application behavior, which is very hard to prove with unit
> testing alone.  But if you _only_ did Cucumber tests, your test to see
> if a form exists on a page (to use your example) would be too broad.
> If it failed, where do you look first?  Is the view broken?  The
> controller code?  Do you even have a model for the view to operate on?
>  Etc.
> 

Thank you very much. That is much more understandable. This made me realize
I forgot the controller testing for the feature I'm talking about.


> My own view...  Well, my view is that I've tried that and been driven
> nuts by it.  Writing specs for controllers and views can take me many
> times longer than writing the code.  Mocking out the models for
> controllers is frustrating and fragile to me, and view specs are just
> obvious and tedious.  I don't have any _fun_ writing those specs.  And
> if I'm not having fun, I find myself not motivated to program.
> 
> So I stopped writing those specs, and now I mostly just write model
> specs and Cucumber features.  It usually doesn't take that long for me
> to look at a failing Cucumber test and figure out what went wrong --
> from the failure text, a stacktrace, or sometimes just manually
> running the action and eyeballing it.  Sometimes, if the controller
> action is unusual, I will write a spec for it, but only if my own
> instincts tell me it's warranted.  (Or if something failed in an odd
> way and I want to make sure that doesn't happen again.)
> 
> That's my current answer based on past experience.  Next month I might
> have a different way of doing things.  I'm not going to make the case
> here that I'm right and you should never write controller/view specs
> for ordinary actions.  (If nothing else, doing it a bunch of times --
> and getting some things wrong, then fixing them -- is a great way to
> learn how controllers and views really work.)
> 

Yeah, that's what I'm worried about. I wrote probably 5 examples just to
test the existence of one field and ensure it had the options I wanted. I'm
worried about it taking way too long. But I do like the security provided by
extensive unit tests.

Thanks,
Brandon



From andrew at avit.ca  Sun Mar 29 19:14:13 2009
From: andrew at avit.ca (Andrew Vit)
Date: Sun, 29 Mar 2009 16:14:13 -0700 (PDT)
Subject: [rspec-users] spec_server not reloading model classes
In-Reply-To: <4eab1d15-ce00-4992-a81a-9fdcc9d02eb0@z16g2000prd.googlegroups.com>
References: <1106da77-505a-4262-b9df-a67c9af6027b@w35g2000prg.googlegroups.com>
	<49CF1F6E.7080905@railsnewbie.com>
	<7a9e7cb7-5bc3-499e-9986-36cb6e4a8e69@j9g2000prh.googlegroups.com>
	<49CF3411.9040409@railsnewbie.com>
	<4eab1d15-ce00-4992-a81a-9fdcc9d02eb0@z16g2000prd.googlegroups.com>
Message-ID: <ea11042e-f460-45bf-81b8-6af226a894eb@s12g2000prc.googlegroups.com>

It appears this is a bug, with an apparently simple fix in
spec_server.rb (rails 2.3 compatibility):

https://rspec.lighthouseapp.com/projects/5645/tickets/759

However, now that it's reloading my app, it's not reloading the setup
from my fixture/factory gems and throwing up a bunch of errors on re-
run. (I've tried it with both factory_girl and machinist now.) These
are required in my spec_helper.rb:

config.gem 'notahat-machinist', :lib => 'machinist', :source =>
'http://gems.github.com'
require File.dirname(__FILE__) + '/blueprints'

or:

config.gem 'thoughtbot-factory_girl', :lib => 'factory_girl', :source
=> 'http://gems.github.com'
# automatically loaded from spec/factories/*.rb

Not sure where to look for a solution.


On Mar 29, 3:15?am, Andrew Vit <and... at avit.ca> wrote:
> On Mar 29, 1:40?am, Scott Taylor <sc... at railsnewbie.com> wrote:
>
> > Actually I meant poking around your app with a browser in dev mode ;)
>
> Ok, I get it, I wasn't sure what you were driving at! ;-) Yes,
> everything is reloading fine in the browser under development.
>
> > I'm pretty sure that rails will still try to run the test environment,
> > even with RAILS_ENV set to a different value, anyway.
>
> The RAILS_ENV is being set conditionally in my script files, except
> script/autospec where it isn't defined.
> ENV["RAILS_ENV"] ||= 'test'
>
> > I was thinking of any explicit requires which may occur in app/ and lib/.
>
> Nothing out of the ordinary...
>
> > AFAIK, this is more of a rails loading issue than an rspec one.
>
> I just tried this on a clean new rails app, and the reloading still
> doesn't work when running spec_server and autospec with --drb. It
> works fine when I'm not using spec_server, but then it reloads all of
> rails each time. Works fine, except when using spec_server.
>
> The rspec site says:
> [http://rspec.info/rails/runners.html]
>
> > Note that there are some classes and modules that, by default, won?t get reloaded
> > by Rails, which means they won?t be reloaded by spec_server. There are a number
> > of strategies available for coercing Rails to reload files every time in a given
> > environment. See the Rails documentation for more information.
>
> Does that include my app/models? I wouldn't have thought so... Another
> post on this mailing list seemed to suggest those don't need manual
> reloading and "just work".
>
> $ gem list rails
> rails (2.3.2)
> $ gem list rspec
> rspec (1.2.2)
> rspec-rails (1.2.2)
> $ rails test_spec_server && cd test_spec_server
> $ script/plugin install git://github.com/dchelimsky/rspec-rails.git
> $ script/generate rspec
> $ script/generate rspec_model car name:string
> # edit config/environments/test.rb => config.cache_classes = false
> # edit spec/spec.opts => --drb
> $ rake spec:server:start
> $ script/autospec
> # 1 example, 0 failures
> # edit app/models/car.rb => add invalid syntax!
> # 1 example, 0 failures
>
> Can anyone confirm/reproduce? (Or else tell me what I'm doing wrong?)
>
> Thanks,
> Andrew Vit
> _______________________________________________
> rspec-users mailing list
> rspec-us... at rubyforge.orghttp://rubyforge.org/mailman/listinfo/rspec-users

From zach.dennis at gmail.com  Sun Mar 29 22:43:57 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Sun, 29 Mar 2009 22:43:57 -0400
Subject: [rspec-users] Cucumber step definitions vs. RSpec examples
In-Reply-To: <000101c9afac$0fd828f0$2f887ad0$@com>
References: <000101c9afac$0fd828f0$2f887ad0$@com>
Message-ID: <85d99afe0903291943j7283c0b3lef9f4ba696f2fa0c@mail.gmail.com>

On Sat, Mar 28, 2009 at 9:49 AM, Brandon Olivares
<programmer2188 at gmail.com> wrote:
> Hi,
>
> So, I'm confused. I've been trying to use Cucumber and RSpec, but step
> definitions and RSpec examples just seem to be overlapping. What should go
> in either one of these?

Cucumber is intended to drive out the behaviour of the application and
RSpec is used to drive out the design and behaviour for the components
and objects that make up that application. Cucumber and RSpec are
bound to overlap. They're providing you insights at different levels
about how the application is expected to be working.

>
> For instance, let's say I'm testing if a form exists on a page. What goes in
> Cucumber and what goes in RSpec?

Does the scenario successfully drive the implementation of the form
and the page its on? If so, I would probably stick with the scenario.
However, if it doesn't then I drop down to a view spec and spec
whatever else the page needs that the scenario doesn't cover.

Scenarios usually don't communicate well the expectations against a
page for showing and hiding information, etc based on permissions or
roles. RSpec works great for this. It provides a wonderful way to
simply and concisely make each of those expectations clear rather than
some strange side-effect of a scenario which is focused on something
else.

>
> What I did for now is put Webrat methods in the step definitions, like
> fill_in, select, etc, without submitting since I'm not testing processing
> yet; and then put selector matchers in the RSpec examples.
>
> But I have no idea if that's right. How do you separate these and keep them
> from duplicating one another?

At some level duplication will happen, especially in a web app since
the way you verify the application is working is by
POSTing/GETting/etc and verifying output on the page itself AND it's
also what you have to do when you creating the individual views and
the controllers that make up those pages and respond to those
requests.

You may find that a scenario drives you to make a view with a form and
a controller with a #create action to process it. This may be adequate
and you may be able to confidently move forward without writing a view
spec or a controller spec. I know I have found this it the case many
times.

On the flip side, when something additional or conditional occurs that
is usually a good time to drive that with an example in a spec.

I use my scenarios to drive my app from the outside, and then specs to
drive the implementation for each of the underlying pieces. The more
I've practiced the easier and more natural it has become to know when
to do or not to do something. Also, the only way to not have something
feel like it's taking too long is to know your tools.  These things
won't just come because you want it to. It takes practice.
Remember to practice.

http://www.vimeo.com/3756344

-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From zach.dennis at gmail.com  Sun Mar 29 23:09:58 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Sun, 29 Mar 2009 23:09:58 -0400
Subject: [rspec-users] Cucumber step definitions vs. RSpec examples
In-Reply-To: <1fb4df0903291247q47d0a851q9f66f4b77a2e153c@mail.gmail.com>
References: <000101c9afac$0fd828f0$2f887ad0$@com>
	<1fb4df0903291247q47d0a851q9f66f4b77a2e153c@mail.gmail.com>
Message-ID: <85d99afe0903292009j41100946vfd9e0e6e512025d9@mail.gmail.com>

On Sun, Mar 29, 2009 at 3:47 PM, Stephen Eley <sfeley at gmail.com> wrote:
> On Sat, Mar 28, 2009 at 9:49 AM, Brandon Olivares
> <programmer2188 at gmail.com> wrote:
>>
>> So, I'm confused. I've been trying to use Cucumber and RSpec, but step
>> definitions and RSpec examples just seem to be overlapping. What should go
>> in either one of these?
>
> This is a subjective judgment call that doesn't have an absolute
> 'right' answer.  Ask a dozen programmers how they test and you're
> likely to get at least three dozen answers.
>
> I believe the purists would say that the duplication is a feature.
> The gist of this point of view is that RSpec's main strength is on the
> unit testing level: you want to test that model code works separate
> from your controller code, and your controller code separate from your
> view code.  Then if one fails, you know exactly what class went wrong
> and what to fix.
>
> Cucumber's main strength is on the acceptance or integration level:
> you want to make sure it all comes together correctly and creates the
> right application behavior, which is very hard to prove with unit
> testing alone.  But if you _only_ did Cucumber tests, your test to see
> if a form exists on a page (to use your example) would be too broad.
> If it failed, where do you look first?  Is the view broken?  The
> controller code?  Do you even have a model for the view to operate on?
>  Etc.
>
> So you need to have bot levels.  You specify your overall behavior
> with Cucumber, then you specify the isolated behaviors of the pieces
> to make that work, and then you write your code.  That's the
> full-round-trip, complete by-the-RSpec-book BDD answer.
>
> My own view...  Well, my view is that I've tried that and been driven
> nuts by it.  Writing specs for controllers and views can take me many
> times longer than writing the code.  Mocking out the models for
> controllers is frustrating and fragile to me, and view specs are just
> obvious and tedious.  I don't have any _fun_ writing those specs.  And
> if I'm not having fun, I find myself not motivated to program.
>
> So I stopped writing those specs, and now I mostly just write model
> specs and Cucumber features.  It usually doesn't take that long for me
> to look at a failing Cucumber test and figure out what went wrong --
> from the failure text, a stacktrace, or sometimes just manually
> running the action and eyeballing it.  Sometimes, if the controller
> action is unusual, I will write a spec for it, but only if my own
> instincts tell me it's warranted.  (Or if something failed in an odd
> way and I want to make sure that doesn't happen again.)
>
> That's my current answer based on past experience.  Next month I might
> have a different way of doing things.  I'm not going to make the case
> here that I'm right and you should never write controller/view specs
> for ordinary actions.  (If nothing else, doing it a bunch of times --
> and getting some things wrong, then fixing them -- is a great way to
> learn how controllers and views really work.)
>
> I think the real answer is to try it a few different ways, decide what
> works within your comfort level *and* leads to good code, and let
> yourself experiment.  And then, if you develop an effective working
> pattern down the road that you think makes good general sense, share
> it with the community as one more way of doing things.   >8->
>

I like a lot of what Steve is saying. To summarize and communicate in
my own way...

It is good to know how and when to do something. Like writing view
specs and controller specs. If you don't know how then you'll never
know when. Sometimes learning to take small steps seems ridiculous,
but it's by being able to work in small steps that you can be
confident about making larger ones.

Here are three questions I ask myself when I get frustrated:

 1 - Am I doing it wrong?
 2 - Should I be doing this in the first place?
 3 - Am I experiencing a skills deficiency?

Usually I think it's #1 and then I quickly jump to #2 when I don't get
it resolved in 5 minutes of googling. And then I find out a day later
it was because of #3 and I needed to go home and practice a little
more so I better understood what I was doing, why I was doing it, and
how I could leverage the tools to make it easier.

We all learn to make good decisions by first making bad ones, and
practice lets us do that w/o putting giant turds in an application's
production codebase.

-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From lists at ruby-forum.com  Mon Mar 30 00:19:27 2009
From: lists at ruby-forum.com (Zhenning Guan)
Date: Mon, 30 Mar 2009 06:19:27 +0200
Subject: [rspec-users] what is the context?
Message-ID: <ecb7624027079684eb3aed26c1502c74@ruby-forum.com>

describe MovieList do
  context "when first created" do
    it "should be empty" do
      movie_list = MovieList.new
      movie_list.should be_empty
    end
  end
end


what is the context work for?
-- 
Posted via http://www.ruby-forum.com/.

From dchelimsky at gmail.com  Mon Mar 30 00:42:11 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Sun, 29 Mar 2009 23:42:11 -0500
Subject: [rspec-users] what is the context?
In-Reply-To: <ecb7624027079684eb3aed26c1502c74@ruby-forum.com>
References: <ecb7624027079684eb3aed26c1502c74@ruby-forum.com>
Message-ID: <57c63afe0903292142k2d5902fdy29bdc98582af5ff9@mail.gmail.com>

On Sun, Mar 29, 2009 at 11:19 PM, Zhenning Guan <lists at ruby-forum.com> wrote:
> describe MovieList do
> ?context "when first created" do
> ? ?it "should be empty" do
> ? ? ?movie_list = MovieList.new
> ? ? ?movie_list.should be_empty
> ? ?end
> ?end
> end
>
>
> what is the context work for?

context() is an alias of describe(). They do the same thing, but they
read differently in your spec.

> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From matt at mattwynne.net  Mon Mar 30 03:35:31 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Mon, 30 Mar 2009 08:35:31 +0100
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <1fb4df0903291218o78799aj6e0b91d3fad5f802@mail.gmail.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
	<3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>
	<57c63afe0903270536r51e25c72v1e00616da3469fd@mail.gmail.com>
	<1fb4df0903271303w78a544besf8bcf97642b2c808@mail.gmail.com>
	<FF4E42E9-8135-426C-94F4-FB3D762640FB@gmail.com>
	<1fb4df0903291218o78799aj6e0b91d3fad5f802@mail.gmail.com>
Message-ID: <C633394C-3A61-4D98-9E5B-5C342EE91127@mattwynne.net>


On 29 Mar 2009, at 20:18, Stephen Eley wrote:

> # This line ensures that RSpec will run in the 'test' environment
> # regardless of defaults set by other tools.  If you have reasons to  
> run
> # specs in other environments, you can allow this value to be  
> overridden
> # by changing the line to:
> #
> # ENV['RAILS_ENV'] ||= 'test'


Just to explain: I think it was me who asked for this, though the  
change wasn't in generated code, it was in a file in rspec-rails that  
gets run when you require 'spec/rails'. We use a 'features'  
environment for running our features (so we can run them in parallel  
with specs) and it was causing some weird behaviour as the constant  
was changing under our feet as the features (which use some rspec- 
rails matchers) were run.

Matt Wynne
http://beta.songkick.com
http://blog.mattwynne.net




From matt at mattwynne.net  Mon Mar 30 03:39:57 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Mon, 30 Mar 2009 08:39:57 +0100
Subject: [rspec-users] [Rails] specifying that a layout yields?
In-Reply-To: <0396dca8-75a3-4856-8918-ebd3f3fd8099@e18g2000yqo.googlegroups.com>
References: <0396dca8-75a3-4856-8918-ebd3f3fd8099@e18g2000yqo.googlegroups.com>
Message-ID: <4415AC0B-C05D-4F7D-9DBD-A8E175BD8009@mattwynne.net>


On 29 Mar 2009, at 02:33, Brandt Kurowski wrote:

> I recently had a bug in a layout due to the layout not calling "yield"
> to display the actual content. I wanted to write a spec to describe
> what was missing, but it wasn't obvious how, so I just fixed the
> problem first and doubled back to spec it later.
>
> Anyway, the most succinct thing I was able to come up with was the
> following:
>
>  # http://gist.github.com/87246
>  describe "/layouts/application" do
>    it "should show the content" do
>      class << template
>        attr_accessor :did_render_content
>      end
>      template.did_render_content = false
>      render :inline => "<% self.did_render_content = true
> %>", :layout => 'application'
>      template.did_render_content.should be_true
>    end
>  end
>
> But I'm not quite satisfied with this, as it's not as clear and
> expressive as specs usually are. I thought I'd write a custom matcher
> for it, but it's not obvious to me what I'd even want the spec to look
> like.
>
> Any ideas?
>
> Thanks,
>
> Brandt

That's some pretty nifty code Brandt :)

Did you consider testing this aspect of the view's behaviour from a  
higher-level Cucumber acceptance test? I think that's what I would  
have probably done.

Matt Wynne
http://beta.songkick.com
http://blog.mattwynne.net




From apremdas at gmail.com  Mon Mar 30 05:41:42 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Mon, 30 Mar 2009 10:41:42 +0100
Subject: [rspec-users] [Cucumber] Bug with background
Message-ID: <88fd8ddc0903300241v329e9184p135d67d50eaa1d4d@mail.gmail.com>

Seem to be getting a problem when running a feature with background. Running
the whole file works fine however running an individual feature fails. The
background steps are

Background:
  Given an admin user Philip exists
  When I login as Philip
  Then I should be logged in as Philip


running the following scenario on its own causes an error

Scenario: Admin should be able to run a feed #
features/admin/manage_feeds.feature:23
    Given an admin user Philip exists    #
features/step_definitions/accounts/creation.steps.rb:66
      Validation failed: Login has already been taken, Email has already
been taken (ActiveRecord::RecordInvalid)

/Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:210:in
`generate!'

/Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:32:in
`spawn'

/Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:209:in
`/^I create a user with login (\w*)$/'
      features/admin/manage_feeds.feature:7:in `Given an admin user Philip
exists'
    Given there is 1 valid feed                #
features/step_definitions/admin/admin_supplier_feed.steps.rb:8

Now this only happens if there is at least one scenario in the file before
the tested scenario, so I'm speculating that when you run a feature using
'cucumber path/to/feature/feature:xx -r path/to/steps, then background is
not doing is

1) Running for preceding scenarios
2) Not clearing the database for a scenario run by line number

Wondering if anyone else can replicate this, or has any ideas about it
before I put this in lighthouse.

Cheers

Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090330/9f4c9bb8/attachment-0001.html>

From programmer2188 at gmail.com  Mon Mar 30 07:08:36 2009
From: programmer2188 at gmail.com (Brandon Olivares)
Date: Mon, 30 Mar 2009 07:08:36 -0400
Subject: [rspec-users] Cucumber step definitions vs. RSpec examples
In-Reply-To: <85d99afe0903292009j41100946vfd9e0e6e512025d9@mail.gmail.com>
References: <000101c9afac$0fd828f0$2f887ad0$@com>	<1fb4df0903291247q47d0a851q9f66f4b77a2e153c@mail.gmail.com>
	<85d99afe0903292009j41100946vfd9e0e6e512025d9@mail.gmail.com>
Message-ID: <000301c9b127$e0212800$a0637800$@com>



> -----Original Message-----
> From: rspec-users-bounces at rubyforge.org [mailto:rspec-users-
> bounces at rubyforge.org] On Behalf Of Zach Dennis
> Sent: Sunday, March 29, 2009 11:10 PM
> To: rspec-users
> Subject: Re: [rspec-users] Cucumber step definitions vs. RSpec examples
> > I like a lot of what Steve is saying. To summarize and communicate in
> my own way...
> 
> It is good to know how and when to do something. Like writing view
> specs and controller specs. If you don't know how then you'll never
> know when. Sometimes learning to take small steps seems ridiculous,
> but it's by being able to work in small steps that you can be
> confident about making larger ones.
> 
> Here are three questions I ask myself when I get frustrated:
> 
>  1 - Am I doing it wrong?
>  2 - Should I be doing this in the first place?
>  3 - Am I experiencing a skills deficiency?
> 
> Usually I think it's #1 and then I quickly jump to #2 when I don't get
> it resolved in 5 minutes of googling. And then I find out a day later
> it was because of #3 and I needed to go home and practice a little
> more so I better understood what I was doing, why I was doing it, and
> how I could leverage the tools to make it easier.
> 
> We all learn to make good decisions by first making bad ones, and
> practice lets us do that w/o putting giant turds in an application's
> production codebase.
> 

Thanks for that explanation.

For me, it's either TDD or BDD, honestly. I've experienced the assurance
having tests for nearly every line of code affords me, and don't want to
forgo that. But I like the semantics of BDD a lot better, after reading the
RSpec book.

Thanks,
Brandon


From aslak.hellesoy at gmail.com  Mon Mar 30 07:16:00 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Mon, 30 Mar 2009 13:16:00 +0200
Subject: [rspec-users] [Cucumber] Bug with background
In-Reply-To: <88fd8ddc0903300241v329e9184p135d67d50eaa1d4d@mail.gmail.com>
References: <88fd8ddc0903300241v329e9184p135d67d50eaa1d4d@mail.gmail.com>
Message-ID: <8d961d900903300416y27d6ceafn95779e0f84330ec4@mail.gmail.com>

2009/3/30 Andrew Premdas <apremdas at gmail.com>

> Seem to be getting a problem when running a feature with background.
> Running the whole file works fine however running an individual feature
> fails. The background steps are
>
> Background:
>   Given an admin user Philip exists
>   When I login as Philip
>   Then I should be logged in as Philip
>
>
> running the following scenario on its own causes an error
>
> Scenario: Admin should be able to run a feed #
> features/admin/manage_feeds.feature:23
>     Given an admin user Philip exists    #
> features/step_definitions/accounts/creation.steps.rb:66
>       Validation failed: Login has already been taken, Email has already
> been taken (ActiveRecord::RecordInvalid)
>
> /Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:210:in
> `generate!'
>
> /Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:32:in
> `spawn'
>
> /Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:209:in
> `/^I create a user with login (\w*)$/'
>       features/admin/manage_feeds.feature:7:in `Given an admin user Philip
> exists'
>     Given there is 1 valid feed                #
> features/step_definitions/admin/admin_supplier_feed.steps.rb:8
>
> Now this only happens if there is at least one scenario in the file before
> the tested scenario, so I'm speculating that when you run a feature using
> 'cucumber path/to/feature/feature:xx -r path/to/steps, then background is
> not doing is
>
> 1) Running for preceding scenarios
> 2) Not clearing the database for a scenario run by line number
>
> Wondering if anyone else can replicate this, or has any ideas about it
> before I put this in lighthouse.
>

Sounds like a bug. It would be wonderful if you could also provide some
files for us to put under examples/tickets/features to reproduce it. See
examples/tickets/features/246.feature for an example.

Cheers,
Aslak


>
> Cheers
>
> Andrew
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090330/1f7085e9/attachment.html>

From dchelimsky at gmail.com  Mon Mar 30 08:23:44 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 30 Mar 2009 07:23:44 -0500
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <C633394C-3A61-4D98-9E5B-5C342EE91127@mattwynne.net>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
	<3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>
	<57c63afe0903270536r51e25c72v1e00616da3469fd@mail.gmail.com>
	<1fb4df0903271303w78a544besf8bcf97642b2c808@mail.gmail.com>
	<FF4E42E9-8135-426C-94F4-FB3D762640FB@gmail.com>
	<1fb4df0903291218o78799aj6e0b91d3fad5f802@mail.gmail.com>
	<C633394C-3A61-4D98-9E5B-5C342EE91127@mattwynne.net>
Message-ID: <57c63afe0903300523u7854f17ev3b1ff06de2d2fdf5@mail.gmail.com>

On Mon, Mar 30, 2009 at 2:35 AM, Matt Wynne <matt at mattwynne.net> wrote:
>
> On 29 Mar 2009, at 20:18, Stephen Eley wrote:
>
>> # This line ensures that RSpec will run in the 'test' environment
>> # regardless of defaults set by other tools. ?If you have reasons to run
>> # specs in other environments, you can allow this value to be overridden
>> # by changing the line to:
>> #
>> # ENV['RAILS_ENV'] ||= 'test'
>
>
> Just to explain: I think it was me who asked for this, though the change
> wasn't in generated code, it was in a file in rspec-rails that gets run when
> you require 'spec/rails'. We use a 'features' environment for running our
> features (so we can run them in parallel with specs) and it was causing some
> weird behaviour as the constant was changing under our feet as the features
> (which use some rspec-rails matchers) were run.

What was the code doing to make the rspec-rails matchers available?
There's no reason you'd need to load 'spec/spec_helper.rb' to do that.

>
> Matt Wynne
> http://beta.songkick.com
> http://blog.mattwynne.net
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From zach.dennis at gmail.com  Mon Mar 30 09:56:46 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Mon, 30 Mar 2009 09:56:46 -0400
Subject: [rspec-users] [Rails] specifying that a layout yields?
In-Reply-To: <0396dca8-75a3-4856-8918-ebd3f3fd8099@e18g2000yqo.googlegroups.com>
References: <0396dca8-75a3-4856-8918-ebd3f3fd8099@e18g2000yqo.googlegroups.com>
Message-ID: <85d99afe0903300656x31b85f48ob381dd805c7ad68d@mail.gmail.com>

On Sat, Mar 28, 2009 at 9:33 PM, Brandt Kurowski
<brandtkurowski at gmail.com> wrote:
> I recently had a bug in a layout due to the layout not calling "yield"
> to display the actual content. I wanted to write a spec to describe
> what was missing, but it wasn't obvious how, so I just fixed the
> problem first and doubled back to spec it later.
>
> Anyway, the most succinct thing I was able to come up with was the
> following:
>
> ?# http://gist.github.com/87246
> ?describe "/layouts/application" do
> ? ?it "should show the content" do
> ? ? ?class << template
> ? ? ? ?attr_accessor :did_render_content
> ? ? ?end
> ? ? ?template.did_render_content = false
> ? ? ?render :inline => "<% self.did_render_content = true
> %>", :layout => 'application'
> ? ? ?template.did_render_content.should be_true
> ? ?end
> ?end
>
> But I'm not quite satisfied with this, as it's not as clear and
> expressive as specs usually are. I thought I'd write a custom matcher
> for it, but it's not obvious to me what I'd even want the spec to look
> like.
>
> Any ideas?

There's no need for a custom matcher. You just utilize the :layout
option that render has. e.g. the follow example ensures the layout
renders the content it is given (via a yield block):

describe "layouts/application.html.erb" do
  it "should render the context given" do
    render :text => "foobar", :layout => "layouts/application.html.erb"
    response.should include_text("foobar")
  end
end



>
> Thanks,
>
> Brandt
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From sfeley at gmail.com  Mon Mar 30 10:15:13 2009
From: sfeley at gmail.com (Stephen Eley)
Date: Mon, 30 Mar 2009 10:15:13 -0400
Subject: [rspec-users] Cucumber step definitions vs. RSpec examples
In-Reply-To: <000301c9b127$e0212800$a0637800$@com>
References: <000101c9afac$0fd828f0$2f887ad0$@com>
	<1fb4df0903291247q47d0a851q9f66f4b77a2e153c@mail.gmail.com>
	<85d99afe0903292009j41100946vfd9e0e6e512025d9@mail.gmail.com>
	<000301c9b127$e0212800$a0637800$@com>
Message-ID: <1fb4df0903300715r2f1e587dv74b17cbf7f32f983@mail.gmail.com>

On Mon, Mar 30, 2009 at 7:08 AM, Brandon Olivares
<programmer2188 at gmail.com> wrote:
>
> For me, it's either TDD or BDD, honestly. I've experienced the assurance
> having tests for nearly every line of code affords me, and don't want to
> forgo that. But I like the semantics of BDD a lot better, after reading the
> RSpec book.

Interesting.  I don't think what you're saying is invalid, but I do
think it's an _unusual_ perspective to consider TDD and BDD as an
either/or.  Depending on whom you ask, BDD is most often seen either
as an evolution/elaboration on TDD, or else the differences are viewed
as purely semantic.

Either way, though, by practicing BDD you're generally doing
everything you'd do in TDD.  You're still specifying
success-vs.-failure conditions before you write the code, and then
writing only the code necessary to achieve success.  Whether you call
those conditions 'behaviors' or 'tests' doesn't change that
fundamental pattern.


-- 
Have Fun,
   Steve Eley (sfeley at gmail.com)
   ESCAPE POD - The Science Fiction Podcast Magazine
   http://www.escapepod.org

From aslak.hellesoy at gmail.com  Mon Mar 30 11:14:02 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Mon, 30 Mar 2009 17:14:02 +0200
Subject: [rspec-users] [Cucumber] ANN: Cucumber 0.2.3
Message-ID: <8d961d900903300814g31f69415i9b18f4d5a79d059c@mail.gmail.com>

http://github.com/aslakhellesoy/cucumber/blob/142b1618616ca688308d4ddd7fa3203bc0f435a0/History.txt

Enjoy!

Aslak
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090330/eb582c5d/attachment.html>

From matt at mattwynne.net  Mon Mar 30 11:37:51 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Mon, 30 Mar 2009 16:37:51 +0100
Subject: [rspec-users] RSpec-rails 1.2.2: autospec passes but "rake
	spec" fails
In-Reply-To: <57c63afe0903300523u7854f17ev3b1ff06de2d2fdf5@mail.gmail.com>
References: <96708edb0903251216w6ed2c2e1qd3320e493557c2b4@mail.gmail.com>
	<0b7738d5bc7383d8d47a47ead73b2524@ruby-forum.com>
	<1fb4df0903251247p1d030ebdh457f7bdea6aa9a96@mail.gmail.com>
	<ecc0d27b7672d8c857a515de8d83ac82@ruby-forum.com>
	<3c30da400903251558p64381aa0s73ca651cc2ca5599@mail.gmail.com>
	<57c63afe0903270536r51e25c72v1e00616da3469fd@mail.gmail.com>
	<1fb4df0903271303w78a544besf8bcf97642b2c808@mail.gmail.com>
	<FF4E42E9-8135-426C-94F4-FB3D762640FB@gmail.com>
	<1fb4df0903291218o78799aj6e0b91d3fad5f802@mail.gmail.com>
	<C633394C-3A61-4D98-9E5B-5C342EE91127@mattwynne.net>
	<57c63afe0903300523u7854f17ev3b1ff06de2d2fdf5@mail.gmail.com>
Message-ID: <984FA046-8909-486F-9463-2A907D3BD2CF@mattwynne.net>


On 30 Mar 2009, at 13:23, David Chelimsky wrote:

> On Mon, Mar 30, 2009 at 2:35 AM, Matt Wynne <matt at mattwynne.net>  
> wrote:
>>
>> On 29 Mar 2009, at 20:18, Stephen Eley wrote:
>>
>>> # This line ensures that RSpec will run in the 'test' environment
>>> # regardless of defaults set by other tools.  If you have reasons  
>>> to run
>>> # specs in other environments, you can allow this value to be  
>>> overridden
>>> # by changing the line to:
>>> #
>>> # ENV['RAILS_ENV'] ||= 'test'
>>
>>
>> Just to explain: I think it was me who asked for this, though the  
>> change
>> wasn't in generated code, it was in a file in rspec-rails that gets  
>> run when
>> you require 'spec/rails'. We use a 'features' environment for  
>> running our
>> features (so we can run them in parallel with specs) and it was  
>> causing some
>> weird behaviour as the constant was changing under our feet as the  
>> features
>> (which use some rspec-rails matchers) were run.
>
> What was the code doing to make the rspec-rails matchers available?

require 'spec/rails'

> There's no reason you'd need to load 'spec/spec_helper.rb' to do that.

Maybe I'm getting two things mixed up, but I thought the change we  
were talking about here was this commit: http://github.com/dchelimsky/rspec-rails/commit/d6af98c1ffd992d81723fba70f5da9fbbb9e0a58

I didn't realise that the generated spec/spec_helper.rb file was also  
going something similar.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From scott at railsnewbie.com  Mon Mar 30 11:48:16 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Mon, 30 Mar 2009 11:48:16 -0400
Subject: [rspec-users] autospec fails but rake spec tasks pass
In-Reply-To: <22746792.post@talk.nabble.com>
References: <22746792.post@talk.nabble.com>
Message-ID: <19C7ADDF-2D12-4C21-9E5A-93A2E1D86B0A@railsnewbie.com>


On Mar 27, 2009, at 4:38 PM, jakepaul wrote:

>
> I can't figure out what is causing this problem. I'm using the  
> latest rspec
> and rspec-rails gems on rails 2.3.2.
>
> When I run autospec, the tests in the model spec that I am editing  
> will all
> fail. The error messages are like this:
>
> ActiveRecord::RecordInvalid in 'Job new record should create a new  
> record
> given valid attributes'
> Validation failed:
>
> (Nothing after Validation Failed:, just blank). It doesn't matter what
> attributes I pass to create the new model, and it doesn't matter if  
> I do it
> using a regular create! method or using Machinist, the same error  
> happens.
>
> Now, if I make a change, autospec will run the specs from that one  
> model
> spec again, and they will all pass. Then it runs all of my specs  
> again and
> that's when the specific spec I'm editing fails (only when it runs  
> all the
> specs). When I run rake spec:models or rake spec:controllers,  
> everything
> passes as it should. So I figured it might have something to do with  
> the
> controller specs, and if I remove those, autospec passes again. Then  
> if I
> put the controller specs back, autospec still passes. It only starts  
> failing
> if I again edit the model specs.
>
> This is happening in multiple models, not just one. It's making it
> impossible to work with, so I'd really appreciate any thoughts you  
> might
> have. Thank you!
>

Your problem is one of load order.

I'd suggest running the debugger at the start of your failing spec:

it "should ..." do
   require 'rubygems'; require 'ruby-debug'; debugger

   ...
end

Run the specs in the failing case, and debug from there.

Scott

From brandtkurowski at gmail.com  Mon Mar 30 11:25:30 2009
From: brandtkurowski at gmail.com (Brandt Kurowski)
Date: Mon, 30 Mar 2009 08:25:30 -0700 (PDT)
Subject: [rspec-users] [Rails] specifying that a layout yields?
In-Reply-To: <4415AC0B-C05D-4F7D-9DBD-A8E175BD8009@mattwynne.net>
References: <0396dca8-75a3-4856-8918-ebd3f3fd8099@e18g2000yqo.googlegroups.com>
	<4415AC0B-C05D-4F7D-9DBD-A8E175BD8009@mattwynne.net>
Message-ID: <c7400a5a-4add-47da-a406-3cffd2b48cfb@e3g2000vbe.googlegroups.com>

On Mar 30, 3:39 am, Matt Wynne <m... at mattwynne.net> wrote:
> On 29 Mar 2009, at 02:33, Brandt Kurowski wrote:
> > I recently had a bug in a layout due to the layout not calling "yield"
> > to display the actual content. I wanted to write a spec to describe
> > what was missing, but it wasn't obvious how, so I just fixed the
> > problem first and doubled back to spec it later.
>
> Did you consider testing this aspect of the view's behaviour from a
> higher-level Cucumber acceptance test? I think that's what I would
> have probably done.

Thanks Matt. It was actually a Cucumber feature that found the bug
(this is a new project that I've yet to actually open a browser on, I
think), so in that sense it's already covered. But I wanted to somehow
specify this very particular piece of behavior so that in the future
if someone breaks it, there's a spec that points right to the problem.
I think that if someone breaks my layout this way (e.g. accidentally
removing the yield in a future edit), most (all?) of my acceptance
tests will fail but it won't be immediately obvious why.

Brandt

From brandtkurowski at gmail.com  Mon Mar 30 11:29:34 2009
From: brandtkurowski at gmail.com (Brandt Kurowski)
Date: Mon, 30 Mar 2009 08:29:34 -0700 (PDT)
Subject: [rspec-users] [Rails] specifying that a layout yields?
In-Reply-To: <85d99afe0903300656x31b85f48ob381dd805c7ad68d@mail.gmail.com>
References: <0396dca8-75a3-4856-8918-ebd3f3fd8099@e18g2000yqo.googlegroups.com>
	<85d99afe0903300656x31b85f48ob381dd805c7ad68d@mail.gmail.com>
Message-ID: <d6d1bd2c-ca99-4f47-8a81-00ca74c1926a@e24g2000vbe.googlegroups.com>

On Mar 30, 9:56?am, Zach Dennis <zach.den... at gmail.com> wrote:
> On Sat, Mar 28, 2009 at 9:33 PM, Brandt Kurowski
> > ?#http://gist.github.com/87246
> > ?describe "/layouts/application" do
> > ? ?it "should show the content" do
> > ? ? ?class << template
> > ? ? ? ?attr_accessor :did_render_content
> > ? ? ?end
> > ? ? ?template.did_render_content = false
> > ? ? ?render :inline => "<% self.did_render_content = true
> > %>", :layout => 'application'
> > ? ? ?template.did_render_content.should be_true
> > ? ?end
> > ?end
>
> There's no need for a custom matcher. You just utilize the :layout
> option that render has. e.g. the follow example ensures the layout
> renders the content it is given (via a yield block):
>
> describe "layouts/application.html.erb" do
> ? it "should render the context given" do
> ? ? render :text => "foobar", :layout => "layouts/application.html.erb"
> ? ? response.should include_text("foobar")
> ? end
> end

Doh! Looks like I was so focused on the mechanism behind the failure
that I ended up writing my spec for the details of the implementation
rather than just the desired behavior. Thanks for pointing out what in
retrospect should've been obvious Zach.

Brandt

From dchelimsky at gmail.com  Mon Mar 30 12:55:02 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Mon, 30 Mar 2009 11:55:02 -0500
Subject: [rspec-users] autospec fails but rake spec tasks pass
In-Reply-To: <19C7ADDF-2D12-4C21-9E5A-93A2E1D86B0A@railsnewbie.com>
References: <22746792.post@talk.nabble.com>
	<19C7ADDF-2D12-4C21-9E5A-93A2E1D86B0A@railsnewbie.com>
Message-ID: <57c63afe0903300955o637ef59em767400be96392f0e@mail.gmail.com>

On Mon, Mar 30, 2009 at 10:48 AM, Scott Taylor <scott at railsnewbie.com> wrote:
>
> On Mar 27, 2009, at 4:38 PM, jakepaul wrote:
>
>>
>> I can't figure out what is causing this problem. I'm using the latest
>> rspec
>> and rspec-rails gems on rails 2.3.2.
>>
>> When I run autospec, the tests in the model spec that I am editing will
>> all
>> fail. The error messages are like this:
>>
>> ActiveRecord::RecordInvalid in 'Job new record should create a new record
>> given valid attributes'
>> Validation failed:
>>
>> (Nothing after Validation Failed:, just blank). It doesn't matter what
>> attributes I pass to create the new model, and it doesn't matter if I do
>> it
>> using a regular create! method or using Machinist, the same error happens.
>>
>> Now, if I make a change, autospec will run the specs from that one model
>> spec again, and they will all pass. Then it runs all of my specs again and
>> that's when the specific spec I'm editing fails (only when it runs all the
>> specs). When I run rake spec:models or rake spec:controllers, everything
>> passes as it should. So I figured it might have something to do with the
>> controller specs, and if I remove those, autospec passes again. Then if I
>> put the controller specs back, autospec still passes. It only starts
>> failing
>> if I again edit the model specs.
>>
>> This is happening in multiple models, not just one. It's making it
>> impossible to work with, so I'd really appreciate any thoughts you might
>> have. Thank you!
>>
>
> Your problem is one of load order.
>
> I'd suggest running the debugger at the start of your failing spec:
>
> it "should ..." do
> ?require 'rubygems'; require 'ruby-debug'; debugger
>
> ?...
> end

Or, if you're using rspec-1.2.2, just:

it "should ...." do
  debugger

and then use the --debugger option on the command line :)

Cheers,
David

>
> Run the specs in the failing case, and debug from there.
>
> Scott
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From THart at picagroup.com  Mon Mar 30 15:00:13 2009
From: THart at picagroup.com (Tim Hart)
Date: Mon, 30 Mar 2009 14:00:13 -0500
Subject: [rspec-users] Variable argument matchers for Cucumber
Message-ID: <C5F680ED.FD0F%THart@picagroup.com>

List,

Given a Cucumber script like

Then /^the (?:(first|second|third|fourth) line of the )?(.*) section of the (.*) should be (.*)$/ do |*args|
    #...
end

Cucumber errors with
expected 0 block argument(s), got 4 (Cucumber::ArityMismatchError)

While it's perfectly legal in generic ruby to do this

def foo(&block)
  block.call 1,2,3,4,5
end

foo do |*args|
  #...
End

Is this an intended limitation? I can work around it, but I'll end up with 2 different 'Then' calls that do nothing but call a common method
--
Tim Hart
Senior Software Engineer
PICA Group
615-713-9956 :cell
timothyjhart :Y!
tjhart at me.com :AIM

*****************************************************************************

Disclaimer: This electronic message may contain information that is Confidential or legally privileged. It is intended only for the use of the individual(s) and entity named in the message. If you are not an intended recipient of this message, please notify the sender immediately and delete the material from your computer. Do not deliver, distribute or copy this message and do not disclose its contents or take any action in reliance on the information it contains.

*****************************************************************************



From programmer2188 at gmail.com  Mon Mar 30 17:31:38 2009
From: programmer2188 at gmail.com (Brandon Olivares)
Date: Mon, 30 Mar 2009 17:31:38 -0400
Subject: [rspec-users] Cucumber step definitions vs. RSpec examples
In-Reply-To: <1fb4df0903300715r2f1e587dv74b17cbf7f32f983@mail.gmail.com>
References: <000101c9afac$0fd828f0$2f887ad0$@com>	<1fb4df0903291247q47d0a851q9f66f4b77a2e153c@mail.gmail.com>	<85d99afe0903292009j41100946vfd9e0e6e512025d9@mail.gmail.com>	<000301c9b127$e0212800$a0637800$@com>
	<1fb4df0903300715r2f1e587dv74b17cbf7f32f983@mail.gmail.com>
Message-ID: <009401c9b17e$eab97c70$c02c7550$@com>



> -----Original Message-----
> From: rspec-users-bounces at rubyforge.org [mailto:rspec-users-
> bounces at rubyforge.org] On Behalf Of Stephen Eley
> Sent: Monday, March 30, 2009 10:15 AM
> To: rspec-users
> Subject: Re: [rspec-users] Cucumber step definitions vs. RSpec examples
> 
> Interesting.  I don't think what you're saying is invalid, but I do
> think it's an _unusual_ perspective to consider TDD and BDD as an
> either/or.  Depending on whom you ask, BDD is most often seen either
> as an evolution/elaboration on TDD, or else the differences are viewed
> as purely semantic.
> 
> Either way, though, by practicing BDD you're generally doing
> everything you'd do in TDD.  You're still specifying
> success-vs.-failure conditions before you write the code, and then
> writing only the code necessary to achieve success.  Whether you call
> those conditions 'behaviors' or 'tests' doesn't change that
> fundamental pattern.
> 
> 

Yeah I guess I didn't express that quite right, and I see what you mean.
Either way, I mean I have to do some kind of test driven development, in
whatever form it is.

Brandon


From aslak.hellesoy at gmail.com  Mon Mar 30 17:37:29 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Mon, 30 Mar 2009 23:37:29 +0200
Subject: [rspec-users] Variable argument matchers for Cucumber
In-Reply-To: <C5F680ED.FD0F%THart@picagroup.com>
References: <C5F680ED.FD0F%THart@picagroup.com>
Message-ID: <8d961d900903301437k719d8866oaf1b12611d4378f@mail.gmail.com>

On Mon, Mar 30, 2009 at 9:00 PM, Tim Hart <THart at picagroup.com> wrote:

> List,
>
> Given a Cucumber script like
>
> Then /^the (?:(first|second|third|fourth) line of the )?(.*) section of the
> (.*) should be (.*)$/ do |*args|
>    #...
> end
>
> Cucumber errors with
> expected 0 block argument(s), got 4 (Cucumber::ArityMismatchError)
>
> While it's perfectly legal in generic ruby to do this
>
> def foo(&block)
>  block.call 1,2,3,4,5
> end
>
> foo do |*args|
>  #...
> End
>
> Is this an intended limitation? I can work around it, but I'll end up with
> 2 different 'Then' calls that do nothing but call a common method


It's intended. Let me explain with an example:

http://gist.github.com/87890

Ruby 1.8 doesn't know how to distinguish between a Proc with no args (and no
pipes) and a Proc with varargs. They both have arity -1. This means Cucumber
(while running on Ruby 1.8) can't really tell whether you forgot to define
any args or if you're deliberately using varargs. Since the first case is
more likely than the second, this is what Cucumber assumes.

I don't want to sacrifice this aide just so people can use varargs. The
benefit of getting help when you forget to define prog args outweighs the
drawback of not being able to use varargs.

That said, I'd like to make Cucumber smart enough to accept varargs on Ruby
1.9.

Does this sound like an OK compromise?

Aslak


>
> --
> Tim Hart
> Senior Software Engineer
> PICA Group
> 615-713-9956 :cell
> timothyjhart :Y!
> tjhart at me.com :AIM
>
>
> *****************************************************************************
>
> Disclaimer: This electronic message may contain information that is
> Confidential or legally privileged. It is intended only for the use of the
> individual(s) and entity named in the message. If you are not an intended
> recipient of this message, please notify the sender immediately and delete
> the material from your computer. Do not deliver, distribute or copy this
> message and do not disclose its contents or take any action in reliance on
> the information it contains.
>
>
> *****************************************************************************
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090330/e5137fe1/attachment-0001.html>

From aslak.hellesoy at gmail.com  Mon Mar 30 18:59:32 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Tue, 31 Mar 2009 00:59:32 +0200
Subject: [rspec-users] Variable argument matchers for Cucumber
In-Reply-To: <8d961d900903301437k719d8866oaf1b12611d4378f@mail.gmail.com>
References: <C5F680ED.FD0F%THart@picagroup.com>
	<8d961d900903301437k719d8866oaf1b12611d4378f@mail.gmail.com>
Message-ID: <8d961d900903301559q1d92a578k6dd537650f7f5846@mail.gmail.com>

On Mon, Mar 30, 2009 at 11:37 PM, aslak hellesoy
<aslak.hellesoy at gmail.com>wrote:

>
>
> On Mon, Mar 30, 2009 at 9:00 PM, Tim Hart <THart at picagroup.com> wrote:
>
>> List,
>>
>> Given a Cucumber script like
>>
>> Then /^the (?:(first|second|third|fourth) line of the )?(.*) section of
>> the (.*) should be (.*)$/ do |*args|
>>    #...
>> end
>>
>> Cucumber errors with
>> expected 0 block argument(s), got 4 (Cucumber::ArityMismatchError)
>>
>> While it's perfectly legal in generic ruby to do this
>>
>> def foo(&block)
>>  block.call 1,2,3,4,5
>> end
>>
>> foo do |*args|
>>  #...
>> End
>>
>> Is this an intended limitation? I can work around it, but I'll end up with
>> 2 different 'Then' calls that do nothing but call a common method
>
>
> It's intended. Let me explain with an example:
>
> http://gist.github.com/87890
>
> Ruby 1.8 doesn't know how to distinguish between a Proc with no args (and
> no pipes) and a Proc with varargs. They both have arity -1. This means
> Cucumber (while running on Ruby 1.8) can't really tell whether you forgot to
> define any args or if you're deliberately using varargs. Since the first
> case is more likely than the second, this is what Cucumber assumes.
>
> I don't want to sacrifice this aide just so people can use varargs. The
> benefit of getting help when you forget to define prog args outweighs the
> drawback of not being able to use varargs.
>
> That said, I'd like to make Cucumber smart enough to accept varargs on Ruby
> 1.9.
>
> Does this sound like an OK compromise?
>

You can use varargs now, but only on Ruby 1.9

http://github.com/aslakhellesoy/cucumber/commit/e58e1ed376b06204d48c52371b16f657630cd6ac

Aslak


>
> Aslak
>
>
>>
>> --
>> Tim Hart
>> Senior Software Engineer
>> PICA Group
>> 615-713-9956 :cell
>> timothyjhart :Y!
>> tjhart at me.com :AIM
>>
>>
>> *****************************************************************************
>>
>> Disclaimer: This electronic message may contain information that is
>> Confidential or legally privileged. It is intended only for the use of the
>> individual(s) and entity named in the message. If you are not an intended
>> recipient of this message, please notify the sender immediately and delete
>> the material from your computer. Do not deliver, distribute or copy this
>> message and do not disclose its contents or take any action in reliance on
>> the information it contains.
>>
>>
>> *****************************************************************************
>>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090331/6f7fc9a1/attachment.html>

From walketim at gmail.com  Mon Mar 30 19:29:53 2009
From: walketim at gmail.com (Tim Walker)
Date: Mon, 30 Mar 2009 17:29:53 -0600
Subject: [rspec-users] Variable argument matchers for Cucumber
In-Reply-To: <8d961d900903301437k719d8866oaf1b12611d4378f@mail.gmail.com>
References: <C5F680ED.FD0F%THart@picagroup.com>
	<8d961d900903301437k719d8866oaf1b12611d4378f@mail.gmail.com>
Message-ID: <1ebf5a4d0903301629p6da41c18xbf0a7301a6e889d@mail.gmail.com>

Howdy,

Just an observation, hope it's helpful...

>> I can work around it, but I'll end up with 2 different 'Then' calls that do nothing but call a common method

Not sure this is necessary. If you provide all the arguments in the
one step then you can test them for value ( blank?) in the one method.

--
Tim 2


2009/3/30 aslak hellesoy <aslak.hellesoy at gmail.com>:
>
>
> On Mon, Mar 30, 2009 at 9:00 PM, Tim Hart <THart at picagroup.com> wrote:
>>
>> List,
>>
>> Given a Cucumber script like
>>
>> Then /^the (?:(first|second|third|fourth) line of the )?(.*) section of
>> the (.*) should be (.*)$/ do |*args|
>> ? ?#...
>> end
>>
>> Cucumber errors with
>> expected 0 block argument(s), got 4 (Cucumber::ArityMismatchError)
>>
>> While it's perfectly legal in generic ruby to do this
>>
>> def foo(&block)
>> ?block.call 1,2,3,4,5
>> end
>>
>> foo do |*args|
>> ?#...
>> End
>>
>> Is this an intended limitation? I can work around it, but I'll end up with
>> 2 different 'Then' calls that do nothing but call a common method
>
> It's intended. Let me explain with an example:
>
> http://gist.github.com/87890
>
> Ruby 1.8 doesn't know how to distinguish between a Proc with no args (and no
> pipes) and a Proc with varargs. They both have arity -1. This means Cucumber
> (while running on Ruby 1.8) can't really tell whether you forgot to define
> any args or if you're deliberately using varargs. Since the first case is
> more likely than the second, this is what Cucumber assumes.
>
> I don't want to sacrifice this aide just so people can use varargs. The
> benefit of getting help when you forget to define prog args outweighs the
> drawback of not being able to use varargs.
>
> That said, I'd like to make Cucumber smart enough to accept varargs on Ruby
> 1.9.
>
> Does this sound like an OK compromise?
>
> Aslak
>
>>
>> --
>> Tim Hart
>> Senior Software Engineer
>> PICA Group
>> 615-713-9956 :cell
>> timothyjhart :Y!
>> tjhart at me.com :AIM
>>
>>
>> *****************************************************************************
>>
>> Disclaimer: This electronic message may contain information that is
>> Confidential or legally privileged. It is intended only for the use of the
>> individual(s) and entity named in the message. If you are not an intended
>> recipient of this message, please notify the sender immediately and delete
>> the material from your computer. Do not deliver, distribute or copy this
>> message and do not disclose its contents or take any action in reliance on
>> the information it contains.
>>
>>
>> *****************************************************************************
>>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From lists-rspec at shopwatch.org  Mon Mar 30 23:06:55 2009
From: lists-rspec at shopwatch.org (Jay Levitt)
Date: Mon, 30 Mar 2009 23:06:55 -0400
Subject: [rspec-users] [Cucumber] autotest+growl or similar?
Message-ID: <49D188CF.9030703@shopwatch.org>

I've got autotest 4.0.0 working with Cucumber 0.2.3 by following the 
Autotest Integration instructions in the wiki.  But I can't figure out a way 
to get automatically notified of the results, via growl or anything else:

- Cucumber doesn't trigger the :red and :green hooks in autotest.  (I think 
that's known, and referenced in #108[1]).

- autotest/growl doesn't seem to do anything anymore.

- autotest/pretty relies on the apparently-abandoned AquaTerm, and in any 
case, probably relies on the red/green hooks too.

- growl_glue doesn't understand Cucumber yet.

- RSpactor doesn't understand Cucumber yet.

Is there some other way on OS X to get a more concise dashboard or 
notification for Cucumber's autotest results?  Or do I have to [gasp] look 
at the output?

[1] 
https://rspec.lighthouseapp.com/projects/16211/tickets/108-add-support-for-autotest-red-green-hooks


From apremdas at gmail.com  Tue Mar 31 05:31:38 2009
From: apremdas at gmail.com (Andrew Premdas)
Date: Tue, 31 Mar 2009 10:31:38 +0100
Subject: [rspec-users] [Cucumber] Bug with background
In-Reply-To: <8d961d900903300416y27d6ceafn95779e0f84330ec4@mail.gmail.com>
References: <88fd8ddc0903300241v329e9184p135d67d50eaa1d4d@mail.gmail.com>
	<8d961d900903300416y27d6ceafn95779e0f84330ec4@mail.gmail.com>
Message-ID: <88fd8ddc0903310231n312940b4rbae3fc9df92ef47c@mail.gmail.com>

Submitted bug :
https://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/270-background-transactions-and-xx

Put some features and output in a gist that show this bug, hope its
sufficient.

All best

Andrew

2009/3/30 aslak hellesoy <aslak.hellesoy at gmail.com>

>
>
> 2009/3/30 Andrew Premdas <apremdas at gmail.com>
>
> Seem to be getting a problem when running a feature with background.
>> Running the whole file works fine however running an individual feature
>> fails. The background steps are
>>
>> Background:
>>   Given an admin user Philip exists
>>   When I login as Philip
>>   Then I should be logged in as Philip
>>
>>
>> running the following scenario on its own causes an error
>>
>> Scenario: Admin should be able to run a feed #
>> features/admin/manage_feeds.feature:23
>>     Given an admin user Philip exists    #
>> features/step_definitions/accounts/creation.steps.rb:66
>>       Validation failed: Login has already been taken, Email has already
>> been taken (ActiveRecord::RecordInvalid)
>>
>> /Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:210:in
>> `generate!'
>>
>> /Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:32:in
>> `spawn'
>>
>> /Users/andy/Sites/mvor/vendor/plugins/object_daddy/lib/object_daddy.rb:209:in
>> `/^I create a user with login (\w*)$/'
>>       features/admin/manage_feeds.feature:7:in `Given an admin user Philip
>> exists'
>>     Given there is 1 valid feed                #
>> features/step_definitions/admin/admin_supplier_feed.steps.rb:8
>>
>> Now this only happens if there is at least one scenario in the file before
>> the tested scenario, so I'm speculating that when you run a feature using
>> 'cucumber path/to/feature/feature:xx -r path/to/steps, then background is
>> not doing is
>>
>> 1) Running for preceding scenarios
>> 2) Not clearing the database for a scenario run by line number
>>
>> Wondering if anyone else can replicate this, or has any ideas about it
>> before I put this in lighthouse.
>>
>
> Sounds like a bug. It would be wonderful if you could also provide some
> files for us to put under examples/tickets/features to reproduce it. See
> examples/tickets/features/246.feature for an example.
>
> Cheers,
> Aslak
>
>
>>
>> Cheers
>>
>> Andrew
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090331/c7d2ba8d/attachment.html>

From joshuachisholm at gmail.com  Tue Mar 31 05:34:50 2009
From: joshuachisholm at gmail.com (Josh Chisholm)
Date: Tue, 31 Mar 2009 10:34:50 +0100
Subject: [rspec-users] [Cucumber] World { nil } causes undefined method
	`exception=' in backtraces from steps called from other steps
Message-ID: <1126d7ae0903310234g62bbef7cj73b8eedf57a6891f@mail.gmail.com>

We were using the following style of setting up a world:

World do
  def a_helper
    ...
  end
end

I don't know where I came up with that. I now realise we should have
been returning a world class here, but the above style seems to be
supported. Is it?

Anyway, we got away with it so far. And it still works after upgrading
cucumber to 0.2+, but when an exception is raised from a step that is
called by another step, we don't get a full backtrace through the step
definitions, but instead get this cryptic message:

undefined method `exception=' for nil:NilClass (NoMethodError)

Here's the full gist:
http://gist.github.com/87941

FWIW I made the weird message go away:
http://github.com/joshski/cucumber/commit/27a6f718451a417e9d42f9713911e6712aa48e8b

I suspect this solution is wrong because we weren't doing the right
thing. Obviously we can just return a world class like the wiki
suggests. If returning nil from the World block is unsupported, maybe
it should be caught early?

Cheers,

Josh

From lists at ruby-forum.com  Tue Mar 31 05:39:16 2009
From: lists at ruby-forum.com (Fernando Perez)
Date: Tue, 31 Mar 2009 11:39:16 +0200
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
Message-ID: <537533f3441d1651cb688abe73790685@ruby-forum.com>

Fernando Perez wrote:
> Hi,
> 
> Today is a big day. I officially transitioned from manually testing by
> clicking around in my app, to automated testing with RSpec + Autotest.

6 months since my initial post, what happened in between?

- My controllers are getting anorexic, and that's good. An action 
typically does only 1 call to a model and behind the scenes that model 
will make other calls to other models and do some fancy stuff, this used 
to happen in the controller which was bad. Now it has become so easy to 
write model specs.

- I don't spec controllers, because it's too painful to do. I don't spec 
views either, because I tweak them too often, and it would take me more 
time rewriting view specs then actually coding the views. If there is 
something to test for is the rendering of the css across browsers, 
because that's terrible!

- I use cucumber+webrat to test that some important public pages render 
without a 500 error. I don't care if the view has such div except if it 
is a critical one. What I mean is that I won't test, all the assignments 
that should be on the page, as some tutorials demonstrate. This is 
nearly impossible to maintain.

- I can refactor my code, immediately spot areas where my code got 
broken, and fix it. Before some parts of my app would be broken without 
having me knowing about it for a long time until some cool customers 
report a few bugs, but this was not an acceptable situation.

- I don't use Autotest, it sucks too much power, and it is too much 
distracting. From time to time I run specs to check if things look good, 
and always before updating the code on the server.

- I have written my own Factory. It's not OOP, it could be refactored, 
but it works 100% as advertised, provides default values, can handle 
associations, etc. I am pleased with it (I tried factory girl, 
machinist, etc and got pissed off). I encourage anyone to write his own 
little factory, to get a better hang of how to write good specs. I 
totally got mad with fixtures, it is impossible to maintain specs/tests 
with fixtures. Impossible.

- I don't do true BDD, i.e: I still write code before specs, because 
that's what motivates me. I consider that seeing my app living and 
writing code for my app more important than writing specs. Specs are 
still important, but only as a bug reporting tool, they don't add any 
value for the customer. In this crisis If I wanted an employee to resign 
by himself without paying him benefits (that's how it works in Europe), 
I would make him write specs all day long, and forbid him from seeing 
the app and play with it. He wouldn't last 1 week doing this.

What about you?


Best regards,
-- 
Posted via http://www.ruby-forum.com/.

From aslak.hellesoy at gmail.com  Tue Mar 31 06:34:08 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Tue, 31 Mar 2009 12:34:08 +0200
Subject: [rspec-users] [Cucumber] World { nil } causes undefined method
	`exception=' in backtraces from steps called from other steps
In-Reply-To: <1126d7ae0903310234g62bbef7cj73b8eedf57a6891f@mail.gmail.com>
References: <1126d7ae0903310234g62bbef7cj73b8eedf57a6891f@mail.gmail.com>
Message-ID: <8d961d900903310334gbdf724t57cfe749068595ca@mail.gmail.com>

On Tue, Mar 31, 2009 at 11:34 AM, Josh Chisholm <joshuachisholm at gmail.com>wrote:

> We were using the following style of setting up a world:
>
> World do
>  def a_helper
>    ...
>  end
> end
>
> I don't know where I came up with that. I now realise we should have
> been returning a world class here, but the above style seems to be
> supported. Is it?
>

The result of this block is nil, so that wouldn't work so well...
I'll add a guard against this so you get a better error message.


>
> Anyway, we got away with it so far. And it still works after upgrading
> cucumber to 0.2+, but when an exception is raised from a step that is
> called by another step, we don't get a full backtrace through the step
> definitions, but instead get this cryptic message:
>
> undefined method `exception=' for nil:NilClass (NoMethodError)
>
> Here's the full gist:
> http://gist.github.com/87941
>
> FWIW I made the weird message go away:
>
> http://github.com/joshski/cucumber/commit/27a6f718451a417e9d42f9713911e6712aa48e8b
>

That doesn't really solve the problem. It shouldn't be allowed to use the
nil singleton as a World since lots of modules would get mixed into it and
mess things up.


>
> I suspect this solution is wrong because we weren't doing the right
> thing. Obviously we can just return a world class like the wiki
> suggests. If returning nil from the World block is unsupported, maybe
> it should be caught early?
>

Done:
http://github.com/aslakhellesoy/cucumber/commit/6c7f039ac2874775558734108f40ed1c61e1466b

Aslak


>
> Cheers,
>
> Josh
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090331/3c7bbfbb/attachment.html>

From joshuachisholm at gmail.com  Tue Mar 31 07:10:43 2009
From: joshuachisholm at gmail.com (Josh Chisholm)
Date: Tue, 31 Mar 2009 12:10:43 +0100
Subject: [rspec-users] [Cucumber] World { nil } causes undefined method
	`exception=' in backtraces from steps called from other steps
In-Reply-To: <8d961d900903310334gbdf724t57cfe749068595ca@mail.gmail.com>
References: <1126d7ae0903310234g62bbef7cj73b8eedf57a6891f@mail.gmail.com>
	<8d961d900903310334gbdf724t57cfe749068595ca@mail.gmail.com>
Message-ID: <1126d7ae0903310410o3234a441s53359a8ff5477ac1@mail.gmail.com>

Great. Thanks!

2009/3/31 aslak hellesoy <aslak.hellesoy at gmail.com>:
>
>
> On Tue, Mar 31, 2009 at 11:34 AM, Josh Chisholm <joshuachisholm at gmail.com>
> wrote:
>>
>> We were using the following style of setting up a world:
>>
>> World do
>> ?def a_helper
>> ? ?...
>> ?end
>> end
>>
>> I don't know where I came up with that. I now realise we should have
>> been returning a world class here, but the above style seems to be
>> supported. Is it?
>
> The result of this block is nil, so that wouldn't work so well...
> I'll add a guard against this so you get a better error message.
>
>>
>> Anyway, we got away with it so far. And it still works after upgrading
>> cucumber to 0.2+, but when an exception is raised from a step that is
>> called by another step, we don't get a full backtrace through the step
>> definitions, but instead get this cryptic message:
>>
>> undefined method `exception=' for nil:NilClass (NoMethodError)
>>
>> Here's the full gist:
>> http://gist.github.com/87941
>>
>> FWIW I made the weird message go away:
>>
>> http://github.com/joshski/cucumber/commit/27a6f718451a417e9d42f9713911e6712aa48e8b
>
> That doesn't really solve the problem. It shouldn't be allowed to use the
> nil singleton as a World since lots of modules would get mixed into it and
> mess things up.
>
>>
>> I suspect this solution is wrong because we weren't doing the right
>> thing. Obviously we can just return a world class like the wiki
>> suggests. If returning nil from the World block is unsupported, maybe
>> it should be caught early?
>
> Done:
> http://github.com/aslakhellesoy/cucumber/commit/6c7f039ac2874775558734108f40ed1c61e1466b
>
> Aslak
>
>>
>> Cheers,
>>
>> Josh
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From lists at ruby-forum.com  Tue Mar 31 08:06:48 2009
From: lists at ruby-forum.com (Kevin Olbrich)
Date: Tue, 31 Mar 2009 14:06:48 +0200
Subject: [rspec-users] Getting the file a scenario is defined in (Cucumber)
Message-ID: <c7ca7f87a85ccd52f955d23805c56ec3@ruby-forum.com>

In Cucumber...
Is there a simple way to find out what file a scenario is defined in?

I'd like to use this information to load a set of fixtures depending on
which feature is being run.  So if I'm running the 'login.feature' file,
I'd like to be able to load the set of fixtures under
'/fixtures/login/*.yml'

_Kevin
-- 
Posted via http://www.ruby-forum.com/.

From phlip2005 at gmail.com  Tue Mar 31 08:19:45 2009
From: phlip2005 at gmail.com (Phlip)
Date: Tue, 31 Mar 2009 05:19:45 -0700
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <537533f3441d1651cb688abe73790685@ruby-forum.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
	<537533f3441d1651cb688abe73790685@ruby-forum.com>
Message-ID: <gqt1p3$9jf$1@ger.gmane.org>

Fernando Perez wrote:

> 6 months since my initial post, what happened in between?
> 
> - My controllers are getting anorexic, and that's good. An action 
> typically does only 1 call to a model and behind the scenes that model 
> will make other calls to other models and do some fancy stuff, this used 
> to happen in the controller which was bad. Now it has become so easy to 
> write model specs.

By "getting", do you mean new controllers arrive skinny? Or that you have 
refactored the same fat controllers, over time, until they are skinny?

The latter is preferred, because we should not be writing the same sites over 
and over again. In theory!

> - I don't spec controllers, because it's too painful to do. I don't spec 
> views either, because I tweak them too often, and it would take me more 
> time rewriting view specs then actually coding the views. If there is 
> something to test for is the rendering of the css across browsers, 
> because that's terrible!

We TDD, and refactor, the living shit out of controllers and views. Tools like 
assert_xhtml and form_test_helper make TDDing them easier than creating them by 
code-and-fix.

> - I use cucumber+webrat to test that some important public pages render 
> without a 500 error. I don't care if the view has such div except if it 
> is a critical one. What I mean is that I won't test, all the assignments 
> that should be on the page, as some tutorials demonstrate. This is 
> nearly impossible to maintain.

How often do you run your tests? Your editor should help you run them after 
every couple of edits. A lot of BDD is actually "cargo cult" "Test-Driven 
Development" (Google the terms independently to see what I mean).

Someone would get the benefits you describe doing just some of the TDD cycle, 
but if they left out other parts they might blame the views for the remaining 
irritations.

> - I can refactor my code, immediately spot areas where my code got 
> broken, and fix it. Before some parts of my app would be broken without 
> having me knowing about it for a long time until some cool customers 
> report a few bugs, but this was not an acceptable situation.

Right: Your car now has headlights, _and_ brakes. This means you can go faster.

> - I don't use Autotest, it sucks too much power, and it is too much 
> distracting. From time to time I run specs to check if things look good, 
> and always before updating the code on the server.

But you should _want_ to test every few edits. More important, you should be 
able to correctly predict the result of each run.

-- 
   Phlip


From mark at sabado.com  Tue Mar 31 08:36:13 2009
From: mark at sabado.com (Mark Lynn)
Date: Tue, 31 Mar 2009 08:36:13 -0400
Subject: [rspec-users] [Cucumber] Running single feature from command line
Message-ID: <15F72ADB-05BB-4904-8C2F-AD283BAE74D0@sabado.com>

I am using Cucumber 0.2.3 and am having problems running a single  
feature. In particular, the cucumber Textmate bundle was not working  
so I traced it back and discovered that I could not run single files  
or features from the command line either. My setup has the following  
line in cucumber.yml

default: -r features/support/env.rb -r features/support/plain.rb -r  
features/steps features/plain

When I run just plain cucumber from the command line, all my scenarios  
run and all features pass. However, if I try to run the command

cucumber -r features/support/env.rb -r features/support/plain.rb -r  
features/steps features/plain

OR

cucumber -r features/support/env.rb -r features/support/plain.rb -r  
features/steps features/plain/login.feature

I get

Failed to load features/support/env.rb	from /Library/Ruby/Site/1.8/ 
rubygems/custom_require.rb:31:in `polyglot_original_require'
	from /Library/Ruby/Gems/1.8/gems/polyglot-0.2.5/lib/polyglot.rb:54:in  
`require'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:144:in `invoke_requires'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:143:in `each'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:143:in `invoke_requires'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:104:in `initialize'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ 
ruby/1.8/optparse.rb:1291:in `call'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ 
ruby/1.8/optparse.rb:1291:in `parse_in_order'
	 ... 31 levels...
	from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/cucumber/ 
cli/main.rb:20:in `execute'
	from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
	from /usr/bin/cucumber:19:in `load'
	from /usr/bin/cucumber:19

I'm assuming the repeated use of the -r flag is not acceptable, but I  
need to specify multiple files. How can I get this to work from the  
command line so I can also use it in Textmate?

- Mark

Mark Lynn
Sabado Technologies





From joe at josephwilk.net  Tue Mar 31 09:26:08 2009
From: joe at josephwilk.net (Joseph Wilk)
Date: Tue, 31 Mar 2009 14:26:08 +0100
Subject: [rspec-users] [Cucumber] Running single feature from command
 line
In-Reply-To: <15F72ADB-05BB-4904-8C2F-AD283BAE74D0@sabado.com>
References: <15F72ADB-05BB-4904-8C2F-AD283BAE74D0@sabado.com>
Message-ID: <49D219F0.4020407@josephwilk.net>

Mark Lynn wrote:
> I am using Cucumber 0.2.3 and am having problems running a single 
> feature. In particular, the cucumber Textmate bundle was not working 
> so I traced it back and discovered that I could not run single files 
> or features from the command line either. My setup has the following 
> line in cucumber.yml
>
> default: -r features/support/env.rb -r features/support/plain.rb -r 
> features/steps features/plain
>
> When I run just plain cucumber from the command line, all my scenarios 
> run and all features pass. However, if I try to run the command
>
> cucumber -r features/support/env.rb -r features/support/plain.rb -r 
> features/steps features/plain
>
> OR
>
> cucumber -r features/support/env.rb -r features/support/plain.rb -r 
> features/steps features/plain/login.feature
>
> I get
>
> Failed to load features/support/env.rb    from 
> /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in 
> `polyglot_original_require'
>     from 
> /Library/Ruby/Gems/1.8/gems/polyglot-0.2.5/lib/polyglot.rb:54:in 
> `require'
>     from 
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:144:in 
> `invoke_requires'
>     from 
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:143:in 
> `each'
>     from 
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:143:in 
> `invoke_requires'
>     from 
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:104:in 
> `initialize'
>     from 
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1291:in 
> `call'
>     from 
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1291:in 
> `parse_in_order'
>      ... 31 levels...
>     from 
> /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/cucumber/cli/main.rb:20:in 
> `execute'
>     from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
>     from /usr/bin/cucumber:19:in `load'
>     from /usr/bin/cucumber:19
>
> I'm assuming the repeated use of the -r flag is not acceptable, but I 
> need to specify multiple files. 

Cucumber will accept multiple -r or --require. It simply pushes all the 
requires onto a stack and requires them all.

Looks like this is a polygot problem. Aslak recently forked and patched 
a copy of Treetop to avoid the dependency on this:

git://github.com/aslakhellesoy/treetop.git

I would suggest you try and install treetop from this source and see if 
that fixes the problem.

HTH
--
Joseph Wilk
http://blog.josephwilk.net

> How can I get this to work from the command line so I can also use it 
> in Textmate?
>
> - Mark
>
> Mark Lynn
> Sabado Technologies
>
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>


From aslak.hellesoy at gmail.com  Tue Mar 31 10:06:17 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Tue, 31 Mar 2009 16:06:17 +0200
Subject: [rspec-users] Getting the file a scenario is defined in
	(Cucumber)
In-Reply-To: <c7ca7f87a85ccd52f955d23805c56ec3@ruby-forum.com>
References: <c7ca7f87a85ccd52f955d23805c56ec3@ruby-forum.com>
Message-ID: <8d961d900903310706y1cef78d1qe22926ff26b4f1b7@mail.gmail.com>

On Tue, Mar 31, 2009 at 2:06 PM, Kevin Olbrich <lists at ruby-forum.com> wrote:

> In Cucumber...
> Is there a simple way to find out what file a scenario is defined in?
>

No, but there is a dirty way:

Before do |scenario|
  f = scenario.instance_variable_get('@feature')
  if f
    puts f.file
  end
end

The scenario variable will be a Scnario, ScenarioOutline or ExampleCells
instance. In the latter case there is no @feature ivar.
Please file a feature request (or better yet - a patch) if you want to see
this improved.

Also take a look at this ticket - maybe a cleaner way to achieve what you
want.
https://rspec.lighthouseapp.com/projects/16211/tickets/229-use-hooks-with-tags

Aslak


>
> I'd like to use this information to load a set of fixtures depending on
> which feature is being run.  So if I'm running the 'login.feature' file,
> I'd like to be able to load the set of fixtures under
> '/fixtures/login/*.yml'
>
> _Kevin
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090331/15ef11a8/attachment.html>

From lists at ruby-forum.com  Tue Mar 31 10:13:09 2009
From: lists at ruby-forum.com (Fernando Perez)
Date: Tue, 31 Mar 2009 16:13:09 +0200
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <gqt1p3$9jf$1@ger.gmane.org>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
	<537533f3441d1651cb688abe73790685@ruby-forum.com>
	<gqt1p3$9jf$1@ger.gmane.org>
Message-ID: <fd2fc179fb28a18ca91540d8c6d1f3fd@ruby-forum.com>

> By "getting", do you mean new controllers arrive skinny? Or that you 
> have
> refactored the same fat controllers, over time, until they are skinny?
> 
> The latter is preferred, because we should not be writing the same sites 
> over
> and over again. In theory!

My good ole' fat pig controllers, are now nice, slim and fancy :-)


> How often do you run your tests? Your editor should help you run them 
> after
> every couple of edits. A lot of BDD is actually "cargo cult" 

It depends. Overall I try to take small steps at a time. But never ever 
will I update the server code unless 100% specs pass!

> But you should _want_ to test every few edits. More important, you 
> should be
> able to correctly predict the result of each run.
As a habit I like to abuse of the save button even if I only corrected 
some typos in comments, or changed the indentation. Suddenly autotest 
would kick in for nothing.

Sometimes I save 4 files one after the other because I forgot about the 
keyboard short cut for saving them all at once, and autospec will run 4 
times instead of only once which is stupid. And growl will be notifying 
me each time which is very distracting.
-- 
Posted via http://www.ruby-forum.com/.

From mark at sabado.com  Tue Mar 31 10:31:54 2009
From: mark at sabado.com (Mark Lynn)
Date: Tue, 31 Mar 2009 10:31:54 -0400
Subject: [rspec-users] [Cucumber] Running single feature from command
	line
In-Reply-To: <49D219F0.4020407@josephwilk.net>
References: <15F72ADB-05BB-4904-8C2F-AD283BAE74D0@sabado.com>
	<49D219F0.4020407@josephwilk.net>
Message-ID: <EC5099E8-B070-4326-986A-427AA9FA765F@sabado.com>


Joseph,

Thanks - treetop did get me past the previous error message. Now, I get

$ cucumber -r features/support/env.rb -r features/support/plain.rb -r  
features/steps features/plain
/Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in  
`gem_original_require': no such file to load -- features/steps  
(LoadError)
Failed to load features/support/env.rb	from /Library/Ruby/Site/1.8/ 
rubygems/custom_require.rb:31:in `require'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:144:in `invoke_requires'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:143:in `each'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:143:in `invoke_requires'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:104:in `initialize'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ 
ruby/1.8/optparse.rb:1291:in `call'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ 
ruby/1.8/optparse.rb:1291:in `parse_in_order'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ 
ruby/1.8/optparse.rb:1247:in `catch'
	 ... 26 levels...
	from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/cucumber/ 
cli/main.rb:20:in `execute'
	from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
	from /usr/bin/cucumber:19:in `load'
	from /usr/bin/cucumber:19

It seems weird that these exact options work in the cucumber.yml file,  
but not from the command line. Any other thoughts?

  - Mark

Mark Lynn
Sabado Technologies



On Mar 31, 2009, at 9:26 AM, Joseph Wilk wrote:

> Mark Lynn wrote:
>> I am using Cucumber 0.2.3 and am having problems running a single  
>> feature. In particular, the cucumber Textmate bundle was not  
>> working so I traced it back and discovered that I could not run  
>> single files or features from the command line either. My setup has  
>> the following line in cucumber.yml
>>
>> default: -r features/support/env.rb -r features/support/plain.rb -r  
>> features/steps features/plain
>>
>> When I run just plain cucumber from the command line, all my  
>> scenarios run and all features pass. However, if I try to run the  
>> command
>>
>> cucumber -r features/support/env.rb -r features/support/plain.rb -r  
>> features/steps features/plain
>>
>> OR
>>
>> cucumber -r features/support/env.rb -r features/support/plain.rb -r  
>> features/steps features/plain/login.feature
>>
>> I get
>>
>> Failed to load features/support/env.rb    from /Library/Ruby/Site/ 
>> 1.8/rubygems/custom_require.rb:31:in `polyglot_original_require'
>>    from /Library/Ruby/Gems/1.8/gems/polyglot-0.2.5/lib/polyglot.rb: 
>> 54:in `require'
>>    from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:144:in `invoke_requires'
>>    from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:143:in `each'
>>    from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:143:in `invoke_requires'
>>    from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:104:in `initialize'
>>    from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/ 
>> lib/ruby/1.8/optparse.rb:1291:in `call'
>>    from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/ 
>> lib/ruby/1.8/optparse.rb:1291:in `parse_in_order'
>>     ... 31 levels...
>>    from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/ 
>> cucumber/cli/main.rb:20:in `execute'
>>    from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
>>    from /usr/bin/cucumber:19:in `load'
>>    from /usr/bin/cucumber:19
>>
>> I'm assuming the repeated use of the -r flag is not acceptable, but  
>> I need to specify multiple files.
>
> Cucumber will accept multiple -r or --require. It simply pushes all  
> the requires onto a stack and requires them all.
>
> Looks like this is a polygot problem. Aslak recently forked and  
> patched a copy of Treetop to avoid the dependency on this:
>
> git://github.com/aslakhellesoy/treetop.git
>
> I would suggest you try and install treetop from this source and see  
> if that fixes the problem.
>
> HTH
> --
> Joseph Wilk
> http://blog.josephwilk.net
>
>> How can I get this to work from the command line so I can also use  
>> it in Textmate?
>>
>> - Mark
>>
>> Mark Lynn
>> Sabado Technologies
>>
>>
>>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From mark at sabado.com  Tue Mar 31 11:22:39 2009
From: mark at sabado.com (Mark Lynn)
Date: Tue, 31 Mar 2009 11:22:39 -0400
Subject: [rspec-users] [Cucumber] Running single feature from command
	line
In-Reply-To: <49D219F0.4020407@josephwilk.net>
References: <15F72ADB-05BB-4904-8C2F-AD283BAE74D0@sabado.com>
	<49D219F0.4020407@josephwilk.net>
Message-ID: <1A5FBE8B-8D96-4990-889E-245D9BA7B261@sabado.com>


When I use Aslak's version of Treetop as Joseph suggested, this does  
get rid of the polyglot error. However, I still get the following when  
running from the command line:

$ cucumber -r features/steps -r features/support/env.rb features/plain/ 
user_home_page.feature
/Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in  
`gem_original_require': no such file to load -- features/steps  
(LoadError)
Failed to load features/support/env.rb	from /Library/Ruby/Site/1.8/ 
rubygems/custom_require.rb:31:in `require'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:144:in `invoke_requires'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:143:in `each'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:143:in `invoke_requires'
	from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
option_parser.rb:104:in `initialize'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ 
ruby/1.8/optparse.rb:1291:in `call'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ 
ruby/1.8/optparse.rb:1291:in `parse_in_order'
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ 
ruby/1.8/optparse.rb:1247:in `catch'
	 ... 26 levels...
	from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/cucumber/ 
cli/main.rb:20:in `execute'
	from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
	from /usr/bin/cucumber:19:in `load'
	from /usr/bin/cucumber:19

Any idea why rspec code is being called here? I did discover that if I  
uninstall cucumber 0.2.3 and try version 0.1.16, then the above  
command line works as does using the profile. I'm not sure if this  
indicates a bug in 0.2.3.

Mark Lynn
Sabado Technologies


On Mar 31, 2009, at 9:26 AM, Joseph Wilk wrote:

> Mark Lynn wrote:
>> I am using Cucumber 0.2.3 and am having problems running a single  
>> feature. In particular, the cucumber Textmate bundle was not  
>> working so I traced it back and discovered that I could not run  
>> single files or features from the command line either. My setup has  
>> the following line in cucumber.yml
>>
>> default: -r features/support/env.rb -r features/support/plain.rb -r  
>> features/steps features/plain
>>
>> When I run just plain cucumber from the command line, all my  
>> scenarios run and all features pass. However, if I try to run the  
>> command
>>
>> cucumber -r features/support/env.rb -r features/support/plain.rb -r  
>> features/steps features/plain
>>
>> OR
>>
>> cucumber -r features/support/env.rb -r features/support/plain.rb -r  
>> features/steps features/plain/login.feature
>>
>> I get
>>
>> Failed to load features/support/env.rb    from /Library/Ruby/Site/ 
>> 1.8/rubygems/custom_require.rb:31:in `polyglot_original_require'
>>    from /Library/Ruby/Gems/1.8/gems/polyglot-0.2.5/lib/polyglot.rb: 
>> 54:in `require'
>>    from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:144:in `invoke_requires'
>>    from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:143:in `each'
>>    from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:143:in `invoke_requires'
>>    from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:104:in `initialize'
>>    from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/ 
>> lib/ruby/1.8/optparse.rb:1291:in `call'
>>    from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/ 
>> lib/ruby/1.8/optparse.rb:1291:in `parse_in_order'
>>     ... 31 levels...
>>    from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/ 
>> cucumber/cli/main.rb:20:in `execute'
>>    from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
>>    from /usr/bin/cucumber:19:in `load'
>>    from /usr/bin/cucumber:19
>>
>> I'm assuming the repeated use of the -r flag is not acceptable, but  
>> I need to specify multiple files.
>
> Cucumber will accept multiple -r or --require. It simply pushes all  
> the requires onto a stack and requires them all.
>
> Looks like this is a polygot problem. Aslak recently forked and  
> patched a copy of Treetop to avoid the dependency on this:
>
> git://github.com/aslakhellesoy/treetop.git
>
> I would suggest you try and install treetop from this source and see  
> if that fixes the problem.
>
> HTH
> --
> Joseph Wilk
> http://blog.josephwilk.net
>
>> How can I get this to work from the command line so I can also use  
>> it in Textmate?
>>
>> - Mark
>>
>> Mark Lynn
>> Sabado Technologies
>>
>>
>>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From aslak.hellesoy at gmail.com  Tue Mar 31 11:56:46 2009
From: aslak.hellesoy at gmail.com (aslak hellesoy)
Date: Tue, 31 Mar 2009 17:56:46 +0200
Subject: [rspec-users] [Cucumber] Running single feature from command
	line
In-Reply-To: <1A5FBE8B-8D96-4990-889E-245D9BA7B261@sabado.com>
References: <15F72ADB-05BB-4904-8C2F-AD283BAE74D0@sabado.com>
	<49D219F0.4020407@josephwilk.net>
	<1A5FBE8B-8D96-4990-889E-245D9BA7B261@sabado.com>
Message-ID: <8d961d900903310856m1ad24751n6e13b105e1f2247@mail.gmail.com>

On Tue, Mar 31, 2009 at 5:22 PM, Mark Lynn <mark at sabado.com> wrote:

>
> When I use Aslak's version of Treetop as Joseph suggested, this does get
> rid of the polyglot error. However, I still get the following when running
> from the command line:
>
> $ cucumber -r features/steps -r features/support/env.rb
> features/plain/user_home_page.feature
> /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require': no such file to load -- features/steps (LoadError)
> Failed to load features/support/env.rb  from
> /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require'
>        from
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:144:in
> `invoke_requires'
>        from
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:143:in
> `each'
>        from
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:143:in
> `invoke_requires'
>        from
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:104:in
> `initialize'
>        from
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1291:in
> `call'
>        from
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1291:in
> `parse_in_order'
>        from
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1247:in
> `catch'
>         ... 26 levels...
>        from
> /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/cucumber/cli/main.rb:20:in
> `execute'
>        from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
>        from /usr/bin/cucumber:19:in `load'
>        from /usr/bin/cucumber:19
>
> Any idea why rspec code is being called here? I did discover that if I
> uninstall cucumber 0.2.3 and try version 0.1.16, then the above command line
> works as does using the profile. I'm not sure if this indicates a bug in
> 0.2.3.
>

It's actually a bug in RSpec that is only triggered in Cucumber 0.2
(bin/cucumber used to consume ARGV, but now leaves it intact, and RSpec
blows up).

https://rspec.lighthouseapp.com/projects/16211/tickets/200
https://rspec.lighthouseapp.com/projects/5645-rspec/tickets/767

Do you have a Rails app? See how Chris Flipse got around the error in the
#200 ticket.

Aslak


>
> Mark Lynn
> Sabado Technologies
>
>
> On Mar 31, 2009, at 9:26 AM, Joseph Wilk wrote:
>
>  Mark Lynn wrote:
>>
>>> I am using Cucumber 0.2.3 and am having problems running a single
>>> feature. In particular, the cucumber Textmate bundle was not working so I
>>> traced it back and discovered that I could not run single files or features
>>> from the command line either. My setup has the following line in
>>> cucumber.yml
>>>
>>> default: -r features/support/env.rb -r features/support/plain.rb -r
>>> features/steps features/plain
>>>
>>> When I run just plain cucumber from the command line, all my scenarios
>>> run and all features pass. However, if I try to run the command
>>>
>>> cucumber -r features/support/env.rb -r features/support/plain.rb -r
>>> features/steps features/plain
>>>
>>> OR
>>>
>>> cucumber -r features/support/env.rb -r features/support/plain.rb -r
>>> features/steps features/plain/login.feature
>>>
>>> I get
>>>
>>> Failed to load features/support/env.rb    from
>>> /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in
>>> `polyglot_original_require'
>>>   from /Library/Ruby/Gems/1.8/gems/polyglot-0.2.5/lib/polyglot.rb:54:in
>>> `require'
>>>   from
>>> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:144:in
>>> `invoke_requires'
>>>   from
>>> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:143:in
>>> `each'
>>>   from
>>> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:143:in
>>> `invoke_requires'
>>>   from
>>> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:104:in
>>> `initialize'
>>>   from
>>> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1291:in
>>> `call'
>>>   from
>>> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1291:in
>>> `parse_in_order'
>>>    ... 31 levels...
>>>   from
>>> /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/cucumber/cli/main.rb:20:in
>>> `execute'
>>>   from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
>>>   from /usr/bin/cucumber:19:in `load'
>>>   from /usr/bin/cucumber:19
>>>
>>> I'm assuming the repeated use of the -r flag is not acceptable, but I
>>> need to specify multiple files.
>>>
>>
>> Cucumber will accept multiple -r or --require. It simply pushes all the
>> requires onto a stack and requires them all.
>>
>> Looks like this is a polygot problem. Aslak recently forked and patched a
>> copy of Treetop to avoid the dependency on this:
>>
>> git://github.com/aslakhellesoy/treetop.git
>>
>> I would suggest you try and install treetop from this source and see if
>> that fixes the problem.
>>
>> HTH
>> --
>> Joseph Wilk
>> http://blog.josephwilk.net
>>
>>  How can I get this to work from the command line so I can also use it in
>>> Textmate?
>>>
>>> - Mark
>>>
>>> Mark Lynn
>>> Sabado Technologies
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090331/2a4408b5/attachment-0001.html>

From lists at ruby-forum.com  Tue Mar 31 12:08:11 2009
From: lists at ruby-forum.com (Fernando Perez)
Date: Tue, 31 Mar 2009 18:08:11 +0200
Subject: [rspec-users] Expecting nil or false
Message-ID: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>

Hi,

I just ran into this issue. I have a method that returns: false, true,
nil or an object.

This method is used by another method to test for true/false. In Ruby
that's easy to handle as nil and false evaluate to false, and everything
else evaluates to true, but RSpec seems to expect an exact value such as
nil, true, false, not_nil, etc.

Do I have to rewrite my return values to always return true or false?
-- 
Posted via http://www.ruby-forum.com/.

From dchelimsky at gmail.com  Tue Mar 31 12:29:18 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Tue, 31 Mar 2009 11:29:18 -0500
Subject: [rspec-users] Expecting nil or false
In-Reply-To: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>
References: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>
Message-ID: <57c63afe0903310929u6ed9b52ei32bf826096bb29f@mail.gmail.com>

On Tue, Mar 31, 2009 at 11:08 AM, Fernando Perez <lists at ruby-forum.com> wrote:
> Hi,
>
> I just ran into this issue. I have a method that returns: false, true,
> nil or an object.
>
> This method is used by another method to test for true/false. In Ruby
> that's easy to handle as nil and false evaluate to false, and everything
> else evaluates to true, but RSpec seems to expect an exact value such as
> nil, true, false, not_nil, etc.
>
> Do I have to rewrite my return values to always return true or false?

No, but you may have to use different matchers. What are you using?

> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From scott at railsnewbie.com  Tue Mar 31 12:35:04 2009
From: scott at railsnewbie.com (Scott Taylor)
Date: Tue, 31 Mar 2009 12:35:04 -0400
Subject: [rspec-users] Expecting nil or false
In-Reply-To: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>
References: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>
Message-ID: <DAFC698D-EBBC-4043-9346-2E8015B4A468@railsnewbie.com>


On Mar 31, 2009, at 12:08 PM, Fernando Perez wrote:

> Hi,
>
> I just ran into this issue. I have a method that returns: false, true,
> nil or an object.
>
> This method is used by another method to test for true/false. In Ruby
> that's easy to handle as nil and false evaluate to false, and  
> everything
> else evaluates to true, but RSpec seems to expect an exact value  
> such as
> nil, true, false, not_nil, etc.

Use the boolean matchers:

def foo?
   nil
end

obj.should be_foo #=> fails
obj.should_not be_foo  #=> passes

Scott


>
>
> Do I have to rewrite my return values to always return true or false?
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users


From bcolfer at shopping.com  Tue Mar 31 12:34:06 2009
From: bcolfer at shopping.com (Colfer, Brian)
Date: Tue, 31 Mar 2009 09:34:06 -0700
Subject: [rspec-users] Expecting nil or false
In-Reply-To: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>
References: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>
Message-ID: <8B4F0C16-4552-4E26-8819-078F463264A8@shopping.com>

What about variable.nil? == true

Sent from Brian's iPhone

On Mar 31, 2009, at 9:26 AM, "Fernando Perez" <lists at ruby-forum.com>  
wrote:

> Hi,
>
> I just ran into this issue. I have a method that returns: false, true,
> nil or an object.
>
> This method is used by another method to test for true/false. In Ruby
> that's easy to handle as nil and false evaluate to false, and  
> everything
> else evaluates to true, but RSpec seems to expect an exact value  
> such as
> nil, true, false, not_nil, etc.
>
> Do I have to rewrite my return values to always return true or false?
> -- 
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

From joe at josephwilk.net  Tue Mar 31 12:48:24 2009
From: joe at josephwilk.net (Joseph Wilk)
Date: Tue, 31 Mar 2009 17:48:24 +0100
Subject: [rspec-users] [Cucumber] Running single feature from command
 line
In-Reply-To: <1A5FBE8B-8D96-4990-889E-245D9BA7B261@sabado.com>
References: <15F72ADB-05BB-4904-8C2F-AD283BAE74D0@sabado.com>	<49D219F0.4020407@josephwilk.net>
	<1A5FBE8B-8D96-4990-889E-245D9BA7B261@sabado.com>
Message-ID: <49D24958.4060606@josephwilk.net>

Mark Lynn wrote:
>
> When I use Aslak's version of Treetop as Joseph suggested, this does 
> get rid of the polyglot error. However, I still get the following when 
> running from the command line:
>
> $ cucumber -r features/steps -r features/support/env.rb 
> features/plain/user_home_page.feature
> /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in 
> `gem_original_require': no such file to load -- features/steps 
> (LoadError)
> Failed to load features/support/env.rb    from 
> /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in `require'
>     from 
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:144:in 
> `invoke_requires'
>     from 
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:143:in 
> `each'
>     from 
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:143:in 
> `invoke_requires'
>     from 
> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:104:in 
> `initialize'
>     from 
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1291:in 
> `call'
>     from 
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1291:in 
> `parse_in_order'
>     from 
> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1247:in 
> `catch'
>      ... 26 levels...
>     from 
> /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/cucumber/cli/main.rb:20:in 
> `execute'
>     from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
>     from /usr/bin/cucumber:19:in `load'
>     from /usr/bin/cucumber:19
>
Just a gut feeling but try:

cucumber -r features/steps/ -r features/support/env.rb 
features/plain/user_home_page.feature

> Any idea why rspec code is being called here? I did discover that if I 
> uninstall cucumber 0.2.3 and try version 0.1.16, then the above 
> command line works as does using the profile. I'm not sure if this 
> indicates a bug in 0.2.3.
>
> Mark Lynn
> Sabado Technologies
>
>
> On Mar 31, 2009, at 9:26 AM, Joseph Wilk wrote:
>
>> Mark Lynn wrote:
>>> I am using Cucumber 0.2.3 and am having problems running a single 
>>> feature. In particular, the cucumber Textmate bundle was not working 
>>> so I traced it back and discovered that I could not run single files 
>>> or features from the command line either. My setup has the following 
>>> line in cucumber.yml
>>>
>>> default: -r features/support/env.rb -r features/support/plain.rb -r 
>>> features/steps features/plain
>>>
>>> When I run just plain cucumber from the command line, all my 
>>> scenarios run and all features pass. However, if I try to run the 
>>> command
>>>
>>> cucumber -r features/support/env.rb -r features/support/plain.rb -r 
>>> features/steps features/plain
>>>
>>> OR
>>>
>>> cucumber -r features/support/env.rb -r features/support/plain.rb -r 
>>> features/steps features/plain/login.feature
>>>
>>> I get
>>>
>>> Failed to load features/support/env.rb    from 
>>> /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in 
>>> `polyglot_original_require'
>>>    from 
>>> /Library/Ruby/Gems/1.8/gems/polyglot-0.2.5/lib/polyglot.rb:54:in 
>>> `require'
>>>    from 
>>> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:144:in 
>>> `invoke_requires'
>>>    from 
>>> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:143:in 
>>> `each'
>>>    from 
>>> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:143:in 
>>> `invoke_requires'
>>>    from 
>>> /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/option_parser.rb:104:in 
>>> `initialize'
>>>    from 
>>> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1291:in 
>>> `call'
>>>    from 
>>> /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/optparse.rb:1291:in 
>>> `parse_in_order'
>>>     ... 31 levels...
>>>    from 
>>> /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/cucumber/cli/main.rb:20:in 
>>> `execute'
>>>    from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
>>>    from /usr/bin/cucumber:19:in `load'
>>>    from /usr/bin/cucumber:19
>>>
>>> I'm assuming the repeated use of the -r flag is not acceptable, but 
>>> I need to specify multiple files.
>>
>> Cucumber will accept multiple -r or --require. It simply pushes all 
>> the requires onto a stack and requires them all.
>>
>> Looks like this is a polygot problem. Aslak recently forked and 
>> patched a copy of Treetop to avoid the dependency on this:
>>
>> git://github.com/aslakhellesoy/treetop.git
>>
>> I would suggest you try and install treetop from this source and see 
>> if that fixes the problem.
>>
>> HTH
>> -- 
>> Joseph Wilk
>> http://blog.josephwilk.net
>>
>>> How can I get this to work from the command line so I can also use 
>>> it in Textmate?
>>>
>>> - Mark
>>>
>>> Mark Lynn
>>> Sabado Technologies
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> rspec-users mailing list
>>> rspec-users at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/rspec-users
>>>
>>
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>


From aslak.hellesoy at gmail.com  Tue Mar 31 12:48:28 2009
From: aslak.hellesoy at gmail.com (=?utf-8?Q?Aslak_Helles=C3=B8y?=)
Date: Tue, 31 Mar 2009 18:48:28 +0200
Subject: [rspec-users] Expecting nil or false
In-Reply-To: <8B4F0C16-4552-4E26-8819-078F463264A8@shopping.com>
References: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>
	<8B4F0C16-4552-4E26-8819-078F463264A8@shopping.com>
Message-ID: <A8EE4226-A2D2-46F2-B2D3-D8B1A5C3E924@gmail.com>



Den 31. mars. 2009 kl. 18.34 skrev "Colfer, Brian"  
<bcolfer at shopping.com>:

> What about variable.nil? == true
>
No, that will not raise anything.

x.should == nil
Or
X.should be_nil
Ditto for false and true.

What have you been trying?

Aslak
> Sent from Brian's iPhone
>
> On Mar 31, 2009, at 9:26 AM, "Fernando Perez" <lists at ruby-forum.com>  
> wrote:
>
>> Hi,
>>
>> I just ran into this issue. I have a method that returns: false,  
>> true,
>> nil or an object.
>>
>> This method is used by another method to test for true/false. In Ruby
>> that's easy to handle as nil and false evaluate to false, and  
>> everything
>> else evaluates to true, but RSpec seems to expect an exact value  
>> such as
>> nil, true, false, not_nil, etc.
>>
>> Do I have to rewrite my return values to always return true or false?
>> -- 
>> Posted via http://www.ruby-forum.com/.
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

From pablolmiranda at gmail.com  Tue Mar 31 13:00:11 2009
From: pablolmiranda at gmail.com (Pablo L. de Miranda)
Date: Tue, 31 Mar 2009 14:00:11 -0300
Subject: [rspec-users] Good introduction to rspec
Message-ID: <2b1500990903311000r618ca3bahae123596df3b012c@mail.gmail.com>

Hi guys,
Someone know some good introduction to rspec, I`m wanting to use Rspec with
my Rails projects, but I don't found a good introduction.

Att,

Pablo Lacerda de Miranda
pablolmiranda at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090331/41aeb0e0/attachment.html>

From zach.dennis at gmail.com  Tue Mar 31 13:10:44 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Tue, 31 Mar 2009 13:10:44 -0400
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <537533f3441d1651cb688abe73790685@ruby-forum.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
	<537533f3441d1651cb688abe73790685@ruby-forum.com>
Message-ID: <85d99afe0903311010w62cb7e1bsa094d76480110c7a@mail.gmail.com>

On Tue, Mar 31, 2009 at 5:39 AM, Fernando Perez <lists at ruby-forum.com> wrote:
> Fernando Perez wrote:
>> Hi,
>>
>> Today is a big day. I officially transitioned from manually testing by
>> clicking around in my app, to automated testing with RSpec + Autotest.
>
> 6 months since my initial post, what happened in between?
>
> - My controllers are getting anorexic, and that's good. An action
> typically does only 1 call to a model and behind the scenes that model
> will make other calls to other models and do some fancy stuff, this used
> to happen in the controller which was bad. Now it has become so easy to
> write model specs.

Great! Keeping controllers simple makes life better on many fronts.

>
> - I don't spec controllers, because it's too painful to do. I don't spec
> views either, because I tweak them too often, and it would take me more
> time rewriting view specs then actually coding the views. If there is
> something to test for is the rendering of the css across browsers,
> because that's terrible!

I usually let Cucumber run through the basics of the action, but I
write controller specs for interesting thing that affect the behaviour
of an action such as requiring logic, or a certain permission, or
special error handling logic, etc. Pulling these things out into a
controller macro makes re-using them extremely simple. The next beta
release for The RSpec Book will cover doing that.

I write view specs because they *change* so much. I don't spec the
structure of the page, just the semantics of it as it pertains to
information I programmatically display or don't display. IME, when
apps are small there is a feeling that Cucumber can do it all, but as
the app grows Cucumber can be a burden as well. Cucumber scenarios
can't do it all, and when you have interesting apps, hundreds of
scenarios and hundreds of steps it becomes way too time consuming to
try to find exactly what and why things died and why. I prefer focused
view specs for this regression rather than simply relying on Cucumber.
 Also cucumber step definitions can become large and unwieldy. I like
focused steps which do enough to prove a scenario works as expected
and I like to drop down to specs for the details of it.

>
> - I use cucumber+webrat to test that some important public pages render
> without a 500 error. I don't care if the view has such div except if it
> is a critical one. What I mean is that I won't test, all the assignments
> that should be on the page, as some tutorials demonstrate. This is
> nearly impossible to maintain.

I disagree with the last two sentences here. I build my views spec
first with examples that expect the result of "project.name" to be on
the page. Only then do I actually add it to the view. I have had no
issue maintaining this. Not only do I get a design benefit when its
not just a simple model attribute, but perhaps a calculated field, I
also get regression for free. I move swiftly, happily, and confidently
on without worrying about manually verifying everything on the page is
as it should be, I let my specs do that.

>
> - I can refactor my code, immediately spot areas where my code got
> broken, and fix it. Before some parts of my app would be broken without
> having me knowing about it for a long time until some cool customers
> report a few bugs, but this was not an acceptable situation.

IMO, this is the case when people don't write view specs. Unless
someone's Cucumber scenario covers everything on the view (which they
don't unless its a super simple CRUD app). Half the time I wonder if
people even know if their views are displaying the write things on the
page over time. How would they not know w/o specs? Do they manually
verify every page every time they deploy? That seems impossible to
maintain.

>
> - I don't use Autotest, it sucks too much power, and it is too much
> distracting. From time to time I run specs to check if things look good,
> and always before updating the code on the server.

Agreed. I loathe autotest, but I don't run specs time to time, I run
my specs all the time. It's a part of my development process. Red
Green Refactor. It's not just a mantra, its a discipline. Although
when I don't know what I want or need to do, I spike something
(without any tests), and once I figure it out I scrape the spike (or
comment it out) and drive it with examples.

>
> - I have written my own Factory. It's not OOP, it could be refactored,
> but it works 100% as advertised, provides default values, can handle
> associations, etc. I am pleased with it (I tried factory girl,
> machinist, etc and got pissed off). I encourage anyone to write his own
> little factory, to get a better hang of how to write good specs. I
> totally got mad with fixtures, it is impossible to maintain specs/tests
> with fixtures. Impossible.

Cool. Is it on github? I wrote my own as well, but then switched to
FactoryGirl because everyone I talked to loved it, but now I wonder if
they really loved it (or how much they actually use it) because it
works for about 80% of the things I need, and fails horribly for the
other 20%. I want to try Machinist next, but I'm sad to see you had
bad experiences with it. :(

And I hate the idea behind ObjectDaddy, adding methods to the model to
generate spec data. Gross.

> - I don't do true BDD, i.e: I still write code before specs, because
> that's what motivates me. I consider that seeing my app living and
> writing code for my app more important than writing specs. Specs are
> still important, but only as a bug reporting tool, they don't add any
> value for the customer. In this crisis If I wanted an employee to resign
> by himself without paying him benefits (that's how it works in Europe),
> I would make him write specs all day long, and forbid him from seeing
> the app and play with it. He wouldn't last 1 week doing this.
>
> What about you?
>

You've probably seen this, but it never gets old, "Testing is for
testers." When you focus on specs solely for the benefit of testing
then you are only getting the tip of the ice berg. Traditional "tests"
are really they to provide safeguard against regression. This is a
secondary benefit to BDD. BDD is about driving your app from the
outside in, focusing on the behaviour at different levels.

For example, Cucumber lets you focus on the app behaviour, while view
specs lets you focus on the expected behaviour of a view (to display
"project.name"), and controller specs let you focus on the behaviour
of a controller (such that only "admins" can destroy a project), and
model specs let you provide examples for how it should be working.
Focusing on the behaviour at these different levels forces you to
write better designed code, more focused objects, simpler controllers,
just-the-right size models, etc.

A better design lets you move fluidly through the app as it evolves
and changes. When you use BDD, you get a better design as a part of
the process. As a nice secondary benefit you get protection against
unwanted regression.

I encourage you and anyone else to practice your BDD more. The more I
practice the more fluently I can drive my app with examples form the
outside-in, and the more capable I am to know when to write a
controller spec and when not to---and it's not based on if it takes
too long. The decision is based on experience for knowing how-to do
it, and how-to do it well, and then asking myself, "Does this get me
anything?"

Not spe'cing something because you don't know how-to spec it well is
most likely not an issue with BDD. It's a skill deficiency with the
developer. The only way to make good decisions it practice and become
more familiar with your tools. Then you will start making informed
decisions that add value to your project. The alternative is that you
make uninformed decisions and you or other developers will suffer down
the road because you made a bad decision but didn't know it because
you lacked the knowledge and/or experience to know it was a bad
decision.


>
> Best regards,
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From lists at ruby-forum.com  Tue Mar 31 13:11:00 2009
From: lists at ruby-forum.com (Fernando Perez)
Date: Tue, 31 Mar 2009 19:11:00 +0200
Subject: [rspec-users] Expecting nil or false
In-Reply-To: <57c63afe0903310929u6ed9b52ei32bf826096bb29f@mail.gmail.com>
References: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>
	<57c63afe0903310929u6ed9b52ei32bf826096bb29f@mail.gmail.com>
Message-ID: <21431c5c1b46eb031b47bd22a59f5c28@ruby-forum.com>


>> Do I have to rewrite my return values to always return true or false?
> No, but you may have to use different matchers. What are you using?

I use: should be_false

Rspec complains it receives nil when it is expecting false.
-- 
Posted via http://www.ruby-forum.com/.

From phlip2005 at gmail.com  Tue Mar 31 13:16:14 2009
From: phlip2005 at gmail.com (Phlip)
Date: Tue, 31 Mar 2009 10:16:14 -0700
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <fd2fc179fb28a18ca91540d8c6d1f3fd@ruby-forum.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>	<537533f3441d1651cb688abe73790685@ruby-forum.com>	<gqt1p3$9jf$1@ger.gmane.org>
	<fd2fc179fb28a18ca91540d8c6d1f3fd@ruby-forum.com>
Message-ID: <gqtj4v$9ab$1@ger.gmane.org>

Fernando Perez wrote:

> As a habit I like to abuse of the save button even if I only corrected 
> some typos in comments, or changed the indentation. Suddenly autotest 
> would kick in for nothing.

Autotest sucks. If we have too many tests, it runs them all, and this slows us down.

Our editor support for TDD also sucks. It should run the most recently edited 
test cases, nearly automatically. Everyone swears by Textmate, and it simply 
can't do that. Then, the Java-based editors also can't do it!


From dchelimsky at gmail.com  Tue Mar 31 13:19:32 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Tue, 31 Mar 2009 12:19:32 -0500
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <gqtj4v$9ab$1@ger.gmane.org>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
	<537533f3441d1651cb688abe73790685@ruby-forum.com>
	<gqt1p3$9jf$1@ger.gmane.org>
	<fd2fc179fb28a18ca91540d8c6d1f3fd@ruby-forum.com>
	<gqtj4v$9ab$1@ger.gmane.org>
Message-ID: <57c63afe0903311019j32cac981td160a7b97a8798c9@mail.gmail.com>

On Tue, Mar 31, 2009 at 12:16 PM, Phlip <phlip2005 at gmail.com> wrote:
> Fernando Perez wrote:
>
>> As a habit I like to abuse of the save button even if I only corrected
>> some typos in comments, or changed the indentation. Suddenly autotest would
>> kick in for nothing.
>
> Autotest sucks. If we have too many tests, it runs them all, and this slows
> us down.

Or, conversely, autotest is awesome if you take the time to learn how to use it:

http://blog.davidchelimsky.net/2008/3/5/limiting-scope-of-autotest

>
> Our editor support for TDD also sucks. It should run the most recently
> edited test cases, nearly automatically. Everyone swears by Textmate, and it
> simply can't do that. Then, the Java-based editors also can't do it!
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From zach.dennis at gmail.com  Tue Mar 31 13:21:29 2009
From: zach.dennis at gmail.com (Zach Dennis)
Date: Tue, 31 Mar 2009 13:21:29 -0400
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <85d99afe0903311010w62cb7e1bsa094d76480110c7a@mail.gmail.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
	<537533f3441d1651cb688abe73790685@ruby-forum.com>
	<85d99afe0903311010w62cb7e1bsa094d76480110c7a@mail.gmail.com>
Message-ID: <85d99afe0903311021o63cc9b32gfd40f575aa657ce@mail.gmail.com>

On Tue, Mar 31, 2009 at 1:10 PM, Zach Dennis <zach.dennis at gmail.com> wrote:
> On Tue, Mar 31, 2009 at 5:39 AM, Fernando Perez <lists at ruby-forum.com> wrote:
>> Fernando Perez wrote:
>>> Hi,
>>>
>>> Today is a big day. I officially transitioned from manually testing by
>>> clicking around in my app, to automated testing with RSpec + Autotest.
>>
>> 6 months since my initial post, what happened in between?
>>
>> - My controllers are getting anorexic, and that's good. An action
>> typically does only 1 call to a model and behind the scenes that model
>> will make other calls to other models and do some fancy stuff, this used
>> to happen in the controller which was bad. Now it has become so easy to
>> write model specs.
>
> Great! Keeping controllers simple makes life better on many fronts.
>
>>
>> - I don't spec controllers, because it's too painful to do. I don't spec
>> views either, because I tweak them too often, and it would take me more
>> time rewriting view specs then actually coding the views. If there is
>> something to test for is the rendering of the css across browsers,
>> because that's terrible!
>
> I usually let Cucumber run through the basics of the action, but I
> write controller specs for interesting thing that affect the behaviour
> of an action such as requiring logic, or a certain permission, or
> special error handling logic, etc. Pulling these things out into a
> controller macro makes re-using them extremely simple. The next beta
> release for The RSpec Book will cover doing that.
>
> I write view specs because they *change* so much. I don't spec the
> structure of the page, just the semantics of it as it pertains to
> information I programmatically display or don't display. IME, when
> apps are small there is a feeling that Cucumber can do it all, but as
> the app grows Cucumber can be a burden as well. Cucumber scenarios
> can't do it all, and when you have interesting apps, hundreds of
> scenarios and hundreds of steps it becomes way too time consuming to
> try to find exactly what and why things died and why. I prefer focused
> view specs for this regression rather than simply relying on Cucumber.
> ?Also cucumber step definitions can become large and unwieldy. I like
> focused steps which do enough to prove a scenario works as expected
> and I like to drop down to specs for the details of it.
>
>>
>> - I use cucumber+webrat to test that some important public pages render
>> without a 500 error. I don't care if the view has such div except if it
>> is a critical one. What I mean is that I won't test, all the assignments
>> that should be on the page, as some tutorials demonstrate. This is
>> nearly impossible to maintain.
>
> I disagree with the last two sentences here. I build my views spec
> first with examples that expect the result of "project.name" to be on
> the page. Only then do I actually add it to the view. I have had no
> issue maintaining this. Not only do I get a design benefit when its
> not just a simple model attribute, but perhaps a calculated field, I
> also get regression for free. I move swiftly, happily, and confidently
> on without worrying about manually verifying everything on the page is
> as it should be, I let my specs do that.
>
>>
>> - I can refactor my code, immediately spot areas where my code got
>> broken, and fix it. Before some parts of my app would be broken without
>> having me knowing about it for a long time until some cool customers
>> report a few bugs, but this was not an acceptable situation.
>
> IMO, this is the case when people don't write view specs. Unless
> someone's Cucumber scenario covers everything on the view (which they
> don't unless its a super simple CRUD app). Half the time I wonder if
> people even know if their views are displaying the write things on the
> page over time. How would they not know w/o specs? Do they manually
> verify every page every time they deploy? That seems impossible to
> maintain.
>
>>
>> - I don't use Autotest, it sucks too much power, and it is too much
>> distracting. From time to time I run specs to check if things look good,
>> and always before updating the code on the server.
>
> Agreed. I loathe autotest, but I don't run specs time to time, I run
> my specs all the time. It's a part of my development process. Red
> Green Refactor. It's not just a mantra, its a discipline. Although
> when I don't know what I want or need to do, I spike something
> (without any tests), and once I figure it out I scrape the spike (or
> comment it out) and drive it with examples.
>
>>
>> - I have written my own Factory. It's not OOP, it could be refactored,
>> but it works 100% as advertised, provides default values, can handle
>> associations, etc. I am pleased with it (I tried factory girl,
>> machinist, etc and got pissed off). I encourage anyone to write his own
>> little factory, to get a better hang of how to write good specs. I
>> totally got mad with fixtures, it is impossible to maintain specs/tests
>> with fixtures. Impossible.
>
> Cool. Is it on github? I wrote my own as well, but then switched to
> FactoryGirl because everyone I talked to loved it, but now I wonder if
> they really loved it (or how much they actually use it) because it
> works for about 80% of the things I need, and fails horribly for the
> other 20%. I want to try Machinist next, but I'm sad to see you had
> bad experiences with it. :(
>
> And I hate the idea behind ObjectDaddy, adding methods to the model to
> generate spec data. Gross.
>
>> - I don't do true BDD, i.e: I still write code before specs, because
>> that's what motivates me. I consider that seeing my app living and
>> writing code for my app more important than writing specs. Specs are
>> still important, but only as a bug reporting tool, they don't add any
>> value for the customer. In this crisis If I wanted an employee to resign
>> by himself without paying him benefits (that's how it works in Europe),
>> I would make him write specs all day long, and forbid him from seeing
>> the app and play with it. He wouldn't last 1 week doing this.
>>
>> What about you?
>>
>
> You've probably seen this, but it never gets old, "Testing is for
> testers." When you focus on specs solely for the benefit of testing
> then you are only getting the tip of the ice berg. Traditional "tests"
> are really they to provide safeguard against regression. This is a
> secondary benefit to BDD. BDD is about driving your app from the
> outside in, focusing on the behaviour at different levels.
>
> For example, Cucumber lets you focus on the app behaviour, while view
> specs lets you focus on the expected behaviour of a view (to display
> "project.name"), and controller specs let you focus on the behaviour
> of a controller (such that only "admins" can destroy a project), and
> model specs let you provide examples for how it should be working.
> Focusing on the behaviour at these different levels forces you to
> write better designed code, more focused objects, simpler controllers,
> just-the-right size models, etc.
>
> A better design lets you move fluidly through the app as it evolves
> and changes. When you use BDD, you get a better design as a part of
> the process. As a nice secondary benefit you get protection against
> unwanted regression.
>
> I encourage you and anyone else to practice your BDD more. The more I
> practice the more fluently I can drive my app with examples form the
> outside-in, and the more capable I am to know when to write a
> controller spec and when not to---and it's not based on if it takes
> too long. The decision is based on experience for knowing how-to do
> it, and how-to do it well, and then asking myself, "Does this get me
> anything?"
>
> Not spe'cing something because you don't know how-to spec it well is
> most likely not an issue with BDD. It's a skill deficiency with the
> developer. The only way to make good decisions it practice and become
> more familiar with your tools. Then you will start making informed
> decisions that add value to your project. The alternative is that you
> make uninformed decisions and you or other developers will suffer down
> the road because you made a bad decision but didn't know it because
> you lacked the knowledge and/or experience to know it was a bad
> decision.

This isn't intended at you Fernando. This is just "in general" my
thoughts, all of which have come from my own journey, as well as many
discussions on-line and off-line.


>
>
>>
>> Best regards,
>> --
>> Posted via http://www.ruby-forum.com/.
>> _______________________________________________
>> rspec-users mailing list
>> rspec-users at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-users
>>
>
>
>
> --
> Zach Dennis
> http://www.continuousthinking.com
> http://www.mutuallyhuman.com
>



-- 
Zach Dennis
http://www.continuousthinking.com
http://www.mutuallyhuman.com

From mark at sabado.com  Tue Mar 31 13:33:59 2009
From: mark at sabado.com (Mark Lynn)
Date: Tue, 31 Mar 2009 13:33:59 -0400
Subject: [rspec-users] [Cucumber] Running single feature from command
	line
In-Reply-To: <8d961d900903310856m1ad24751n6e13b105e1f2247@mail.gmail.com>
References: <15F72ADB-05BB-4904-8C2F-AD283BAE74D0@sabado.com>
	<49D219F0.4020407@josephwilk.net>
	<1A5FBE8B-8D96-4990-889E-245D9BA7B261@sabado.com>
	<8d961d900903310856m1ad24751n6e13b105e1f2247@mail.gmail.com>
Message-ID: <6AFA0A7A-C294-4E4C-A196-205B6A423823@sabado.com>


Aslak,

Thanks! It is nice to at least know where the problem is.  I am  
actually using Cucumber in a Merb project so the Rails solution does  
not help, but I will look for another workaround and post if I find  
something.

Mark Lynn
Sabado Technologies


On Mar 31, 2009, at 11:56 AM, aslak hellesoy wrote:

>
>
> On Tue, Mar 31, 2009 at 5:22 PM, Mark Lynn <mark at sabado.com> wrote:
>
> When I use Aslak's version of Treetop as Joseph suggested, this does  
> get rid of the polyglot error. However, I still get the following  
> when running from the command line:
>
> $ cucumber -r features/steps -r features/support/env.rb features/ 
> plain/user_home_page.feature
>
> /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in  
> `gem_original_require': no such file to load -- features/steps  
> (LoadError)
> Failed to load features/support/env.rb  from /Library/Ruby/Site/1.8/ 
> rubygems/custom_require.rb:31:in `require'
>
>        from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
> option_parser.rb:144:in `invoke_requires'
>        from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
> option_parser.rb:143:in `each'
>        from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
> option_parser.rb:143:in `invoke_requires'
>        from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
> option_parser.rb:104:in `initialize'
>        from /System/Library/Frameworks/Ruby.framework/Versions/1.8/ 
> usr/lib/ruby/1.8/optparse.rb:1291:in `call'
>        from /System/Library/Frameworks/Ruby.framework/Versions/1.8/ 
> usr/lib/ruby/1.8/optparse.rb:1291:in `parse_in_order'
>        from /System/Library/Frameworks/Ruby.framework/Versions/1.8/ 
> usr/lib/ruby/1.8/optparse.rb:1247:in `catch'
>         ... 26 levels...
>
>        from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/ 
> cucumber/cli/main.rb:20:in `execute'
>        from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
>        from /usr/bin/cucumber:19:in `load'
>        from /usr/bin/cucumber:19
>
> Any idea why rspec code is being called here? I did discover that if  
> I uninstall cucumber 0.2.3 and try version 0.1.16, then the above  
> command line works as does using the profile. I'm not sure if this  
> indicates a bug in 0.2.3.
>
> It's actually a bug in RSpec that is only triggered in Cucumber 0.2  
> (bin/cucumber used to consume ARGV, but now leaves it intact, and  
> RSpec blows up).
>
> https://rspec.lighthouseapp.com/projects/16211/tickets/200
> https://rspec.lighthouseapp.com/projects/5645-rspec/tickets/767
>
> Do you have a Rails app? See how Chris Flipse got around the error  
> in the #200 ticket.
>
> Aslak
>
>
>
> Mark Lynn
> Sabado Technologies
>
>
> On Mar 31, 2009, at 9:26 AM, Joseph Wilk wrote:
>
> Mark Lynn wrote:
> I am using Cucumber 0.2.3 and am having problems running a single  
> feature. In particular, the cucumber Textmate bundle was not working  
> so I traced it back and discovered that I could not run single files  
> or features from the command line either. My setup has the following  
> line in cucumber.yml
>
> default: -r features/support/env.rb -r features/support/plain.rb -r  
> features/steps features/plain
>
> When I run just plain cucumber from the command line, all my  
> scenarios run and all features pass. However, if I try to run the  
> command
>
> cucumber -r features/support/env.rb -r features/support/plain.rb -r  
> features/steps features/plain
>
> OR
>
> cucumber -r features/support/env.rb -r features/support/plain.rb -r  
> features/steps features/plain/login.feature
>
> I get
>
> Failed to load features/support/env.rb    from /Library/Ruby/Site/ 
> 1.8/rubygems/custom_require.rb:31:in `polyglot_original_require'
>   from /Library/Ruby/Gems/1.8/gems/polyglot-0.2.5/lib/polyglot.rb: 
> 54:in `require'
>   from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
> option_parser.rb:144:in `invoke_requires'
>   from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
> option_parser.rb:143:in `each'
>   from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
> option_parser.rb:143:in `invoke_requires'
>   from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
> option_parser.rb:104:in `initialize'
>   from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/ 
> lib/ruby/1.8/optparse.rb:1291:in `call'
>   from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/ 
> lib/ruby/1.8/optparse.rb:1291:in `parse_in_order'
>    ... 31 levels...
>   from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/ 
> cucumber/cli/main.rb:20:in `execute'
>   from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
>   from /usr/bin/cucumber:19:in `load'
>   from /usr/bin/cucumber:19
>
> I'm assuming the repeated use of the -r flag is not acceptable, but  
> I need to specify multiple files.
>
> Cucumber will accept multiple -r or --require. It simply pushes all  
> the requires onto a stack and requires them all.
>
> Looks like this is a polygot problem. Aslak recently forked and  
> patched a copy of Treetop to avoid the dependency on this:
>
> git://github.com/aslakhellesoy/treetop.git
>
> I would suggest you try and install treetop from this source and see  
> if that fixes the problem.
>
> HTH
> --
> Joseph Wilk
> http://blog.josephwilk.net
>
> How can I get this to work from the command line so I can also use  
> it in Textmate?
>
> - Mark
>
> Mark Lynn
> Sabado Technologies
>
>
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090331/07f6454f/attachment-0001.html>

From aidy.lewis at googlemail.com  Tue Mar 31 13:38:15 2009
From: aidy.lewis at googlemail.com (aidy lewis)
Date: Tue, 31 Mar 2009 18:38:15 +0100
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <gqtj4v$9ab$1@ger.gmane.org>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
	<537533f3441d1651cb688abe73790685@ruby-forum.com>
	<gqt1p3$9jf$1@ger.gmane.org>
	<fd2fc179fb28a18ca91540d8c6d1f3fd@ruby-forum.com>
	<gqtj4v$9ab$1@ger.gmane.org>
Message-ID: <7ac2300c0903311038j2c69f584if70aeab76ef39691@mail.gmail.com>

Hi Phlip,
On 31/03/2009, Phlip <phlip2005 at gmail.com> wrote:

>  Our editor support for TDD also sucks. It should run the most recently
> edited test cases, nearly automatically. Everyone swears by Textmate, and it
> simply can't do that. Then, the Java-based editors also can't do it!

What editor are you then proposing? Or are you saying that all current
editors lag behind XP practices?

Aidy

From dchelimsky at gmail.com  Tue Mar 31 13:43:19 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Tue, 31 Mar 2009 12:43:19 -0500
Subject: [rspec-users] Expecting nil or false
In-Reply-To: <21431c5c1b46eb031b47bd22a59f5c28@ruby-forum.com>
References: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>
	<57c63afe0903310929u6ed9b52ei32bf826096bb29f@mail.gmail.com>
	<21431c5c1b46eb031b47bd22a59f5c28@ruby-forum.com>
Message-ID: <57c63afe0903311043oca1c78dg5621c3d6794cd015@mail.gmail.com>

On Tue, Mar 31, 2009 at 12:11 PM, Fernando Perez <lists at ruby-forum.com> wrote:
>
>>> Do I have to rewrite my return values to always return true or false?
>> No, but you may have to use different matchers. What are you using?
>
> I use: should be_false
>
> Rspec complains it receives nil when it is expecting false.

As would be expected.

What is the full expression? i.e. what is it that should be false (or nil)?

> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From lists at ruby-forum.com  Tue Mar 31 13:54:22 2009
From: lists at ruby-forum.com (Fernando Perez)
Date: Tue, 31 Mar 2009 19:54:22 +0200
Subject: [rspec-users] Expecting nil or false
In-Reply-To: <57c63afe0903311043oca1c78dg5621c3d6794cd015@mail.gmail.com>
References: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>
	<57c63afe0903310929u6ed9b52ei32bf826096bb29f@mail.gmail.com>
	<21431c5c1b46eb031b47bd22a59f5c28@ruby-forum.com>
	<57c63afe0903311043oca1c78dg5621c3d6794cd015@mail.gmail.com>
Message-ID: <8dce9aa34e6f31e16b6ea8a8047fd8f7@ruby-forum.com>

> What is the full expression? i.e. what is it that should be false (or 
> nil)?

Basically:

def is_it_cool?
  find(blabla, :conditions => 'coolness > 1000')
end

In order to stay consistent and as the question mark suggests that true 
or false will be returned, I have updated my method too:

def is_it_cool?
  !!find(...)
end


Is true that the dynamic aspect of Ruby allows us to not have to 
statically type the return value of a method, so it could be an object, 
nil or a boolean.

What do you think?
-- 
Posted via http://www.ruby-forum.com/.

From lists at ruby-forum.com  Tue Mar 31 13:59:04 2009
From: lists at ruby-forum.com (Fernando Perez)
Date: Tue, 31 Mar 2009 19:59:04 +0200
Subject: [rspec-users] Good introduction to rspec
In-Reply-To: <2b1500990903311000r618ca3bahae123596df3b012c@mail.gmail.com>
References: <2b1500990903311000r618ca3bahae123596df3b012c@mail.gmail.com>
Message-ID: <914d407218e4980dfc36d1132b96cc22@ruby-forum.com>

Pablo L. de Miranda wrote:
> Hi guys,
> Someone know some good introduction to rspec, I`m wanting to use Rspec 
> with
> my Rails projects, but I don't found a good introduction.
> 

>From my own experience:

Write specs for your models and their class / instance methods. If you 
find yourself struggling to do that, it's probably that too much logic 
is floating in your controllers, so move it to your model as much as you 
can.

It took me roughly 5 tries to get a hang of RSpec. By tries I mean: I 
start writing specs, then get pissed off and stop for a few 
weeks/months, then get back to it again.

Don't bother specing your controllers and views. Just stick to the 
models or you'll get pissed off.

To spec controllers and views use Cucumber and webrat, but don't dive 
into it right now.

Oh and by the way, don't use fixtures, instead write your own Factory.

Be very patient, don't try to do too much at a time, and have fun :-)
-- 
Posted via http://www.ruby-forum.com/.

From dchelimsky at gmail.com  Tue Mar 31 13:59:23 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Tue, 31 Mar 2009 12:59:23 -0500
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <537533f3441d1651cb688abe73790685@ruby-forum.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
	<537533f3441d1651cb688abe73790685@ruby-forum.com>
Message-ID: <57c63afe0903311059y29feb0f6p807edb1e0d4d0fb9@mail.gmail.com>

On Tue, Mar 31, 2009 at 4:39 AM, Fernando Perez <lists at ruby-forum.com> wrote:
> Fernando Perez wrote:
>> Hi,
>>
>> Today is a big day. I officially transitioned from manually testing by
>> clicking around in my app, to automated testing with RSpec + Autotest.
>
> 6 months since my initial post, what happened in between?
>
> - My controllers are getting anorexic, and that's good. An action
> typically does only 1 call to a model and behind the scenes that model
> will make other calls to other models and do some fancy stuff, this used
> to happen in the controller which was bad. Now it has become so easy to
> write model specs.
>
> - I don't spec controllers, because it's too painful to do. I don't spec
> views either, because I tweak them too often, and it would take me more
> time rewriting view specs then actually coding the views. If there is
> something to test for is the rendering of the css across browsers,
> because that's terrible!
>
> - I use cucumber+webrat to test that some important public pages render
> without a 500 error. I don't care if the view has such div except if it
> is a critical one. What I mean is that I won't test, all the assignments
> that should be on the page, as some tutorials demonstrate. This is
> nearly impossible to maintain.
>
> - I can refactor my code, immediately spot areas where my code got
> broken, and fix it. Before some parts of my app would be broken without
> having me knowing about it for a long time until some cool customers
> report a few bugs, but this was not an acceptable situation.
>
> - I don't use Autotest, it sucks too much power, and it is too much
> distracting. From time to time I run specs to check if things look good,
> and always before updating the code on the server.
>
> - I have written my own Factory. It's not OOP, it could be refactored,
> but it works 100% as advertised, provides default values, can handle
> associations, etc. I am pleased with it (I tried factory girl,
> machinist, etc and got pissed off). I encourage anyone to write his own
> little factory, to get a better hang of how to write good specs. I
> totally got mad with fixtures, it is impossible to maintain specs/tests
> with fixtures. Impossible.
>
> - I don't do true BDD, i.e: I still write code before specs, because
> that's what motivates me. I consider that seeing my app living and
> writing code for my app more important than writing specs. Specs are
> still important, but only as a bug reporting tool, they don't add any
> value for the customer.

Please be careful when making absolute statements like this. First of
all, even "just a bug reporting tool" adds tremendous value for the
customer, because your catching bugs before they make it to
production.

Secondly, the value to your customer of writing specs before code
depends on your personal skill level as it relates to writing them.
Spec-first adds considerable value for my customers because I know how
to move quickly through the red/green/refactor cycle, and it does
impact design, and therefore the quality of my code, and therefore the
short and long term maintenance costs. But, admittedly, I've been on
the TDD train ever since I learned about it back in 2003 and I kinda
know what I'm doing.

> In this crisis If I wanted an employee to resign
> by himself without paying him benefits (that's how it works in Europe),
> I would make him write specs all day long, and forbid him from seeing
> the app and play with it. He wouldn't last 1 week doing this.

Nor would anybody. From what you're writing, it sounds like your
perception is that you write a bunch of specs with no code, and then
write code to pass the specs.

The point of TDD is writing small examples and small bits of code in a
cycle. The point of BDD is to write high level scenarios so you know
what code to write, but then drive it out in detail with TDD. My
personal experience is that writing this way is a lot of fun, filled
with small successes every few minutes. Admittedly, it's not always as
fun as hacking together a quick prototype and seeing it come to life.
But the fun of that approach dies very quickly if the prototype
becomes the actual app and I find myself back-filling specs.

Hope that helps clarify.

Cheers,
David

> What about you?
>
>
> Best regards,
> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From lists at ruby-forum.com  Tue Mar 31 14:00:39 2009
From: lists at ruby-forum.com (Fernando Perez)
Date: Tue, 31 Mar 2009 20:00:39 +0200
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <57c63afe0903311019j32cac981td160a7b97a8798c9@mail.gmail.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
	<537533f3441d1651cb688abe73790685@ruby-forum.com>
	<gqt1p3$9jf$1@ger.gmane.org>
	<fd2fc179fb28a18ca91540d8c6d1f3fd@ruby-forum.com>
	<gqtj4v$9ab$1@ger.gmane.org>
	<57c63afe0903311019j32cac981td160a7b97a8798c9@mail.gmail.com>
Message-ID: <4b1dbdd5f5f4687670ea3fbeb379995e@ruby-forum.com>

> Or, conversely, autotest is awesome if you take the time to learn how to 
> use it:
> 
> http://blog.davidchelimsky.net/2008/3/5/limiting-scope-of-autotest

Well, I find it easier to simply type:

$ rake spec

Then depending on what failed I will from time to time run a single spec 
file:

$ spec spec/models/whatever.rb

-- 
Posted via http://www.ruby-forum.com/.

From phlip2005 at gmail.com  Tue Mar 31 14:04:24 2009
From: phlip2005 at gmail.com (Phlip)
Date: Tue, 31 Mar 2009 11:04:24 -0700
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <7ac2300c0903311038j2c69f584if70aeab76ef39691@mail.gmail.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>	<537533f3441d1651cb688abe73790685@ruby-forum.com>	<gqt1p3$9jf$1@ger.gmane.org>	<fd2fc179fb28a18ca91540d8c6d1f3fd@ruby-forum.com>	<gqtj4v$9ab$1@ger.gmane.org>
	<7ac2300c0903311038j2c69f584if70aeab76ef39691@mail.gmail.com>
Message-ID: <gqtlv9$jfi$1@ger.gmane.org>

aidy lewis wrote:

> What editor are you then proposing? Or are you saying that all current
> editors lag behind XP practices?

http://www.oreillynet.com/onlamp/blog/2008/05/dynamic_languages_vs_editors.html


From lists at ruby-forum.com  Tue Mar 31 15:19:33 2009
From: lists at ruby-forum.com (Fernando Perez)
Date: Tue, 31 Mar 2009 21:19:33 +0200
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <57c63afe0903311059y29feb0f6p807edb1e0d4d0fb9@mail.gmail.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
	<537533f3441d1651cb688abe73790685@ruby-forum.com>
	<57c63afe0903311059y29feb0f6p807edb1e0d4d0fb9@mail.gmail.com>
Message-ID: <e074a16d62ee4232942bee55e80c481b@ruby-forum.com>

> Please be careful when making absolute statements like this. First of
> all, even "just a bug reporting tool" adds tremendous value for the
> customer, because your catching bugs before they make it to
> production.
Value is what a customer is something he is ready to pay more money for. 
Well, we could argue that specing/testing  can improve my workflow and 
get new features added or improved faster... A Ferrari could also get me 
to work quicker ;-)
-- 
Posted via http://www.ruby-forum.com/.

From phlip2005 at gmail.com  Tue Mar 31 15:33:44 2009
From: phlip2005 at gmail.com (Phlip)
Date: Tue, 31 Mar 2009 12:33:44 -0700
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <57c63afe0903311019j32cac981td160a7b97a8798c9@mail.gmail.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>	<537533f3441d1651cb688abe73790685@ruby-forum.com>	<gqt1p3$9jf$1@ger.gmane.org>	<fd2fc179fb28a18ca91540d8c6d1f3fd@ruby-forum.com>	<gqtj4v$9ab$1@ger.gmane.org>
	<57c63afe0903311019j32cac981td160a7b97a8798c9@mail.gmail.com>
Message-ID: <gqtr6p$6tr$1@ger.gmane.org>

David Chelimsky wrote:

> Or, conversely, autotest is awesome if you take the time to learn how to use it:
> 
> http://blog.davidchelimsky.net/2008/3/5/limiting-scope-of-autotest

Even with -f, after it ran our most recently changed test...

...it started the grand wazoo test batch.

Pass! I can just use autotask or the truly stupid trigger.rb script I drag 
around to TDD. They would just defer to test:recent. We have our suites and 
files all cut up into bite-sized chunks for a reason...


From mark at sabado.com  Tue Mar 31 17:12:08 2009
From: mark at sabado.com (Mark Lynn)
Date: Tue, 31 Mar 2009 17:12:08 -0400
Subject: [rspec-users] [Cucumber] Running single feature from command
	line
In-Reply-To: <6AFA0A7A-C294-4E4C-A196-205B6A423823@sabado.com>
References: <15F72ADB-05BB-4904-8C2F-AD283BAE74D0@sabado.com>
	<49D219F0.4020407@josephwilk.net>
	<1A5FBE8B-8D96-4990-889E-245D9BA7B261@sabado.com>
	<8d961d900903310856m1ad24751n6e13b105e1f2247@mail.gmail.com>
	<6AFA0A7A-C294-4E4C-A196-205B6A423823@sabado.com>
Message-ID: <28332AD3-AE60-4653-820A-50E41C325F79@sabado.com>


FYI: I did confirm the problem was the RSpec issue Aslak mentioned. I  
did not see a nice solution without messing around with the RSpec gem,  
and am I familiar enough with the RSpec code to patch it at this time.  
I ended up throwing a constant in my support/env.rb file and testing  
for this in the RSpec spec/runner.rb file. Sloppy workaround, but I  
needed to move on.

Thanks to Joseph and Aslak for their comments.

Mark Lynn
Sabado Technologies




On Mar 31, 2009, at 1:33 PM, Mark Lynn wrote:

>
> Aslak,
>
> Thanks! It is nice to at least know where the problem is.  I am  
> actually using Cucumber in a Merb project so the Rails solution does  
> not help, but I will look for another workaround and post if I find  
> something.
>
> Mark Lynn
> Sabado Technologies
>
>
> On Mar 31, 2009, at 11:56 AM, aslak hellesoy wrote:
>
>>
>>
>> On Tue, Mar 31, 2009 at 5:22 PM, Mark Lynn <mark at sabado.com> wrote:
>>
>> When I use Aslak's version of Treetop as Joseph suggested, this  
>> does get rid of the polyglot error. However, I still get the  
>> following when running from the command line:
>>
>> $ cucumber -r features/steps -r features/support/env.rb features/ 
>> plain/user_home_page.feature
>>
>> /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in  
>> `gem_original_require': no such file to load -- features/steps  
>> (LoadError)
>> Failed to load features/support/env.rb  from /Library/Ruby/Site/1.8/ 
>> rubygems/custom_require.rb:31:in `require'
>>
>>        from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:144:in `invoke_requires'
>>        from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:143:in `each'
>>        from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:143:in `invoke_requires'
>>        from /Library/Ruby/Gems/1.8/gems/rspec-1.2.2/lib/spec/runner/ 
>> option_parser.rb:104:in `initialize'
>>        from /System/Library/Frameworks/Ruby.framework/Versions/1.8/ 
>> usr/lib/ruby/1.8/optparse.rb:1291:in `call'
>>        from /System/Library/Frameworks/Ruby.framework/Versions/1.8/ 
>> usr/lib/ruby/1.8/optparse.rb:1291:in `parse_in_order'
>>        from /System/Library/Frameworks/Ruby.framework/Versions/1.8/ 
>> usr/lib/ruby/1.8/optparse.rb:1247:in `catch'
>>         ... 26 levels...
>>
>>        from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/../lib/ 
>> cucumber/cli/main.rb:20:in `execute'
>>        from /Library/Ruby/Gems/1.8/gems/cucumber-0.2.3/bin/cucumber:6
>>        from /usr/bin/cucumber:19:in `load'
>>        from /usr/bin/cucumber:19
>>
>> Any idea why rspec code is being called here? I did discover that  
>> if I uninstall cucumber 0.2.3 and try version 0.1.16, then the  
>> above command line works as does using the profile. I'm not sure if  
>> this indicates a bug in 0.2.3.
>>
>> It's actually a bug in RSpec that is only triggered in Cucumber 0.2  
>> (bin/cucumber used to consume ARGV, but now leaves it intact, and  
>> RSpec blows up).
>>
>> https://rspec.lighthouseapp.com/projects/16211/tickets/200
>> https://rspec.lighthouseapp.com/projects/5645-rspec/tickets/767
>>
>> Do you have a Rails app? See how Chris Flipse got around the error  
>> in the #200 ticket.
>>
>> Aslak

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090331/f0a4b983/attachment-0001.html>

From dchelimsky at gmail.com  Tue Mar 31 17:35:07 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Tue, 31 Mar 2009 16:35:07 -0500
Subject: [rspec-users] Expecting nil or false
In-Reply-To: <8dce9aa34e6f31e16b6ea8a8047fd8f7@ruby-forum.com>
References: <54311a566492b0c7f33200ea9605da26@ruby-forum.com>
	<57c63afe0903310929u6ed9b52ei32bf826096bb29f@mail.gmail.com>
	<21431c5c1b46eb031b47bd22a59f5c28@ruby-forum.com>
	<57c63afe0903311043oca1c78dg5621c3d6794cd015@mail.gmail.com>
	<8dce9aa34e6f31e16b6ea8a8047fd8f7@ruby-forum.com>
Message-ID: <57c63afe0903311435v264c852flda28638f053b0fa2@mail.gmail.com>

On Tue, Mar 31, 2009 at 12:54 PM, Fernando Perez <lists at ruby-forum.com> wrote:
>> What is the full expression? i.e. what is it that should be false (or
>> nil)?
>
> Basically:
>
> def is_it_cool?
> ?find(blabla, :conditions => 'coolness > 1000')
> end
>
> In order to stay consistent and as the question mark suggests that true
> or false will be returned, I have updated my method too:
>
> def is_it_cool?
> ?!!find(...)
> end
>
>
> Is true that the dynamic aspect of Ruby allows us to not have to
> statically type the return value of a method, so it could be an object,
> nil or a boolean.
>
> What do you think?

I don't know if you're familiar with the concept of truthiness, but
that is what you're talking about here. IMO, be_true should be
specific. I'm open to other opinions, and would consider changing the
way it works if we can do it without breaking everybody's stuff.

Somebody joked about having a be_truthy matcher. Perhaps he actually wrote one.

As for how I handle these things now, I would do this:

something.should be_cool

def cool?
  !!find(...)
end

I find that almost every time I approach it this way, I land on a
predicate method that is ruby-ish. is_it_cool? is not ruby-ish. nor
would is_cool?

FWIW,
David

> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From pablolmiranda at gmail.com  Tue Mar 31 18:01:22 2009
From: pablolmiranda at gmail.com (Pablo L. de Miranda)
Date: Tue, 31 Mar 2009 19:01:22 -0300
Subject: [rspec-users] Good introduction to rspec
In-Reply-To: <914d407218e4980dfc36d1132b96cc22@ruby-forum.com>
References: <2b1500990903311000r618ca3bahae123596df3b012c@mail.gmail.com>
	<914d407218e4980dfc36d1132b96cc22@ruby-forum.com>
Message-ID: <2b1500990903311501o65399d9bq1396dfc8899f03c1@mail.gmail.com>

Hi Fernando,
Are know, or have, some material ( tutorial, article, etc.. ) to recommend
me?

Att,

Pablo Lacerda de Miranda
Graduando Sistemas de Informa??o
Universidade Estadual de Montes Claros
pablolmiranda at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090331/2d0f26fb/attachment.html>

From dchelimsky at gmail.com  Tue Mar 31 18:27:30 2009
From: dchelimsky at gmail.com (David Chelimsky)
Date: Tue, 31 Mar 2009 17:27:30 -0500
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <e074a16d62ee4232942bee55e80c481b@ruby-forum.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
	<537533f3441d1651cb688abe73790685@ruby-forum.com>
	<57c63afe0903311059y29feb0f6p807edb1e0d4d0fb9@mail.gmail.com>
	<e074a16d62ee4232942bee55e80c481b@ruby-forum.com>
Message-ID: <57c63afe0903311527p1627f31al1851ed785dcabbd9@mail.gmail.com>

On Tue, Mar 31, 2009 at 2:19 PM, Fernando Perez <lists at ruby-forum.com> wrote:
>> Please be careful when making absolute statements like this. First of
>> all, even "just a bug reporting tool" adds tremendous value for the
>> customer, because your catching bugs before they make it to
>> production.
> Value is what a customer is something he is ready to pay more money for.
> Well, we could argue that specing/testing ?can improve my workflow and
> get new features added or improved faster... A Ferrari could also get me
> to work quicker ;-)

If (if!!!!) writing specs first makes you go faster, then you're
faster for free. The Ferrari bears a bit of a different cost/benefit
ratio :)

Cheers,
David

> --
> Posted via http://www.ruby-forum.com/.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

From sarahg.gray at gmail.com  Tue Mar 31 18:47:25 2009
From: sarahg.gray at gmail.com (Sarah Gray)
Date: Tue, 31 Mar 2009 17:47:25 -0500
Subject: [rspec-users] Good introduction to rspec
In-Reply-To: <2b1500990903311501o65399d9bq1396dfc8899f03c1@mail.gmail.com>
References: <2b1500990903311000r618ca3bahae123596df3b012c@mail.gmail.com>
	<914d407218e4980dfc36d1132b96cc22@ruby-forum.com>
	<2b1500990903311501o65399d9bq1396dfc8899f03c1@mail.gmail.com>
Message-ID: <44821e060903311547v63255b7axf6386863a65a2328@mail.gmail.com>

There are some great peepcode screencasts, if you like that kind of thing:

http://peepcode.com/products/rspec-basics
http://peepcode.com/products/rspec-mocks-and-models
http://peepcode.com/products/rspec-controllers-and-tools

Also the book is coming out it's in beta now,
http://www.pragprog.com/titles/achbd/the-rspec-book

hth.

2009/3/31 Pablo L. de Miranda <pablolmiranda at gmail.com>

> Hi Fernando,
> Are know, or have, some material ( tutorial, article, etc.. ) to recommend
> me?
>
> Att,
>
> Pablo Lacerda de Miranda
> Graduando Sistemas de Informa??o
> Universidade Estadual de Montes Claros
> pablolmiranda at gmail.com
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>



-- 
http://www.fabled.net/blog/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090331/4ead5f7c/attachment.html>

From matt at mattwynne.net  Tue Mar 31 19:10:42 2009
From: matt at mattwynne.net (Matt Wynne)
Date: Wed, 1 Apr 2009 00:10:42 +0100
Subject: [rspec-users] RSpec makes me want to write better code
In-Reply-To: <57c63afe0903311019j32cac981td160a7b97a8798c9@mail.gmail.com>
References: <25ae8c0f5f9b09f50538e8be2539f1f0@ruby-forum.com>
	<537533f3441d1651cb688abe73790685@ruby-forum.com>
	<gqt1p3$9jf$1@ger.gmane.org>
	<fd2fc179fb28a18ca91540d8c6d1f3fd@ruby-forum.com>
	<gqtj4v$9ab$1@ger.gmane.org>
	<57c63afe0903311019j32cac981td160a7b97a8798c9@mail.gmail.com>
Message-ID: <0425FF03-D897-4FAA-ABF6-4DF7739E2465@mattwynne.net>


On 31 Mar 2009, at 18:19, David Chelimsky wrote:

>> Autotest sucks. If we have too many tests, it runs them all, and  
>> this slows
>> us down.
>
> Or, conversely, autotest is awesome if you take the time to learn  
> how to use it:
>
> http://blog.davidchelimsky.net/2008/3/5/limiting-scope-of-autotest


Thank you.

Matt Wynne
http://blog.mattwynne.net
http://www.songkick.com


From pablolmiranda at gmail.com  Tue Mar 31 19:25:16 2009
From: pablolmiranda at gmail.com (Pablo L. de Miranda)
Date: Tue, 31 Mar 2009 20:25:16 -0300
Subject: [rspec-users] Good introduction to rspec
In-Reply-To: <44821e060903311547v63255b7axf6386863a65a2328@mail.gmail.com>
References: <2b1500990903311000r618ca3bahae123596df3b012c@mail.gmail.com>
	<914d407218e4980dfc36d1132b96cc22@ruby-forum.com>
	<2b1500990903311501o65399d9bq1396dfc8899f03c1@mail.gmail.com>
	<44821e060903311547v63255b7axf6386863a65a2328@mail.gmail.com>
Message-ID: <2b1500990903311625y23c5fedfv75476415f3228754@mail.gmail.com>

Hi Sarah,
I will take a look in the peepcode videos.

Thank you,

Pablo Lacerda de Miranda
pablolmiranda at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rspec-users/attachments/20090331/5462f406/attachment.html>