…ure of dynamically generated example descriptions.
This makes it push the reports into a consistent location if CI_REPORTS is not set.
… runs. What's that all about? At a guess, rm_f doesn't actually take globs.
* feature/cucumber-integration: The remainder of the specs, I think. Not test-driving is painful... Big pile o' passing specs. I suppose it's testing that it interacts correctly with the underlying API... Spec out the CucumberFailure. Nuke the CucumberDoc version for now. Inherit directly from Ast::Visitor. Accept (and demonstrate) that Cucumber doesn't differentiate between failures and errors. Implement catching and reporting of errors. If there are 0 errors, don't check for errors elements. Reimplement the visitor. I must have been smoking something on Friday. Pending steps should not be reported as errors. Start of an implementation of the visitor. Expect a slightly different filename. We have to require the cucumber loader slightly differently otherwise it doesn't autoload step definitions. Acceptance tests for cucumber integration. Add in a place to stick specs for the Cucumber integration. Add in some tests for the Cucumber setup rake task. Infrastructure for Cucumber integration.
…orrectly with the underlying API...
At least until I have the need to implement it. :)
We don't need to worry too much about outputting some '.'s to STDOUT, so let's just inherit directly from the Visitor.
…failures and errors.
Now at least it actually creates testcases too, instead of erroneously creating new test suites. What a numpty.
This keeps the Cucumber implementation in step with the RSpec one. Shame there isn't a way of reporting pending steps, though?