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_functional_workflow.py vs. test_functional_work_flow.py in tox.ini #155

Open
mtelka opened this issue Jul 25, 2024 · 0 comments · May be fixed by #156
Open

test_functional_workflow.py vs. test_functional_work_flow.py in tox.ini #155

mtelka opened this issue Jul 25, 2024 · 0 comments · May be fixed by #156
Labels

Comments

@mtelka
Copy link

mtelka commented Jul 25, 2024

Describe the bug
I believe there is a typo in the tox.ini file and this should be applied:

--- pytest-xprocess-1.0.2/tox.ini.orig
+++ pytest-xprocess-1.0.2/tox.ini
@@ -20,7 +20,7 @@
     coverage
 commands=
     coverage run -m pytest -v
-    coverage report --omit="*/.tox/*,*/test_functional_workflow.py" --fail-under=90
+    coverage report --omit="*/.tox/*,*/test_functional_work_flow.py" --fail-under=90
 usedevelop = True
 
 [testenv:linting]

To Reproduce
Without the above patch I'm getting this line in the coverage report:

/tmp/pytest-of-marcel/pytest-15/test_functional_work_flow0/test_functional_work_flow.py                                                                18      0   100%

Expected behavior
With the patch above I'm getting this line in the report instead:

test_functional_workflow.py                                                                                                                            10      0   100%

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • OS: OpenIndiana
  • Python Version 3.9.19
  • pytest-xprocess version 1.0.2

Additional context

@mtelka mtelka added the bug label Jul 25, 2024
@mtelka mtelka linked a pull request Nov 11, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant