similar to: Return code for running stories

Hey all, I have a spec that is hanging when it is running. How do I get the rspec runner to show what specs it''s running so I can which one is hanging? I am calling the runner from my rails project. Thanks, Ben

I have played a bit with RSpec specs and now want to check out stories. I note that there is no generator for rspec stories pre se (unless I managed to miss all references to one ) and that the only directory relating to stories added by installing rspec is ./stories itself. The documentation at rspec.info seems to presume a great deal of prior knowledge. What I am looking for is a guided tour

Hi! And now for the second part of the subject of my previous mails :) $ cat cucumber.yml default: . autotest: -v . autotest-all: -v -f progress . $ cucumber -i . -f progress PP Pending Scenarios: 1) enlightenment (meditation) $ AUTOFEATURE=true autospec # bug! prompt returns immediately, ZenTest gem not a dependency? a warning that autotest was not found would be nice. $ sudo gem

Hi, all! I have a story steps array.rb and the story array.story. I can run it with ruby array.rb But when I execute spec array.rb nothing happened. I''m wondering how can I use spec command to execute stories? (executing examples is OK) Or maybe another question. If I have to run stories with `ruby'' command, how can I choose the output format? (I think there''s

Hi, How can I have a common set of steps that all my stories share? i.e. My stories often start out looking like this: Given a user Joe Given a user Jordan then: Given("a user $username") do |username| @users ||= {} @user_sessions ||= {} @users[username] = create_user(:username => username) @user_sessions[username] = login_as(@users[username]) end I want to share that

Hey guys, just poppin in to ask if anyone knows when stories will be somewhat stable? We''re starting to use integration tests at work, we''re already using rspec, and I''d like to avoid integration tests if possible. Thanks, Nate "fowlduck" Sutton

Hi all, I''m just getting to grips with rspec, and I''m trying to put together a showy demo. We''re trying to use the (plain text) stories feature, rather than the specs. I''d like to show off a fancy HTML report of the results if possible. So it seems I can do this from the spec command line tool, but I can''t make it work for a story. I''ve got

hello there, i have been trying my hand at this rbehave material, specifically in terms of integration testing a rails application, and i am curious about the most friendly way to deal with session data. currently, the only way i have found to simulate a session is to open a session and refer to everything afterward via the @session variable stored after open_session. it seems to be workable,

Hello, how can I execute some code after each step of a story. Is there some kind of listener documentated. Thank you in advance, Armin

Yes, slides will be available afterwards. Additionally, a very similar talk will be presented at SCALE this year as well. Do you have any more info about how tinc is used by NYC mesh? Ben On Sun, Nov 15, 2015 at 3:55 PM, Daniel J. Grinkevich < danielgrinkevich at gmail.com> wrote: > Will the slides be posted after the talk? > > We use tinc for NYC Mesh to connect nodes that do

I''m taking my first fledgling steps driving a new ruby (non-rails) project with BDD. I''ve got a (test) story working. However, when I run the story in TextMate (via command-r), the output is plain text. See: http://skitch.com/georgeanderson/8grg/run-examples How do I get the output to look pretty (formatted)? rspec-1.1.3 OS X 10.5.2 TextMate v1.5.7 (1455) Thanks, /g --

http://bugs.freedesktop.org/show_bug.cgi?id=19450 Summary: 6600GT on G5(Dual Head) - Pointer to flat panel table invalid Product: xorg Version: 7.2 Platform: PowerPC OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo:

Here''s an excellent blog post on Story Runner, which will be part of the next release and is undergoing active development in trunk: http://evang.eli.st/blog/2007/9/1/user-stories-with-rspec-s-story-runner

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

I''ve got an RSpec story that reads like: ------------------------------------------------------------------- Given that a post exists And I am logged in And I have edit permissions When I visit the post details page Then there should be a link to add a new comment ------------------------------------------------------------------- The issue I''m having is that I can''t

Hi, I am confused (a normal state for me) about the State-Of-The-Art Story API to use. examples/calculator.rb has one syntax, the Blogs have another Syntax, so do the various tutorials. I realize that Stories are ongoing work, but it would be nice if there were something I could refer to to make sure that I am not using a syntax that will soon be deprecated, and that I am doing "what is

I recently noticed the HTML formatter for the story runner, but I''m unable to figure out how to make it function. ''ruby stories/all.rb --format html'' seems like it should work, in that --help works as expected, but I still get only plain text output. Maybe it''s not been wired up yet and/or this is a bug. Maybe I''m just being dumb. I have no clue at

Hi, If I write the HTML format stories output to ~/ccrb_build-build_number/Stories/index.html. To get all styles rendered, I also need to copy /vendor/plugins/rspec/story_server/prototype/stylesheets/ and /vendor/plugins/rspec/story_server/prototype/javascripts/ to the ~/ccrb_build-build_number/Stories/. Just wonder is this the right way to do it? or there is a better/preferred way? Thanks Yi

RSpec-1.1.3 has been released. If you''re using RSpec and autotest, you''ll have to upgrade to RSpec-1.1.3 and ZenTest-3.9.0 at the same time. == Version 1.1.3 Maintenance release. * Tightened up exceptions list in autotest/rails_spec. Closes #264. * Applied patch from Ryan Davis for ZenTest-3.9.0 compatibility * Applied patch from Kero to add step_upcoming to story listeners.

Hi all, Are there any plans for better documentation for the new StoryRunner feature? I tried to use it today (with Rails), and had a hard time getting my head around whether I was doing it "right" and exactly what things are appropriate to test at that level (this might be exacerbated by the fact that I''ve never really used integration testing that much). A full example of