headers
Elizabeth Keogh (JIRA | 12 Aug 2008 16:20

[jira] Created: (JBEHAVE-127) Doesn't find scenarios with numbers in the title

Doesn't find scenarios with numbers in the title
------------------------------------------------

                 Key: JBEHAVE-127
                 URL: http://jira.codehaus.org/browse/JBEHAVE-127
             Project: JBehave
          Issue Type: Bug
            Reporter: Elizabeth Keogh

cells_with_3_neighbours_are_born -> CellsWith3NeighboursAreBorn, throws ScenarioNotFoundException
cells_with3_neighbours_are_born works OK, but should be able to do either.

--

-- 
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 | 5 comments |
headers
Elizabeth Keogh (JIRA | 18 Aug 2008 20:41

[jira] Closed: (JBEHAVE-110) Pending steps optionally break the build


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

Elizabeth Keogh closed JBEHAVE-110.
-----------------------------------

    Resolution: Fixed

Can be done either by specifying the strategy as part of the configuration, or by setting the System
property -Dorg.jbehave.failonpending to something non-null.

> Pending steps optionally break the build
> ----------------------------------------
>
>                 Key: JBEHAVE-110
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-110
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Elizabeth Keogh
>            Assignee: Elizabeth Keogh
>             Fix For: 2.0
>
>
> Given a scenario with pending steps
> Given I choose to break the build on pending steps
> When I run the scenario
> Then my build should break
(Continue reading)

Permalink | Reply | 0 comments |
headers
Elizabeth Keogh (JIRA | 18 Aug 2008 20:41

[jira] Closed: (JBEHAVE-124) Eclipse can't find the test to run when it's in JBehave's jar


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

Elizabeth Keogh closed JBEHAVE-124.
-----------------------------------

    Resolution: Fixed

Making the source available. Alternative is for projects suffering this problem to create their own
extension of the Scenario class and delegate the test method.

> Eclipse can't find the test to run when it's in JBehave's jar
> -------------------------------------------------------------
>
>                 Key: JBEHAVE-124
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-124
>             Project: JBehave
>          Issue Type: Improvement
>            Reporter: Elizabeth Keogh
>             Fix For: 2.0
>
>
> This works fine when we have the source available. Is there a way of including the source for Scenario in the
jar, to get Eclipse to notice that there really is a test?

--

-- 
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
Elizabeth Keogh (JIRA | 20 Aug 2008 14:28

[jira] Closed: (JBEHAVE-111) Only output broken scenarios


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

Elizabeth Keogh closed JBEHAVE-111.
-----------------------------------

    Resolution: Fixed

Can configure output of all scenarios with system property org.jbehave.outputall

> Only output broken scenarios
> ----------------------------
>
>                 Key: JBEHAVE-111
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-111
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Elizabeth Keogh
>            Assignee: Elizabeth Keogh
>             Fix For: 2.0
>
>
> Given I have many scenarios, some of which are broken
> Given I choose not to output working scenarios
> When I run the build
> Then I should only see the output from broken scenarios

--

--
(Continue reading)

Permalink | Reply | 0 comments |
headers
Elizabeth Keogh (JIRA | 20 Aug 2008 14:28

[jira] Closed: (JBEHAVE-106) Should be able to have multiple scenarios in a story


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

Elizabeth Keogh closed JBEHAVE-106.
-----------------------------------

    Resolution: Fixed

Done - use

Scenario: <Title>

<steps>

Scenario: <Title>

<steps>

> Should be able to have multiple scenarios in a story
> ----------------------------------------------------
>
>                 Key: JBEHAVE-106
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-106
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Elizabeth Keogh
>             Fix For: 2.0
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Elizabeth Keogh (JIRA | 20 Aug 2008 14:30

[jira] Closed: (JBEHAVE-123) JBehave configuration classes


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

Elizabeth Keogh closed JBEHAVE-123.
-----------------------------------

    Resolution: Fixed

We now have PropertyBasedConfiguration, which allows us to do things like output all scenarios, fail the
build on pending scenarios, etc.

> JBehave configuration classes
> -----------------------------
>
>                 Key: JBEHAVE-123
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-123
>             Project: JBehave
>          Issue Type: New Feature
>            Reporter: Elizabeth Keogh
>            Assignee: Elizabeth Keogh
>             Fix For: 2.0
>
>
> I'm starting to find that there are multiple different things I might want to do, and the dependency
injection mechanism isn't really working as well as I'd like for this.
> It would be nice to produce a configuration that's easy to set up, and use that for everything. We could then
have different ways of configuring JBehave, eg: environment-driven, settable, null (so you have to
specify everything yourself), etc.
> Going to have a play with this, driving it using the "broken scenarios only".
(Continue reading)

Permalink | Reply | 0 comments |
headers
Elizabeth Keogh (JIRA | 20 Aug 2008 14:30

[jira] Closed: (JBEHAVE-112) Output pending scenarios as well as broken when option to break build on pending is selected


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

Elizabeth Keogh closed JBEHAVE-112.
-----------------------------------

    Resolution: Fixed

I'm outputting all scenarios that require attention by default; feedback suggests this is most useful and
holistic option.

> Output pending scenarios as well as broken when option to break build on pending is selected
> --------------------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-112
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-112
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Elizabeth Keogh
>            Assignee: Elizabeth Keogh
>             Fix For: 2.0
>
>
> Given I have chosen to break the build on pending scenarios
> Given I have several scenarios, some of which are pending
> When I run the build
> Then I should see the pending scenarios in the output
(Continue reading)

Permalink | Reply | 0 comments |
headers
Elizabeth Keogh (JIRA | 20 Aug 2008 14:32

[jira] Closed: (JBEHAVE-118) Check that punctuation after args doesn't stop it working


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

Elizabeth Keogh closed JBEHAVE-118.
-----------------------------------

    Resolution: Fixed

I know this works, because I can do "When I click the cell at ($x, $y)" - so word boundaries are recognised

> Check that punctuation after args doesn't stop it working
> ---------------------------------------------------------
>
>                 Key: JBEHAVE-118
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-118
>             Project: JBehave
>          Issue Type: Task
>            Reporter: Elizabeth Keogh
>

--

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

Permalink | Reply | 0 comments |
headers
Elizabeth Keogh (JIRA | 22 Aug 2008 14:25

[jira] Closed: (JBEHAVE-108) Story narratives


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

Elizabeth Keogh closed JBEHAVE-108.
-----------------------------------

    Resolution: Fixed

Introduced StoryDefinition and ScenarioDefinition

> Story narratives
> ----------------
>
>                 Key: JBEHAVE-108
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-108
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Elizabeth Keogh
>             Fix For: 2.0
>
>
> Given a story file with several scenarios
> Given the story has a narrative
> When I output the scenarios
> Then I should see the narrative

--

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

Permalink | Reply | 0 comments |
headers
Elizabeth Keogh (JIRA | 22 Aug 2008 14:25

[jira] Closed: (JBEHAVE-107) Should be able to title scenarios


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

Elizabeth Keogh closed JBEHAVE-107.
-----------------------------------

    Resolution: Fixed

Introduced StoryDefinition and ScenarioDefinition

> Should be able to title scenarios
> ---------------------------------
>
>                 Key: JBEHAVE-107
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-107
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Elizabeth Keogh
>             Fix For: 2.0
>
>
> Given a scenario title before a scenario
> When I run the scenario
> Then I want to see the same title appear in the output

--

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

Permalink | Reply | 0 comments |

Gmane