Debugging unit tests hangs indefinitely

[veuncent]

Environment data

• VS Code version: 1.21.0 x64
• Extension version (available under the Extensions sidebar): Python 2018.2.1
• OS and version: Windows 10
• Python version: 2.7.14

Actual behavior

When clicking Debug Test nothing happens, except showing the Running Tests throbber at the bottom of the window indefinitely.

Expected behavior

Debugging line-by-line using breakpoints.

Steps to reproduce:

1. I set up a minimal repo to reproduce this: https://github.com/veuncent/vsc-debug-test
2. Open the folder in VSC
3. Open the test.py file
4. Click Debug Test above the testSomeService function

Logs

Output of Python Test Log at startup of VSC: Output 1.txt

No output is given when using the Debug Test text button above the testSomeFunction function.

Output after running a unit test using the Run Test button above the testSomeFunction function:

----------------------------------------------------------------------
Ran 1 test in 0.019s

OK

[DonJayamanne]

You haven't configured the unit tests in VS Code (see here https://code.visualstudio.com/docs/python/unit-testing)

Another way to do this is

• Delete your settings.json file
• Go into your command palette Python: Run All Unit Tests
• Follow the prompts (select nose and select . as the directory containing the tests`

I've tested your repo at my end and it works.

[veuncent]

I did exactly as you asked and the problem is still there, unfortunately.
Is there any other information I can give you?

By the way: my Python VSC extension was updated yesterday to 2018.2.1, but nothing changed regarding this bug.

[DonJayamanne]

Please could you send your launch.json so I could have a look at that.

[veuncent]

I use the launch.json in the git repo:
https://github.com/veuncent/vsc-debug-test/blob/master/.vscode/launch.json

That's the default one created by vsc

[DonJayamanne]

You might want to check the docs https://code.visualstudio.com/docs/python/unit-testing

First, go into the command palette and select Run All Unittests, configure the test framework and use the code lense to debug a test or check it the documentation.

You cannot debug unit tests via debug configuration in launch.json unless you configure everything manually (the code lenses make it much simpler).

Between line 5 & 6 you'll find the code lense Debug Test, click on that (look at the screenshot you have attached).

[veuncent]

I did exactly that what you describe :) And I do not debug via the debug configuration in launch.json.
Here is what I did:

• From the command palette I ran Run all Unittests
• I clicked Enable and configure a Test Framework (see screenshot)
• Selected Nose from the dropdown menu
• Selected . Root directory from the dropdown menu

This results in the creation of this settings,json:

{
    "python.unitTest.nosetestArgs": [
        "."
    ],
    "python.unitTest.nosetestsEnabled": true
}

(I just pushed that settings file to the repo here)

Subsequently the unit tests are discovered and the Code Lens buttons (Run Test | Debug Test) appear above my class and method.

When I click any of the Run Test code lens buttons the test runs fine and Python Test Log gives expected output (Ran 2 tests in 0.003s).

However, when I click any of the Debug Test code lens buttons, nothing happens, except for the Running Tests text appearing in the bottom of the screen:

[veuncent]

P.s. I also tried:

• Reinstalling VSC including the Python extension
• Setting up from scratch, choosing unittest instead of nose

To no avail.

[jitbasemartin]

Same issue here, but I use py.test
Windows 10 64bit, Python 2.7.14, pytest-3.4.2, py-1.5.2, pluggy-0.6.0

[DonJayamanne]

@veuncent @moimart1
Please could you install the latest development version of the extension from here and test this out once again.

[jitbasemartin]

Yeah it works for me with pytest :)
Thanks @DonJayamanne !

[veuncent]

Works for me as well, thanks @DonJayamanne !

…

On Wed, Mar 21, 2018 at 2:50 PM, Martin ***@***.***> wrote: Yeah it works for me with pytest :) Thanks @DonJayamanne <https://github.com/donjayamanne> ! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1009 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHhxWwB08N3ZVOdE00v5s__ypcXQG_qjks5tglqugaJpZM4Skqjv> .

[DonJayamanne]

Reopening to create news entry