gmane.comp.java.jbehave.devel

[jira] (JBEHAVE-783) Better integration into JUnit

David Tanner (JIRA — 2012-05-16T20:44:02

David Tanner created JBEHAVE-783:
------------------------------------

             Summary: Better integration into JUnit
                 Key: JBEHAVE-783
                 URL: https://jira.codehaus.org/browse/JBEHAVE-783
             Project: JBehave
          Issue Type: Improvement
          Components: Core
    Affects Versions: 3.6.4
         Environment: N/A
            Reporter: David Tanner
            Priority: Minor
         Attachments: Configuration change.txt, Improved Test Description.txt, JUnit StoryReporter.txt

Problem statement:
As has been stated in miscellaneous other Issues, it would be nice to have better integration into JUnit by JBehave. 

Recommended Code Change:
Add two variables to the MostUsefulConfiguration, one to hold RunNotifier, and the other to hold the TestDescriptions.
Increase the JUnit Description depth by parsing out the scenarios, and steps when creating the Story descriptions in AnnotatedPathRunner.
Add a StoryReporter that reports to the RunNotifier using the prov

[jira] (JBEHAVE-782) Minor change to function parseScenario in RegexStoryParser

David Tanner (JIRA — 2012-05-16T20:22:02

David Tanner created JBEHAVE-782:
------------------------------------

             Summary: Minor change to function parseScenario in RegexStoryParser
                 Key: JBEHAVE-782
                 URL: https://jira.codehaus.org/browse/JBEHAVE-782
             Project: JBehave
          Issue Type: Improvement
          Components: Core
    Affects Versions: 3.6.4
         Environment: N/A
            Reporter: David Tanner
            Priority: Trivial


Problem Statement:
When the RegexStoryParser parses out a scenario, it attempts to remove the title from the step to get the scenario without title, but the function doesn't account for Scenario:\n before the title.  I don't think this will affect anything, and I don't think anything was broken initally, I just noticed as debugging that it didn't strip out the actual title because of the Scenario keyword, newline, and space before it.

Actual Code:
RegexStoryParser line 151: 

String scenarioWithoutTitle = removeStart(scenarioAsText, title);

Recommen

[jira] (JBEHAVE-781) Deprecate ConfigurableEmbedder addSteps() methods in favour of useStepsFactory()

Mauro Talevi (JIRA — 2012-05-15T09:52:03

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

Mauro Talevi resolved JBEHAVE-781.
----------------------------------

    Resolution: Fixed
      Assignee: Mauro Talevi
    


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

[jira] (JBEHAVE-781) Deprecate ConfigurableEmbedder addSteps() methods in favour of useStepsFactory()

Mauro Talevi (JIRA — 2012-05-15T09:48:03

Mauro Talevi created JBEHAVE-781:
------------------------------------

             Summary: Deprecate ConfigurableEmbedder addSteps() methods in favour of useStepsFactory()
                 Key: JBEHAVE-781
                 URL: https://jira.codehaus.org/browse/JBEHAVE-781
             Project: JBehave
          Issue Type: Task
          Components: Core
            Reporter: Mauro Talevi
            Priority: Minor
             Fix For: 3.6.7




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

[jira] (JBEHAVE-780) Isolate parameter data from .story files

Mauro Talevi (JIRA — 2012-05-12T07:24:02

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

Mauro Talevi commented on JBEHAVE-780:
--------------------------------------

You can parametrise a scenario using the table data loaded from a separate file:

http://jbehave.org/reference/stable/parametrised-scenarios.html

When contributing new ideas, please start from asking on the mailing lists if it's already possible with the current functionality:

http://jbehave.org/reference/stable/how-to-contribute.html

An issue can be opened once the idea has been discussed. 

                

--
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 unsub

[jira] (JBEHAVE-780) Isolate parameter data from .story files

prem (JIRA — 2012-05-11T19:01:03

prem created JBEHAVE-780:
----------------------------

             Summary: Isolate parameter data from .story files
                 Key: JBEHAVE-780
                 URL: https://jira.codehaus.org/browse/JBEHAVE-780
             Project: JBehave
          Issue Type: Story
          Components: Core
            Reporter: prem


Would like to segregate data from story file so that maintenance between stories and datas can be easy. 

For example,
Given I log into mail account as user $username with password $password

example 
username xxx
password xxx.

Would like to keep the example part in one file(.xml or text file) and .story file may not have example part. I want to create a mapping between $username from .story file and the data 'xxx' from .xml/.txt file. When Jbehave executes the scenario in step file, it should able to read the data('xxx') from data file and map to appropriate filed($username). Is this possible in present Jbehave framework? Could help us to do this





--
This message is automati

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

Mauro Talevi (JIRA — 2012-05-11T17:58:03

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

Mauro Talevi commented on JBEHAVE-778:
--------------------------------------

As an aside, in 3.x one could implement a custom StoryReporter implementation that timed the steps using the beforeStep() to start the time and the successful() or failed() methods to stop it.  
                

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

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

Mauro Talevi (JIRA — 2012-05-11T17:56:03

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

Mauro Talevi commented on JBEHAVE-778:
--------------------------------------

The results are now produced by the CrossReference class, and called xref.xml or xml.json. This file is produced in the target/jbehave/view at every execution.  You can share it however you feel most appropriate.  
 
There is no easy way to do this in 3.x branch, as this approach relies on the tree structure to collect the results.   I think it'd be preferable to focus on the new functionality in 4.x rather than trying to port it to 3.x in a half-baked way.  In the end, the execution times of single steps is not such a fundamental functionality, and we have the execution times of the stories implemented.

Sure, we can discuss the use of AOP although we need to clarify what behaviour we are trying to obtain by it.


                

--
This message is automatically gen

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

Brian Repko (JIRA — 2012-05-11T13:04:02

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

Brian Repko commented on JBEHAVE-778:
-------------------------------------

Mauro - agreed - the overhead of timing is small, so just doing it all the time and adding it to StepResult makes tons of sense.  We could do that in the 3.6 branch as well (its backward compatible).  Once we decide where to code this (4.x AND? 3.6), then I would request to close this issue (make it about timing).  We may want to open up the issue of AOP steps as an enhancement if it doesn't already exist.  I know that it was asked on the user list (Christian Zulehner) a while back but I'm not sure that we have it captured as an enhancement.  The issue is that the JBehave framework doesn't recognize those steps classes as the AOP wipes out the JBehave annotations and we talked about an unwrap method on some interface to get to the actual class.

                

--
This

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

prem (JIRA — 2012-05-11T11:01:04

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

prem commented on JBEHAVE-778:
------------------------------

Thanks. That is nice. Is it possible to share the relevant dependencies/jar's because you have done capturing duration of step result?. Otherwise, could you please tell me some temporary solution to fix this issue using annotation in Jbehave framework?.
                

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

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

Mauro Talevi (JIRA — 2012-05-11T10:39:03

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

Mauro Talevi commented on JBEHAVE-778:
--------------------------------------

I've added the capture of the step duration in millis in the step result (in the jbehave-4.x branch)

The step results are currently serialised in the target/jbehave/view/tree.{xml|json} files. 

I'm thinking the < at >Profiled annotation may be redundant if just used to trigger the duration capture, although we could use it to add more features relative to profiling. 

                

--
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 v

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

Mauro Talevi (JIRA — 2012-05-11T10:29:03

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

Work on JBEHAVE-778 started by Mauro Talevi.


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

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

Mauro Talevi (JIRA — 2012-05-11T10:29:03

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

Mauro Talevi reassigned JBEHAVE-778:
------------------------------------

    Assignee: Mauro Talevi
    

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

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

Mauro Talevi (JIRA — 2012-05-10T21:55:02

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

Mauro Talevi commented on JBEHAVE-778:
--------------------------------------

There is no mechanism at present to define custom annotations by the user.  We could think about this feature in 4.x.  A first beta of 4.0 could be out relatively soon but no date has been yet set.
                

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

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

Mauro Talevi (JIRA — 2012-05-10T21:53:03

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

Mauro Talevi commented on JBEHAVE-778:
--------------------------------------

I'm more oriented on a simpler approach that does not use neither AOP, nor Spring, nor Perf4J.  Simply time the execution interval before and after a step execution.   In fact, given it's a small overhead, I'm thinking that it could be done by default on all steps and reported in the StepResult.  
                

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

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

prem (JIRA — 2012-05-10T18:11:09

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

prem commented on JBEHAVE-778:
------------------------------

Thanks Brian Repko. Right now, I would like to log the step method execution time details. So, could please explain how to create AOP-enhanced Steps classes?. Any additional configuration required for this?

If you have some demos /references to work with AOP-enhanced Steps and Perf4j annotation, could you share me?.

Thanks in advance

                

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

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

Brian Repko (JIRA — 2012-05-10T14:42:02

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

Brian Repko commented on JBEHAVE-778:
-------------------------------------

One can add a Perf4J (for example) annotation to your Steps classes now.  The problem that you then run into is the enhancement request to work with AOP-enhanced Steps classes.  This kind of integration would leave all performance reporting up to you as part of your Perf4J integration (this by the way is what I'd like to show for AOP integration).  If you want the reporting of timings included in the JBehave reports - then I think we have to have a deeper integration with Perf4J or write our own.

This enhancement would probably better be addressed with Perf4J integration and deal with the AOP issue - my 2c.
                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.cod

[jira] (JBEHAVE-778) Capture the execution time of steps annotated by < at >Profiled

prem (JIRA — 2012-05-10T09:35:02

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

prem commented on JBEHAVE-778:
------------------------------

Thanks for considering this feature as part of Jbehave framework.

I have few queries on this feature. Is there any way to create and add the < at >Profiled annotation by our own in Jbehave framework ?. If yes, could you give us the procedure/steps to create and add this annotation in jbehave framework. 

Because, we have created custom annotation using Spring and AOP and integrated it with Jbehave. But, the custom annotation is not identified by Jbehave and hence, our goal is satisfied yet. Could you please provide the way to add custom annotaion with Jbeave. May be it give temporary solution for us. 

BTW, may i know when the ver 4.x release will happen? 

                

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA

[jira] (JBEHAVE-779) Change of ExamplesTableFactory constructor in patch release

Mauro Talevi (JIRA — 2012-05-10T07:42:02

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

Mauro Talevi resolved JBEHAVE-779.
----------------------------------

    Resolution: Fixed

Constructors in ExamplesTable and ExamplesTableFactory reinstated.  Thanks for heads up.
                

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

[jira] (JBEHAVE-779) Change of ExamplesTableFactory constructor in patch release

Mauro Talevi (JIRA — 2012-05-10T07:40:03

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

Mauro Talevi updated JBEHAVE-779:
---------------------------------

    Fix Version/s: 3.6.6
    

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

[jira] (JBEHAVE-779) Change of ExamplesTableFactory constructor in patch release

Daniel Schneller (JIRA — 2012-05-09T21:17:02

Daniel Schneller created JBEHAVE-779:
----------------------------------------

             Summary: Change of ExamplesTableFactory constructor in patch release
                 Key: JBEHAVE-779
                 URL: https://jira.codehaus.org/browse/JBEHAVE-779
             Project: JBehave
          Issue Type: Bug
          Components: Core
    Affects Versions: 3.6.5, 3.6.4
            Reporter: Daniel Schneller
            Priority: Minor


With JBEHAVE-718 the constructor 

    public ExamplesTableFactory(Keywords keywords, ResourceLoader resourceLoader,
            ParameterConverters parameterConverters)

was changed to

    public ExamplesTableFactory(Keywords keywords, ResourceLoader resourceLoader,
            ParameterConverters parameterConverters, TableTransformers tableTranformers)

when the TableTransformers feature was introduced.

This is a backwards incompatible change and should not have been included like that in a patch revision with only the last digit of the version number changed, as