-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Unit tests won't run #11128
Comments
I have the same problem. It was introduced in 2.38.0 |
It works on my computer 😄 |
For context: #10692 Can you confirm and can we close this issue? |
Yes, I can confirm this, but opened a PR to fix the docs. |
Closing this one as the PR has started getting approvals. |
* fix unittest documentation #11128 * udpate * Update docs/content/en/contributing/how-to-write-a-parser.md Co-authored-by: Charles Neill <[email protected]> * Update docs/content/en/contributing/how-to-write-a-parser.md Co-authored-by: Charles Neill <[email protected]> --------- Co-authored-by: Charles Neill <[email protected]>
Problem description
Attempting to run a unit test for any parser results in the following error:
======================================================================
ERROR: unittests (unittest.loader._FailedTest.unittests)
ImportError: Failed to import test module: unittests
Traceback (most recent call last):
File "/usr/local/lib/python3.11/unittest/loader.py", line 162, in loadTestsFromName
module = import(module_name)
^^^^^^^^^^^^^^^^^^^^^^^
ModuleNotFoundError: No module named 'unittests'
Steps to reproduce
Steps to reproduce the behavior:
The same error occurs when using both of these commands
./dc-unittest.sh --test-case unittests.tools.test__parser.TestParser
docker compose exec uwsgi bash -c 'python manage.py test unittests.tools._parser.TestParser'
This goes for the parser I've written as well as existing unmodified parsers.
Expected behavior
Expected behavior is for the unit test to run.
Deployment method (select with an
X
)Environment information
The text was updated successfully, but these errors were encountered: