JBehave Core - Version 2.5.6 (May 15, 2010)

Improvement

  • [JBEHAVE-207] - Exclude SCM patterns from ScenarioClassNameFinder
  • [JBEHAVE-287] - Dry-run Scenario to determine that no steps are Pending

JBehave Core - Version 2.5.5 (May 8, 2010)

Improvement

  • [JBEHAVE-283] - Report Renderer should be failure aware

Task

JBehave Core - Version 2.5.4 (May 5, 2010)

Bug

  • [JBEHAVE-282] - Using GivenScenarios causes failed tests to be forgotten

JBehave Core - Version 2.5.3 (May 3, 2010)

Bug

JBehave Core - Version 2.5.2 (May 1, 2010)

Bug

  • [JBEHAVE-277] - Reports are outputted to $ANT_HOME/lib instead of target dir
  • [JBEHAVE-278] - 'And' Step (AndStep) ignores CandidateStep step type
  • [JBEHAVE-279] - GivenScenarios runs called scenario as PENDING not the implemented version

Improvement

  • [JBEHAVE-276] - Clarify the Scenario Reporters example and API

Task

  • [JBEHAVE-273] - Ensure jbehave-core dependencies are excluded or shaded
  • [JBEHAVE-274] - Add example showing use of SpringJUnit4ClassRunner

JBehave Core - Version 2.5.1 (Apr 5, 2010)

Improvement

  • [JBEHAVE-245] - Abstract scenarios should not be executed
  • [JBEHAVE-250] - Provide better exception handling when Maven/Ant fails with classloader injected
  • [JBEHAVE-252] - Improve documentation on scenario and step configuration
  • [JBEHAVE-253] - ClassLoader-aware Spring ApplicationContext factory

JBehave Core - Version 2.5 (Mar 9, 2010)

Bug

  • [JBEHAVE-206] - Regex overflow in using Examples table
  • [JBEHAVE-242] - Regex Stackoverflow error with ExampleTables on Windows

Improvement

  • [JBEHAVE-162] - Need to be able to set order of steps for matching
  • [JBEHAVE-243] - Get rid of trailing whitespaces after the table

New Feature

  • [JBEHAVE-133] - Allow Steps dependencies to be composable via PicoContainer
  • [JBEHAVE-163] - Support comments in plain-text scenarios
  • [JBEHAVE-230] - Add Narrative elements to Story parsing
  • [JBEHAVE-239] - Add @BeforeStory and @AfterStory annotations in candidate steps
  • [JBEHAVE-240] - Allow Steps dependencies to be composable via Spring
  • [JBEHAVE-241] - Allow Steps dependencies to be composable via Guice

Task

  • [JBEHAVE-235] - Improve documentation on running trader example with reports
  • [JBEHAVE-236] - Checking out, building and testing JBehave from scratch

JBehave Core - Version 2.4.1 (Feb 6, 2010)

Improvement

  • [JBEHAVE-237] - HTML/XML reports should handle better missing or null values from the examples table
  • [JBEHAVE-238] - Provide default values for KeyWords, when not reading from a I18n bundle

New Feature

  • [JBEHAVE-163] - Support comments in plain-text scenarios

Task

  • [JBEHAVE-235] - Improve documentation on running trader example with reports
  • [JBEHAVE-236] - Checking out, building and testing JBehave from scratch

JBehave Core - Version 2.4 (Jan 20, 2010)

Bug

  • [JBEHAVE-200] - Candidate step does not match AND steps
  • [JBEHAVE-211] - StringListConverter converts an empty String to a one element List instead of an empty List
  • [JBEHAVE-212] - Starting words are not updated when keywords are overridden in steps configuration
  • [JBEHAVE-221] - Maven runner documentation has incorrect capitalization (should be camel case)
  • [JBEHAVE-223] - 0.0 gets parsed as a Long
  • [JBEHAVE-224] - Double.NaN should be parseable into a double
  • [JBEHAVE-225] - Multiline scenario title is parsed as empty

Improvement

  • [JBEHAVE-165] - Allow scenarios to run in batch mode
  • [JBEHAVE-175] - Add support for BigDecimal and BigInteger parameters
  • [JBEHAVE-196] - Candidate steps should be aware of the method annotation type when matching textual steps
  • [JBEHAVE-199] - Allow ScenarioClassLoader to instantiate scenarios using default constructor
  • [JBEHAVE-202] - Allow class loader injection to be optional in scenario classes when running in command line
  • [JBEHAVE-204] - Scenario runner should report before and after story only once when running given scenarios
  • [JBEHAVE-209] - Add ParameterConverter for ExamplesTable
  • [JBEHAVE-210] - Report embedded status in before/after story events
  • [JBEHAVE-215] - Allow a step to be reused between scenarios with and without example tables
  • [JBEHAVE-217] - Allow configuration to be overridden
  • [JBEHAVE-219] - Create standard human and machine-readable reports
  • [JBEHAVE-222] - Add/rename examples events in ScenarioReporter
  • [JBEHAVE-229] - PatternScenarioParser should depend on KeyWords and not Configuration
  • [JBEHAVE-231] - Allow CandidateSteps methods to be defined in POJOs

New Feature

Task

  • [JBEHAVE-197] - Improve documentation of candidate steps and aliases in reference guide
  • [JBEHAVE-203] - StepsBehaviour tests fail with JDK 1.5

JBehave Core - Version 2.3.2 (Nov 3, 2009)

Bug

  • [JBEHAVE-200] - Candidate step does not match AND steps

Improvement

  • [JBEHAVE-199] - Allow ScenarioClassLoader to instantiate scenarios using default constructor
  • [JBEHAVE-202] - Allow class loader injection to be optional in scenario classes when running in command line

JBehave Core - Version 2.3.1 (Oct 31, 2009)

Bug

  • [JBEHAVE-198] - I18n keywords resource bundle not found by Ant task

Improvement

  • [JBEHAVE-175] - Add support for BigDecimal and BigInteger parameters
  • [JBEHAVE-196] - Candidate steps should be aware of the method annotation type when matching textual steps

Task

  • [JBEHAVE-197] - Improve documentation of candidate steps and aliases in reference guide

JBehave Core - Version 2.3 (Oct 10, 2009)

Improvement

  • [JBEHAVE-164] - I18N Keywords
  • [JBEHAVE-173] - Support annotated named parameters in Steps methods
  • [JBEHAVE-174] - Improve documentation
  • [JBEHAVE-178] - Allow output patterns to be overridden and localised in PrintStreamScenarioReporter

New Feature

Task

JBehave Core - Version 2.2.1 (Aug 25, 2009)

Improvement

  • [JBEHAVE-170] - Alias (singular) annotation in addition to Aliases (plural)

JBehave Core - Version 2.2 (Apr 25, 2009)

Bug

  • [JBEHAVE-127] - Doesn't find scenarios with numbers in the file name
  • [JBEHAVE-152] - Scenario's in the default package cause NullPointerException
  • [JBEHAVE-155] - Maven plugin can't identify Scenario classes in src/test/java

Improvement

  • [JBEHAVE-117] - Should throw an exception if two candidate step methods have the same annotation
  • [JBEHAVE-144] - Ensure utility methods should be independent of unit-testing framework
  • [JBEHAVE-145] - Unit-test runners should decorate Exceptions a bit more clearly
  • [JBEHAVE-147] - Improve javadocs
  • [JBEHAVE-154] - Scenario keyword should include any separation char, e.g. ":"
  • [JBEHAVE-159] - Support multiple CandidateSteps instances in Stepdoc generation
  • [JBEHAVE-160] - Improve regex-based scenario parsing

New Feature

  • [JBEHAVE-131] - Aliases for steps
  • [JBEHAVE-158] - Generate StepDoc from annotated methods of CandidateSteps instance

Task

  • [JBEHAVE-27] - Document best practices and suggested use cases

JBehave Core - Version 2.1 (Oct 25, 2008)

Bug

  • [JBEHAVE-135] - Scenario class lookup fails on Windows
  • [JBEHAVE-138] - Bug recognising Step with content starting with Given, When, Then, And

Improvement

  • [JBEHAVE-132] - Support multiple test frameworks
  • [JBEHAVE-134] - Extract CandidateSteps interface
  • [JBEHAVE-137] - Make default converter classes publicly accessible and allow configuration of number format

New Feature

Task

  • [JBEHAVE-143] - Improve documentation for scenario developers

Wish

  • [JBEHAVE-140] - new StepMonitor method - executingStep(..)
  • [JBEHAVE-141] - Allow mutability of StepsConfiguration instance
  • [JBEHAVE-142] - RunnableScenario.addSteps(CandidateSteps) -> method needed

JBehave Core - Version 2.0.1 (Oct 7, 2008)

Bug

  • [JBEHAVE-135] - Scenario class lookup fails on Windows

Improvement

  • [JBEHAVE-137] - Make default converter classes publicly accessible and allow configuration of number format

JBehave Core - Version 2.0 (Sep 1, 2008)

Bug

  • [JBEHAVE-105] - Should not require a space before a new line
  • [JBEHAVE-114] - Build isn't running the scenarios
  • [JBEHAVE-121] - Only Parentheses are escaped in DollarStepPatternBuilder

Improvement

  • [JBEHAVE-26] - Two Minute Intro for JBehave needs some work
  • [JBEHAVE-116] - Need really great javadoc for all injectable / configurable classes
  • [JBEHAVE-119] - DollarArgThingumy should take the $ as an argument - this is what people are most likely to want to change
  • [JBEHAVE-124] - Eclipse can't find the test to run when it's in JBehave's jar
  • [JBEHAVE-128] - Candidate step should support generic parameter conversion

New Feature