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.

Sign up for GitHub

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

Jump to bottom

Warning while running tests #64

Open
filbranden opened this issue Jan 8, 2021 · 0 comments
Open

Warning while running tests #64

filbranden opened this issue Jan 8, 2021 · 0 comments

Comments

@filbranden
Copy link

I see this warning when running tests/test_skip_if_exists.py:

$ pytest tests/test_skip_if_exists.py
============================================================================== test session starts ==============================================================================
platform linux -- Python 3.8.6, pytest-4.6.11, py-1.10.0, pluggy-0.13.1
rootdir: ~/devel/jupyter-packaging
plugins: anyio-2.0.2
collected 2 items                                                                                                                                                               

tests/test_skip_if_exists.py ..                                                                                                                                           [100%]

=============================================================================== warnings summary ================================================================================
tests/test_skip_if_exists.py:7
  ~/devel/jupyter-packaging/tests/test_skip_if_exists.py:7: PytestCollectionWarning: cannot collect test class 'TestCommand' because it has a __init__ constructor (from: tests/test_skip_if_exists.py)
    class TestCommand(BaseCommand):

-- Docs: https://docs.pytest.org/en/latest/warnings.html
===================================================================== 2 passed, 1 warnings in 0.09 seconds ======================================================================

Can this be fixed not to produce a warning and finish with a fully clean run?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@filbranden