Re: [rspec-users] Cucumber - Testing ActionMailer

2009-05-02 Thread Brandt Kurowski
On Apr 29, 10:37 am, Ben Mabey wrote: > However, that is not done yet.  As it stands now you > have two options: a) have the test execution and script in the same > process or b) Use ARMailer[1] in your testing environment.  ARMailer > places the messages in a database for queuing.  So instead of

Re: [rspec-users] Cucumber/Webrat/Selenium + SSL?

2009-04-29 Thread Brandt Kurowski
On Apr 29, 6:04 am, Wincent Colaiuta wrote: > Webrat will "automatically start the Selenium Java server process and   > an instance of Mongrel when a test is run". So there is no way that I   > can see to force Webrat to launch the Selenium server process with the   > custom Firefox profile. You

Re: [rspec-users] How to write a spec file for a helper

2009-04-14 Thread Brandt Kurowski
On Apr 13, 11:26 am, Pat Maddox wrote: > If this is a module that you're using to extend the behavior of > Numeric classes, just mix it in somewhere and write examples for the > class that got the mixin. I prefer to test modules in isolation by mixing them into a stub in the spec, in order to mak

Re: [rspec-users] [Rails] specifying that a layout yields?

2009-03-30 Thread Brandt Kurowski
On Mar 30, 9:56 am, Zach Dennis 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 >

Re: [rspec-users] [Rails] specifying that a layout yields?

2009-03-30 Thread Brandt Kurowski
On Mar 30, 3:39 am, Matt Wynne 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 i

[rspec-users] [Rails] specifying that a layout yields?

2009-03-29 Thread Brandt Kurowski
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