headers
Mauro Talevi (JIRA | 1 Apr 2010 10:45

[jira] Updated: (JBEHAVE-254) Review story/steps configuration


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

Mauro Talevi updated JBEHAVE-254:
---------------------------------

    Description: 
Story and steps configuration should be reviewed to maintain what worked well and remove what did not.   

Criterias for refactor:
- Adopt similar paradigm for story and steps configuration
- Elements of the configuration should always have default values and should 
be overridable singularly, after instantiation
- Immutability of configuration can be obtained by decorating a configuration and disabling the use*
methods.  
- Default configurations should always be available to runners and should not be required as parameters in
super() invocations.

Have a base abstract class [Story|Steps]Configuration that holds the elements of the configuration,
injectable both via constructor and after instantiation via use* methods.  

Have a MostUseful[Story|Steps]Configuration that holds the default configuration that can be used as
base for overriding individual elements. 

Have an Immutable[Story|Steps]Configuration throwing an exception when use* methods invoked.

  was:
Story configuration should be possible by composition rather than inheritance.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 1 Apr 2010 10:46

[jira] Updated: (JBEHAVE-254) Review story/steps configuration


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

Mauro Talevi updated JBEHAVE-254:
---------------------------------

    Description: 
Story and steps configuration should be reviewed to maintain what worked well and remove what did not.   

Criterias for refactor:
- Adopt similar paradigm for story and steps configuration
- Elements of the configuration should always have default values and should be overridable singularly,
after instantiation
- Immutability of configuration can be obtained by decorating a configuration and disabling the use*
methods.  
- Default configurations should always be available to runners and should not be required as parameters in
super() invocations.

Changes:
- Have a base abstract class [Story|Steps]Configuration that holds the elements of the configuration,
injectable both via constructor and after instantiation via use* methods.  
- Have a MostUseful[Story|Steps]Configuration that holds the default configuration that can be used as
base for overriding individual elements. 
- Have an Immutable[Story|Steps]Configuration throwing an exception when use* methods invoked.

  was:
Story and steps configuration should be reviewed to maintain what worked well and remove what did not.   

Criterias for refactor:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 1 Apr 2010 15:33

[jira] Updated: (JBEHAVE-156) Allow running of multiple textual stories using a single Java RunnableStory


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

Mauro Talevi updated JBEHAVE-156:
---------------------------------

    Description: 
I want to be able to run multiple textual stories from the same Java RunnableStory, provided they use the
same StoryConfiguration and the same CandidateSteps instances.

This would avoid the need to define a Java RunnableStory class for each textual story.

  was:
As a scenario runner, I want to be able to run multiple textual scenarios from the same Java Scenario class,
using a single Steps class instance that contains all my steps. 

The main refactor (backward-compatible) would be to add a method to ScenarioNameResolver

List<String> resolveAll(Class<? extends Scenario> scenarioClass);

which as a special case returns a single path.   In the implementation we'd also need to provide some way to
configure which textual scenarios are to run.

This would be useful as a start of a web or wiki-based scenario runner. 

        Summary: Allow running of multiple textual stories using a single Java RunnableStory   (was: Allow
resolution of multiple textual scenarios from a single Java scenario)

> Allow running of multiple textual stories using a single Java RunnableStory
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 1 Apr 2010 15:33

[jira] Updated: (JBEHAVE-156) Allow running of multiple textual stories using a single Java RunnableStory


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

Mauro Talevi updated JBEHAVE-156:
---------------------------------

    Comment: was deleted

(was: Bumping out of 2.2 release until consensus is reached on how to approach problem.)

> Allow running of multiple textual stories using a single Java RunnableStory 
> ----------------------------------------------------------------------------
>
>                 Key: JBEHAVE-156
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-156
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 2.0
>            Reporter: Mauro Talevi
>             Fix For: 3.0
>
>
> I want to be able to run multiple textual stories from the same Java RunnableStory, provided they use the
same StoryConfiguration and the same CandidateSteps instances.
> This would avoid the need to define a Java RunnableStory class for each textual story.

--

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

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 2 Apr 2010 12:40

[jira] Created: (JBEHAVE-255) Make column separator configurable in ExamplesTable

Make column separator configurable in ExamplesTable
---------------------------------------------------

                 Key: JBEHAVE-255
                 URL: http://jira.codehaus.org/browse/JBEHAVE-255
             Project: JBehave
          Issue Type: Improvement
          Components: Core
            Reporter: Mauro Talevi
            Priority: Minor
             Fix For: 3.0

When trying to read from external sources, like a wiki, some characters like "|" may be reserved and we need
to allow for use of others. 

The parser should allow configuration of other column separators when parsing tables.

--

-- 
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 | 6 comments |
headers
Mauro Talevi (JIRA | 2 Apr 2010 12:44

[jira] Created: (JBEHAVE-256) Stories should be retrievable from remote sources

Stories should be retrievable from remote sources
-------------------------------------------------

                 Key: JBEHAVE-256
                 URL: http://jira.codehaus.org/browse/JBEHAVE-256
             Project: JBehave
          Issue Type: New Feature
          Components: Core
            Reporter: Mauro Talevi
             Fix For: 3.0

I want to be able to specify my stories in an external/remote source, e.g. a wiki. 

The stories resources should then be identifiable via a URL or some such, of which local class path
resources are a special case.

--

-- 
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 | 4 comments |
headers
Mauro Talevi (JIRA | 3 Apr 2010 16:12

[jira] Updated: (JBEHAVE-256) Stories should be retrievable from external or remote sources


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

Mauro Talevi updated JBEHAVE-256:
---------------------------------

    Description: 
I want to be able to specify my stories in an external or remote source, e.g. a file directory or a wiki. 

The stories resources should then be identifiable via a URL or some such, of which local class path
resources are a special case.

  was:
I want to be able to specify my stories in an external/remote source, e.g. a wiki. 

The stories resources should then be identifiable via a URL or some such, of which local class path
resources are a special case.

        Summary: Stories should be retrievable from external or remote sources  (was: Stories should be
retrievable from remote sources)

> Stories should be retrievable from external or remote sources
> -------------------------------------------------------------
>
>                 Key: JBEHAVE-256
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-256
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 3 Apr 2010 16:16

[jira] Created: (JBEHAVE-257) Migration path from JBehave 2.x to JBehave 3.x

Migration path from JBehave 2.x to JBehave 3.x
----------------------------------------------

                 Key: JBEHAVE-257
                 URL: http://jira.codehaus.org/browse/JBEHAVE-257
             Project: JBehave
          Issue Type: Task
          Components: Documentation
            Reporter: Mauro Talevi
             Fix For: 3.0

Document migration path from 2.x to 3.x. 

--

-- 
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 | 3 comments |
headers
Mauro Talevi (JIRA | 3 Apr 2010 18:25

[jira] Assigned: (JBEHAVE-156) Allow running of multiple textual stories using a single Java RunnableStory


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

Mauro Talevi reassigned JBEHAVE-156:
------------------------------------

    Assignee: Mauro Talevi

> Allow running of multiple textual stories using a single Java RunnableStory 
> ----------------------------------------------------------------------------
>
>                 Key: JBEHAVE-156
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-156
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 2.0
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>             Fix For: 3.0
>
>
> I want to be able to run multiple textual stories from the same Java RunnableStory, provided they use the
same StoryConfiguration and the same CandidateSteps instances.
> This would avoid the need to define a Java RunnableStory class for each textual story.

--

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

Permalink | Reply | 0 comments |
headers
Mauro Talevi (JIRA | 3 Apr 2010 18:25

[jira] Updated: (JBEHAVE-156) Allow running of multiple textual stories using a single Java RunnableStory


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

Mauro Talevi updated JBEHAVE-156:
---------------------------------

    Comment: was deleted

(was: This feature may or may not be relevant any more - e.g. the JBehave Web Runner by-passes the Scenario
and uses the Configuration and Steps directly.     Still useful to discuss if this one-to-one mapping for IDE
integration - simple and effective - may not be overcome while still preserving the same simplicity and
effectiveness for scenarios that use the same Steps instance.

)

> Allow running of multiple textual stories using a single Java RunnableStory 
> ----------------------------------------------------------------------------
>
>                 Key: JBEHAVE-156
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-156
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 2.0
>            Reporter: Mauro Talevi
>             Fix For: 3.0
>
>
> I want to be able to run multiple textual stories from the same Java RunnableStory, provided they use the
(Continue reading)

Permalink | Reply | 0 comments |

Gmane