headers
Mauro Talevi (JIRA | 1 Jun 2011 08:58

[jira] Updated: (JBEHAVE-524) Add page URL to screenshot console message


     [
http://jira.codehaus.org/browse/JBEHAVE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mauro Talevi updated JBEHAVE-524:
---------------------------------

    Fix Version/s: web-3.3.4
       Issue Type: Improvement  (was: Bug)
          Summary: Add page URL to screenshot console message  (was: Add correlating URL to screen-shots in output)

> Add page URL to screenshot console message
> ------------------------------------------
>
>                 Key: JBEHAVE-524
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-524
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Web Selenium
>            Reporter: Paul Hammant
>            Assignee: Paul Hammant
>             Fix For: web-3.4, web-3.3.4
>
>

--

-- 
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
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul Hammant (JIRA | 1 Jun 2011 12:58

[jira] Commented: (JBEHAVE-526) Steps could benefit from a pre-requisite check


    [
http://jira.codehaus.org/browse/JBEHAVE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269259#action_269259
] 

Paul Hammant commented on JBEHAVE-526:
--------------------------------------

That might be a better way of handling it Brian. The method/instance is passed in to the applicable handler.
We should also leverage annotation chaining.

// ** In use **

 <at> ForUrlPrefix("/shoppingCart")
public void someWhen() {
// etc
}

// ** Defined like so **

// a custom use of  <at> BeforeStep for my client
 <at> BeforeStep
public  <at> interface ForUrlPrefix {
String value(); // the url prefix
}

> Steps could benefit from a pre-requisite check
> ----------------------------------------------
>
>                 Key: JBEHAVE-526
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 2 Jun 2011 18:27

[jira] Created: (JBEHAVE-527) Composed steps not being matched when using non-named parameter matching for the composite step

Composed steps not being matched when using non-named parameter matching for the composite step
-----------------------------------------------------------------------------------------------

                 Key: JBEHAVE-527
                 URL: http://jira.codehaus.org/browse/JBEHAVE-527
             Project: JBehave
          Issue Type: Bug
    Affects Versions: 3.4.1, 3.4
         Environment: After the introduction of the specifications of parameters as meta (JBEHAVE-487) the
composed steps are not being matched if meta parameters are specified as they superseed the parameters
specified in the composite step. 

Need to merge the two set of parameters rather than choosing one over the other. 

            Reporter: Mauro Talevi
            Assignee: Mauro Talevi
             Fix For: 3.4.2

--

-- 
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
(Continue reading)

Permalink | Reply | 1 comment |
headers
Paul Hammant (JIRA | 2 Jun 2011 21:19

[jira] Created: (JBEHAVE-528) Examples Table for subset of steps

Examples Table for subset of steps
----------------------------------

                 Key: JBEHAVE-528
                 URL: http://jira.codehaus.org/browse/JBEHAVE-528
             Project: JBehave
          Issue Type: New Feature
    Affects Versions: 3.4
            Reporter: Paul Hammant
            Priority: Minor
             Fix For: 3.5

http://jbehave.org/reference/stable/tabular-parameters.html is great, but pertains to a single step.

{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter <foo> in the foo field
Then the bar field is auto-completed with <bar>

Examples:
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}

http://jbehave.org/reference/legacy/table-examples.html (note no /stable/ version of this page)
gives the general theme, but suggests that all the Given/When/Then steps are repeated.

In the linked-to example, it is the only one given.  What this change is about is the fact that only the
When/Then steps need to be repeated.  This is implicit because the Given line does not refer to any of the
(Continue reading)

Permalink | Reply | 4 comments |
headers
Mauro Talevi (JIRA | 2 Jun 2011 23:47

[jira] Updated: (JBEHAVE-528) Examples Table for subset of steps


     [
http://jira.codehaus.org/browse/JBEHAVE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mauro Talevi updated JBEHAVE-528:
---------------------------------

    Description: 
http://jbehave.org/reference/stable/tabular-parameters.html is great, but pertains to a single step.

{quote}
Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
When I enter <foo> in the foo field
Then the bar field is auto-completed with <bar>

Examples:
| foo | bar |
| eggs | bacon |
| toast | marmite |
{quote}

http://jbehave.org/reference/stable/parametrised-scenarios.html suggests that all the
Given/When/Then steps are repeated.

In the linked-to example, it is the only one given.  What this change is about is the fact that only the
When/Then steps need to be repeated.  This is implicit because the Given line does not refer to any of the
table params.

If this needs to be explicit, it could be a team's choice to set this for the entire set of stories:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 2 Jun 2011 23:58

[jira] Commented: (JBEHAVE-528) Examples Table for subset of steps


    [
http://jira.codehaus.org/browse/JBEHAVE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269442#action_269442
] 

Mauro Talevi commented on JBEHAVE-528:
--------------------------------------

Composite steps (http://jbehave.org/reference/stable/composite-steps.html) is one option that
allows to group a subset of scenario steps.

Another approach is to have the part that is not repeated contained in a GivenStory precondition, leaving
the repeated steps in the parametrised scenario. 

Supporting the tabular parameters for arbitrary subset of steps is likely to be non trivial, and possibly
confusing unless we can come up with a clear way to spell out which steps are executed in which order.

> Examples Table for subset of steps
> ----------------------------------
>
>                 Key: JBEHAVE-528
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-528
>             Project: JBehave
>          Issue Type: New Feature
>    Affects Versions: 3.4
>            Reporter: Paul Hammant
>            Priority: Minor
>             Fix For: 3.5
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Brian Repko (JIRA | 3 Jun 2011 00:21

[jira] Commented: (JBEHAVE-528) Examples Table for subset of steps


    [
http://jira.codehaus.org/browse/JBEHAVE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269443#action_269443
] 

Brian Repko commented on JBEHAVE-528:
-------------------------------------

GivenStory was exactly what I was thinking.  I'm concerned that we don't have a clear model of what can happen
when during the execution of a story/scenario/step and having a clear definition of what is there might
help us identify the gaps.  That's where my head is at on this.

> Examples Table for subset of steps
> ----------------------------------
>
>                 Key: JBEHAVE-528
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-528
>             Project: JBehave
>          Issue Type: New Feature
>    Affects Versions: 3.4
>            Reporter: Paul Hammant
>            Priority: Minor
>             Fix For: 3.5
>
>
> http://jbehave.org/reference/stable/tabular-parameters.html is great, but pertains to a single step.
> {quote}
> Given I'm on the FooBar Page which is 20 mins of clicking through prelim pages
> When I enter <foo> in the foo field
> Then the bar field is auto-completed with <bar>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Miguel | 3 Jun 2011 18:16
Picon
Favicon

Re: A request to improve adoption

I am sorry to say this but it is not compiling at all. 
We have spent several hours trying to install this and 
we keep getting this error: Failed to run xsite.

Having read the comments of this post I think there is 
not a chance of fixing this issue anytime soon. So bye 
bye from a former potential adopter.

I will try to do a master in maven if I have time.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 1 comment |
headers
Mauro Talevi (JIRA | 4 Jun 2011 10:38

[jira] Resolved: (JBEHAVE-527) Composed steps not being matched when using non-named parameter matching for the composite step


     [
http://jira.codehaus.org/browse/JBEHAVE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mauro Talevi resolved JBEHAVE-527.
----------------------------------

    Resolution: Fixed

> Composed steps not being matched when using non-named parameter matching for the composite step
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-527
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-527
>             Project: JBehave
>          Issue Type: Bug
>    Affects Versions: 3.4, 3.4.1
>         Environment: After the introduction of the specifications of parameters as meta (JBEHAVE-487) the
composed steps are not being matched if meta parameters are specified as they superseed the parameters
specified in the composite step. 
> Need to merge the two set of parameters rather than choosing one over the other. 
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>             Fix For: 3.4.2
>
>

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 4 Jun 2011 20:12

[jira] Created: (JBEHAVE-529) Simplify trader-ant example to not depend on the Maven pom.xml

Simplify trader-ant example to not depend on the Maven pom.xml
--------------------------------------------------------------

                 Key: JBEHAVE-529
                 URL: http://jira.codehaus.org/browse/JBEHAVE-529
             Project: JBehave
          Issue Type: Task
          Components: Documentation
            Reporter: Mauro Talevi
            Assignee: Mauro Talevi
            Priority: Minor
             Fix For: 3.4.2

--

-- 
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
Permalink | Reply | 1 comment |

Gmane