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

Python "Debug Unit Test" launch configuration in settings.json ignored #14388

Closed
artificial-aidan opened this issue Oct 13, 2020 · 3 comments
Closed
Assignees
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug needs proposal Need to make some design decisions verified Verification succeeded
Milestone

Comments

@artificial-aidan
Copy link

Environment data

  • VS Code version: 1.50.0-insider
  • Extension version (available under the Extensions sidebar): v2020.9.114305
  • OS and version: OSX 10.15.6
  • Python version (& distribution if applicable, e.g. Anaconda): 3.8.5
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pyenv
  • Value of the python.languageServer setting: Pylance

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]

Expected behaviour

Not sure if this belongs here, or if there is a separate place to log test issues.

When I set up a Debug Unit Test configuration in settings.json then it should be used by default when running python unit tests.

Example settings.json

    "launch": {
        "version": "0.2.0",
        "configurations": [
            {
                "name": "Debug Unit Test",
                "type": "python",
                "request": "test",
                "justMyCode": false,
            }
        ]
    }

Actual behaviour

The justMyCode: false setting is ignored from the main settings.json. Instead I have to add individual Debug Unit Test configurations to every project that needs it.

@artificial-aidan artificial-aidan added triage-needed Needs assignment to the proper sub-team bug Issue identified by VS Code Team member as probable bug labels Oct 13, 2020
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Oct 13, 2020
@kimadeline
Copy link

Hi @artificial-aidan, thank you for reaching out.

As you pointed out, we don't support launch configurations defined outside of launch.json at the moment. We need to find a way to retrieve all launch configs irrespective of location.

@kimadeline kimadeline added area-debugging needs proposal Need to make some design decisions and removed triage labels Oct 13, 2020
@kimadeline kimadeline assigned luabud and unassigned kimadeline Oct 13, 2020
@karrtikr
Copy link

Is still an issue with #15790?

@kimadeline
Copy link

Yes, since we've revamped the testing implementation this is a duplicate of microsoft/vscode-python-debugger#525. @MetRonnie @teichert and @artificial-aidan feel free to upvote microsoft/vscode-python-debugger#525 as well.

@karrtikr karrtikr added this to the October 2021 milestone Oct 25, 2021
@karrtikr karrtikr added the verified Verification succeeded label Oct 25, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug needs proposal Need to make some design decisions verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

6 participants