-
Notifications
You must be signed in to change notification settings - Fork 221
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
Fix gherkin terminal report colouring #372
base: master
Are you sure you want to change the base?
Fix gherkin terminal report colouring #372
Conversation
aeca959
to
e6bfb7e
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #372 +/- ##
==========================================
+ Coverage 95.40% 95.47% +0.06%
==========================================
Files 49 49
Lines 1764 1789 +25
Branches 193 196 +3
==========================================
+ Hits 1683 1708 +25
Misses 53 53
Partials 28 28
☔ View full report in Codecov by Sentry. |
e60130e
to
a050720
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
any update on this, please. |
Merge, please? |
@hristiy4n Could you rebase your code and submit it again ? I'd love to have this feature. |
- the skipped parameter can be used to track which steps have been skipped and adjust the behaviour appropriatelly (ex. change the output colour to yellow)
- the hook and the pluging work in a similar way to the fail hook and plugin where they set a flag wether the step is skipped or not
- trigger the skip hook if a step is skipped
- use the output of the individual steps to decide the output colour
- the PR proposes to expand the step with an additional skipped bool, to track weather the step has been skipped or not, therefor the expected behaviour of the steps in the tests should be modified
- when a step is skipped the step should have skipped set to True
a050720
to
6eca0a3
Compare
for more information, see https://pre-commit.ci
I rebased the MR, lets hope it gets merged this time. |
@youtux Could you please review this ? I'd like to avoid it to fall back into oblivion. |
@hristiy4n Could you ask for another reviewer ? |
I re-requested the review from @olegpidsadnyi. I do not think I have the permissions to request a review from someone else. |
@olegpidsadnyi @youtux Sorry for the brute forcing, but could you please review this please ? |
I looked into the cucumber spec, I don't see any magic tag that skips the scenario from the scenario definition itself. So the cucumber is deselecting them from the command line by negating the tags. It could be any tag. |
Add a extra hook to mark steps as skipped, which will allow to distinguish if a step is skipped or not and therefor the output colouring could be done properly.
This PR closes #214 #299 #248