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

Testing folder tree. #17281

Closed
yuanzhe-tian opened this issue Sep 3, 2021 · 8 comments · Fixed by #17306
Closed

Testing folder tree. #17281

yuanzhe-tian opened this issue Sep 3, 2021 · 8 comments · Fixed by #17306
Assignees
Labels
area-testing bug Issue identified by VS Code Team member as probable bug regression Bug didn't exist in a previous release

Comments

@yuanzhe-tian
Copy link

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.60.0
  • OS Version: windows

Steps to Reproduce:

1.click Testing
2.expend folder tree
3.all of child folder is root folder name, and those root folder can be expend.

update 2021-09-04
this is my setting.json on project root.

  "python.testing.pytestArgs": [
    "vulman-api", "vulman-core"
  ],
  "python.testing.pytestEnabled": true,

my project dir begin with workspace, and vulman-api, vulman-core within workspace.
when i check testing, i found my testing directory tree only has workspace, and click workspace still workspace.
When I click on the front arrow, Will be displayed vulman-core, but it was replaced workspace immediately.

like this

  • workspace
    • workspace
      • workspace
        • workspace

my project:

  • workspace
    • vulman-core
      • test
    • vulman-api
      • api_test
@connor4312 connor4312 assigned karthiknadig and unassigned connor4312 Sep 4, 2021
@karthiknadig karthiknadig transferred this issue from microsoft/vscode Sep 4, 2021
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Sep 4, 2021
@karthiknadig
Copy link
Member

@YuanzheTian Can you provide your workspace settings and if possible can you provide a minimal repro for this?

@yuanzhe-tian
Copy link
Author

yuanzhe-tian commented Sep 4, 2021

@YuanzheTian Can you provide your workspace settings and if possible can you provide a minimal repro for this?
this is my setting.json
{
"python.pythonPath": "/home/workspace/py3/bin/python",
"python.testing.pytestArgs": [
"vulman-api", "vulman-core"
],
"python.testing.pytestEnabled": true,
"python.testing.unittestEnabled": false,
"python.formatting.provider": "autopep8",
"terminal.integrated.env.linux": {
"PYTHONPATH": "",
"ENV_PATH": "terminal"
},
"gitlens.advanced.messages": {
"suppressGitVersionWarning": true
},
"workbench.editorAssociations": {
"*.ipynb": "jupyter-notebook"
},
"git.ignoreLegacyWarning": true,
}

this is my project dir tree.
my test file in red box.
f764a927471f7259c7c243091f8dd2b
this is dir tree where his bug.
a68de19ee153ea78b99afd4f8c98e3e

@yuanzhe-tian
Copy link
Author

@YuanzheTian Can you provide your workspace settings and if possible can you provide a minimal repro for this?

when id click Arrow on the left, it will show vulman-core with me, and this is correct result. but it changed to workspace as soon,
like parent dir:
fa1a5b3d9da51c187669e549b6a9d1b

but i found an strange phenomenon, when i click view as list, it will be get currect result, and change back vul as tree, is can be work.
9dd6a250ba2ef28d5eda2214f79e3d7
c3f336883c0e3dbd8dce1b053c0d276
284343be5972250d2c7fd8e7f8640fe

That's what I wanted, except all of parent dir workspace. But do it this way, i cannot refresh test, and remote conncet will be disconncet as soon.., i dont know is it going to help me solve my problem..

Is there any more information I need to provide? Such as log

@karthiknadig
Copy link
Member

@YuanzheTian Thanks for the details, I am able to repro the issue.

@yuanzhe-tian
Copy link
Author

is this a bug? Will this be fixed in the next release?

@karthiknadig karthiknadig added area-testing needs PR regression Bug didn't exist in a previous release bug Issue identified by VS Code Team member as probable bug and removed triage-needed Needs assignment to the proper sub-team labels Sep 7, 2021
@karthiknadig
Copy link
Member

Yes, this is a bug. We marked it as "needs PR" indicating that it is ready to be worked on.

@ievgennaida
Copy link

Right click to debug is also affected!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-testing bug Issue identified by VS Code Team member as probable bug regression Bug didn't exist in a previous release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants
@connor4312 @karthiknadig @ievgennaida @yuanzhe-tian and others