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

Test Case is missing in report when It failed because of pytest worker crash #825

Open
2 tasks
chandra0714 opened this issue Jul 19, 2024 · 1 comment
Open
2 tasks

Comments

@chandra0714
Copy link

I'm submitting a ...

  • [✓] bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

In my Jenkins CI, we run Selenium automation using pytest with a Selenium Grid. Sometimes, the pytest worker crashes, causing the test case to fail with the status “FAILED”. When a test case fails due to a pytest worker crash, the failed test case is missing from the report

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

Python Code to reproduce the Issue:

import os

def test_simulate_crash():
if os.environ.get("PYTEST_XDIST_WORKER", None):
os._exit(1) # This will crash the worker process
assert True

def test_normal():
assert True

pytest-worker-crash-console-logs
pytest-worker-crash-allure-report
pytest-worker-crash-html-report

What is the expected behaviour?

The Failed Test Case ('test_simulate_crash' in the above code) should be shown in the allure report.

For reference, I attached the HTML report where we could see the Failed Test Cases.

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

  • Allure version: 2.29.0
  • Test framework: Python 3.9.6
  • Allure adaptor: allure-pytest-2.8.40

Other information

Related ticket for pytest worker crash
pytest-dev/pytest-xdist#466

@chandra0714
Copy link
Author

@delatrie

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

No branches or pull requests

1 participant