pytest 5.1.0 seems to break the test adapter
See original GitHub issueIssue Type: Bug
After updating VSCode from v1.36.1 to v1.37.1 (in WSL), pytest unit tests are no longer displaying green/red status in the side bar. An error pop-up is displayed with the following message:
There was an error in running the tests. Source Python (Extension)
The OUTPUT tab indicates that the test passed, but there is also an error message that seems like it is related to the extension issue:
============================= test session starts ==============================
platform linux -- Python 3.6.8, pytest-5.1.0, py-1.8.0, pluggy-0.12.0
rootdir: /mnt/c/Users/.../
plugins: cov-2.7.1
collected 1 item
tests/test___init__.py . [100%]
-------------- generated xml file: /tmp/tmp-2499XLU6ay233ncl.xml ---------------
============================== 1 passed in 0.06s ===============================
Error: TypeError: Cannot read property '$' of undefined
Extension version: 2019.8.30787 VS Code version: Code 1.37.1 (f06011ac164ae4dc8e753a3fe7f9549844d15e35, 2019-08-15T16:17:55.855Z) OS version: Windows_NT x64 10.0.17134 Remote OS version: Linux x64 4.4.0-17134-Microsoft
System Info
Item | Value |
---|---|
CPUs | Intel® Xeon® CPU X5650 @ 2.67GHz (12 x 3800) |
GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: enabled skia_deferred_display_list: disabled_off skia_renderer: disabled_off surface_synchronization: enabled_on video_decode: enabled viz_display_compositor: disabled_off webgl: enabled webgl2: enabled |
Load (avg) | undefined |
Memory (System) | 24.00GB (14.93GB free) |
Process Argv | –folder-uri=vscode-remote://wsl+default/mnt/c/Users/…/ --remote=wsl+default |
Screen Reader | no |
VM | 50% |
Item | Value |
---|---|
Remote | WSL |
OS | Linux x64 4.4.0-17134-Microsoft |
CPUs | Intel® Xeon® CPU X5650 @ 2.67GHz (12 x 3800) |
Memory (System) | 24.00GB (14.93GB free) |
VM | 50% |
Issue Analytics
- State:
- Created 4 years ago
- Reactions:55
- Comments:14 (1 by maintainers)
Top Results From Across the Web
pytest Documentation - Read the Docs
The first test passed and the second failed. You can easily see the intermediate values in the assertion to help you under-.
Read more >In latest visual studio code 1.37.1 and the latest pytest==5.1.1 ...
The problem seems to be with pytest version 5.1.0. Until the problem is fixed well have to resort to using an older version...
Read more >Adapter V4 Release Notes - NUnit Docs
NUnit3 Test Adapter for Visual Studio - Version 4.3.1 - Nov 19, 2022. This is a hotfix release for three major and critical...
Read more >Changelog — pytest documentation
<patch> ). Backward incompatible (breaking) changes will only be introduced in major versions with advance notice in the Deprecations section of releases.
Read more >What's New | Oracle, Software. Hardware. Complete.
Packages Released on Oracle Linux Yum Server · tmt-1.20.0-1.el8 - Test Management Tool (Update) · pulseaudio-qt-1.3-2.el8 - Qt bindings for PulseAudio (New) ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@krazyace78, thanks for letting us know about this. It looks like pytest 5.1.0 changed something in their XML output. We’ll get this fixed as soon as we can.
Upon further examination, the output between 5.1.0 and 5.0.1 seems to be the same, so I do not know why this would trigger an error, but I know that downgrading to 5.0.1 fixed it for me.