VSCode "Debug" test cwd is workspace root, not package root for tests

[Crzyrndm]

Setup: https://github.com/Crzyrndm/ra-executing-directory

A package nested in a workspace, the tests (unit + integration) just print std::env::current_dir() and then panic (so that the print is always visible)

• cargo test --no-fail-fast: prints the package root directory for both unit and integration no matter what directory it is run in
• VSCode "Run test" button: prints the package root directory
• VSCode "Debug" button: prints the workspace root directory

This makes debugging tests that need to load a data file quite awkward

rust-analyzer version: rust-lang.rust-analyzer 0.3.1170 (current stable)

rustc version: rustc 1.63.0 (4b91a6ea7 2022-08-08)

Tested OS is Windows 10

relevant settings:

[Crzyrndm]

Disclaimer: I have never used JS/TS so take the following as you will

From what I can tell, the Debug executing directory is set here and is unconditionally the workspace/open folder root directory.

After some changes to the example repo and looking through cargo source:

• Examples and bins are not localised (or more completely, cargo run doesn't modify cwd)
• tests (and likely #[bench]) are localised to the package

The target appears to be known in the same scope although I don't know if that's package/folder/something else at this point. Presumably whether it's a run/test(/example/benchmark) or not can be obtained from this

E: Tests and benchmarks are definitely run the same way by cargo. This appears to be where the cmd is built for both.

[esiegel]

In addition it doesn't include any of the cargo environment variables that could be used to help normalize a path. For example, CARGO_MANIFEST_DIR is missing