Add option to run tests in background by default

[leep-frog]

Is your feature request related to a problem? Please describe.

This extension defaults to opening the output tab in the panel whenever a go test is run. This behavior should be configurable for a few reasons:

• When the panel automatically opens (via outputChannel.show()), the terminal sometimes doesn't open fully (and instead does split screen). I'd prefer to update my keybinding for go.test.package to run go.test.package and then call toggleMaximizedPanel (using multi-command) to ensure the output tab always opens in full screen
• I have tests that take a while and I want to stay in my editor while tests run
• I have tests that I know work and I just want to see the coverage report in my code editor

Describe the solution you'd like

I think there are two approaches:

1. Provide supplementary commands for all test commands (e.g. go.test.package and go.test.packageAsync/Background)
2. Allow test commands to accept a keybinding args object that allows individual keybindings to specify background behavior (and possibly other testConfig in the future).

Describe alternatives you've considered

I can use the multi-command extension to run go tests, then close the panel, then open the maximized panel, but that is inconsistent (without a long delay), and is a bad user experience

Additional context
Add any other context or screenshots about the feature request here.

[gopherbot]

Change https://go.dev/cl/567995 mentions this issue: allow args.background parameter for go.test.* commands

[hyangah]

We hope to deprecate the old UI (the test output channel) in favor of the test explorer UI. (#2044)

It looks like VSCode's testing.openTesting setting for the new UI is similar to what you want. How about using the setting instead of inventing a new knob that is going to be deprecated? Its default is openOnTestStart which matches the current behavior of the old UI's test output channel. What do you think?

[leep-frog]

Oh good to know about! When will the new go-test UI be released? Thanks, Greg

…

On Wed, May 29, 2024 at 1:28 PM Hyang-Ah Hana Kim ***@***.***> wrote: We hope to deprecate the old UI (the test output channel) in favor of the test explorer UI. (#2044 <#2044> ) It looks like VSCode's testing.openTesting setting for the new UI is similar to what you want. How about using the setting instead of inventing a new knob that is going to be deprecated? Its default is openOnTestStart which matches the current behavior of the old UI's test output channel. What do you think? — Reply to this email directly, view it on GitHub <#3154 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AP4ZD3H2Y7ROVWIIR2YOIATZEYF2RAVCNFSM6AAAAABCV2YCFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZXHEZDEMJSGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>