Re: [rspec-users] [BDD] View specs and cucumber -- duplication of effort?

IMHO steps can test everything that view specs can test, but in a much faster and will less effort. You don't have to build a huge feature to test a complex view, you can just split it into different scenarios. In the profile example of a social site, you could have a scenario for friend, one for

Re: [rspec-users] Cucumber + Webrat + Selenium + ActionMailer

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

Re: [rspec-users] [cucumber] Cucumber and CI

>David Chelimsky >That may be so, but one view of agile is that each iteration is a >mini-waterfall. BDD suggests that we *should* define all of the >scenarios in the iteration planning meeting because we use them as a >planning tool (how can we estimate a feature at all before we've >talked about

Re: [rspec-users] Cucumber + Webrat + Selenium + ActionMailer

>1. >http://seattlerb.rubyforge.org/ar_mailer/classes/ActionMailer/ARMailer.html > P.S. I'll follow up with a confirmation post just to let the people know > how it worked out for us with ARMailer. Yeap everything worked like a charm, once again checking email contents like there is no tomorrow

Re: [rspec-users] Cucumber + Webrat + Selenium + ActionMailer

Thanks guys, very interesting points. As a good collegue of mine says, its all about trade offs :) I agree with changing your production code to make it more testable, definitely, especially early on in the development process, once your site is up and running it would have to be done with extr

[rspec-users] Cucumber + Webrat + Selenium + ActionMailer

Hi, We are upgrading to cucumber 0.1.99 in the process we also upgraded to the latest versions of webrat and rspec. However now we are having difficulties checking for ActionMailer.deliveries in the selenium features. I seem to recall being able to check for these without problems using webrat's

Re: [rspec-users] Spec'ing via features

> Wow, if that's it in a nutshell... :) > > Pat Thanks Pat, great summary. I have to admit that I'm as crazy as Yehuda, and believe that all we need are just acceptance tests, at different layers of abstraction, for clients and developers. I also see the benefits of speccing out single object's

Re: [rspec-users] Spec'ing via features

r (I know this is not a problem in static languages, but still, there is a clear coupling between implementation code and test code which I'm concerned with) Looking forward to your comments and suggestions. Kind Regards, Raimond Garcia

Re: [rspec-users] RESTful Routes

> > On 4.2.2008, at 19.16, Raimond Garcia wrote: >> Interesting Jarkko... >> >> The restful routes, seem clearer than using urls, maybe not so much >> for this case, but for very long urls, that include for example the >> title of a blog, I would rather use bl

Re: [rspec-users] RESTful Routes

>> Hi, >> >> I'm trying to test the behavior of a route with a delete method. >> >> Something like this: >> When "the admin clicks on 'delete'" do >>delete admin_blog_path(@blog) >> end >> >> which raises the following exception: >> NoMethodError: You have a nil object when you didn't expect i

Re: [rspec-users] RESTful Routes

> > On 4.2.2008, at 14.54, Raimond Garcia wrote: > >> Hi, >> >> I'm trying to test the behavior of a route with a delete method. >> >> Something like this: >> When "the admin clicks on 'delete'" do >>dele

Re: [rspec-users] rspec-users Digest, Vol 20, Issue 6

On Feb 4, 2008, at 5:07 PM, [EMAIL PROTECTED] wrote: On 4.2.2008, at 14.54, Raimond Garcia wrote: Hi, I'm trying to test the behavior of a route with a delete method. Something like this: When "the admin clicks on 'delete'" do delete admin_blog_path(@blo

Re: [rspec-users] RESTful Routes

On Feb 4, 2008 6:54 AM, Raimond Garcia <[EMAIL PROTECTED]> wrote: Hi, I'm trying to test the behavior of a route with a delete method. Something like this: When "the admin clicks on 'delete'" do delete admin_blog_path(@blog) end which raises the followin

[rspec-users] RESTful Routes

expect it! The error occurred while evaluating nil.env If I change the delete, for a get or a post it works like a charm. What am I missing here? Thanks in advance! Raimond Garcia ___ rspec-users mailing list rspec-users@rubyforge.org http://rubyfo

Re: [rspec-users] Testing Models without fixtures

Hi guys, Thanks for the help, will check out Exemplar and ModelStubbing, for the moment this screencast about FixtureReplacement looks very useful. http://railsnewbie.com/files/fixture_replacement_demo.mov Rai On Nov 20, 2007, at 5:27 PM, Nathan Sutton wrote: > Ok, if you want to do it messy

Re: [rspec-users] Testing Models without fixtures

ssing the password parameters and the such. Thanks again! Keep up the great work with rSpec! Rai On Nov 20, 2007, at 3:40 PM, David Chelimsky wrote: > On Nov 20, 2007 6:57 AM, Raimond Garcia <[EMAIL PROTECTED]> > wrote: >> Hi, >> >> I would like to test a sorting met

[rspec-users] Testing Models without fixtures

Hi, I would like to test a sorting method that is in the user model, it's a class method called search. What I would like to do is create 2 users and load the test database with just those 2 users, so that I can call User.search("john") and it would return those two users. Not sure how to cle