Hi Jörgen,  please try with 3.2-beta-4, as it contains fix for
http://jira.codehaus.org/browse/JBEHAVE-407.

On 26/01/2011 11:41, Jörgen Falk wrote:
> Hi
>
> we use a continuous integration server (Hudson) that runs our JBehave
> integration tests. The problem we have is to configure JBehave /
> JBehave-Maven-Plugin to run all tests, generate reports (including the
> view/reports.html file) AND (!!!) let Maven return FAILURE if some
> test failed or SUCCESS if all tests went well. We can configure
> JBehave to generate the view/reports-file but then Maven always return
> SUCCESS or we can configure Maven-JBehave-plugin to return
> FAILURE/SUCCESS but then we get no view/reports.html file.
>
> We really need to both have reports and to signal FAILURE/SUCCESS so
> that we can trigger email notifcations, lava lamps etc from Hudson and
> be able to present a nice error report.
>
> Our pom look like this:
>
>             <plugin>
>                 <groupId>org.jbehave</groupId>
>                 <artifactId>jbehave-maven-plugin</artifactId>
>                 <version>3.1.2</version>
>                 <executions>
>                     <execution>
>                         <id>run-stories-as-embeddables</id>
>                         <phase>integration-test</phase>
>                         <configuration>
>                             <includes>
>                                 <include>**/*Stories.java</include>
>                             </includes>
>                             <metaFilters>
>                                 <metaFilter>-InProgress</metaFilter>
>                             </metaFilters>
>                             <batch>true</batch>
>                           
>  <generateViewAfterStories>true</generateViewAfterStories>
>                           
>  <ignoreFailureInStories>false</ignoreFailureInStories>
>                           
>  <ignoreFailureInView>false</ignoreFailureInView>>
>                             <scope>test</scope>
>                         </configuration>
>                         <goals>
>                             <goal>run-stories-as-embeddables</goal>
>                         </goals>
>                     </execution>
>                 </executions>
>                 <dependencies>
>                     <dependency>
>                         <groupId>log4j</groupId>
>                         <artifactId>log4j</artifactId>
>                         <version>1.2.16</version>
>                     </dependency>
>                 </dependencies>
>             </plugin>
>
> We've tried with many different configurations but none gives us the
> desired result. We also tried with the trader example and it behave
> (almost) the same. Given the information in other threads and
> jira-issues, setting <batch>true</batch> and the <ignoreFailureXXX>
> flags to false should to the trick, but I'm not sure exactly how these
> settings should be applied, specially in conjunction with the
> MostUsefulConfiguration().withXXX() settings in our "BaseStories" (i.e
> the extension to JUnitStories). Note that you can have
>  <configuration> elements both under the <plugin> node and under each
> <execution> node.. You also have the
> <goal>generate-stories-view</goal>... Many options, but little
> documentation on how they work....
>
> Can you provide a configuration (both pom and the
> "MostUsefulConfiguration()") for the Trader example that will, using
> Maven, run all test, generate view/reports AND Maven will return
> FAILURE (since there are some tests that fail in the trader example)?


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

    http://xircles.codehaus.org/manage_email


Reply via email to