This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 131684 - Support for RSpec Story
Summary: Support for RSpec Story
Status: NEW
Alias: None
Product: ruby
Classification: Unclassified
Component: Testing (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker with 1 vote (vote)
Assignee: issues@ruby
Depends on:
Reported: 2008-04-01 08:28 UTC by Martin Krauskopf
Modified: 2011-01-28 20:11 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Martin Krauskopf 2008-04-01 08:28:36 UTC
That is RSpec stories are not supported and hardly (likely not at all) workaroundable by the user due to issue 116563.
Comment 1 Martin Krauskopf 2008-04-02 00:37:47 UTC
Adding Tim's comments from user@ruby.nb ML

1) Ability to run story with a single keypress when the plain text story file has focus

2) Ability with single keypress to switch between plain text story and the ruby steps file

3) Visual indicator in the plain text story view as to which steps are still pending

4) syntax highlighting as per previous email..

5) Code Templates

6) Rspec in general - have keyboard accessable ways in running in progress mode or specdoc mode.

Reassigning (I thought that it is just about file-type recognition, so I could help)
Comment 2 timhaines 2008-04-02 23:19:46 UTC
priority 2b - at the end of a story step line, when pressing return sets the cursor directly below the start of the
current line, ready to start entering the next step.
Comment 3 timhaines 2008-04-03 23:54:02 UTC
priority 1b - In the project pane, allow stories to sit as the first "folder" in the list, and "rspec" as the second -
both above controllers.  The theory is you should write stories first, then your specs, then the app code..
Comment 4 timhaines 2008-04-10 02:31:29 UTC
Priority 2aish - after typing in a plain text story, it would be nice if there was a keypress to generate stubs for the
yet to be written steps in the step file.  (and have them sorted into the given/when/then order...maybe)
Comment 5 timhaines 2008-04-11 03:55:48 UTC
Note for "2) Ability with single keypress to switch between plain text story and the ruby steps file"

A story may utilise many step files, and a step implementation can live in any of those step files - or it may not be
written yet.

See a demo app at:
Comment 6 timhaines 2008-04-11 04:50:13 UTC
When you run a story with pending steps, the pending steps are listed at the bottom of the output.  Would be great if
these were links to the plain text step in question.