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

pytest results doesn't shows in Test Explorer #7285

Closed
rmerkushin opened this issue Sep 8, 2019 · 4 comments
Closed

pytest results doesn't shows in Test Explorer #7285

rmerkushin opened this issue Sep 8, 2019 · 4 comments
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@rmerkushin
Copy link

Environment data

  • VS Code version: 1.38
  • Extension version (available under the Extensions sidebar): 2019.9.34911
  • OS and version: Windows 10 1903 x64
  • Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.4
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
  • Relevant/affected Python packages and their versions: XXX
  • Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info How to update the language server to the latest stable version #3977): Language Server

Expected behaviour

Shows passed tests in Test Explorer sidebar

Actual behaviour

Doesn't Show passed tests in Test Explorer sidebar

Steps to reproduce:

  1. Configure pytest.ini:
    [pytest]
    addopts = -n=5 --reruns=2 --driver=Remote --variables=capabilities.json
  2. Run test in Test Explorer

Logs

Output:

python c:\Users\rmerkushin\.vscode\extensions\ms-python.python-2019.9.34911\pythonFiles\testing_tools\run_adapter.py discover pytest -- -s --cache-clear .
python c:\Users\rmerkushin\.vscode\extensions\ms-python.python-2019.9.34911\pythonFiles\testing_tools\run_adapter.py discover pytest -- -s --cache-clear
============================= test session starts =============================
platform win32 -- Python 3.7.4, pytest-5.1.2, py-1.8.0, pluggy-0.12.0
driver: Remote
sensitiveurl: .*
rootdir: c:\Workspace\Test, inifile: pytest.ini
plugins: allure-pytest-2.8.2, base-url-1.4.1, forked-1.0.2, html-1.22.0, metadata-1.8.0, rerunfailures-7.0, selenium-1.17.0, variables-1.7.1, xdist-1.29.0
gw0 I / gw1 I / gw2 I / gw3 I / gw4 I
gw0 [5] / gw1 [5] / gw2 [5] / gw3 [5] / gw4 [5]

.....                                                                    [100%]
- generated xml file: C:\Users\RMERKU~1\AppData\Local\Temp\tmp-25332Snd65oYNrrUG.xml -
============================= 5 passed in 11.68s ==============================
Error: TypeError: Cannot read property '$' of undefined

P.S.

File with tests is placed in root of project directory with pytest.ini

VSCode:
vscode

Terminal:
terminal

@rmerkushin rmerkushin added triage-needed Needs assignment to the proper sub-team bug Issue identified by VS Code Team member as probable bug labels Sep 8, 2019
@Almenon
Copy link

Almenon commented Sep 8, 2019

I got the same error when running against jsonpickle/jsonpickle@350d16a with python 3.6.8, pytest 5.1.0, and pytest-cov 2.6.1 on windows 10 vscode 1.38

python ext info:

Name: Python
Id: ms-python.python
Description: Linting, Debugging (multi-threaded, remote), Intellisense, code formatting, refactoring, unit tests, snippets, and more.
Version: 2019.9.34911
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-python.python

@Almenon
Copy link

Almenon commented Sep 8, 2019

actually this appears to be a duplicate of #6990

@bladane
Copy link

bladane commented Sep 9, 2019

Exactly the same error (no representation of results in Test Explorer) in my setup with addition of following error.
Error: TypeError: Cannot read property '$' of undefined

@luabud
Copy link
Member

luabud commented Sep 9, 2019

Thanks for taking the time to report this, I'm closing since it is a duplicate of #6990.

@luabud luabud closed this as completed Sep 9, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Sep 9, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Sep 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

4 participants