[jbehave-dev] [jira] Updated: (JBEHAVE-489) AfterStories.xml and BeforeStories.xml being corrupt or zero length will break the Hudson plugin causing build failures after an otherwise successful JBehav
[ http://jira.codehaus.org/browse/JBEHAVE-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Hammant updated JBEHAVE-489: - Description: AfterStories.xml can be zero bytes on occasion. BeforeStories.xml can have invalid XML on occasion. I'll assume its zero length because there were no @AfterStories steps that were run for the job in question ( I guess there were @BeforeStories steps that were run) was:I'll assume its zero length because there were no @AfterStories steps that were run for the job in question ( I guess there were @BeforeStories steps that were run) Summary: AfterStories.xml and BeforeStories.xml being corrupt or zero length will break the Hudson plugin causing build failures after an otherwise successful JBehave job (was: AfterStories.xml can be zero bytes on occasion. This will break the Hudson plugin causing build failures.) > AfterStories.xml and BeforeStories.xml being corrupt or zero length will > break the Hudson plugin causing build failures after an otherwise successful > JBehave job > - > > Key: JBEHAVE-489 > URL: http://jira.codehaus.org/browse/JBEHAVE-489 > Project: JBehave > Issue Type: Bug > Components: Hudson Support >Reporter: Paul Hammant > > AfterStories.xml can be zero bytes on occasion. > BeforeStories.xml can have invalid XML on occasion. > I'll assume its zero length because there were no @AfterStories steps that > were run for the job in question ( I guess there were @BeforeStories steps > that were run) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-489) AfterStories.xml can be zero bytes on occasion. This will break the Hudson plugin causing build failures.
AfterStories.xml can be zero bytes on occasion. This will break the Hudson plugin causing build failures. -- Key: JBEHAVE-489 URL: http://jira.codehaus.org/browse/JBEHAVE-489 Project: JBehave Issue Type: Bug Components: Hudson Support Reporter: Paul Hammant I'll assume its zero length because there were no @AfterStories steps that were run for the job in question ( I guess there were @BeforeStories steps that were run) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-488) Scenario with nested or recursive example table
[ http://jira.codehaus.org/browse/JBEHAVE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264227#action_264227 ] kk sure commented on JBEHAVE-488: - Hmm. Looks like a good solution. > Scenario with nested or recursive example table > --- > > Key: JBEHAVE-488 > URL: http://jira.codehaus.org/browse/JBEHAVE-488 > Project: JBehave > Issue Type: New Feature >Reporter: kk sure > > We have a UI functionality that repeats on many pages (say it is a JSPF > component that is reusable, with configurable variation). But it is important > to test this on all pages since the functionality is slightly different on > each of these pages. > h2. How we have to code this today: > Scenario: Food widget in Home page > Given I am on Home page > When I enter in the menu field > Then I see in the dropdown > Examples: > |food_item|related_food_items| > |pizza|"cheese, chicken, bacon"| > |fruit_salad|"mangoes, strawberry, grapes"| > |rice|"brown, white, fried"| > The exact same test will repeat on a different page like below > Scenario: Food widget in OrderFood page > Given I am on OrderFood page > When I enter in the menu field > Then I see in the dropdown > Examples: > |food_item|related_food_items| > |pizza|"cheese, chicken, bacon"| > |fruit_salad|"mangoes, strawberry, grapes"| > |rice|"brown, white, fried"| > h2. Problem Statement: We want to run a particular scenario with 'examples' > over another parametrized value (e.g 'Page' here). > h2. Proposed solution: foreach meta-tag at scenario level that has processing > implications. > Scenario: > Meta: > @foreach Page: Home, OrderFood, CheckStatus, CancelOrder > Given I am on the page > When I enter in the menu field > Then I see in the dropdown > Examples: > |food_item|related_food_items| > |pizza|"cheese, chicken, bacon"| > |fruit_salad|"mangoes, strawberry, grapes"| > |rice|"brown, white, fried"| -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-488) Scenario with nested or recursive example table
[
http://jira.codehaus.org/browse/JBEHAVE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264209#action_264209
]
Mauro Talevi commented on JBEHAVE-488:
--
This sounds like an interesting use case, but I would not use a meta property
to drive it. Rather, we could enhance the Examples: syntax. E.g.
Examples:
{foreach Page: Home, OrderFood, CheckStatus, CancelOrder}
... table as usual
The advantage is that we keep the parameters of the examples self-contained in
the ExamplesTable (which can parse the directives too)
> Scenario with nested or recursive example table
> ---
>
> Key: JBEHAVE-488
> URL: http://jira.codehaus.org/browse/JBEHAVE-488
> Project: JBehave
> Issue Type: New Feature
>Reporter: kk sure
>
> We have a UI functionality that repeats on many pages (say it is a JSPF
> component that is reusable, with configurable variation). But it is important
> to test this on all pages since the functionality is slightly different on
> each of these pages.
> h2. How we have to code this today:
> Scenario: Food widget in Home page
> Given I am on Home page
> When I enter in the menu field
> Then I see in the dropdown
> Examples:
> |food_item|related_food_items|
> |pizza|"cheese, chicken, bacon"|
> |fruit_salad|"mangoes, strawberry, grapes"|
> |rice|"brown, white, fried"|
> The exact same test will repeat on a different page like below
> Scenario: Food widget in OrderFood page
> Given I am on OrderFood page
> When I enter in the menu field
> Then I see in the dropdown
> Examples:
> |food_item|related_food_items|
> |pizza|"cheese, chicken, bacon"|
> |fruit_salad|"mangoes, strawberry, grapes"|
> |rice|"brown, white, fried"|
> h2. Problem Statement: We want to run a particular scenario with 'examples'
> over another parametrized value (e.g 'Page' here).
> h2. Proposed solution: foreach meta-tag at scenario level that has processing
> implications.
> Scenario:
> Meta:
> @foreach Page: Home, OrderFood, CheckStatus, CancelOrder
> Given I am on the page
> When I enter in the menu field
> Then I see in the dropdown
> Examples:
> |food_item|related_food_items|
> |pizza|"cheese, chicken, bacon"|
> |fruit_salad|"mangoes, strawberry, grapes"|
> |rice|"brown, white, fried"|
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-488) Scenario with nested or recursive example table
[ http://jira.codehaus.org/browse/JBEHAVE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Hammant updated JBEHAVE-488: - Description: We have a UI functionality that repeats on many pages (say it is a JSPF component that is reusable, with configurable variation). But it is important to test this on all pages since the functionality is slightly different on each of these pages. h2. How we have to code this today: Scenario: Food widget in Home page Given I am on Home page When I enter in the menu field Then I see in the dropdown Examples: |food_item|related_food_items| |pizza|"cheese, chicken, bacon"| |fruit_salad|"mangoes, strawberry, grapes"| |rice|"brown, white, fried"| The exact same test will repeat on a different page like below Scenario: Food widget in OrderFood page Given I am on OrderFood page When I enter in the menu field Then I see in the dropdown Examples: |food_item|related_food_items| |pizza|"cheese, chicken, bacon"| |fruit_salad|"mangoes, strawberry, grapes"| |rice|"brown, white, fried"| h2. Problem Statement: We want to run a particular scenario with 'examples' over another parametrized value (e.g 'Page' here). h2. Proposed solution: foreach meta-tag at scenario level that has processing implications. Scenario: Meta: @foreach Page: Home, OrderFood, CheckStatus, CancelOrder Given I am on the page When I enter in the menu field Then I see in the dropdown Examples: |food_item|related_food_items| |pizza|"cheese, chicken, bacon"| |fruit_salad|"mangoes, strawberry, grapes"| |rice|"brown, white, fried"| was: We have a UI functionality that repeats on many pages. But it is important to test this on all pages since the functionality is slightly different on each of these pages. For eg. Scenario: Given I am on Home page When I enter in the menu field Then I see in the dropdown Examples: |food_item|related_food_items| |pizza|"cheese, chicken, bacon"| |fruit_salad|"mangoes, strawberry, grapes"| |rice|"brown, white, fried"| The exact same test will repeat on a different page like below Scenario: Given I am on OrderFood page When I enter in the menu field Then I see in the dropdown Examples: |food_item|related_food_items| |pizza|"cheese, chicken, bacon"| |fruit_salad|"mangoes, strawberry, grapes"| |rice|"brown, white, fried"| h2. Problem Statement: We want to run a particular test with examples over another parametrized value (e.g 'Page' here). h2. Proposed solution Scenario: Meta: @foreach Page: Home, OrderFood, CheckStatus, CancelOrder Given I am on the Page page When I enter in the menu field Then I see in the dropdown Examples: |food_item|related_food_items| |pizza|"cheese, chicken, bacon"| |fruit_salad|"mangoes, strawberry, grapes"| |rice|"brown, white, fried"| > Scenario with nested or recursive example table > --- > > Key: JBEHAVE-488 > URL: http://jira.codehaus.org/browse/JBEHAVE-488 > Project: JBehave > Issue Type: New Feature >Reporter: kk sure > > We have a UI functionality that repeats on many pages (say it is a JSPF > component that is reusable, with configurable variation). But it is important > to test this on all pages since the functionality is slightly different on > each of these pages. > h2. How we have to code this today: > Scenario: Food widget in Home page > Given I am on Home page > When I enter in the menu field > Then I see in the dropdown > Examples: > |food_item|related_food_items| > |pizza|"cheese, chicken, bacon"| > |fruit_salad|"mangoes, strawberry, grapes"| > |rice|"brown, white, fried"| > The exact same test will repeat on a different page like below > Scenario: Food widget in OrderFood page > Given I am on OrderFood page > When I enter in the menu field > Then I see in the dropdown > Examples: > |food_item|related_food_items| > |pizza|"cheese, chicken, bacon"| > |fruit_salad|"mangoes, strawberry, grapes"| > |rice|"brown, white, fried"| > h2. Problem Statement: We want to run a particular scenario with 'examples' > over another parametrized value (e.g 'Page' here). > h2. Proposed solution: foreach meta-tag at scenario level that has processing > implications. > Scenario: > Meta: > @foreach Page: Home, OrderFood, CheckStatus, CancelOrder > Given I am on the page > When I enter in the menu field > Then I see in the dropdown > Examples: > |food_item|related_food_items| > |pizza|"cheese, chicken, bacon"| > |fruit_salad|"mangoes, strawberry, grapes"| > |rice|"brown, white, fried"| -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To uns
[jbehave-dev] [jira] Created: (JBEHAVE-488) Scenario with nested or recursive example table
Scenario with nested or recursive example table --- Key: JBEHAVE-488 URL: http://jira.codehaus.org/browse/JBEHAVE-488 Project: JBehave Issue Type: New Feature Reporter: kk sure We have a UI functionality that repeats on many pages. But it is important to test this on all pages since the functionality is slightly different on each of these pages. For eg. Scenario: Given I am on Home page When I enter in the menu field Then I see in the dropdown Examples: |food_item|related_food_items| |pizza|"cheese, chicken, bacon"| |fruit_salad|"mangoes, strawberry, grapes"| |rice|"brown, white, fried"| The exact same test will repeat on a different page like below Scenario: Given I am on OrderFood page When I enter in the menu field Then I see in the dropdown Examples: |food_item|related_food_items| |pizza|"cheese, chicken, bacon"| |fruit_salad|"mangoes, strawberry, grapes"| |rice|"brown, white, fried"| h2. Problem Statement: We want to run a particular test with examples over another parametrized value (e.g 'Page' here). h2. Proposed solution Scenario: Meta: @foreach Page: Home, OrderFood, CheckStatus, CancelOrder Given I am on the Page page When I enter in the menu field Then I see in the dropdown Examples: |food_item|related_food_items| |pizza|"cheese, chicken, bacon"| |fruit_salad|"mangoes, strawberry, grapes"| |rice|"brown, white, fried"| -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-1-5-gd53cb4d
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-core". The branch, master has been updated via d53cb4db96b8fbbfdd8729e76b61e562af9463b3 (commit) from 7654d689909f954c1bd38851685729c58535c74d (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit d53cb4db96b8fbbfdd8729e76b61e562af9463b3 Author: Mauro Talevi Date: Wed Apr 20 15:02:40 2011 +0200 JBEHAVE-487: Improved language --- Summary of changes: .../trader/steps/MetaParametrisationSteps.java |5 + .../trader/stories/meta_parametrisation.story |2 +- 2 files changed, 2 insertions(+), 5 deletions(-) hooks/post-receive -- jbehave-core To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Updated: (JBEHAVE-450) If story is 'excluded' because of meta-filtering, we need a way to totally exclude it such that there are not monitor or StoryReporter calls for it.
[ http://jira.codehaus.org/browse/JBEHAVE-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Hammant updated JBEHAVE-450: - Summary: If story is 'excluded' because of meta-filtering, we need a way to totally exclude it such that there are not monitor or StoryReporter calls for it. (was: If story is excluded, we need a way to totally exclude it such that there are not monitor or StoryReporter calls for it.) > If story is 'excluded' because of meta-filtering, we need a way to totally > exclude it such that there are not monitor or StoryReporter calls for it. > > > Key: JBEHAVE-450 > URL: http://jira.codehaus.org/browse/JBEHAVE-450 > Project: JBehave > Issue Type: New Feature >Affects Versions: web-3.2 >Reporter: Paul Hammant > > I'm opening browsers in Saucelabs, the closing them a few seconds later. > Pointlessly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Commented: (JBEHAVE-485) The option to leave a browser window open at the end of a run.
[ http://jira.codehaus.org/browse/JBEHAVE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264185#action_264185 ] Paul Hammant commented on JBEHAVE-485: -- Because of JBEHAVE-486 this is happening whenever there is a step failure for typical web-selenium cases. > The option to leave a browser window open at the end of a run. > -- > > Key: JBEHAVE-485 > URL: http://jira.codehaus.org/browse/JBEHAVE-485 > Project: JBehave > Issue Type: New Feature > Components: Web Selenium >Reporter: Paul Hammant >Assignee: Paul Hammant > > For PerStoryWebDriverSteps (and others), it would be nice to obey and option > (command line or other) to NOT close the browser frame on failure. > Developers like to run single stories at a time, and want to be able to debug > when a failure happens. A failing screen-shot is one thing, but having the > actual browser open is better still. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-1-4-g7654d68
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-core". The branch, master has been updated via 7654d689909f954c1bd38851685729c58535c74d (commit) from 482fb397d40ea8965668fa7ab0a6367bc8627c93 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 7654d689909f954c1bd38851685729c58535c74d Author: Paul Hammant Date: Wed Apr 20 06:22:50 2011 -0500 JBEHAVE-487: expand example to show alternate use --- Summary of changes: .../trader/steps/MetaParametrisationSteps.java |9 + 1 files changed, 9 insertions(+), 0 deletions(-) hooks/post-receive -- jbehave-core To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-1-3-g482fb39
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "jbehave-core". The branch, master has been updated via 482fb397d40ea8965668fa7ab0a6367bc8627c93 (commit) from fc3b02c1d689ec8ade478affa10e9b31f610ac26 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - commit 482fb397d40ea8965668fa7ab0a6367bc8627c93 Author: Paul Hammant Date: Wed Apr 20 05:58:39 2011 -0500 JBEHAVE-487: expand example to show alternate use --- Summary of changes: .../trader/steps/MetaParametrisationSteps.java | 12 +--- .../trader/stories/meta_parametrisation.story | 13 +++-- 2 files changed, 20 insertions(+), 5 deletions(-) hooks/post-receive -- jbehave-core To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Work started: (JBEHAVE-487) Allow parameters to be specified as meta properties
[
http://jira.codehaus.org/browse/JBEHAVE-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JBEHAVE-487 started by Mauro Talevi.
> Allow parameters to be specified as meta properties
> ---
>
> Key: JBEHAVE-487
> URL: http://jira.codehaus.org/browse/JBEHAVE-487
> Project: JBehave
> Issue Type: New Feature
> Components: Core
>Reporter: Mauro Talevi
>Assignee: Mauro Talevi
> Fix For: 3.4
>
>
> As suggested by Paul, parameters may be specified as Meta properties:
> {noformat}
> Meta:
> @theme parameters
> Scenario:
> Meta:
> @variant named
> Given I have specified the
> And a
> Then the theme is parameters with variant named
> {noformat}
> The named meta parameters would be matched by usual @Named mechanism, also
> used in story or scenario parametrisation.
> {code}
> @Given("I have specified the ")
> public void givenIHaveSpecifiedTheTheme(@Named("theme") String theme){
> this.theme = theme;
> }
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
[jbehave-scm] jbehave-core branch, master, updated. jbehave-3.4-beta-1-2-gfc3b02c
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "jbehave-core".
The branch, master has been updated
via fc3b02c1d689ec8ade478affa10e9b31f610ac26 (commit)
from c3be791ce66ea91ab0ce36442c6ae13c4fba216c (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -
commit fc3b02c1d689ec8ade478affa10e9b31f610ac26
Author: Mauro Talevi
Date: Wed Apr 20 10:58:47 2011 +0200
JBEHAVE-487: Added support for meta parameters, i.e. parameters specified
as meta properties.
---
Summary of changes:
.../org/jbehave/examples/trader/TraderStories.java |3 +-
.../org/jbehave/examples/trader/TraderStory.java |3 +-
.../trader/steps/MetaParametrisationSteps.java | 31
...{PendingStats.java => MetaParametrisation.java} |4 +-
.../trader/stories/meta_parametrisation.story | 14 +
.../org/jbehave/core/embedder/StoryRunner.java |9 +-
6 files changed, 59 insertions(+), 5 deletions(-)
create mode 100644
examples/trader/src/main/java/org/jbehave/examples/trader/steps/MetaParametrisationSteps.java
copy
examples/trader/src/main/java/org/jbehave/examples/trader/stories/{PendingStats.java
=> MetaParametrisation.java} (63%)
create mode 100644
examples/trader/src/main/java/org/jbehave/examples/trader/stories/meta_parametrisation.story
hooks/post-receive
--
jbehave-core
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email";>http://xircles.codehaus.org/manage_email
[jbehave-dev] [jira] Created: (JBEHAVE-487) Allow parameters to be specified as meta properties
Allow parameters to be specified as meta properties
---
Key: JBEHAVE-487
URL: http://jira.codehaus.org/browse/JBEHAVE-487
Project: JBehave
Issue Type: New Feature
Components: Core
Reporter: Mauro Talevi
Assignee: Mauro Talevi
Fix For: 3.4
As suggested by Paul, parameters may be specified as Meta properties:
{noformat}
Meta:
@theme parameters
Scenario:
Meta:
@variant named
Given I have specified the
And a
Then the theme is parameters with variant named
{noformat}
The named meta parameters would be matched by usual @Named mechanism, also used
in story or scenario parametrisation.
{code}
@Given("I have specified the ")
public void givenIHaveSpecifiedTheTheme(@Named("theme") String theme){
this.theme = theme;
}
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
