Permalink
Commits on Sep 6, 2011
  1. Release 0.1.4

    jbpros committed Sep 6, 2011
Commits on Sep 5, 2011
  1. Improve variable names in CLI support code loader

    Thanks to @fernandoacorreia for the suggestion.
    jbpros committed Sep 5, 2011
Commits on Sep 3, 2011
  1. Release 0.1.3

    jbpros committed Sep 3, 2011
  2. Allow several features to run at once and improve support code loadin…

    …g (CLI) (close #14)
    
    - Allow several features to run at once
    - Add support for --require
    - Improve features and support code API
    - Add "Cli" and "Volatile" configurations
    - Internal refactoring and cleanup
    - Cucumber.js can now fully test itself
    - Remove run_all_features script in favor of bin/cucumber.js
    - Refactorings
    jbpros committed Sep 3, 2011
Commits on Aug 9, 2011
  1. Refactor Cucumber.Parser to accept a hash of features instead of a si…

    …ngle feature source string (wip #14)
    jbpros committed Aug 9, 2011
Commits on Aug 8, 2011
  1. Add Cucumber.Runtime

    - Move `Cucumber` logic to `Cucumber.Runtime`
    - Make `Cucumber` a simple wrapper around `Cucumber.Runtime`
    jbpros committed Aug 8, 2011
  2. Update History

    jbpros committed Aug 8, 2011
  3. Add History

    jbpros committed Aug 8, 2011
Commits on Aug 2, 2011
Commits on Aug 1, 2011
  1. Release 0.1.2

    jbpros committed Aug 1, 2011
  2. Add failure reporting (close #20)

    - Exception messages and stack traces are now reported by the progress formatter
    - Failed scenario names and line numbers are also printed out
    jbpros committed Aug 1, 2011
Commits on Jul 28, 2011
  1. Release 0.1.1

    This is the first release to be published to NPM.
    jbpros committed Jul 28, 2011
  2. Throw a more explicit exception on missing feature path CLI argument

    But we need better CLI argument parsing/handling anyway.
    jbpros committed Jul 28, 2011
  3. Unify features with cucumber-features (close #21)

    - In addition to Aruba, Cucumber.js can now run the "common features" against itself. It uses the same inner step definitions as Aruba.
    - A few debug methods were added.
    jbpros committed Jul 28, 2011
Commits on Jul 26, 2011
  1. Clean up features (wip #21)

    - move JS step definitions from cucumber_js_mappings.rb to .js files
    - add a script to run all features at once
    - move legacy features to features/legacy
    jbpros committed Jul 26, 2011
Commits on Jul 25, 2011
  1. Make all core.feature scenarios pass

    - All core scenarios are green!
    - Let's hit 0.1
    jbpros committed Jul 25, 2011
Commits on Jul 24, 2011
  1. Add support for undefined steps (close #19)

    - Fourth core.feature scenario passing!
    - The tree walker handles undefined steps and scenarios nicely
    - Progress formatter also knows this concept
    jbpros committed Jul 24, 2011
Commits on Jul 23, 2011
  1. Add support for pending steps (close #18)

    - This marks the third core.feature scenario passing
    - The progress formatter is also ready for pending steps
    jbpros committed Jul 23, 2011
Commits on Jul 22, 2011
Commits on Jul 21, 2011
  1. Handle failures and add 'progress' formatter (close #6, #16, #17)

    - Failing steps are now properly handled and following steps in scenario are skipped
    - Second core.feature scenario is passing
    - Progress formatter is now available and used by default
    - We still miss stack trace output on failure
    jbpros committed Jul 21, 2011
Commits on Jul 19, 2011
  1. Load Gherkin module without any hack in browsers

    All Gherkin languages are now potentially supported by Cucumber.js in browsers.
    jbpros committed Jul 19, 2011
Commits on Jul 17, 2011
  1. Modularize Cucumber.js (close #3)

    - This temporarily limits Gherkin language support to English only. Browserify does not know how to handle dynamic module names and Gherkin is just doing that.
    jbpros committed Jul 17, 2011