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

DRAFT: pytest discovery #265

Closed
wants to merge 3 commits into from
Closed

Conversation

cclauss
Copy link
Contributor

@cclauss cclauss commented Jul 2, 2024

https://docs.pytest.org/en/stable/explanation/goodpractices.html#conventions-for-python-test-discovery

git mv pylib/gyp/generator/msvs_test.py \
       pylib/gyp/generator/test_msvs.py && \
git mv pylib/gyp/generator/ninja_test.py \
       pylib/gyp/generator/test_ninja.py && \
git mv pylib/gyp/generator/xcode_test.py \
       pylib/gyp/generator/test_xcode.py && \
git mv pylib/gyp/MSVSSettings_test.py \
       pylib/gyp/test_MSVSSettings.py && \
git mv pylib/gyp/common_test.py \
       pylib/gyp/test_common.py && \
git mv pylib/gyp/easy_xml_test.py \
       pylib/gyp/test_easy_xml.py && \
git mv pylib/gyp/input_test.py \
       pylib/gyp/test_input.py && \
git mv pylib/gyp/xcode_emulation_test.py \
       pylib/gyp/test_xcode_emulation.py

@cclauss cclauss requested a review from legendecas July 2, 2024 11:10
@legendecas
Copy link
Member

I think the doc says the test files can either be prefixed by test or be suffixed like test_*.py and *_test.py?

@cclauss
Copy link
Contributor Author

cclauss commented Jul 3, 2024

Agreed. Closing.

All their examples prepend test_ which is what I always see but both are allowed.

@cclauss cclauss closed this Jul 3, 2024
@cclauss cclauss deleted the pytest-discovery branch July 3, 2024 05:00
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.

2 participants