Cucumber7compatibility #457
Open
Conversation
This file contains 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
filippor
force-pushed
the
cucumber7compatibility
branch
from
8f7f196
to
79ad436
Compare
|
@filippor Just wanted to note: there is no immediate need to support both cucumber 6+7, we can simply support cucumber 7 from now on at 3.x and use 2.x for cucumber 6! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🤔 What's changed?
Use dto to transfer messages from running execution and plugin
createe different plugin for cxucumber v6 and cucumber v7
⚡️ What's your motivation?
make compatible with cucumber 7
🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
find a way to select the right plugin
check the behavior
📋 Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.