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

Cucumber JSON report is generated without skipped tests info #567

Open
waad19 opened this issue Oct 20, 2022 · 1 comment · May be fixed by #729
Open

Cucumber JSON report is generated without skipped tests info #567

waad19 opened this issue Oct 20, 2022 · 1 comment · May be fixed by #729

Comments

@waad19
Copy link

waad19 commented Oct 20, 2022

Environment:
platform darwin -- Python 3.9.12, pytest-7.1.2, pluggy-1.0.0
plugins: splinter-3.3.2, bdd-6.0.1, clarity-1.0.1

Steps to reproduce:

  1. Create simple pytest-bdd setup with feature file and tests.
  2. In feature file and default @Skip flag like this:
    @skip
    Scenario: Test1
    When blabla
    Then blablabla
    Or any other way to skip test execution
  3. Run pytest with addopts = -vv -rsfx --cucumber-json=cucumber_report.json --gherkin-terminal-reporter --color=yes in pytest.ini or same alternative in CLI
  4. Gherkin terminal output will contain test_bla.py::test_bla <- venv/lib/python3.9/site-packages/pytest_bdd/scenario.py SKIPPED (unconditional skip)

Actual result:
5. cucumber.json file doesn't contain any info about skipped test at all

Expected result:
5. cucumber.json file contains info about skipped test (at least ..."result": {"status": "skipped"... )

@janluak janluak linked a pull request Oct 25, 2024 that will close this issue
@janluak
Copy link

janluak commented Oct 25, 2024

Hi @waad19,

it seems it took a while - I just opened a PR which fixes at least if skipping a scenario. If the full feature is skipped it's not covered by my fix. Yet, hope to deliver that sometime soon as well ;)

Best,
janluak

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 a pull request may close this issue.

2 participants