cucumber-jvm

we already have automated testcases using cucumber-gherkin feature files with WebDriver. Right now we are able to execute feature files parallel, however we are not able to execute parallel at scenario/scenario outline level. By this way we want to minimize the execution time and utilize the cloud service at maximum level. I read this post , which claims one can run gherkin as QAF scenario so it will have features like run configuration, reporting, parallel execution, step listener . Before migrating, I want to know if anybody has tried or know any limitation as our test bed is very large. Yes

I have a project with cucumber and maven also I am using the JUnit. I am able to run and build my project successfully from Eclipse. Now I want to run the test from command line in another system which does(should) not have eclipse or cucumber installed. I have an idea that we can create a JAR from jar we can run the tests by java cli commands. Below are the combinations I am trying to run my tests from , also I am pasting the pom.xml and RunCukesTest.java file.. pom.xml <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=

I try to build my first executable specifications with Java and Maven. I created a simple project with this structure: specification |-src |-test |-java |-mypackage |-MyFeatureTest.java |-resources |-MyFeature.feature In the junit test MyFeatureTest.java I have this: import org.junit.runner.RunWith; import cucumber.junit.Cucumber; @RunWith(Cucumber.class) public class HomepageTest { } Now https://github.com/cucumber/cucumber-jvm/wiki/IDE-support says that I should add the following line: @Cucumber.Options(paths={"my/super.feature:34"}) I tried to modify that to @Cucumber.Options(paths={"src

Is there any way to continue executing Cucumber Steps even when one of the steps fails. In my current setup when a step fails , cucumber skips remaining steps....I wonder if there is some way to twick cucumber runner setup.. I could comment out failing steps but its not practical when you dont know which step will fail...If i could continue with remaining step i would know complete set of failing Tests in one shot....rather than going in cycle over cycle... Environment: Cucumber JVM , R , Java , Ibatis , Spring Framework, Maven joshuanapoli It is not a good idea to continue executing steps

I have cucumber feature file located at below location on my local: C:\ProjectWork\Workspace\Cucumber\DIT_Cucumber\src\cucumber\featureOne.feature and Junit jar at below location: C:\DurgeshProjectWork\Workspace\JarFiles\junit-4.11.jar When I have tried several commands like below to execute the feature file from command prompt however all the time getting same error as Could not fine class Below are the commands which I used: Command 1: C:\>java -cp C:\ProjectWork\Workspace\JarFiles\junit-4.11.jar org.junit.runner.JUnitCore C:\DurgeshProjectWork\Workspace\Cucumbe r\DIT_Cucumber\bin\cucumber

I am running a maven project in Eclipse for my Cucumber tests. My test runner class looks like this: @RunWith(Cucumber.class) @CucumberOptions( tags = { "@Now" }, // tags = { "@Ready" }, // tags = { "@Draft" }, features = { "src/test/java/com/myCompany/FaultReporting/Features" }, glue = { "com.myCompany.myApp.StepDefinitions" } ) public class RunnerTest { } Instead of having to hard code the tags into the test runner, I am keen to pass them in using the .command file. (i.e. using System.getProperty("cucumber.tag") However, I get an error when I add the line of code to the above test runner:

I have a Cucumber-JVM, JUnit, Selenium setup. I initiate the run by running RunSmokeTests.java using JUnit within Eclipse. I have also set up a maven profile to run the tests from command line, and possibly Jenkins in the future. When the tests are run then some of them may fail sometimes, mainly due to the application taking longer than expected. I would then have to re-run these scenarios. At the moment I run them by manually attaching @rerun tag to the ones that failed and then running RunReruns.java , which is similar to RunSmokeTest.java but with @rerun tag. With the increasing number of