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

Enhancement Request: Scenario Failure Retry + Context Injection support within Cucumber #1322

Closed
chakraborty-rupam opened this issue Feb 12, 2018 · 4 comments
Labels
⌛ stale Will soon be closed by stalebot unless there is activity ⚡ enhancement Request for new functionality

Comments

@chakraborty-rupam
Copy link

Hi,
Below are 2 extremely useful and important features I think Cucumber is missing today and users would be immensely benifitted :

  1. Ability to configure test execution with "Failure Retry" option - often UI test are flaky and rerunning them reveals the test has passed. This feature would allow retrials of failed scenarios within the execution flow based on the count set for the option.

  2. Out of the box support for context injection. I know this is possible today using other libraries, but would be nice to have one integrated within the Cucumber framework.

Thanks

@mpkorstanje
Copy link
Contributor

mpkorstanje commented Feb 12, 2018

Heya,

  1. This is currently not supported out of the box. And I doubt it will happen unless someone implements it in a PR. However if you are using the JUnit runner, once SUREFIRE-1372 Filter tests to be rerun by description apache/maven-surefire#150 is released you will be able to rerun failed scenarios by using surefires rerun mechanism.

  2. I am a bit confused by this request. While not entirely out of the box dependency injection is provided with cucumber-jvm. The simplest way is by adding cucumber-picocontainer as a dependency. Once you've done that you'll have DI.

@mlvandijk mlvandijk added the ⚡ enhancement Request for new functionality label Feb 13, 2018
@stale
Copy link

stale bot commented Apr 14, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs.

@stale stale bot added the ⌛ stale Will soon be closed by stalebot unless there is activity label Apr 14, 2018
@mpkorstanje
Copy link
Contributor

Lets not wait for that. Surefire has been released.

@lock
Copy link

lock bot commented Apr 14, 2019

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 Apr 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
⌛ stale Will soon be closed by stalebot unless there is activity ⚡ enhancement Request for new functionality
Projects
None yet
Development

No branches or pull requests

3 participants