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

[SDTEST-481] Skip Before/After hooks in cucumber when scenario is skipped by intelligent test runner #211

Merged
merged 2 commits into from
Jul 31, 2024

Conversation

anmarchenko
Copy link
Contributor

What does this PR do?
Improves test skipping by intelligent test runner: if we bail out of test execution early we save more time by skipping before/after hooks that could be expensive

Motivation
I noticed that intelligent test runner does not skip test hooks in cucumber which reduces time saved by skipping tests

How to test the change?
Unit test is adapted to reflect the new behaviour

@anmarchenko anmarchenko requested review from a team as code owners July 31, 2024 11:11
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.84%. Comparing base (0e24d28) to head (507b4e8).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #211      +/-   ##
==========================================
- Coverage   98.84%   98.84%   -0.01%     
==========================================
  Files         254      253       -1     
  Lines       11638    11630       -8     
  Branches      522      521       -1     
==========================================
- Hits        11504    11496       -8     
  Misses        134      134              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@anmarchenko anmarchenko merged commit f00caf6 into main Jul 31, 2024
28 checks passed
@anmarchenko anmarchenko deleted the anmarchenko/cucumber_better_test_skipping branch July 31, 2024 11:37
@github-actions github-actions bot added this to the 1.4.0 milestone Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants