Hi Caolite, On 02/05/2011 01:15, Caoilte O'Connor wrote: > Thanks Again Mauro, > > I seem to have everything working very nicely now and I'm not sure why > I wasn't seeing the stack trace for the story failure before. It might > have been because I was experimenting with run-with-annotated-embedder > instead of run-stories-as-embeddables, or because I was trying to use > an InjectableEmbedder instead of the (seemingly) more reliable > JUnitStories. Yes, different embeddables have different use cases but by far the easiest and most common is to extend JUnitStories. > I'm extremely pleased with how powerful jbehave is. If anyone is > interested, here are the areas where I had difficulty and found the > learning curve a little steep. We're very pleased that you find JBehave useful and we welcome your feedback. > 1) Figuring out what the different configuration parameters meant. > There are a lot of links to Javadocs, but these don't provide any more > information. For example, I'm still not quite sure what the difference > between > > @BeforeStory(uponGivenStory = true) > > and > > @BeforeStory(uponGivenStory = false) > This allows the annotated method to be executed only upon a "given story" or not
http://jbehave.org/reference/stable/given-stories.html We'll add some more clarification around this. > 2) Figuring out classpath issues in the Maven plugin. > > It would seem that the plugin requires you to add all dependencies > that your tests require as dependencies of the plugin. This isn't > clear and took a while to figure out. Not sure what you mean - the dependencies are specified at POM level, not plugin level. If you send us an example of the POM configuration (or better yet a simple sample project) we can work out these issues with you. > 3) Understanding which embedders work in which situations > > I was able to get JUnitStory/JUnitStories to work everywhere, but I > couldn't get the AnnotatedEmbedderUsingGuice to work via maven at all. > Possibly it doesn't - as there were no examples I could find. The use case that drove the development of AnnotatedEmbedder has been the integration with the JUnit Runner framework, e.g. in IDEs. We can look into the issues of Maven integration of the AnnotatedEmbedder. > And a few areas where I couldn't achieve quite as much as I hoped I > would be able to, > > 1) If there are errors then I would like the report to be generated > AND for the build to fail. This doesn't seem to be easily possible. > That is the default. Again - if you send us your example we can see why it's not working. > 2) I was able to use the ExamplesTable to populate my DB using dbunit, > but it was a bit cumbersome. I'm sure I'll improve the process but it > seems like an easy thing to provide out of the box (as EasyB does). Could you raise a JIRA issue explaining this use case in more detail? We could provide a DbUnitExamplesTable that folks may decide to use. By default ExamplesTable is "dumb" - all it's meant to do is to hold the parsed parameter data (converted as appropriate). But we can extend it for specific use cases. > > All in all, a great product though. > Thanks :-) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
