Re: [rspec-users] Cucumber: Running a single feature / scenario

2011-08-22 Thread Nishith R.
For sake of completeness, if you are using bundle in rails3, and don't want to invoke rake [to save init time], you can also execute it the following way: bundle exec cucumber --guess --profile default path/feature_name.feature:line_number HTH Nishith -- Posted via http://www.ruby-forum.com/

Re: [rspec-users] Cucumber: Running a single feature / scenario

2011-08-22 Thread Nishith R.
For sake of completness, if you are using bundle in rails3, and don't want to invoke rake [to save init time], you can also execute it the following way: bundle exec cucumber --guess --profile default path/feature_name.feature:line_number HTH Nishith -- Posted via http://www.ruby-forum.com/.

Re: [rspec-users] Route is valid but not found :(

2011-08-22 Thread ct9a
On Aug 23, 1:55 pm, Justin Ko wrote: > On Mon, Aug 22, 2011 at 9:09 PM, ct9a wrote: > > > Thanks, Justin. > > > I have the part object mocked up before each spec runs. > > > --- Extract begins - > > >    let(:part){ > >        mock_model('Part').as_null_object > >    } > > >

Re: [rspec-users] Route is valid but not found :(

2011-08-22 Thread Justin Ko
On Mon, Aug 22, 2011 at 9:09 PM, ct9a wrote: > > > Thanks, Justin. > > I have the part object mocked up before each spec runs. > > --- Extract begins - > >let(:part){ >mock_model('Part').as_null_object >} > >before do >Part.stub(:new).and_return(par

Re: [rspec-users] Route is valid but not found :(

2011-08-22 Thread ct9a
Thanks, Justin. I have the part object mocked up before each spec runs. --- Extract begins - let(:part){ mock_model('Part').as_null_object } before do Part.stub(:new).and_return(part) end --- Extract ends - With that i

[rspec-users] inheriting test cases vs. mixing them in

2011-08-22 Thread Alexy Khrabrov
I've come across an interesting blog post showing how to inherit tests: http://benbiddington.wordpress.com/2010/11/06/rspec-common-base-specs/ How does it stack against the usual mixing/shared_examples_for, beautifully described in http://blog.davidchelimsky.net/2010/11/07/specifying-mixins-with

[rspec-users] [JRuby] simulating a java exception in a spec

2011-08-22 Thread Lenny Marks
JRuby 1.6.2 rspec-core (2.6.4) rspec-expectations (2.6.0) rspec-mocks (2.6.0) rspec-rails (2.6.1) I'm sure this has more to do with the way JRuby wraps Java exceptions but I figured I'd post here in case anyone here has any insight or pointers. In the context of writing a spec for a model like t

Re: [rspec-users] ruby 1.8.6

2011-08-22 Thread Rob Aldred
On 22 Aug 2011, at 14:10, Chuck Remes wrote: > On Aug 21, 2011, at 9:11 PM, David Chelimsky wrote: > >> Hey all, >> >> It's growing increasingly difficult for RSpec to support Ruby 1.8.6 as other >> libraries that rspec's development environment relies on drop support. >> Noting that 1.8.7 was

Re: [rspec-users] ruby 1.8.6

2011-08-22 Thread Chuck Remes
On Aug 21, 2011, at 9:11 PM, David Chelimsky wrote: > Hey all, > > It's growing increasingly difficult for RSpec to support Ruby 1.8.6 as other > libraries that rspec's development environment relies on drop support. Noting > that 1.8.7 was released over three years ago (6/1/2008), I'd like to

Re: [rspec-users] mock weirdness

2011-08-22 Thread Nikolay Sturm
* David Chelimsky [2011-08-22]: > This means that you need to explicitly stub the load method to do what > you're trying to do: > > let(:bar) { mock(Bar, :load => nil).as_null_object } Thanks for the explanation, David. I wasn't sure whether or not this was accepted behaviour, I would have expec

Re: [rspec-users] mock weirdness

2011-08-22 Thread David Chelimsky
On Aug 22, 2011, at 5:11 AM, Nikolay Sturm wrote: > Hi, > > I have a strange problem with mocking an object that has a method called > 'load'. With Rails 2.3 and rspec-rails 1.3 I could do sth like this: > > describe Foo do > let(:bar) { mock(Bar).as_null_object } > before(:each) do >Bar.s

[rspec-users] mock weirdness

2011-08-22 Thread Nikolay Sturm
Hi, I have a strange problem with mocking an object that has a method called 'load'. With Rails 2.3 and rspec-rails 1.3 I could do sth like this: describe Foo do let(:bar) { mock(Bar).as_null_object } before(:each) do Bar.stub(:new).and_return(bar) end it 'does something' do Foo.

Re: [rspec-users] ruby 1.8.6

2011-08-22 Thread Sidu Ponnappa
Hi David, Sounds good to me. I haven't seen a 1.8.6 project since December last year. Best, Sidu. http://c42.in http://blog.sidu.in On 22 August 2011 07:41, David Chelimsky wrote: > Hey all, > > It's growing increasingly difficult for RSpec to support Ruby 1.8.6 as other > libraries that rspe

Re: [rspec-users] Route is valid but not found :(

2011-08-22 Thread Justin Ko
On Mon, Aug 22, 2011 at 12:14 AM, ct9a wrote: > Hi, guys, > > After reading the rspec book (dec 2010 edition), I went on to write > controller specs for an application I'm porting over from rails 2.3.x > to rails 3. > > > 1) I ran 'rake routes' and got the following: > >parts GET/parts(.

Re: [rspec-users] inheriting test cases vs. mixing them in

2011-08-22 Thread Justin Ko
On Sat, Aug 20, 2011 at 7:53 PM, braver wrote: > I've come across an interesting blog post showing how to inherit > tests: > > http://benbiddington.wordpress.com/2010/11/06/rspec-common-base-specs/ > > How does it stack against the usual mixing/shared_examples_for, > beautifully described in > >