reopen Run Test and Debug execute the code in different working directories

[dnut]

There is already an issue for this but it was closed by mistake and I am unable to reopen it. Several people have replied that the issue was not fixed and yet it remains closed.

#4705

[johannescpk]

Also related: #6661

[d00z3l]

I have struggled with the same issue, I wanted to use a relative path for a source file for my tests and have it work using run/debug in VS Code and also using cargo test --all. My workaround is as follows:

1. Create a local settings.json file, i.e. ./.vscode/settings.json
2. Add the following to the settings file:

{
    "rust-analyzer.runnableEnv": {
        "ENV_ROOT_DIR": "${workspaceFolder}"
    }
}

3. Create a test function create the path:

    pub fn test_data_path() -> String {
        static FILE_PATH : &str = "./tests/my-file-name.csv";
        match std::env::var("ENV_ROOT_DIR") {
            Ok(path) => {
                Path::new(&path).join(FILE_PATH).display().to_string()
            },
            Err(_) => {
                Path::new(&std::env::current_dir().unwrap()).join("../").join(FILE_PATH).display().to_string()
            }
        }
    }

ENV_ROOT_DIR is used in VS Code and the working directory for cargo test

[Marwes]

Also seeing this issue, Run Test seems to correctly execute the test in ./WORKSPACE/PACKAGE whereas Run Debug executes in ./WORKSPACE

[tanveerbadar]

The work-around @d00z3l mentioned works, for the time being until the issue is really fixed.

[kriswuollett]

If test cases are run from same workspace as they are compiled, then for a workaround perhaps using env!("CARGO_MANIFEST_DIR") as the relative directory reference point may be a more direct and stable workaround under refactoring crate location conditions.