Mauro Talevi (JIRA | 1 Feb 09:56 2012

[jira] (JBEHAVE-233) Eclipse plugin for navigating between textual and code steps


    [
https://jira.codehaus.org/browse/JBEHAVE-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290456#comment-290456
] 

Mauro Talevi commented on JBEHAVE-233:
--------------------------------------

The steps classes are not found via the JBehave story editor - and the lines are marked with red. 

The projects have well formed classpaths, generated by m2e (e.g. the JBehave trader examples).

I've tried to add the corresponding packages to the Preferences > JBehave > Class Scanner, but to no avail.

Any more info I can provide? 

 

> Eclipse plugin for navigating between textual and code steps
> ------------------------------------------------------------
>
>                 Key: JBEHAVE-233
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-233
>             Project: JBehave
>          Issue Type: New Feature
>            Reporter: Jonathan Ross
>
> As an avid user of jBehave, I find maintaining steps very laborious, so I would like an eclipse plugin with:
> * support for opening declarations of steps from the scenario files
> * support for finding usages of steps in scenario files from the declaration
(Continue reading)

Craig Tataryn (JIRA | 2 Feb 18:16 2012

[jira] (JBEHAVE-715) Story reports not being published via Hudson Plugin

Craig Tataryn created JBEHAVE-715:
-------------------------------------

             Summary: Story reports not being published via Hudson Plugin
                 Key: JBEHAVE-715
                 URL: https://jira.codehaus.org/browse/JBEHAVE-715
             Project: JBehave
          Issue Type: Bug
          Components: Hudson Support
    Affects Versions: 3.5.4
         Environment: Windows 7 64bit
            Reporter: Craig Tataryn
         Attachments: jbehave.zip

When the jBehave/xUnit plugin kicks in after our stories have executed, it fails to copy the reports with
the following error:

{quote}
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing JBehave-3.x
[xUnit] [INFO] - [JBehave-3.x] - 3 test report file(s) were found with the pattern '**/jbehave/*.xml'
relative to 'C:\bin\hudson\hudson_home\jobs\ConvergencePilotIntegrationTests\workspace' for
the testing framework 'JBehave-3.x'.
[xUnit] [ERROR] - The result file
'C:\bin\hudson\hudson_home\jobs\ConvergencePilotIntegrationTests\workspace\ConvergencePlayerManagementIntegrationTests\target\jbehave\BeforeStories.xml'
for the metric 'JBehave' is empty. The result file has been skipped.
[xUnit] [WARNING] - All test reports are empty.
[xUnit] [INFO] - Check 'Failed Tests' threshold.
[xUnit] [INFO] - Check 'Skipped Tests' threshold.
[xUnit] [INFO] - Setting the build status to SUCCESS
(Continue reading)

Cristiano Gavião (JIRA | 7 Feb 17:58 2012

[jira] (JBEHAVE-716) Add an optional StoryFinder class parameter to <at> UsingPaths annotation

Cristiano Gavião created JBEHAVE-716:
----------------------------------------

             Summary: Add an optional StoryFinder class parameter to  <at> UsingPaths annotation
                 Key: JBEHAVE-716
                 URL: https://jira.codehaus.org/browse/JBEHAVE-716
             Project: JBehave
          Issue Type: New Feature
          Components: Core
            Reporter: Cristiano Gavião
             Fix For: 3.6

Currently  <at> UsingPaths is using one fixed instance of StoryFinder class. 
In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinderClass parameter in the  <at> UsingPaths annotation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.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

Mauro Talevi (JIRA | 8 Feb 12:49 2012

[jira] (JBEHAVE-716) Add an optional StoryFinder class parameter to <at> UsingPaths annotation


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

Mauro Talevi reassigned JBEHAVE-716:
------------------------------------

    Assignee: Mauro Talevi

> Add an optional StoryFinder class parameter to  <at> UsingPaths annotation
> ---------------------------------------------------------------------
>
>                 Key: JBEHAVE-716
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-716
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Cristiano Gavião
>            Assignee: Mauro Talevi
>              Labels: annotation
>             Fix For: 3.6
>
>
> Currently  <at> UsingPaths is using one fixed instance of StoryFinder class. 
> In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinderClass parameter in the  <at> UsingPaths annotation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
(Continue reading)

Mauro Talevi (JIRA | 8 Feb 12:51 2012

[jira] (JBEHAVE-716) Add an optional StoryFinder class element to <at> UsingPaths annotation


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

Work on JBEHAVE-716 started by Mauro Talevi.

> Add an optional StoryFinder class element to  <at> UsingPaths annotation
> -------------------------------------------------------------------
>
>                 Key: JBEHAVE-716
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-716
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Cristiano Gavião
>            Assignee: Mauro Talevi
>              Labels: annotation
>             Fix For: 3.6
>
>
> Currently  <at> UsingPaths is using one fixed instance of StoryFinder class. 
> In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinder element in the  <at> UsingPaths annotation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
(Continue reading)

Mauro Talevi (JIRA | 8 Feb 12:51 2012

[jira] (JBEHAVE-716) Add an optional StoryFinder class element to <at> UsingPaths annotation


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

Mauro Talevi updated JBEHAVE-716:
---------------------------------

    Description: 
Currently  <at> UsingPaths is using one fixed instance of StoryFinder class. 
In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinder element in the  <at> UsingPaths annotation.

  was:
Currently  <at> UsingPaths is using one fixed instance of StoryFinder class. 
In order to use a custom StoryFinder class with the annotation, I would like to include an optional
storyFinderClass parameter in the  <at> UsingPaths annotation.

     Issue Type: Improvement  (was: New Feature)
        Summary: Add an optional StoryFinder class element to  <at> UsingPaths annotation  (was: Add an optional
StoryFinder class parameter to  <at> UsingPaths annotation)

> Add an optional StoryFinder class element to  <at> UsingPaths annotation
> -------------------------------------------------------------------
>
>                 Key: JBEHAVE-716
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-716
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Cristiano Gavião
(Continue reading)

Alexander Lehmann (JIRA | 8 Feb 21:35 2012

[jira] (JBEHAVE-715) Story reports not being published via Hudson Plugin


    [
https://jira.codehaus.org/browse/JBEHAVE-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291176#comment-291176
] 

Alexander Lehmann commented on JBEHAVE-715:
-------------------------------------------

Works for me on an example project (all 3 files are non-empty)

The BeforeStories.xml file in your project is empty, maybe that causes a problem (I think there was an issue
about that before).

An empty file is not a valid xml file, maybe this breaks the plugin somehow.

                
> Story reports not being published via Hudson Plugin
> ---------------------------------------------------
>
>                 Key: JBEHAVE-715
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-715
>             Project: JBehave
>          Issue Type: Bug
>          Components: Hudson Support
>    Affects Versions: 3.5.4
>         Environment: Windows 7 64bit
>            Reporter: Craig Tataryn
>              Labels: hudson
>         Attachments: jbehave.zip
>
(Continue reading)

Alexander Lehmann (JIRA | 8 Feb 21:39 2012

[jira] (JBEHAVE-715) Story reports not being published via Hudson Plugin


    [
https://jira.codehaus.org/browse/JBEHAVE-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291176#comment-291176
] 

Alexander Lehmann edited comment on JBEHAVE-715 at 2/8/12 2:38 PM:
-------------------------------------------------------------------

Works for me on an example project (all 3 files are non-empty)

The BeforeStories.xml file in your project is empty, maybe that causes a problem (there was an issue about
that before JBEHAVE-585).

An empty file is not a valid xml file, maybe this breaks the plugin somehow.

the other issue gives a simple fix for the problem, just delete the empty files (the actual problem is not
resolved though)

                
      was (Author: alexlehm):
    Works for me on an example project (all 3 files are non-empty)

The BeforeStories.xml file in your project is empty, maybe that causes a problem (I think there was an issue
about that before).

An empty file is not a valid xml file, maybe this breaks the plugin somehow.

                  
> Story reports not being published via Hudson Plugin
> ---------------------------------------------------
(Continue reading)

Mauro Talevi (JIRA | 11 Feb 14:43 2012

[jira] (JBEHAVE-717) Make parametrised name delimiters configurable

Mauro Talevi created JBEHAVE-717:
------------------------------------

             Summary: Make parametrised name delimiters configurable
                 Key: JBEHAVE-717
                 URL: https://jira.codehaus.org/browse/JBEHAVE-717
             Project: JBehave
          Issue Type: Improvement
          Components: Core
            Reporter: Mauro Talevi
            Assignee: Mauro Talevi
             Fix For: 3.6

Currently, parametrised names are conventionally delimited by angle brackets (< and >).  The matching
mechanism does not depend on them by the output step decoration that identifies and highlights parameter
values in StepCreator does.

The parameter name delimeters should be abstracted into a ParameterControls configuration element.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.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)

Mauro Talevi (JIRA | 11 Feb 15:02 2012

[jira] (JBEHAVE-717) Make parametrised name delimiters configurable


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

Work on JBEHAVE-717 started by Mauro Talevi.

> Make parametrised name delimiters configurable
> ----------------------------------------------
>
>                 Key: JBEHAVE-717
>                 URL: https://jira.codehaus.org/browse/JBEHAVE-717
>             Project: JBehave
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>             Fix For: 3.6
>
>
> Currently, parametrised names are conventionally delimited by angle brackets (< and >).  The matching
mechanism does not depend on them by the output step decoration that identifies and highlights parameter
values in StepCreator does.
> The parameter name delimeters should be abstracted into a ParameterControls configuration element.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
(Continue reading)


Gmane