From joliss42 at gmail.com Mon Jan 31 14:57:54 2011 From: joliss42 at gmail.com (Jo Liss) Date: Mon, 31 Jan 2011 20:57:54 +0100 Subject: [rspec-devel] Exit code with --drb Message-ID: Hey everyone, I just wanted to ping the list about the "exit code with --drb" problem. (I'm not proposing a solution, so feel free to just ignore me. ^_^) When you run "rspec --drb spec/" (to access a Spork server), rspec will return 0 even when the tests fail. Elliot Winkler wrote about this in Sep 09, but nobody replied: http://groups.google.com/group/rspec/browse_thread/thread/08e08718cc54ce1d/e872cf108fae5671 Cucumber used to have the same problem, and apparently they were able to fix it relying on some change in Spork 0.5.1: https://rspec.lighthouseapp.com/projects/16211/tickets/355-exit-code-is-always-0-with-drb-despite-failure (commits are linked) Grepping the RSpec code and spec for 'drb' scares me sufficiently to not just get hacking on this -- but perhaps someone out there appreciates the pointers. -- Jo Liss http://opinionated-programmer.com/ From joliss42 at gmail.com Mon Jan 31 18:23:25 2011 From: joliss42 at gmail.com (Jo Liss) Date: Tue, 1 Feb 2011 00:23:25 +0100 Subject: [rspec-devel] How to regenerate Cucumber docs? Message-ID: I'd like to make some improvements to the documentation of RSpec, but I'm stuck on how to regenerate the Cucumber documentation. I'm almost embarrassed to ask this on the list, but: How do I generate the pretty HTML output (like http://relishapp.com/rspec/rspec-core/v/2-4/dir/example-groups/basic-structure-describe-it ) from the Cucumber feature description (like https://github.com/rspec/rspec-core/raw/v2.4.0/features/example_groups/basic_structure.feature )? Thanks, Jo -- Jo Liss http://opinionated-programmer.com/ From dchelimsky at gmail.com Mon Jan 31 20:31:34 2011 From: dchelimsky at gmail.com (David Chelimsky) Date: Mon, 31 Jan 2011 19:31:34 -0600 Subject: [rspec-devel] How to regenerate Cucumber docs? In-Reply-To: References: Message-ID: On Jan 31, 2011, at 5:23 PM, Jo Liss wrote: > I'd like to make some improvements to the documentation of RSpec, but > I'm stuck on how to regenerate the Cucumber documentation. I'm almost > embarrassed to ask this on the list, but: How do I generate the pretty > HTML output (like > http://relishapp.com/rspec/rspec-core/v/2-4/dir/example-groups/basic-structure-describe-it > ) from the Cucumber feature description (like > https://github.com/rspec/rspec-core/raw/v2.4.0/features/example_groups/basic_structure.feature > )? At the moment there is no way for you to do it. Relishapp does the formatting and is not open source. But you don't need to submit updates in that format. All I do is update the cukes as I normally would, and then push them up to relishapp using the relish gem (which _is_ open source). So if you submit a pull request, I can merge it in and it'll be part of my next push to relishapp. In terms of formatting, the only place you have any control is in the narrative, and it uses Markdown. Just keep in mind that the left margin is calculated by the position of the left-most characters in the narrative. That's important if you've got any code in the narrative. Does that work for you?