Testing extension - how can I get the link to work for non-standard workspace folder?

[thclark]

HI,

So I have specified my workspace folder to a non-default value. Instead of /workspaces/project-name/ it's now just /workspace.

I do this so I'm able to pre-install a bunch of stuff and settings in one base devcontainer that's common to all my organisation's projects.

How to reproduce

In .devcontainer/Dockerfile:

FROM one-of-the-ms-python-base-images
WORKDIR /workspace

In devcontainer.json:

{
  // + all the other stuff
  "workspaceFolder": "/workspace",
  "workspaceMount": "source=${localWorkspaceFolder},target=/workspace,type=bind",
  "settings": {
    // + all the other settings
    "python.testing.cwd": "/workspace", // I've tried with and without this
  },
}

What happens

The tests run absolutely fine, but the link to 'Go to code' doesn't work.

It keeps pointing to the original (default) workspace folder and doesn't seem to pick up the changed value. Obviously the test file can't be found, because it's not at that location.

I have tried

• restarting vscode
• deleting pytest_cache
• deleting test results
• rebuilding the container
  • both with and without python.testing.cwd set
• checking for any overriding options in eg pytest.ini
• checking and re-checked settings
• adding a pytest.ini file with overridden testpaths entry

Does anyone know how to solve this, please?

[brettcannon]

Could this be the same issue as #11669 ?

[thclark]

I don't believe so. That issue is a bit vague and doesn't really get to the point, but addressing the various things that are suspected over there:

• mine is on a unix machine (well, mac, in a Debian based devcontainer), not windows
• I've specified an absolute, not a relative pathway
• I've attempted to both rebuild the container and restart the window to activate the setting

Also, the tests show up in the test explorer and run just fine, so I actually don't think it's to do with this setting at all to be honest (I was just wildly trying things)

[eleanorjboyd]

Hello! Apologies for the delay- I am currently looking into the issue and will get back to you with a possible solution or if I need more information. Thanks!