[jbehave-dev] [jira] Commented: (JBEHAVE-584) Support loading stories from Google Docs

[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=276744#comment-276744 ] Mauro Talevi commented on JBEHAVE-584: -- Presumably, we should be able to maintain the format

[jbehave-dev] [jira] Commented: (JBEHAVE-584) Support loading stories from Google Docs

[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=276878#comment-276878 ] Mauro Talevi commented on JBEHAVE-584: -- Thanks, applied patch, although had to applied

[jbehave-dev] [jira] Commented: (JBEHAVE-584) Support loading stories from Google Docs

[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=276883#comment-276883 ] Mauro Talevi commented on JBEHAVE-584: -- No problem :-) I find that using command-line git

[jbehave-dev] [jira] Updated: (JBEHAVE-586) Reporting mojos do not resolve output directory relative to project directory, but to relative to current directory

[ https://jira.codehaus.org/browse/JBEHAVE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-586: - Fix Version/s: 3.5 Reporting mojos do not resolve output directory relative to project directory,

[jbehave-dev] [jira] Resolved: (JBEHAVE-586) Reporting mojos do not resolve output directory relative to project directory, but to relative to current directory

[ https://jira.codehaus.org/browse/JBEHAVE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-586. -- Resolution: Fixed Pulled patch, with thanks. Reporting mojos do not resolve output directory

[jbehave-dev] [jira] Updated: (JBEHAVE-588) FailingUponPendingSteps only works for normal steps, it does not do as it suggests for composite steps

[ https://jira.codehaus.org/browse/JBEHAVE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-588: - Affects Version/s: (was: 3.5) 3.4 Fix Version/s: 3.x

[jbehave-dev] [jira] Resolved: (JBEHAVE-587) Website Documentation - Pending Steps page refers to incorrect strategy class FailingPendingStepStrategy

[ https://jira.codehaus.org/browse/JBEHAVE-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-587. -- Resolution: Fixed Fix Version/s: 3.5 Assignee: Mauro Talevi Website Documentation

[jbehave-dev] [jira] Resolved: (JBEHAVE-588) FailingUponPendingSteps only works for normal steps, it does not do as it suggests for composite steps

[ https://jira.codehaus.org/browse/JBEHAVE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-588. -- Resolution: Fixed Fix Version/s: (was: 3.x) 3.5 Assignee:

[jbehave-dev] [jira] Commented: (JBEHAVE-584) Support loading stories from Google Docs

[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277526#comment-277526 ] Mauro Talevi commented on JBEHAVE-584: -- Hi Bart, added jbehave-google-example which can be

[jbehave-dev] [jira] Created: (JBEHAVE-589) Ignorable steps before And steps should not be marked as pending

Ignorable steps before And steps should not be marked as pending Key: JBEHAVE-589 URL: https://jira.codehaus.org/browse/JBEHAVE-589 Project: JBehave Issue Type: Bug

[jbehave-dev] [jira] Resolved: (JBEHAVE-578) Story execution not failing-fast when ignoreFailuresInStories=false

[ https://jira.codehaus.org/browse/JBEHAVE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-578. -- Resolution: Fixed Added threads example to show multi-threading behaviour. Story execution

[jbehave-dev] [jira] Reopened: (JBEHAVE-578) Story execution not failing-fast when ignoreFailuresInStories=false

[ https://jira.codehaus.org/browse/JBEHAVE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reopened JBEHAVE-578: -- Story execution not failing-fast when ignoreFailuresInStories=false

[jbehave-dev] [jira] Resolved: (JBEHAVE-590) Add failed step as UUIDExceptionWrapper message

[ https://jira.codehaus.org/browse/JBEHAVE-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-590. -- Resolution: Fixed Add failed step as UUIDExceptionWrapper message

[jbehave-dev] [jira] Resolved: (JBEHAVE-578) Story execution not failing-fast when ignoreFailuresInStories=false

[ https://jira.codehaus.org/browse/JBEHAVE-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-578. -- Resolution: Fixed Story execution not failing-fast when ignoreFailuresInStories=false

[jbehave-dev] [jira] Updated: (JBEHAVE-584) Support loading stories from Google Docs

[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-584: - Component/s: (was: ODF Support) (was: Core) Google Support

[jbehave-dev] [jira] Resolved: (JBEHAVE-584) Support loading stories from Google Docs

[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-584. -- Resolution: Fixed Support loading stories from Google Docs

[jbehave-dev] [jira] Commented: (JBEHAVE-584) Support loading stories from Google Docs

[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277706#comment-277706 ] Mauro Talevi commented on JBEHAVE-584: -- Hi Bart, as you originally suggested, a separate

[jbehave-dev] [jira] Resolved: (JBEHAVE-558) Maven build should be updated to play well with Eclipse m2e 1.0

[ https://jira.codehaus.org/browse/JBEHAVE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-558. -- Resolution: Fixed Maven build should be updated to play well with Eclipse m2e 1.0

[jbehave-dev] [jira] Resolved: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-543. -- Resolution: Fixed Adriano, resolving issue as it is feature complete. Any additional refactor

[jbehave-dev] [jira] Updated: (JBEHAVE-374) Upgrade to commons-lang 3.0 to correctly escape characters from the Unicode Supplemental Multilingual Plane

[ https://jira.codehaus.org/browse/JBEHAVE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-374: - Fix Version/s: (was: 3.5) 3.x Unfortunately, a commons-lang 3.x is not

[jbehave-dev] [jira] Commented: (JBEHAVE-543) Before/After Story/Scenario methods could accept parameters that have meaning at that moment

[ https://jira.codehaus.org/browse/JBEHAVE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=277718#comment-277718 ] Mauro Talevi commented on JBEHAVE-543: -- Merged, thanks! Before/After Story/Scenario methods

[jbehave-dev] [jira] Resolved: (JBEHAVE-593) Per-stories lifecycle steps requires same-thread executor service

[ https://jira.codehaus.org/browse/JBEHAVE-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-593. -- Resolution: Fixed Per-stories lifecycle steps requires same-thread executor service

[jbehave-dev] [jira] Work started: (JBEHAVE-548) @BeforeExample und @AfterExample

[ https://jira.codehaus.org/browse/JBEHAVE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-548 started by Mauro Talevi. @BeforeExample und @AfterExample Key: JBEHAVE-548 URL:

[jbehave-dev] [jira] Updated: (JBEHAVE-548) Add support for annotated steps before and after example scenarios

[ https://jira.codehaus.org/browse/JBEHAVE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-548: - Summary: Add support for annotated steps before and after example scenarios (was: @BeforeExample

[jbehave-dev] [jira] Commented: (JBEHAVE-163) Support comments in plain-text scenarios

[ https://jira.codehaus.org/browse/JBEHAVE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=278020#comment-278020 ] Mauro Talevi commented on JBEHAVE-163: -- Yes, comments in tables are allowed using the |--

[jbehave-dev] [jira] Created: (JBEHAVE-594) Upgrade to Wicket 1.5

Upgrade to Wicket 1.5 - Key: JBEHAVE-594 URL: https://jira.codehaus.org/browse/JBEHAVE-594 Project: JBehave Issue Type: Task Components: Web Runner Reporter: Mauro Talevi Assignee: Mauro

[jbehave-dev] [jira] Commented: (JBEHAVE-548) Add support for annotated steps before and after example scenarios

[ https://jira.codehaus.org/browse/JBEHAVE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=278184#comment-278184 ] Mauro Talevi commented on JBEHAVE-548: -- Erich, this feature has already been implemented in

[jbehave-dev] [jira] Resolved: (JBEHAVE-594) Upgrade to Wicket 1.5

[ https://jira.codehaus.org/browse/JBEHAVE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-594. -- Resolution: Fixed Upgrade to Wicket 1.5 - Key: JBEHAVE-594

[jbehave-dev] [jira] Resolved: (JBEHAVE-574) Improve documentation on using archetypes

[ https://jira.codehaus.org/browse/JBEHAVE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-574. -- Resolution: Fixed Improve documentation on using archetypes

[jbehave-dev] [jira] Resolved: (JBEHAVE-564) Update Ant and Maven configuration documentation

[ https://jira.codehaus.org/browse/JBEHAVE-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-564. -- Resolution: Fixed Update Ant and Maven configuration documentation

[jbehave-dev] [jira] Updated: (JBEHAVE-586) StoryReporterBuilder code location should be settable from the output directory by Ant tasks and Maven goals

[ https://jira.codehaus.org/browse/JBEHAVE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-586: - Component/s: Ant Tasks Issue Type: Improvement (was: Bug) Summary: StoryReporterBuilder

[jbehave-dev] [jira] Resolved: (JBEHAVE-548) Add support for annotated steps before and after example scenarios

[ https://jira.codehaus.org/browse/JBEHAVE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-548. -- Resolution: Fixed Add support for annotated steps before and after example scenarios

[jbehave-dev] [jira] Resolved: (JBEHAVE-595) Use name as String representation of Format

[ https://jira.codehaus.org/browse/JBEHAVE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-595. -- Resolution: Fixed Use name as String representation of Format

[jbehave-dev] [jira] Resolved: (JBEHAVE-596) Upgrade to Hudson 2.1.0

[ https://jira.codehaus.org/browse/JBEHAVE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-596. -- Resolution: Fixed Upgrade to Hudson 2.1.0 --- Key:

[jbehave-dev] [jira] Created: (JBEHAVE-596) Upgrade to Hudson 2.1.0

Upgrade to Hudson 2.1.0 --- Key: JBEHAVE-596 URL: https://jira.codehaus.org/browse/JBEHAVE-596 Project: JBehave Issue Type: Task Components: Hudson Support Reporter: Mauro Talevi

[jbehave-dev] [jira] Resolved: (JBEHAVE-577) Flash support

[ https://jira.codehaus.org/browse/JBEHAVE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-577. -- Resolution: Fixed Flash support - Key: JBEHAVE-577

[jbehave-dev] [jira] Created: (JBEHAVE-598) Failing build on Windows

Failing build on Windows Key: JBEHAVE-598 URL: https://jira.codehaus.org/browse/JBEHAVE-598 Project: JBehave Issue Type: Task Components: Core Affects Versions: 3.5 Environment: Windows

[jbehave-dev] [jira] Resolved: (JBEHAVE-599) Failures in view do not cause build to fail

[ https://jira.codehaus.org/browse/JBEHAVE-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-599. -- Resolution: Fixed Failures in view do not cause build to fail

[jbehave-dev] [jira] Created: (JBEHAVE-600) Scenario title parsed to empty on Windows

Scenario title parsed to empty on Windows - Key: JBEHAVE-600 URL: https://jira.codehaus.org/browse/JBEHAVE-600 Project: JBehave Issue Type: Bug Affects Versions: 3.5, 3.4.5 Environment:

[jbehave-dev] [jira] Resolved: (JBEHAVE-600) Scenario title parsed to empty on Windows

[ https://jira.codehaus.org/browse/JBEHAVE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-600. -- Resolution: Fixed Scenario title parsed to empty on Windows

[jbehave-dev] [jira] Updated: (JBEHAVE-602) Multiline scenario title appears on one line in HTML report

[ https://jira.codehaus.org/browse/JBEHAVE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-602: - Fix Version/s: 3.5.2 Assignee: Mauro Talevi Summary: Multiline scenario title

[jbehave-dev] [jira] Resolved: (JBEHAVE-602) Multiline scenario title appears on one line in HTML report

[ https://jira.codehaus.org/browse/JBEHAVE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-602. -- Resolution: Fixed Fix Version/s: 3.6 Multiline scenario title appears on one line in HTML

[jbehave-dev] [jira] Created: (JBEHAVE-607) Add Scala support

Add Scala support - Key: JBEHAVE-607 URL: https://jira.codehaus.org/browse/JBEHAVE-607 Project: JBehave Issue Type: New Feature Components: Scala Support Reporter: Mauro Talevi Assignee:

[jbehave-dev] [jira] Work started: (JBEHAVE-607) Add Scala support

[ https://jira.codehaus.org/browse/JBEHAVE-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-607 started by Mauro Talevi. Add Scala support - Key: JBEHAVE-607 URL:

[jbehave-dev] [jira] Created: (JBEHAVE-609) Allow named parameters to be replaced in table row parameters values

Allow named parameters to be replaced in table row parameters values Key: JBEHAVE-609 URL: https://jira.codehaus.org/browse/JBEHAVE-609 Project: JBehave Issue Type:

[jbehave-dev] [jira] Updated: (JBEHAVE-609) Allow named parameters to be replaced in table row parameters values

[ https://jira.codehaus.org/browse/JBEHAVE-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-609: - Description: Named parameters, e.g. coming from the examples table in parametrised scenarios,

[jbehave-dev] [jira] Created: (JBEHAVE-610) Add Jenkins support

Add Jenkins support --- Key: JBEHAVE-610 URL: https://jira.codehaus.org/browse/JBEHAVE-610 Project: JBehave Issue Type: New Feature Reporter: Mauro Talevi Assignee: Mauro Talevi Fix For:

[jbehave-dev] [jira] Updated: (JBEHAVE-610) Add Jenkins support

[ https://jira.codehaus.org/browse/JBEHAVE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-610: - Component/s: Jenkins Support Add Jenkins support --- Key:

[jbehave-dev] [jira] Created: (JBEHAVE-611) The StoryRunner should use the configured FailureStrategy when resetting the story failure state

The StoryRunner should use the configured FailureStrategy when resetting the story failure state Key: JBEHAVE-611 URL: https://jira.codehaus.org/browse/JBEHAVE-611

[jbehave-dev] [jira] Updated: (JBEHAVE-614) Groovy 1.8.3 upgrade

[ https://jira.codehaus.org/browse/JBEHAVE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-614: - Affects Version/s: (was: 3.5.1) Fix Version/s: 3.5.2 Groovy 1.8.3 upgrade

[jbehave-dev] [jira] Work started: (JBEHAVE-611) The StoryRunner should use the configured FailureStrategy when resetting the story failure state

[ https://jira.codehaus.org/browse/JBEHAVE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-611 started by Mauro Talevi. The StoryRunner should use the configured FailureStrategy when resetting the story failure state

[jbehave-dev] [jira] Assigned: (JBEHAVE-611) The StoryRunner should use the configured FailureStrategy when resetting the story failure state

[ https://jira.codehaus.org/browse/JBEHAVE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-611: Assignee: Mauro Talevi The StoryRunner should use the configured FailureStrategy when

[jbehave-dev] [jira] Commented: (JBEHAVE-619) ParameterConverters throwing ConcurrentModificationException

[ https://jira.codehaus.org/browse/JBEHAVE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282391#comment-282391 ] Mauro Talevi commented on JBEHAVE-619: -- Hi Jean, added your contributed test to

[jbehave-dev] [jira] Updated: (JBEHAVE-616) Screenshots don't need to be taken for pending steps

[ https://jira.codehaus.org/browse/JBEHAVE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-616: - Affects Version/s: (was: web-3.5) (was: web-3.4) Fix

[jbehave-dev] [jira] Updated: (JBEHAVE-618) Show SauceLabs URL in StoryNavigator output

[ https://jira.codehaus.org/browse/JBEHAVE-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-618: - Fix Version/s: web-3.5 web-3.4.1 Show SauceLabs URL in StoryNavigator output

[jbehave-dev] [jira] Resolved: (JBEHAVE-620) Allow FlashDriver javascript-enabled delegate to be injected

[ https://jira.codehaus.org/browse/JBEHAVE-620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-620. -- Resolution: Fixed Allow FlashDriver javascript-enabled delegate to be injected

[jbehave-dev] [jira] Updated: (JBEHAVE-603) Add retry and better logging for situations where WebDriverScreenshotOnFailure can't retrieve and save the screenshot.

[ https://jira.codehaus.org/browse/JBEHAVE-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-603: - Fix Version/s: web-3.5 web-3.4.1 Add retry and better logging for situations

[jbehave-dev] [jira] Updated: (JBEHAVE-605) Allow choice of Selenium version on Saucelabs - via system property : selenium.version

[ https://jira.codehaus.org/browse/JBEHAVE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-605: - Fix Version/s: web-3.5 web-3.4.1 Allow choice of Selenium version on Saucelabs -

[jbehave-dev] [jira] Updated: (JBEHAVE-604) SauceLabs takes a 'setContext' equivalent via the executeJavascript() facility - new ContextView to support that.

[ https://jira.codehaus.org/browse/JBEHAVE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-604: - Fix Version/s: web-3.5 web-3.4.1 SauceLabs takes a 'setContext' equivalent via

[jbehave-dev] [jira] Updated: (JBEHAVE-606) Upgrade Selenium to 2.7

[ https://jira.codehaus.org/browse/JBEHAVE-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-606: - Fix Version/s: web-3.5 web-3.4.1 Upgrade Selenium to 2.7

[jbehave-dev] [jira] Updated: (JBEHAVE-612) Groovy base page classes in web-selenium

[ https://jira.codehaus.org/browse/JBEHAVE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-612: - Fix Version/s: web-3.5 web-3.4.1 Groovy base page classes in web-selenium

[jbehave-dev] [jira] Updated: (JBEHAVE-613) PicoConainer Injection type for typical Groovy+WebDriver cases

[ https://jira.codehaus.org/browse/JBEHAVE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-613: - Fix Version/s: web-3.5 web-3.4.1 PicoConainer Injection type for typical

[jbehave-dev] [jira] Updated: (JBEHAVE-614) Groovy 1.8.3 upgrade

[ https://jira.codehaus.org/browse/JBEHAVE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-614: - Fix Version/s: web-3.5 web-3.4.1 3.6 Groovy 1.8.3 upgrade

[jbehave-dev] [jira] Updated: (JBEHAVE-611) The StoryRunner should use the configured FailureStrategy when resetting the story failure state

[ https://jira.codehaus.org/browse/JBEHAVE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-611: - Component/s: Core The StoryRunner should use the configured FailureStrategy when resetting the

[jbehave-dev] [jira] Resolved: (JBEHAVE-611) The StoryRunner should use the configured FailureStrategy when resetting the story failure state

[ https://jira.codehaus.org/browse/JBEHAVE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-611. -- Resolution: Fixed The StoryRunner should use the configured FailureStrategy when resetting the

[jbehave-dev] [jira] Created: (JBEHAVE-621) Pending step failures not detected in stories view generation

Pending step failures not detected in stories view generation - Key: JBEHAVE-621 URL: https://jira.codehaus.org/browse/JBEHAVE-621 Project: JBehave Issue Type: Bug

[jbehave-dev] [jira] Resolved: (JBEHAVE-621) Pending step failures not detected in stories view generation

[ https://jira.codehaus.org/browse/JBEHAVE-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-621. -- Resolution: Fixed Pending step failures not detected in stories view generation

[jbehave-dev] [jira] Resolved: (JBEHAVE-607) Add Scala support

[ https://jira.codehaus.org/browse/JBEHAVE-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-607. -- Resolution: Fixed Add Scala support - Key: JBEHAVE-607

[jbehave-dev] [jira] Created: (JBEHAVE-622) Improve embedder monitoring

Improve embedder monitoring Key: JBEHAVE-622 URL: https://jira.codehaus.org/browse/JBEHAVE-622 Project: JBehave Issue Type: Improvement Components: Ant Tasks, Core, Maven Plugin Reporter:

[jbehave-dev] [jira] Resolved: (JBEHAVE-622) Improve embedder monitoring

[ https://jira.codehaus.org/browse/JBEHAVE-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-622. -- Resolution: Fixed Improve embedder monitoring

[jbehave-dev] [jira] Created: (JBEHAVE-623) Support AtomicInteger and AtomicLong parameters

Support AtomicInteger and AtomicLong parameters --- Key: JBEHAVE-623 URL: https://jira.codehaus.org/browse/JBEHAVE-623 Project: JBehave Issue Type: Improvement Components: Core

[jbehave-dev] [jira] Resolved: (JBEHAVE-623) Support AtomicInteger and AtomicLong parameters

[ https://jira.codehaus.org/browse/JBEHAVE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-623. -- Resolution: Fixed Support AtomicInteger and AtomicLong parameters

[jbehave-dev] [jira] Commented: (JBEHAVE-619) ParameterConverters throwing ConcurrentModificationException

[ https://jira.codehaus.org/browse/JBEHAVE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282414#comment-282414 ] Mauro Talevi commented on JBEHAVE-619: -- Added optional boolean flag to trigger thread-safe

[jbehave-dev] [jira] Resolved: (JBEHAVE-619) ParameterConverters throwing ConcurrentModificationException

[ https://jira.codehaus.org/browse/JBEHAVE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-619. -- Resolution: Fixed Fix Version/s: 3.6 ParameterConverters throwing

[jbehave-dev] [jira] Resolved: (JBEHAVE-610) Add Jenkins support

[ https://jira.codehaus.org/browse/JBEHAVE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-610. -- Resolution: Fixed Add Jenkins support --- Key: JBEHAVE-610

[jbehave-dev] [jira] Commented: (JBEHAVE-625) meta-filter (command line) needs a proper albeit little language

[ https://jira.codehaus.org/browse/JBEHAVE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282680#comment-282680 ] Mauro Talevi commented on JBEHAVE-625: -- We could introduce a prefix-based convention for

[jbehave-dev] [jira] Commented: (JBEHAVE-624) Nested Composite Steps are not resolved

[ https://jira.codehaus.org/browse/JBEHAVE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282708#comment-282708 ] Mauro Talevi commented on JBEHAVE-624: -- The nested composite steps use case was never

[jbehave-dev] [jira] Updated: (JBEHAVE-624) Support nested composite steps

[ https://jira.codehaus.org/browse/JBEHAVE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-624: - Fix Version/s: 3.6 3.5.3 Assignee: Mauro Talevi Issue Type:

[jbehave-dev] [jira] Work started: (JBEHAVE-624) Support nested composite steps

[ https://jira.codehaus.org/browse/JBEHAVE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-624 started by Mauro Talevi. Support nested composite steps -- Key: JBEHAVE-624 URL:

[jbehave-dev] [jira] Commented: (JBEHAVE-624) Support nested composite steps

[ https://jira.codehaus.org/browse/JBEHAVE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=282766#comment-282766 ] Mauro Talevi commented on JBEHAVE-624: -- The use case is valid and is now supported. Please

[jbehave-dev] [jira] Updated: (JBEHAVE-617) Speed up RegexStoryParser by removing leading .*

[ https://jira.codehaus.org/browse/JBEHAVE-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-617: - Fix Version/s: 3.6 Summary: Speed up RegexStoryParser by removing leading .* (was: speed

[jbehave-dev] [jira] Updated: (JBEHAVE-615) Ignore full-stop/period|punctation at end of step

[ https://jira.codehaus.org/browse/JBEHAVE-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-615: - Priority: Minor (was: Major) Fix Version/s: 3.6 3.5.3 Assignee:

[jbehave-dev] [jira] Created: (JBEHAVE-626) Wrap runtime exceptions as MojoFailureException to avoid FATAL outcome

Wrap runtime exceptions as MojoFailureException to avoid FATAL outcome -- Key: JBEHAVE-626 URL: https://jira.codehaus.org/browse/JBEHAVE-626 Project: JBehave Issue Type:

[jbehave-dev] [jira] Resolved: (JBEHAVE-626) Wrap runtime exceptions as MojoFailureException to avoid FATAL outcome

[ https://jira.codehaus.org/browse/JBEHAVE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-626. -- Resolution: Fixed Wrap runtime exceptions as MojoFailureException to avoid FATAL outcome

[jbehave-dev] [jira] Resolved: (JBEHAVE-624) Support nested composite steps

[ https://jira.codehaus.org/browse/JBEHAVE-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-624. -- Resolution: Fixed Support nested composite steps --

[jbehave-dev] [jira] Updated: (JBEHAVE-615) Ignore full-stop/period|punctation at end of step

[ https://jira.codehaus.org/browse/JBEHAVE-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-615: - Fix Version/s: (was: 3.5.3) Ignore full-stop/period|punctation at end of step

[jbehave-dev] [jira] Updated: (JBEHAVE-625) MetaFilter should support logic written in a scripting language

[ https://jira.codehaus.org/browse/JBEHAVE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-625: - Summary: MetaFilter should support logic written in a scripting language (was: meta-filter (command

[jbehave-dev] [jira] Updated: (JBEHAVE-629) Groovy 1.8.4 upgrade

[ https://jira.codehaus.org/browse/JBEHAVE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-629: - Fix Version/s: web-3.4.1 3.6 Groovy 1.8.4 upgrade

[jbehave-dev] [jira] Updated: (JBEHAVE-632) Fluent Selenium (1.0 beta-4) upgrade

[ https://jira.codehaus.org/browse/JBEHAVE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-632: - Issue Type: Task (was: Improvement) Fluent Selenium (1.0 beta-4) upgrade

[jbehave-dev] [jira] Updated: (JBEHAVE-630) Selenium 2.11 upgrade

[ https://jira.codehaus.org/browse/JBEHAVE-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-630: - Issue Type: Task (was: Improvement) Selenium 2.11 upgrade -

[jbehave-dev] [jira] Updated: (JBEHAVE-604) Add SauceLabs ContextView

[ https://jira.codehaus.org/browse/JBEHAVE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-604: - Description: Should use the WebDriver JavascriptExecutor nature to send current scenario context.

[jbehave-dev] [jira] Updated: (JBEHAVE-634) Ant copy-dependencies task (for the bin distribution) doesn't work in Windows

[ https://jira.codehaus.org/browse/JBEHAVE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-634: - Component/s: (was: Build) Ant Tasks Summary: Ant copy-dependencies task

[jbehave-dev] [jira] Resolved: (JBEHAVE-634) Ant copy-dependencies task (for the bin distribution) doesn't work in Windows

[ https://jira.codehaus.org/browse/JBEHAVE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-634. -- Resolution: Fixed Assignee: Mauro Talevi Applied with thanks. Ant copy-dependencies task

[jbehave-dev] [jira] Commented: (JBEHAVE-637) Eliminate Format as a factory for StoryReporter

[ https://jira.codehaus.org/browse/JBEHAVE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=283599#comment-283599 ] Mauro Talevi commented on JBEHAVE-637: -- Not following the line of thought. Format allows to

[jbehave-dev] [jira] Updated: (JBEHAVE-563) Improve thread cancellation logic such that reporters know about such events.

[ https://jira.codehaus.org/browse/JBEHAVE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-563: - Fix Version/s: 3.6 Improve thread cancellation logic such that reporters know about such events.

[jbehave-dev] [jira] Created: (JBEHAVE-641) Close down stats file input stream after loading them

Close down stats file input stream after loading them - Key: JBEHAVE-641 URL: https://jira.codehaus.org/browse/JBEHAVE-641 Project: JBehave Issue Type: Improvement Components:

[jbehave-dev] [jira] Resolved: (JBEHAVE-641) Close down stats file input stream after loading them

[ https://jira.codehaus.org/browse/JBEHAVE-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-641. -- Resolution: Fixed Close down stats file input stream after loading them

[jbehave-dev] [jira] Updated: (JBEHAVE-563) Improve thread cancellation logic such that reporters know about such events.

[ https://jira.codehaus.org/browse/JBEHAVE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-563: - Component/s: Core Improve thread cancellation logic such that reporters know about such events.

[jbehave-dev] [jira] Updated: (JBEHAVE-642) StackOverflowError in RegexStoryParser with long scenario names/descriptions.

[ https://jira.codehaus.org/browse/JBEHAVE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-642: - Fix Version/s: 3.6 3.5.4 Summary: StackOverflowError in RegexStoryParser

[jbehave-dev] [jira] Resolved: (JBEHAVE-642) StackOverflowError in RegexStoryParser with long scenario names/descriptions.

[ https://jira.codehaus.org/browse/JBEHAVE-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-642. -- Resolution: Fixed Assignee: Mauro Talevi StackOverflowError in RegexStoryParser with long

<    6   7   8   9   10   11   12   13   14   15   >