rspec

Comments and changes to this ticket

• 

  David Chelimsky December 10th, 2007 @ 02:41 PM

  • → Assigned user changed from “” to “David Chelimsky”
  • → State changed from “new” to “open”
  • → Milestone changed from “” to “1.1.0”

  As of r3117 this works for non-rails apps but not rails apps.

• 

  David Chelimsky December 14th, 2007 @ 06:36 AM

  • → Milestone changed from “1.1.0” to “1.1.1”
• 

  David Chelimsky December 18th, 2007 @ 05:18 AM

  • → Milestone changed from “1.1.1” to “1.1.2”
• 

  David Chelimsky January 16th, 2008 @ 02:53 PM

  • → Milestone changed from “1.1.2” to “1.1.3”
• 

  David Chelimsky February 5th, 2008 @ 04:42 PM

  • → Milestone cleared.
• 

  Aslak Hellesøy February 22nd, 2008 @ 08:09 AM

  We've had this since 1.1.0

  ruby all.rb -fh
  

• 

  Aslak Hellesøy February 22nd, 2008 @ 08:08 AM

  • → State changed from “open” to “resolved”
• 

  Bryan Helmkamp March 2nd, 2008 @ 02:22 AM

  What needs to be done to make this work for Rails apps? I'd re-open this ticket, but the status dropdown is not showing up for me.

• 

  Bryan Helmkamp March 3rd, 2008 @ 12:31 AM

  I've got this tracked down pretty well to the handling of ARGV in spec/extensions/main.rb and story/runner.rb interacting badly, but I'm struggling with a fix.

  I tried duping ARGV before we process it, which seems to work in my manual tests, but causes spec failures. Not sure if they are legit failures, or simply because the specs are unnecessarily depending on ARGV to be reset between spec runs (which could be handled by the specs not the code).

  --Bryan

• 

  Aslak Hellesøy March 4th, 2008 @ 06:23 PM

  • → State changed from “resolved” to “open”
• 

  Aslak Hellesøy March 4th, 2008 @ 06:24 PM

  I reopened this one - not sure why I resolved it before - still seems broken.

• 

  David Chelimsky March 4th, 2008 @ 06:30 PM

  It's only broken in rails. I think you may have closed it because it

  worked for non-rails.

• 

  Jonathan del Strother March 4th, 2008 @ 09:19 PM

  Just in the interim, I though I'd point out that

  ruby all.rb -- -fh
  

  seems to work fine...

• 

  Bryan Helmkamp March 5th, 2008 @ 03:33 AM

  The HTML output from story runner doesn't seem to be self contained and styled like the spec HTML output.

  I've got TextMate integration working for plain text stories, but the lack of a good HTML output format diminishes its value.

  Addressing this is on my personal TODO, but I thought it was worth mentioning in this thread.

• 

  Pirkka Hartikainen March 17th, 2008 @ 02:48 PM

  I did a quick rspec.css file for formatting the html output... but it looks like the backtrace is missing from the failed stories.

  However, even this simple color-coded html file compiling all the stories is useful for communicating with other people in the project. ^__^

  But it would be awesome for this to work just like the normal specs right out of the box.

  • rspec.css 2.4 KB
• 

  Aslak Hellesøy March 17th, 2008 @ 03:52 PM

  Pirkka - there is already a css in rspec/story_server/prototype/stylesheets/rspec.css.

• 

  Pirkka Hartikainen March 17th, 2008 @ 04:49 PM

  Uh oh thanks, I wasn't exactly aware of Story Server's existence. :)

  I took the existing css for a test drive but for now I'm sticking with my own, as reporting of user stories to domain people and editing them seem to be two different "use cases". I don't really need my domain folks editing plain text stories just yet, it's enough to have a nice single document to wave around.

  The browser editor for stories could really rock in the meetings though, hope there will be a server available soon!