Option to disable "run test | debug test" links

[telamonian]

I'm having the same issue as this guy from a while back on vscode-go, but with the Python extension:

Hi,

just a minor nit -- is there any way to disable these two links?

When writing tests, these lines show up when the code is OK, but they disappear every time there's a syntax error - effectively every time I save a _test.go file that doesn't compile.

The showing up / hiding causes the code to jump up and down and it gets too much of my attention and slows me down.

The code jumping up and down while I type kind of makes me seasick. Is there any way to disable just this one codelens for Python tests (or tests in general, for that matter)? There's always:

"editor.codeLens": false

but that disables all code lenses everywhere, which is less than ideal.

[brettcannon]

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.

[jpangburn]

I came here to file this same bug, but searched first and found this. Fairly annoying when you have more than 2-3 tests because the code at the bottom jumps by the number of tests plus the number of classes. So if you have one class with 15 tests, it'll jump by 16 lines every time these things appear/disappear.

Maybe some would argue that the source class should be simplified for less tests or something, but I don't think 15 tests is unreasonable.

I'd prefer to keep these codelens adornments, as they're kind of useful, if there's a way to stop this jumping behavior while coding tests. But if the choice is have them disabled entirely (e.g. "python.testing.codeLens" or something) or use the setting to disable all codelens in the project (using editor.codeLens), I'd happily disable just these python unittest codelens adornments if the feature was available.

[frediy]

I also came here looking for a way to turn off the lens. I run tests for most projects in the terminal in a docker environment, so the lens is just taking up space. It would be useful to have an option to hide it.

[luabud]

We can add a setting called "python.testing.codeLensesEnabled" that can be true by default, but will have code lenses disabled if set to false.
I think it may make sense to have it in the User scope only, but I don't think it'd be bad to have it in the Workspace scope either.

[jpangburn]

@luabud I guess that means it's difficult to make it stop jumping around so we can keep them?

Assuming that's the case, I'd agree with the User scope thing because this seems to pretty clearly be a personal preference rather than related to a specific project. Although I can't imagine who isn't bothered by the text jumping around as you edit more than 3-4 tests.

[pachecoke]

@luabud I guess that means it's difficult to make it stop jumping around so we can keep them?

Assuming that's the case, I'd agree with the User scope thing because this seems to pretty clearly be a personal preference rather than related to a specific project. Although I can't imagine who isn't bothered by the text jumping around as you edit more than 3-4 tests.

I just wanted to echo this. I don't mind having the adornments/code lens there, it's the code bobbing up and down that could use a fix.

[jdunns]

Perhaps another idea would be to put the adornment in-line with the function declaration. Either to the left or the right of the text. Having it take up a brand new line seems to be part of the issue.

Thanks!

[AAraKKe]

I just want to +1 this. I am teaching python and decided to use VSCode because it is very simple to install and use and works for many languages but working with tests is frustrating because students cannot follow what I do due to all these jumps. I have to disable code lenses but it is not ideal.

I am not sure how PyCharm does it, but in there you get a play button to the left of the tests that does not move ever, it does not even matter if pytest, unittests or whatever testing frame you use can discover the tests. They are just recognized. No matter what. If there is an import error (which causes the discovered test disappear due to pytest not being able to find them) vscode fails to recognize the test, this does not happen in pycharm.

Not sure why the code lenses disappear so often but maybe, if you the same discovery procedure as done in pycharm cannot be replicated, you might want to consider to put the codelense somewhere else, like inline with the test as @1studlyman mentioned.