In my case the problem with vscode being unable to discover tests was the coverage module being enabled in the setup.cfg (alternatively this could be a pytest .ini), i.e. addopts= –cov -ra which caused the test discovery to fail due to low coverage. The solution was to remove that line from the config file.
# Example 2: have pytest look for files with test and example # content of pytest .ini [ pytest ] python_files = test_*.py example_*.py Note the python_functions and python_classes options has no effect for unittest.TestCase test discovery because pytest delegates discovery of test case methods to unittest code.
This problem will happen if you have a tests.py file and a tests folder with tests/__init__.py.. During the collection pytest finds the folder, but when it tries to import the test files from the folder, tests.py file will cause the import problem. To fix simply remove the tests.py file and put all your tests inside the tests/ folder.. For your specific case the fix will be precisely:, python c:Usersu613766.vscodeextensionsms-python.python-2019.11.49689pythonFilestesting_tools run_adapter.py discover pytest — –rootdir c:Usersu613766SourceReposmetallopy -s –cache-clear Test Discovery failed : SyntaxError: Unexpected end of JSON input, 7/11/2019 · The key problem is that, with pytest .ini in the test root, pytest returns filenames (for both discovery and execution) that are relative to the test root. In all other cases they are relative to the workspace root. However, the extension code makes the assumption that the relative filenames are always relative to the workspace root.
I have this same problem. Adapting the run_adapter.py command above to my use case returns an empty string. The logs in vscode also complain about an empty string stdout: ” – Sebastien Martin Oct 19 ’20 at 16:36, 6/24/2020 · Thanks. That helps. Note that the only thing the python.testing.cwd setting does is set the current working directory for the spawned Python process that will discover /run the tests.–rootdir=. should provide the right value to pytest .
The VS Code Python extension supports unit tests as well as pytest . Here’s how to enable the framework: Open Command Palette (ctrl +shift +P) and start typing ‘python: configure tests.’ It …
Hi there. I would like to ask you for help. I am having issues with Test discovery on my project. I use pytest with configuration in setup.cfg. Pytest (called in terminal) itself works without any issues, but when I try to discover tests or the automatic discovery runs, it fails, see output below. I had the Test discovery working earlier today. Then I tried to install extensions for test …
Configure pytest to test a project directory. 2a. configure python.testing.cwd in settings.json to the project root. Discover tests and observe that all tests are discovered. Run all tests. 4a. Observe the test session starts and all tests pass that do not need to load fixtures from disk. 4b. Observe the output logs look like this:
