Paul Hammant (JIRA | 1 Apr 01:54 2011

[jira] Commented: (JBEHAVE-400) Error in WebDriverProvider initialize method ignored due to NPE in StoryRunner


    [
http://jira.codehaus.org/browse/JBEHAVE-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262164#action_262164
] 

Paul Hammant commented on JBEHAVE-400:
--------------------------------------

yay!

> Error in WebDriverProvider initialize method ignored due to NPE in StoryRunner
> ------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-400
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-400
>             Project: JBehave
>          Issue Type: Bug
>          Components: Web Selenium
>    Affects Versions: web-3.1
>            Reporter: Paul Hammant
>             Fix For: web-3.3
>
>         Attachments: BadlyInitializingWebDriverStepsTest.java
>
>
> {noformat} 
> new WebDriverProvider() {
>    public void initialize() { 
>      throw new RuntimeException(); //  or Error or something
>    } 
(Continue reading)

Mauro Talevi (JIRA | 1 Apr 12:16 2011

[jira] Resolved: (JBEHAVE-462) Add standalone WebQueue to run stories asynchronously and redirect output to story navigator


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

Mauro Talevi resolved JBEHAVE-462.
----------------------------------

    Resolution: Fixed

> Add standalone WebQueue to run stories asynchronously and redirect output to story navigator
> --------------------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-462
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-462
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Web Queue
>            Reporter: Mauro Talevi
>            Assignee: Paul Hammant
>             Fix For: web-3.3
>
>

--

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

(Continue reading)

Mauro Talevi | 2 Apr 14:17 2011

JBehave Core 3.3 and Web 3.3 released

All,

the JBehave Team is happy to announce the release of Core 3.3 and Web 3.3:

http://jbehave.org/2011/04/01/jbehave-3-3-released/

http://jbehave.org/2011/04/01/jbehave-web-3-3-released/

Cheers

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Mauro Talevi (JIRA | 3 Apr 12:23 2011

[jira] Updated: (JBEHAVE-148) Auto-generate steps from template


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

Mauro Talevi updated JBEHAVE-148:
---------------------------------

      Description: 
Automated the process of writing the matching Java steps by auto-generating stubs for steps from
template. It would involve defining a template of steps that specifies the name and type of the parameter
(with a given convention, such as colon separated).  So, e.g.

Given a condition $condition:Condition
When an $event:Event
Then the result is $result:Result

which would map steps 

Given a condition aCondition
When an anEvent
Then the result is aResult

to methods

 <at> Given("a condition $condition")
public void aCondition(Condition condition){
}

 <at> When("an event $event")
public void anEvent(Event event){
(Continue reading)

Agnes Crepet (JIRA | 3 Apr 16:39 2011

[jira] Created: (JBEHAVE-464) Specify a mvn repository for weld-se

Specify a mvn repository for weld-se
------------------------------------

                 Key: JBEHAVE-464
                 URL: http://jira.codehaus.org/browse/JBEHAVE-464
             Project: JBehave
          Issue Type: Improvement
          Components: Documentation
    Affects Versions: 3.3
            Reporter: Agnes Crepet

I've just tried to test the last 3.3 release. And I had to add a repository in my settings.xml:
http://repository.jboss.org/nexus/content/groups/public-jboss
for dependendy :
    <dependency>
      <groupId>org.jboss.weld.se</groupId>
      <artifactId>weld-se</artifactId>
      <version>1.1.0.Final</version>
    </dependency>

in pom.xml of the module jbehave-weld

--

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

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

Jan Tietjens (JIRA | 4 Apr 17:45 2011

[jira] Created: (JBEHAVE-465) Methods annotated with AfterStories are not called if a step is causing a RuntimeException

Methods annotated with AfterStories are not called if a step is causing a RuntimeException
------------------------------------------------------------------------------------------

                 Key: JBEHAVE-465
                 URL: http://jira.codehaus.org/browse/JBEHAVE-465
             Project: JBehave
          Issue Type: Bug
          Components: Core
    Affects Versions: web-3.3
            Reporter: Jan Tietjens

The AfterStory/BeforeStory annotations works in this case, so I would expect the same for the
AfterStories annotation.

Here is the setup code:

{code}
    StoryPathResolver storyPathResolver = new UnderscoredCamelCaseResolver(".story");
    Class storyClass = this.getClass();
    Properties viewProperties = new Properties();
    viewProperties.put("decorateNonHtml", "true");
    URL codeLocation = CodeLocations.codeLocationFromClass(storyClass);
    Configuration configuration = new MostUsefulConfiguration()
            .useStoryControls(new StoryControls().doDryRun(false).doSkipScenariosAfterFailure(false))
            .useStoryLoader(new LoadFromClasspath(storyClass.getClassLoader()))
            .useStoryReporterBuilder(new StoryReporterBuilder()
                    .withCodeLocation(codeLocation)
                    .withDefaultFormats()
                    .withViewResources(viewProperties)
                    .withFormats(StoryReporterBuilder.Format.CONSOLE, StoryReporterBuilder.Format.TXT,
(Continue reading)

Mauro Talevi (JIRA | 5 Apr 16:08 2011

[jira] Created: (JBEHAVE-466) Provide <at> Pending annotation to mark methods that have yet not been implemented

Provide  <at> Pending annotation to mark methods that have yet not been implemented
------------------------------------------------------------------------------

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

As suggested by Jonathan Woods, a  <at> Pending annotation can be used to mark not yet implemented methods,
either auto-generated or not.

--

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

Mauro Talevi (JIRA | 5 Apr 16:23 2011

[jira] Updated: (JBEHAVE-466) Provide <at> Pending annotation to mark methods that have not yet been implemented


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

Mauro Talevi updated JBEHAVE-466:
---------------------------------

    Summary: Provide  <at> Pending annotation to mark methods that have not yet been implemented  (was: Provide
 <at> Pending annotation to mark methods that have yet not been implemented)

> Provide  <at> Pending annotation to mark methods that have not yet been implemented
> ------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-466
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-466
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>             Fix For: 3.4
>
>
> As suggested by Jonathan Woods, a  <at> Pending annotation can be used to mark not yet implemented methods,
either auto-generated or not.

--

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

Mauro Talevi (JIRA | 5 Apr 17:27 2011

[jira] Work started: (JBEHAVE-466) Provide <at> Pending annotation to mark methods that have not yet been implemented


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

Work on JBEHAVE-466 started by Mauro Talevi.

> Provide  <at> Pending annotation to mark methods that have not yet been implemented
> ------------------------------------------------------------------------------
>
>                 Key: JBEHAVE-466
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-466
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>             Fix For: 3.4
>
>
> As suggested by Jonathan Woods, a  <at> Pending annotation can be used to mark not yet implemented methods,
either auto-generated or not.

--

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

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

Mauro Talevi (JIRA | 6 Apr 14:07 2011

[jira] Work started: (JBEHAVE-148) Auto-generate method stubs for pending steps


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

Work on JBEHAVE-148 started by Mauro Talevi.

> Auto-generate method stubs for pending steps
> --------------------------------------------
>
>                 Key: JBEHAVE-148
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-148
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Mauro Talevi
>            Assignee: Mauro Talevi
>             Fix For: 3.4
>
>
> Automated the process of writing the matching Java steps by auto-generating stubs for steps from
template. It would involve defining a template of steps that specifies the name and type of the parameter
(with a given convention, such as colon separated).  So, e.g.
> Given a condition $condition:Condition
> When an $event:Event
> Then the result is $result:Result
> which would map steps 
> Given a condition aCondition
> When an anEvent
> Then the result is aResult
> to methods
(Continue reading)


Gmane