Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rerun functionality executes scenarios unnecessarily even the scenarios are passed #840

Closed
Prabat opened this issue Mar 3, 2015 · 2 comments

Comments

@Prabat
Copy link

Prabat commented Mar 3, 2015

If any scenarios are failed in execution then rerun functionality working fine & executed only failed scenarios But in passed condition -> rerun.txt is blank/empty & it is initiating all the scenarios unnecessarily.

TriggerTest.java

@RunWith(Cucumber.class)
@CucumberOptions(
        features = { "classpath:script"},
        plugin = { "pretty","rerun:target/rerun.txt","html:target/report/html-basic",
                                "json:target/report/cucumber.json" }, 
                glue = { "script" }
        ,tags = { "@Sprint1"}
        )
public class TriggerTest {

}

RerunTest.java

@RunWith(Cucumber.class)
@CucumberOptions(
        features = { "@target/rerun.txt" },
        plugin = { "pretty","html:target/report/rerun/html-basic",         
                                "json:target/report/rerun/cucumber.json" }, 
                glue = { "script" }
        )
public class RerunTest {

}

Above are two Test files used in project

  • TriggerTest.java file is the main test execution -> save the failed scenarios in the file "target/rerun.txt"
  • RerunTest.java file is the second test execution for failed scenarios by taking input from "target/rerun.txt"

Please look into this issue for scenario's passed condition & Provide the solution if it can be done in a different way.

@aslakhellesoy
Copy link
Contributor

@Prabat Please don't request that others fix bugs for you. This is an open source project, which means we rely on bugs to be fixed by the community.

Wold you be willing to spend time fixing this yourself and send us a pull request? You'd start by writing a failing automated test (unit test or scenario) to reproduce the incorrect behaviour, then make it pass.

@lock
Copy link

lock bot commented Oct 25, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants