- Revision
- 1373
- Author
- mauro
- Date
- 2009-10-31 11:16:12 -0500 (Sat, 31 Oct 2009)
Log Message
Minor additions to FAQ and running-scenarios pages. Updated download to latest release.
Modified Paths
Diff
Modified: trunk/core/distribution/src/site/content/download.html (1372 => 1373)
--- trunk/core/distribution/src/site/content/download.html 2009-10-31 16:08:33 UTC (rev 1372) +++ trunk/core/distribution/src/site/content/download.html 2009-10-31 16:16:12 UTC (rev 1373) @@ -14,10 +14,10 @@ <ul> <li><a - href="" + href="" bin distribution</a></li> <li><a - href="" + href="" src distribution</a></li> </ul>
Modified: trunk/core/distribution/src/site/content/faq.html (1372 => 1373)
--- trunk/core/distribution/src/site/content/faq.html 2009-10-31 16:08:33 UTC (rev 1372) +++ trunk/core/distribution/src/site/content/faq.html 2009-10-31 16:16:12 UTC (rev 1373) @@ -10,12 +10,13 @@ <h3>What is BDD?</h3> -<p>stands for Behaviour-Driven Development and you can learn -more about BBD from our <a href="" on BDD</a> page.</p> +<p>BDD stands for <b>Behaviour-Driven Development</b> and you can +learn more about BBD from our <a href="" on BDD</a> +page.</p> <h3>What Java version is required by JBehave?</h3> -<p>JBehave uses Java 5 annotations, so any JDK 1.5+ will work.</p> +<p>JBehave requires a JDK 1.5 or greater.</p> <h3>How do I use JBehave within my development environment?</h3> @@ -23,7 +24,10 @@ tests.</p> <p>Scenarios can also be run on command line, see <a - href="" scenarios</a>.</p> + href="" scenarios</a>. It can also be +run via web runner, although the web support is not part of JBehave +Core. For more info on web support refer to <a + href="" Web</a>.</p> <h3>What libraries does JBehave depend on?</h3> @@ -73,8 +77,8 @@ } </pre> -<p>Note that we don't tend to use TestNG so this solution as not -been tested. If you encounter any issues please let us know.</p> +<p>Note that as we don't tend to use TestNG this solution has not +been well-tested. If you encounter any issues please let us know.</p> <h3>How do I make my scenarios fail when steps are not matched and are shown as pending?</h3>
Modified: trunk/core/distribution/src/site/content/running-scenarios.html (1372 => 1373)
--- trunk/core/distribution/src/site/content/running-scenarios.html 2009-10-31 16:08:33 UTC (rev 1372) +++ trunk/core/distribution/src/site/content/running-scenarios.html 2009-10-31 16:16:12 UTC (rev 1373) @@ -11,7 +11,9 @@ <p>JBehave was designed to be embeddable in different development environments. The JBehave Core module contains support for running scenarios as JUnit tests - which can be run either in your favourite IDE -or in your command-line build that supports JUnit tests.</p> +or in your command-line build that supports JUnit tests. Other unit +testing frameworks, e.g. TestNG, can also be used very easily, c.f. <a + href="" <p>You can also run scenarios using the JBehave Ant or Maven extensions. Both support two way to lookup scenarios, by list of @@ -23,10 +25,13 @@ <pre class="brush: xml"> <taskdef name="scenarioRunner" classname="org.jbehave.ant.ScenarioRunnerTask" - classpathref="your.runtime.classpath"></taskdef> + classpathref="your.runtime.classpath" /> <scenarioRunner scenarioIncludes="**/scenarios/*.java" - scenarioExcludes="**/*Steps.java"></scenarioRunner> + scenarioExcludes="**/*Steps.java" + skip="[true|false]" + ignoreFailure="[true|false]" + scope="[compile|test]"/> </pre> <p>Remember that you need to include <b>jbehave-ant</b> to your @@ -50,6 +55,9 @@ <scenarioExcludes> <scenarioExclude>**/*Steps.java</scenarioExclude> </scenarioExcludes> + <skip>[true|false]</skip> + <ignoreFailure>[true|false]</ignoreFailure> + <scope>[compile|test]</scope> </configuration> <goals> <goal>run-scenarios</goal> @@ -59,9 +67,10 @@ </plugin> </pre> -<p><b>NOTE</b>: Running scenarios with Maven requires each Scenario class to have a constructor with a single ClassLoader parameter. -Maven uses this constructor to instantiate the Scenario class using the classpath constructed with the POM depedendencies. -</p> +<p><b>NOTE</b>: Running scenarios with Maven requires each Scenario +class to have a constructor with a single ClassLoader parameter. Maven +uses this constructor to instantiate the Scenario class using the +classpath constructed with the POM depedendencies.</p> <div class="clear"> <hr />
To unsubscribe from this list please visit:
