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

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

             Summary: Add an optional StoryFinder class parameter to @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 @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 @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

[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

[jira] (JBEHAVE-714) Move optional web-selenium classes to separate package so they can be excluded by OSGi compilers that don't play well with optional dependencies

Mauro Talevi created JBEHAVE-714:
------------------------------------

             Summary: Move optional web-selenium classes to separate package so they can be excluded by OSGi compilers
that don't play well with optional dependencies 
                 Key: JBEHAVE-714
                 URL: https://jira.codehaus.org/browse/JBEHAVE-714
             Project: JBehave
          Issue Type: Improvement
            Reporter: Mauro Talevi
            Assignee: Mauro Talevi
            Priority: Minor

--
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-713) Web Runner results leak between invocations

Paul Hammant created JBEHAVE-713:
------------------------------------

             Summary: Web Runner results leak between invocations
                 Key: JBEHAVE-713
                 URL: https://jira.codehaus.org/browse/JBEHAVE-713
             Project: JBehave
          Issue Type: Bug
          Components: Web Runner
            Reporter: Paul Hammant

Take a story that passes:

{noformat} 
Scenario:
Given a threshold of 10.0
When the stock is traded at 5.0
Then the alert status should be OFF
When the stock is traded at 11.0
Then the alert status should be ON
{noformat}

Confirm it passes.  Change it so that it does not pass.  In this case, change 5.0 to 888.  The re-run.  

Note that it fails as expected. 

Change it back to the 'passing' grammar again, and re-run.

Note that it apparently fails.  Any repeated clicking of the 'run' button shows the failed results again and
again 

[jira] (JBEHAVE-712) Spaces in path breaks StoryFinder().findPaths()

Marcin Zajaczkowski created JBEHAVE-712:
-------------------------------------------

             Summary: Spaces in path breaks StoryFinder().findPaths()
                 Key: JBEHAVE-712
                 URL: https://jira.codehaus.org/browse/JBEHAVE-712
             Project: JBehave
          Issue Type: Bug
          Components: Core
    Affects Versions: 3.5.4
         Environment: JBehave 3.6-beta-3, Fedora 15, 64-bit, Java HotSpot 1.6.0_30, 64-bit
            Reporter: Marcin Zajaczkowski
            Priority: Minor

Constructions like:
List<String> storyPaths = new StoryFinder().findPaths(codeLocationFromClass(getClass()),
"**/*.story", "**/*examples.story");
or
List<String> storyPaths = new StoryFinder().findPaths(codeLocationFromPath("somePath"),
"**/*.story", "**/*examples.story");
doesn't work when there are spaces in a path (which are replaced to %20).

An issue similar to JBEHAVE-389.

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

---------------------------------------------------------------------

[jira] (JBEHAVE-711) empty lines in example tables should be ignored

Alexander Lehmann created JBEHAVE-711:
-----------------------------------------

             Summary: empty lines in example tables should be ignored
                 Key: JBEHAVE-711
                 URL: https://jira.codehaus.org/browse/JBEHAVE-711
             Project: JBehave
          Issue Type: Improvement
          Components: Core
    Affects Versions: 3.5.4
            Reporter: Alexander Lehmann
            Priority: Minor

I tried to improve the layout of an example table in one story by adding newlines before each comment line (to
improve the legibility a bit),

however it turns out that an empty line in the table gives a list of empty parameters in the examples (e.g. |||
when you have 2 parameters).

I think it would be better if empty lines are ignored, unless I'm missing something.

If that is ok, I can write a patch.

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

[jira] (JBEHAVE-710) Pending steps methods should remove even more characters

Alexander Lehmann created JBEHAVE-710:
-----------------------------------------

             Summary: Pending steps methods should remove even more characters
                 Key: JBEHAVE-710
                 URL: https://jira.codehaus.org/browse/JBEHAVE-710
             Project: JBehave
          Issue Type: Bug
          Components: Core
    Affects Versions: 3.5.4
            Reporter: Alexander Lehmann
            Priority: Minor

Following up on JBEHAVE-681, I noticed that even more characters should be removed when creating the
method name (e.g. %)

I have changed the method name filter to use isJavaIdentifierPart and added a unit test to check for all characters

--
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-709) Named parameters sorrounded by quotes are not handled properly

Rui Miguel Pereira Figueira created JBEHAVE-709:
---------------------------------------------------

             Summary: Named parameters sorrounded by quotes are not handled properly
                 Key: JBEHAVE-709
                 URL: https://jira.codehaus.org/browse/JBEHAVE-709
             Project: JBehave
          Issue Type: Bug
          Components: Core
    Affects Versions: 3.5.4
            Reporter: Rui Miguel Pereira Figueira

Wnen using jbehave with named parameters, order is not respected in parameter injection if the named
parameters are sorrounded with non-white characters (for example, quotes).
Here is a simple test:

{code}
public class QuoteNamedParametersStory extends JUnitStory {

  public static class QuotNamedParametersSteps {

    @Then("\"$foo\" then \"$bar\"")
    public void otherOrderQuotes(@Named("bar") String bar, @Named("foo") String foo) {
      assertThat(foo, equalTo("foo"));
      assertThat(bar, equalTo("bar"));
    }
  }

  @Override
  public Configuration configuration() {

Parameterizing GivenStories and the parent scenario

[jira] (JBEHAVE-708) Upgrade Selenium to 2.17, Groovy to 1.8.5, and Guava to 11.0.1

Paul Hammant created JBEHAVE-708:
------------------------------------

             Summary: Upgrade Selenium to 2.17, Groovy to 1.8.5, and Guava to 11.0.1
                 Key: JBEHAVE-708
                 URL: https://jira.codehaus.org/browse/JBEHAVE-708
             Project: JBehave
          Issue Type: Task
          Components: Web Selenium
            Reporter: Paul Hammant
            Assignee: Paul Hammant
            Priority: Trivial
             Fix For: web-3.5

--
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-707) Add Maven web archetypes

Mauro Talevi created JBEHAVE-707:
------------------------------------

             Summary: Add Maven web archetypes
                 Key: JBEHAVE-707
                 URL: https://jira.codehaus.org/browse/JBEHAVE-707
             Project: JBehave
          Issue Type: New Feature
          Components: Archetypes
            Reporter: Mauro Talevi
            Assignee: Mauro Talevi
             Fix For: web-3.5

Add archetypes using jbehave-web-selenium.

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