The entry point for our test runs looks something like the following:
@RunWith(WeldAnnotatedEmbedderRunner.class)
@Configure()
@UsingEmbedder(embedder = Embedder.class,
verboseFailures = true,
generateViewAfterStories = true,
ignoreFailureInStories = true,
ignoreFailureInView = false,
metaFilters = "-skip",
storyTimeoutInSecs = Long.MAX_VALUE)
@UsingWeld
public class WeldAnnotatedStoryRunner
extends InjectableEmbedder
{
@Override
@Test
public void run()
{
final String storiesDirectory =
TestConfiguration.getInstance().getStoriesDirectory();
final String storyPathInclusion =
TestConfiguration.getInstance().getStoryPathInclusion();
this.injectedEmbedder().runStoriesAsPaths(this.getStoryPaths(storiesDirectory,
storyPathInclusion));
}
What does your entry point look like?
On Tue, Jun 3, 2014 at 5:57 AM, Russ Davidson <russ.david...@fixnetix.com>
wrote:
> Hi,
>
>
>
> I’m just looking to see if you’re able to help me with setting up the
> JBehave examples to be executed from Jenkins.
>
>
>
> I have successfully run the examples within Eclipse, but copying over the
> exact same files/configuration and using the same libraries in Jenkins, the
> job successfully runs, but does not run any of the actual tests.
>
>
>
> The only difference that I can see in the Jenkins console log is that
> surefire fails to find tests.
>
> [INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @
> jbehave.quickstart ---
>
> [INFO] No tests to run.
>
>
>
> The “No tests to run” message is not found in the Eclipse console log,
> where the tests are actually run.
>
> (I have attached the console logs for both Eclipse and Jenkins, with and
> without the maven “-X” debug option)
>
>
>
> I have used the jbehave-web-selenium-java-spring-archetype:3.5.5 (as the
> 3.6-beta-2 causes m2e errors) to create the project. The only change to the
> code is to use the “PropertyWebDriverProvider” instead of the default
> “FirefoxWebDriverProvider” in the etsy-steps.xml file, and passing the
> “-Dbrowser=htmlunit” maven option.
>
>
>
> This works with Eclipse, but fails to run the tests with Jenkins.
>
>
>
> JDK – 1.7.0_60
>
> Maven – 3.2.1
>
> Jenkins – 1.566
>
> Eclipse – 4.3.2.v20140221-1852
>
>
>
> Any help that you’re able to provide to get the tests working in Jenkins
> would be greatly appreciated.
>
>
>
> Cheers,
>
> Russ
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
--
--------------------------------------------
Frank M. Pedroza - Software Engineer
Partnet - Development
801.708.5050
-----------------------------------------------------------------
The nice part about being a pessimist is that you are constantly being
either proven right or pleasantly surprised.
-- George F. Will
