similar to: new pending feature (pending release)

Thanks to discussions on this list, suggestions from many of you and a patch from Pat Maddox, we now have Plain Text User Stories in Story Runner. Read more: http://blog.davidchelimsky.net/articles/2007/10/21/story-runner-in-plain-english Cheers, David

Hi All, I''m trying to make use of template.expects_render, is outlined in David''s post(http://blog.davidchelimsky.net/articles/2007/06/28/ template-expects_render). I get an undefined method error on expects_render. I made sure I had the 1.0.8 gem as well as reinstalling the plugin and redoing the bootstrap. Still no luck. So I created a clean project, installed the

Hi, I''ve been following this thread and I can get the example stories to run with the ruby command. But I''ve been unable to get the example from http://blog.davidchelimsky.net/articles/2007/10/25/plain-text-stories-part-iii to run with all.rb ruby stories/all.rb /home/edh/story/stories/additions/steps/addition_steps.rb:2: undefined method `steps_for'' for main:Object

All, One of the things I learned when I started to do TDD was that you should write enough tests to give you the courage to move forward. For some, that results in more tests than others. In approaching BDD, my initial thinking was to write examples for all of the possible behaviours in every context. I''ve had a change of thinking on this. Please check out my blog on it and let me know

Hi there, newb q: The "pending" support for spec''s and steps is nice. I''m just wondering why a scenario itself can''t be pending? I.e. it seems to me like it would be nice to write up scenario titles for scenarios as you think of them, and for low-priority fringe scenarios leave the steps unwritten until it comes time to implement the scenario? Is there a

If you want to use rspec-0.9.2 with autotest (ZenTest-3.5.2), you''ll want to read this blog: http://blog.davidchelimsky.net/articles/2007/05/01/rspec-0-9-1-and-autotest-zentest-3-5-2 Enjoy! David

Good morning rspec people! Still rspec nuby: I must do something wrong obviously. How can I spec about redirect_to at ApplicationController describe ApplicationController do it "method login_required should redirect to home path without login" do pending "I tried to use controller.login_required.should be_redirected and got NoMethodError with nil object

I love the way I can throw a call to pending() in the top of an unfinished RSpec example and stop it from failing the build. Is there a similar way to do such a thing with good ole'' cucumber? cheers, Matt ---- http://blog.mattwynne.net http://songkick.com In case you wondered: The opinions expressed in this email are my own and do not necessarily reflect the views of any former,

Hello. You''re saying that: To get rspec to behave as it did before this change, use this: --pattern "**/*.rb" I tried like this (rspec 1.03) and it wasn''t same as before (rspec 1.08). Now it also loads all other files in current directory and in all subdirectories and not only from directory and subdirectories given to spec as a parameter. So, for example, I have

On Dec 27, 2007 3:18 PM, Shot (Piotr Szotkowski) <shot at hot.pl> wrote: > Shot (Piotr Szotkowski): > > > I happily hand-compiled Ruby 1.9.0-0 into /home/shot/opt/ruby today > > and I''m running into a strange error with RSpec ? all my examples work > > perfectly with Ruby 1.8 but are considered peding on Ruby 1.9. > > FWIW, I get the same result with

I''m trying to spec my views with 0.7.1 on edge rails per the instructions on the rspec site [1] and David''s blog [2], but I''m not having much luck. Here''s my spec in specs/views/accounts/ new_view_spec.rb: require File.dirname(__FILE__) + ''/../../spec_helper'' context "The new account form" do specify "should have an

We have a few unfinished examples in our code of the form it "should and does do something" do # stuff end it "should do something someday" it "should and does do something else" do # more stuff end Now since I upgraded my gem to rspec 1.8 today, the empty example is failing with the error ArgumentError in "should do something someday":

If I have an object `obj` that is a SpecTask, and subsequently invoke it, is there a way to programmatically determine the number of tests that were successful, failed, and pending as a result of running that SpecTask? -- John Feminella Principal Consultant, Distilled Brilliance

Is there some reason that pending() *MUST* take an argument? Scott

Do have the latest versions? RSpec-1.0.3 ZenTest-3.6.0 ---------- Forwarded message ---------- From: Jonathan Linowes <jonathan at parkerhill.com> Date: May 29, 2007 11:47 AM Subject: Re: [rspec-users] questions rspec on rails To: rspec-users <rspec-users at rubyforge.org> Hi, I should have mentioned I already did that. Here''s my spec.opts file --colour --format progress

I can''t get my plain text stories to show pending actions like the example addition plain text story. Any tips? (See below) http://pastie.caboo.se/119627 Nathan Sutton fowlduck at gmail.com rspec edge revision 2910 rspec_on_rails edge revision 2909 rails edge revision 8167

So, I''ve been following the recommendations for controller specs here: http://blog.davidchelimsky.net/articles/2006/11/09/tutorial-rspec-stubs-and-mocks Most notably: a single expectation per specify block; the setup block contains only stubs; mock expectations each get their own specify block. (I''m still using 0.8, so I haven''t gotten the describe/it goodness yet.) I

http://blog.davidchelimsky.net/2011/11/06/rspec-280rc1-is-released/ See the blog post for more information, but highlights include: 1. tag overrides Now you can set tag/filter defaults in .rspec: --tag ~javascript or in RSpec.configure (in spec_helper.rb): RSpec.configure {|c| c.filter_run_excluding :javascript} and then override that from the command line when you want to run the

First of all, please direct me into how better to search existing threads in this mailing list. Ok to my rspec 2.0.1 mocha 0.9.8 issue: given a controller test before do subject.expects(:authenticate).once end it "should bla bla" do pending "PENDING, shouldn''t fail?" end with config.mock_with :rspec it''s ok: pending, but with

The RSpec Development Team is happy to announce the release of RSpec-1.1.4. See http://rspec.info/changes.html for details of what changed in this release. For Rails developers: * This release of RSpec supports Rails-2.1.0-RC1, 2.0.2, 1.2.6 More info at http://rspec.info. Cheers, David