Custom `rust-analyzer.runnables.test.overrideCommand` breaks `Debug` runnable button

[DavisVaughan]

With #21137 (comment) I now have the following setup:

    // `Run Test` and `Run Tests` nextest support
    "rust-analyzer.runnables.test.overrideCommand": [
        "cargo",
        "nextest",
        "run",
        "--package",
        "${package}",
        "${target_arg}",
        "${target}",
        "--",
        "${test_name}",
        "${exact}",
        "${include_ignored}"
    ],

This seems to break the Debug runnables button

Are they meant to be connected in this manner?

test2.mov

[ChayimFriedman2]

True, we don't support debugging non-Cargo runnables. We probably should disable the Debug len.

[DavisVaughan]

So I guess these ideas aren't fully independent?

• Using nextest as the way I run tests
• Using cargo (?) as the backend for debugging

Like, ideally I'd be able to use nextest for Run Tests in particular, because we really need its "1 test per process" guarantee, while also just using whatever the standard machinery is for single test debugging. But it sounds like that probably isn't possible, maybe because I'm essentially "requesting" that nextest be used to generate all test binaries, and you need those for debugging but don't know how to find/request the ones nextest makes?

[ChayimFriedman2]

Not every custom command even has a matching Cargo test, but we probably can have a setting for where it does.