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

Detect and list flaky scenarios in the list of not ok scenarios #1159

Merged
merged 1 commit into from
Jul 16, 2017

Conversation

brasmusson
Copy link
Contributor

Summary

Detect and list flaky scenarios in the list of not ok scenarios

Details

  • Detect and list flaky scenarios in the list of not ok scenarios
  • Add a colour definition for flaky results.
  • Also updated the retry feature for the separation of flaky scenarios to a separate category in the scenario counts.

Depends on cucumber/cucumber-ruby-core#141.

Motivation and Context

This is needed to complete the introduction of the flaky result type in cucumber/cucumber-ruby-core#141.

How Has This Been Tested?

The retry feature has been updated to verify this behaviour.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • I've added tests for my code
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

Also updated the retry feature for the separation of flaky scenarios to
a separate category in the scenario counts.
@ghost ghost assigned brasmusson Jul 14, 2017
@brasmusson brasmusson merged commit 7b6302e into master Jul 16, 2017
brasmusson added a commit that referenced this pull request Jul 16, 2017
@brasmusson brasmusson deleted the report-flaky-scenarios branch July 16, 2017 07:12
@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

Successfully merging this pull request may close these issues.

1 participant