[jbehave-dev] [jira] Created: (JBEHAVE-474) Pending step method generation fails with And steps
Pending step method generation fails with And steps
---
Key: JBEHAVE-474
URL: http://jira.codehaus.org/browse/JBEHAVE-474
Project: JBehave
Issue Type: Bug
Components: Core
Affects Versions: 3.3.1, 3.4
Environment: JDK 1.6.0_24 on Mac OS Snow Leopard
Reporter: Jonathan Woods
Priority: Minor
When I run over a scenario with 'and' steps, pending method generation fails.
The same scenario without the 'and' steps generates methods without any problem
(and is jolly useful).
The failure happens in 3.3.1 and in 3.4-SNAPSHOT, commit c27f34.
The failure results from an NPE; JBehave knows the story has failed, but the
run times out and then exits with 'pass' from the JUnit POV. Is that the
expected behaviour, btw?
Failing scenario:
Scenario: When I log in with good credentials after having been redirected to
the login page from my intended page, I am redirected to my intended page
Given I am not logged in
And I have been redirected from my intended page to the login page
When I log in with good credentials
Then I am redirected to my intended page
And I am logged in
Console output:
Scenario: When I log in with good credentials after having been redirected to
the login page from my intended page, I am redirected to my intended page
Given I am not logged in (PENDING)
And I have been redirected from my intended page to the login page (PENDING)
When I log in with good credentials (PENDING)
Then I am redirected to my intended page (PENDING)
And I am logged in (PENDING)
Failed to run story
package.name.here/login/i_can_log_in_with_correct_credentials.story
java.lang.NullPointerException
at
org.jbehave.core.steps.PendingStepMethodGenerator.stepStartsWithWord(PendingStepMethodGenerator.java:86)
at
org.jbehave.core.steps.PendingStepMethodGenerator.findStepType(PendingStepMethodGenerator.java:64)
at
org.jbehave.core.steps.PendingStepMethodGenerator.generateMethod(PendingStepMethodGenerator.java:32)
at
org.jbehave.core.embedder.StoryRunner.generatePendingStepMethods(StoryRunner.java:287)
at
org.jbehave.core.embedder.StoryRunner.runScenarioSteps(StoryRunner.java:272)
at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:170)
at org.jbehave.core.embedder.StoryRunner.run(StoryRunner.java:95)
at
org.jbehave.core.embedder.Embedder$EnqueuedStory.call(Embedder.java:686)
at
org.jbehave.core.embedder.Embedder$EnqueuedStory.call(Embedder.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Story package.name.here/login/i_can_log_in_with_correct_credentials.story has
timed out after 61 seconds
Generating reports view to
'/Users/jonathanwoods/Documents/workspaces/main/mobile/target/jbehave' using
formats '[stats, console, txt, html, xml]' and view properties
'{decorateNonHtml=true}'
Reports view generated with 5 stories (of which 2 pending) containing 3
scenarios (of which 0 failed and 3 pending)
--
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
[jbehave-dev] [jira] Commented: (JBEHAVE-424) Test run with Eclipse but no with maven
[ http://jira.codehaus.org/browse/JBEHAVE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263453#action_263453 ] Jonathan Woods commented on JBEHAVE-424: Juan - Have you really checked that applicationContext.xml is in target/test-classes? When this happens for me, it's because Eclipse/m2eclipse/Maven hasn't bothered to copy across the resource. Sometimes, modifying then saving it is enough to cause the copying to take place. Jon > Test run with Eclipse but no with maven > --- > > Key: JBEHAVE-424 > URL: http://jira.codehaus.org/browse/JBEHAVE-424 > Project: JBehave > Issue Type: Bug > Components: Maven Plugin >Affects Versions: 3.1.2 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_04 > Java home: C:\Archivos de programa\Java\jdk1.6.0_04\jre > Default locale: es_AR, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Gardella Juan Pablo > Attachments: sample.zip > > > I want to integrate Jbehave with maven and have a lot of troubles. I attach a > sample with an example. The Story pass if I run as Junit test in eclipse, but > when I try with maven fail. > Is a classloader problem. The exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: IOException > pars > ing XML document from class path resource [applicationContext.xml]; nested > excep > tion is java.io.FileNotFoundException: class path resource > [applicationContext.x > ml] cannot be opened because it does not exist > But to fix this I must pass ALL dependencies to the plugin. > I hope there is a solution to this. Thanks. -- 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
[jbehave-dev] [jira] Commented: (JBEHAVE-424) Test run with Eclipse but no with maven
[ http://jira.codehaus.org/browse/JBEHAVE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263458#action_263458 ] Jonathan Woods commented on JBEHAVE-424: This time, I've actually downloaded your sample (apologies for not trying the first time). At first glance, it looks as though it's because Eclipse unhelpfully merges compile and test scope, but Maven doesn't. So your Spring config, which is test scope, simply isn't visible in the Maven runtime classpath. But I'll double-check and report back. > Test run with Eclipse but no with maven > --- > > Key: JBEHAVE-424 > URL: http://jira.codehaus.org/browse/JBEHAVE-424 > Project: JBehave > Issue Type: Bug > Components: Maven Plugin >Affects Versions: 3.1.2 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_04 > Java home: C:\Archivos de programa\Java\jdk1.6.0_04\jre > Default locale: es_AR, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Gardella Juan Pablo > Attachments: sample.zip > > > I want to integrate Jbehave with maven and have a lot of troubles. I attach a > sample with an example. The Story pass if I run as Junit test in eclipse, but > when I try with maven fail. > Is a classloader problem. The exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: IOException > pars > ing XML document from class path resource [applicationContext.xml]; nested > excep > tion is java.io.FileNotFoundException: class path resource > [applicationContext.x > ml] cannot be opened because it does not exist > But to fix this I must pass ALL dependencies to the plugin. > I hope there is a solution to this. Thanks. -- 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
[jbehave-dev] [jira] Issue Comment Edited: (JBEHAVE-424) Test run with Eclipse but no with maven
[ http://jira.codehaus.org/browse/JBEHAVE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263458#action_263458 ] Jonathan Woods edited comment on JBEHAVE-424 at 4/13/11 9:34 AM: - This time, I've actually downloaded your sample (apologies for not trying the first time). At first glance, it looks as though it's because Eclipse unhelpfully merges compile and test scope, wrongly treating them the same; but Maven rightly doesn't. So your Spring config, which is test scope, simply isn't visible in the Maven runtime classpath. But I'll double-check and report back. was (Author: scintos): This time, I've actually downloaded your sample (apologies for not trying the first time). At first glance, it looks as though it's because Eclipse unhelpfully merges compile and test scope, but Maven doesn't. So your Spring config, which is test scope, simply isn't visible in the Maven runtime classpath. But I'll double-check and report back. > Test run with Eclipse but no with maven > --- > > Key: JBEHAVE-424 > URL: http://jira.codehaus.org/browse/JBEHAVE-424 > Project: JBehave > Issue Type: Bug > Components: Maven Plugin >Affects Versions: 3.1.2 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_04 > Java home: C:\Archivos de programa\Java\jdk1.6.0_04\jre > Default locale: es_AR, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Gardella Juan Pablo > Attachments: sample.zip > > > I want to integrate Jbehave with maven and have a lot of troubles. I attach a > sample with an example. The Story pass if I run as Junit test in eclipse, but > when I try with maven fail. > Is a classloader problem. The exception is: > org.springframework.beans.factory.BeanDefinitionStoreException: IOException > pars > ing XML document from class path resource [applicationContext.xml]; nested > excep > tion is java.io.FileNotFoundException: class path resource > [applicationContext.x > ml] cannot be opened because it does not exist > But to fix this I must pass ALL dependencies to the plugin. > I hope there is a solution to this. Thanks. -- 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
[jbehave-dev] [jira] Commented: (JBEHAVE-149) Support loading of stories from ODT format
[ http://jira.codehaus.org/browse/JBEHAVE-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263577#action_263577 ] Jonathan Woods commented on JBEHAVE-149: I wonder if this is the time to introduce a strategy such as StorySource: List getStories(). Then all these various... er, story sources could be used by anything which needed stories, via Configuration implementations or whatever. And it would make mocking nice and easy. I realise that many story sources get their stories from a path, but that's not a necessary feature of being a StorySource as suggested here. > Support loading of stories from ODT format > -- > > Key: JBEHAVE-149 > URL: http://jira.codehaus.org/browse/JBEHAVE-149 > Project: JBehave > Issue Type: New Feature > Components: ODF Support >Reporter: Mauro Talevi >Assignee: Mauro Talevi > Fix For: 3.4 > > > As a BA I want to be able to write my story in a ODT format -- 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
