Permalink
Commits on Dec 21, 2010
  1. compatibility with rspec 2.2+, backwards compatible with rspec 1.x/2.0

    Daniel Weaver & Stephan "Zed" Zuercher: sz committed Dec 21, 2010
Commits on Oct 13, 2010
  1. 1.6.3 gemspec

    nicksieger committed Oct 13, 2010
  2. 1.6.3 docs

    nicksieger committed Oct 13, 2010
Commits on Oct 12, 2010
Commits on Oct 11, 2010
Commits on Jul 13, 2010
  1. -Get the spec name *after* the spec has run. This allows for the capt…

    …ure of dynamically generated example descriptions.
    justfalter committed with nicksieger Jun 11, 2010
Commits on Jun 26, 2010
Commits on Jun 25, 2010
Commits on Mar 26, 2010
  1. Version 1.6.2

    nicksieger committed Mar 26, 2010
Commits on Mar 25, 2010
  1. Update copyright dates

    nicksieger committed Mar 25, 2010
  2. Version 1.6.1

    nicksieger committed Mar 25, 2010
Commits on Feb 23, 2010
  1. Report rspec before(:all) failures

    Edgars Beigarts committed Jan 13, 2010
Commits on May 5, 2009
  1. Update version to 1.6.0

    nicksieger committed May 5, 2009
Commits on May 4, 2009
  1. Set the prefix to be features, rather than cucumber.

    This makes it push the reports into a consistent location if CI_REPORTS is not set.
    mathie committed May 4, 2009
  2. Turns out that the reports directory isn't getting nuked between test…

    … runs.
    
    What's that all about? At a guess, rm_f doesn't actually take globs.
    mathie committed May 4, 2009
  3. Merge branch 'feature/cucumber-integration'

    * 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.
    mathie committed May 4, 2009
  4. Big pile o' passing specs. I suppose it's testing that it interacts c…

    …orrectly with the underlying API...
    mathie committed May 4, 2009
  5. Spec out the CucumberFailure.

    mathie committed May 4, 2009
  6. Nuke the CucumberDoc version for now.

    At least until I have the need to implement it. :)
    mathie committed May 4, 2009
  7. Inherit directly from Ast::Visitor.

    We don't need to worry too much about outputting some '.'s to STDOUT, so let's just inherit directly from the Visitor.
    mathie committed May 4, 2009
  8. Accept (and demonstrate) that Cucumber doesn't differentiate between …

    …failures and errors.
    mathie committed May 4, 2009
  9. Reimplement the visitor. I must have been smoking something on Friday.

    Now at least it actually creates testcases too, instead of erroneously creating new test suites.  What a numpty.
    mathie committed May 4, 2009