[WIP] Tracking deprecations from cucumber testsuit #164
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Author
|
Tested this locally and it doesn't work. cucumber doesn't seem to share same thread with rails application that it runs tests against. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
fixes #163
Adds "track_cucumber" method to gather deprecation's from cucumber testsuit.
Motivation and Context
I'm working on couple of projects that have extensive cucumber testsuits and would like to use it for Deprecation Tracker.
How Has This Been Tested?
Still testing on our own application.. Will update this issue with progress.
Screenshots:
I will abide by the code of conduct