Execute the current unittest file not executing all tests

Environment data

VS Code version: 1.31.1
Extension version (available under the Extensions sidebar): 2019.2.5416
OS and version: W10 Enterprise 10.0.17134
Python version (& distribution if applicable, e.g. Anaconda): 3.6
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: Extension

Expected behaviour

Run all unittests on file

Actual behaviour

Runs only the first unittest.

Steps to reproduce:

Create an unittest class. (class Class(unittest.TestCase):)
Add a method to test.
Add another method to test.
Click right mouse button.
Click "Execute the current unittest file" (Translated from Portuguese, not sure if it's exactly how it shows.
Just the first test will execute, ignoring all others.

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

test_instancia (test.test_api_infobip.InfobipTestCase) ... ok

----------------------------------------------------------------------
Ran 1 test in 0.001s

OK

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

[Extension Host] Python Extension: Cached data exists getEnvironmentVariables, c:\Programas\servicosmsf_v2
console.ts:134 [Extension Host] Python Extension: Cached data exists ActivatedEnvironmentVariables, c:\Programas\servicosmsf_v2
console.ts:134 [Extension Host] Python Extension: getActivatedEnvironmentVariables, Class name = b, Arg 1: <Uri:c:\Programas\servicosmsf_v2>, Arg 2: undefined
console.ts:134 [Extension Host] Python Extension: Cached data exists getEnvironmentVariables, c:\Programas\servicosmsf_v2
console.ts:134 [Extension Host] Python Extension: Cached data exists getEnvironmentVariables, extension-output-#5

+1 - I ran into this as well.

From the Test Side Bar, running tests from the .py file will only run the first test (which I assume the "Python: Run Current Unit Test File" does.

Running tests at the class level will execute all tests in the class.

Hope this helps.

Damon Allison (@damonallison)

Damon Allison (@damonallison)

Please could you provide some sample code we can use to repro the issues at our end?
Thanks

Don Jayamanne (@DonJayamanne)

Don Jayamanne (@DonJayamanne)

You bet - run the tests in this repo. https://github.com/damonallison/python-examples

The screenshots I posted were from this repo, so they should look familiar. Let me know if you're not able to repro it. Thanks!

Awesome, I can replicate this at my end, thanks.

Add news entry for microsoft#4567

I've run at this issue as well. I've created a file test_add.py with the following tests

import unittest


class AddTests(unittest.TestCase):
    def test_two_plus_one_is_three(self):
        self.assertEqual(3, 2 + 1)

    def test_two_plus_two_is_five(self):
        self.assertEqual(5, 2 + 2)

    def test_two_plus_zero_is_two(self):
        self.assertEqual(2, 2 + 0)

And in the logs I can see that command line specifies the test to run.

> C:\Python27\python.exe c:\Users\<###>\.vscode\extensions\ms-python.python-2019.9.34911\pythonFiles\visualstudio_py_testlauncher.py --us=. --up=*test*.py --uvInt=2 --result-port=53405 -ttest_add.AddTests.test_two_plus_one_is_three --testFile=<###>\sample\test_add.py
cwd: <###>\sample
> C:\Python27\python.exe c:\Users\<###>\.vscode\extensions\ms-python.python-2019.9.34911\pythonFiles\visualstudio_py_testlauncher.py --us=. --up=*test*.py --uvInt=2 --result-port=53405 -ttest_add.AddTests.test_two_plus_one_is_three --testFile=<###>\sample\test_add.py
cwd: <###>\sample

By the log it looks like the file node has an incorrect nameToRun value, so I've modified TestsParser for unittest. Please see PR #7783.

N Kondratyev (@kondratyev-nv)

N Kondratyev (@kondratyev-nv), FYI I plan on taking a look at your PR in the next few days.

Thank you! I look forward to it.

Fix the "nameToRun" for test files in unittest results. (#7783)

N Kondratyev (@kondratyev-nv)

Validated, thanks again N Kondratyev (@kondratyev-nv)

Luciana Abud (@luabud)

Luciana Abud (@luabud), happy now? 😁️

Navigation Menu

Repository navigation

Execute the current unittest file not executing all tests #4567

Environment data

Expected behaviour

Actual behaviour

Steps to reproduce:

Logs

4 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Execute the current unittest file not executing all tests #4567

Description

Environment data

Expected behaviour

Actual behaviour

Steps to reproduce:

Logs

Activity

damonallison commented on Apr 12, 2019

DonJayamanne commented on Apr 17, 2019

damonallison commented on Apr 19, 2019

DonJayamanne commented on Apr 22, 2019

kondratyev-nv commented on Oct 5, 2019

4 remaining items

ericsnowcurrently commented on Oct 21, 2019

kondratyev-nv commented on Oct 22, 2019

karrtikr commented on Nov 7, 2019

ericsnowcurrently commented on Nov 8, 2019

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions