[jbehave-dev] [jira] Updated: (JBEHAVE-567) Excluded (filtered-out) scenarios are reported as pending as well

[ https://jira.codehaus.org/browse/JBEHAVE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-567: - Fix Version/s: 3.5 Assignee: Mauro Talevi > Excluded (filtered-out) scenarios are reported a

[jbehave-dev] [jira] Resolved: (JBEHAVE-570) Excluded scenarios should not be included into ScenarioSuccessful count

[ https://jira.codehaus.org/browse/JBEHAVE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-570. -- Resolution: Fixed Fix Version/s: 3.5 Applied patch with thanks. > Excluded scenarios should

[jbehave-dev] [jira] Created: (JBEHAVE-571) Shorten method and annotation signature in BeforeOrAfterFalled message

Shorten method and annotation signature in BeforeOrAfterFalled message -- Key: JBEHAVE-571 URL: https://jira.codehaus.org/browse/JBEHAVE-571 Project: JBehave Issue Type: Imp

[jbehave-dev] [jira] Work started: (JBEHAVE-571) Compatify method and annotation information in BeforeOrAfterFalled message

[ https://jira.codehaus.org/browse/JBEHAVE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-571 started by Mauro Talevi. > Compatify method and annotation information in BeforeOrAfterFalled message > --

[jbehave-dev] [jira] Updated: (JBEHAVE-571) Compatify method and annotation information in BeforeOrAfterFalled message

[ https://jira.codehaus.org/browse/JBEHAVE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-571: - Summary: Compatify method and annotation information in BeforeOrAfterFalled message (was: Shorten me

[jbehave-dev] [jira] Updated: (JBEHAVE-571) Compactify method and annotation information in BeforeOrAfterFalled message

[ https://jira.codehaus.org/browse/JBEHAVE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-571: - Summary: Compactify method and annotation information in BeforeOrAfterFalled message (was: Compatify

[jbehave-dev] [jira] Resolved: (JBEHAVE-557) When story has multiple failed scenarios, only one screenshot is created

[ https://jira.codehaus.org/browse/JBEHAVE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-557. -- Resolution: Fixed Pulled commit: https://github.com/karacz/jbehave-core/commit/0c81e1f5e49bf8ee70

[jbehave-dev] [jira] Updated: (JBEHAVE-557) When story has multiple failed scenarios, only one screenshot is created

[ https://jira.codehaus.org/browse/JBEHAVE-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-557: - Fix Version/s: 3.5 > When story has multiple failed scenarios, only one screenshot is created > -

[jbehave-dev] [jira] Commented: (JBEHAVE-573) Step Marked as PENDING without preceding FAILED step - silent failure???

[ https://jira.codehaus.org/browse/JBEHAVE-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274889#comment-274889 ] Mauro Talevi commented on JBEHAVE-573: -- What's the usecase for the different method signature

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

Improve documentation on using archetypes - Key: JBEHAVE-574 URL: https://jira.codehaus.org/browse/JBEHAVE-574 Project: JBehave Issue Type: Task Reporter: Mauro Talevi Assignee:

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

Flash support - Key: JBEHAVE-577 URL: https://jira.codehaus.org/browse/JBEHAVE-577 Project: JBehave Issue Type: New Feature Components: Web Selenium Reporter: Mauro Talevi Assignee: Mauro Talevi

[jbehave-dev] [jira] Updated: (JBEHAVE-575) Upgrade Selenium to 2.3.1

[ https://jira.codehaus.org/browse/JBEHAVE-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-575: - Fix Version/s: web-3.4 > Upgrade Selenium to 2.3.1 > - > > Ke

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

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

[jbehave-dev] [jira] Updated: (JBEHAVE-568) Selenium 2.1.0 upgrade

[ https://jira.codehaus.org/browse/JBEHAVE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-568: - Fix Version/s: web-3.4 Issue Type: Task (was: Improvement) > Selenium 2.1.0 upgrade > ---

[jbehave-dev] [jira] Resolved: (JBEHAVE-554) Upgrade to Selenium 2.0.0 final

[ https://jira.codehaus.org/browse/JBEHAVE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-554. -- Resolution: Fixed > Upgrade to Selenium 2.0.0 final > --- > >

[jbehave-dev] [jira] Updated: (JBEHAVE-568) Selenium 2.1.0 upgrade

[ https://jira.codehaus.org/browse/JBEHAVE-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-568: - Component/s: Web Selenium > Selenium 2.1.0 upgrade > -- > > Key:

[jbehave-dev] [jira] Updated: (JBEHAVE-572) Selenium 2.2 upgrade.

[ https://jira.codehaus.org/browse/JBEHAVE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-572: - Fix Version/s: web-3.4 > Selenium 2.2 upgrade. > - > > Key: JBEHA

[jbehave-dev] [jira] Updated: (JBEHAVE-572) Selenium 2.2 upgrade.

[ https://jira.codehaus.org/browse/JBEHAVE-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-572: - Component/s: Web Selenium > Selenium 2.2 upgrade. > - > > Key: JB

[jbehave-dev] [jira] Updated: (JBEHAVE-576) Allow for setting of environment vars on Firefox binary (for DISPLAY amongst others)

[ https://jira.codehaus.org/browse/JBEHAVE-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-576: - Fix Version/s: web-3.4 > Allow for setting of environment vars on Firefox binary (for DISPLAY amongst

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

Story execution not failing-fast when ignoreFailuresInStories=false --- Key: JBEHAVE-578 URL: https://jira.codehaus.org/browse/JBEHAVE-578 Project: JBehave Issue Type: Bug A

[jbehave-dev] [jira] Work started: (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 ] Work on JBEHAVE-578 started by Mauro Talevi. > Story execution not failing-fast when ignoreFailuresInStories=false > -

[jbehave-dev] [jira] Updated: (JBEHAVE-582) Base WebDriverPage should implement HasCapabilities, JavascriptExecutor and HasInputDevices

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

[jbehave-dev] [jira] Updated: (JBEHAVE-583) Of multiple exclusion meta filters only one is evaluated

[ https://jira.codehaus.org/browse/JBEHAVE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-583: - Fix Version/s: 3.5 Thanks, added test cases. > Of multiple exclusion meta filters only one is evalua

[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: - Assignee: Mauro Talevi > Support loading stories from Google Docs > -

[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: - Fix Version/s: 3.5 > Support loading stories from Google Docs > -

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

[ https://jira.codehaus.org/browse/JBEHAVE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JBEHAVE-584 started by Mauro Talevi. > Support loading stories from Google Docs > > > Key: JBEHAVE-584 >

[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-tabpanel&focusedCommentId=276624#comment-276624 ] Mauro Talevi commented on JBEHAVE-584: -- Hi Bart, added your contributed Google docs loader,

[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-tabpanel&focusedCommentId=276719#comment-276719 ] Mauro Talevi commented on JBEHAVE-584: -- For the moment, we are exporting to use odf formats,

[jbehave-dev] [jira] Resolved: (JBEHAVE-583) Of multiple exclusion meta filters only one is evaluated

[ https://jira.codehaus.org/browse/JBEHAVE-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-583. -- Resolution: Fixed Assignee: Mauro Talevi > Of multiple exclusion meta filters only one is eva

[jbehave-dev] [jira] Commented: (JBEHAVE-585) BeforeStories.xml can be zero length ( causing xUnit to fail a Jenkins job )

[ https://jira.codehaus.org/browse/JBEHAVE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276738#comment-276738 ] Mauro Talevi commented on JBEHAVE-585: -- So what is the proposed fix from JBehave's pov (i.e.

[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-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=276878#comment-276878 ] Mauro Talevi commented on JBEHAVE-584: -- Thanks, applied patch, although had to applied change

[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-tabpanel&focusedCommentId=276883#comment-276883 ] Mauro Talevi commented on JBEHAVE-584: -- No problem :-) I find that using command-line "git d

[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 rel

[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 > FailingUpon

[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: Mau

[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-tabpanel&focusedCommentId=277526#comment-277526 ] Mauro Talevi commented on JBEHAVE-584: -- Hi Bart, added jbehave-google-example which can be e

[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 C

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

[ https://jira.codehaus.org/browse/JBEHAVE-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-589. -- Resolution: Fixed > Ignorable steps before And steps should not be marked as pending >

[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 no

[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] Created: (JBEHAVE-590) Add failed step as UUIDExceptionWrapper message

Add failed step as UUIDExceptionWrapper message --- Key: JBEHAVE-590 URL: https://jira.codehaus.org/browse/JBEHAVE-590 Project: JBehave Issue Type: Improvement Reporter: Mauro Talevi

[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] Resolved: (JBEHAVE-534) Lazy instantiation of steps classes, only if candidate steps are matched

[ https://jira.codehaus.org/browse/JBEHAVE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-534. -- Resolution: Fixed > Lazy instantiation of steps classes, only if candidate steps are matched >

[jbehave-dev] [jira] Resolved: (JBEHAVE-540) ANSI-coded console output

[ https://jira.codehaus.org/browse/JBEHAVE-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-540. -- Resolution: Fixed > ANSI-coded console output > - > > Key:

[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-tabpanel&focusedCommentId=277706#comment-277706 ] Mauro Talevi commented on JBEHAVE-584: -- Hi Bart, as you originally suggested, a separate jb

[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 s

[jbehave-dev] [jira] Resolved: (JBEHAVE-571) Compactify method and annotation information in BeforeOrAfterFailed message

[ https://jira.codehaus.org/browse/JBEHAVE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-571. -- Resolution: Fixed > Compactify method and annotation information in BeforeOrAfterFailed message > -

[jbehave-dev] [jira] Updated: (JBEHAVE-571) Compactify method and annotation information in BeforeOrAfterFailed message

[ https://jira.codehaus.org/browse/JBEHAVE-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-571: - Summary: Compactify method and annotation information in BeforeOrAfterFailed message (was: Compactif

[jbehave-dev] [jira] Resolved: (JBEHAVE-535) Template-based reporters

[ https://jira.codehaus.org/browse/JBEHAVE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-535. -- Resolution: Fixed Provided HtmlTemplateOutput as initial implementation of template-based reporter

[jbehave-dev] [jira] Resolved: (JBEHAVE-537) Pluggable template processor for view generator

[ https://jira.codehaus.org/browse/JBEHAVE-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-537. -- Resolution: Fixed > Pluggable template processor for view generator >

[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 backwar

[jbehave-dev] [jira] Created: (JBEHAVE-591) Build not working on JDK 1.7

Build not working on JDK 1.7 Key: JBEHAVE-591 URL: https://jira.codehaus.org/browse/JBEHAVE-591 Project: JBehave Issue Type: Task Components: Build Environment: JDK 1.7 Reporter: Ma

[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-tabpanel&focusedCommentId=277718#comment-277718 ] Mauro Talevi commented on JBEHAVE-543: -- Merged, thanks! > Before/After Story/Scenario method

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

Per-stories lifecycle steps requires same-thread executor service - Key: JBEHAVE-593 URL: https://jira.codehaus.org/browse/JBEHAVE-593 Project: JBehave Issue Type: Improvement

[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] Assigned: (JBEHAVE-548) @BeforeExample und @AfterExample

[ https://jira.codehaus.org/browse/JBEHAVE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi reassigned JBEHAVE-548: Assignee: Mauro Talevi > @BeforeExample und @AfterExample > >

[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 und

[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-tabpanel&focusedCommentId=278020#comment-278020 ] Mauro Talevi commented on JBEHAVE-163: -- Yes, comments in tables are allowed using the "|--" s

[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-tabpanel&focusedCommentId=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-

[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] Created: (JBEHAVE-595) Use name as String representation of Format

Use name as String representation of Format --- Key: JBEHAVE-595 URL: https://jira.codehaus.org/browse/JBEHAVE-595 Project: JBehave Issue Type: Improvement Components: Core Report

[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: JBEH

[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 Assignee

[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] Created: (JBEHAVE-599) Failures in view do not cause build to fail

Failures in view do not cause build to fail --- Key: JBEHAVE-599 URL: https://jira.codehaus.org/browse/JBEHAVE-599 Project: JBehave Issue Type: Bug Components: Core Affects Versions: 3.5,

[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: Wi

[jbehave-dev] [jira] Updated: (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 updated JBEHAVE-600: - Fix Version/s: 3.6 > Scenario title parsed to empty on Windows >

[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] Resolved: (JBEHAVE-598) Failing build on Windows

[ https://jira.codehaus.org/browse/JBEHAVE-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi resolved JBEHAVE-598. -- Resolution: Fixed > Failing build on Windows > > > Key: JB

[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 appea

[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: Maur

[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: https://jira.codehaus.org/bro

[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: Improve

[jbehave-dev] [jira] Resolved: (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 resolved JBEHAVE-609. -- Resolution: Fixed > Allow named parameters to be replaced in table row parameters values >

[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, should

[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: 3

[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: JBE

[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] Commented: (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:comment-tabpanel&focusedCommentId=281277#comment-281277 ] Mauro Talevi commented on JBEHAVE-615: -- We could make the ignoring of the period configurable

[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 resetti

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

[ https://jira.codehaus.org/browse/JBEHAVE-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mauro Talevi updated JBEHAVE-619: - Fix Version/s: 3.5.2 Assignee: Mauro Talevi > ParameterConverters throwing ConcurrentModific

<    10   11   12   13   14   15   16   17   18   19   >