Unable to disable terminal on launch
See original GitHub issueIn the 4.4.0
release notes, I see this new feature highlighted:
enhanced test output discovery by automatically opening TestExplorer terminal upon launch.
Is there an option to disable this? I personally use this extension for quick success/failure visualization in the code margins, and I switch to my terminal app (not a panel within VSCode) when I need more granular test output. I don’t use VSCode terminals and I’d prefer not to have to close them every time I launch or reload the window.
Thanks for all your great work on this extension — it’s invaluable!
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:23
Top Results From Across the Web
Disabling Terminal Services before you install, upgrade ... - IBM
Disable Windows Terminal Services before update, roll back, modify, or uninstall operations. Open a command prompt. To disable Remote Desktop, run this command: ......
Read more >A way to stop the integrated terminal from launching at startup
VSCode version: 1.65.2 I use VSCode to develop Rust project. If I run a build task (such as cargo build), it runs in...
Read more >How to temporarily disable Terminal Server Client Logons
Stop connectivity for a specific user in User Manager by opening the user account and selecting CONFIG. Here you can uncheck the box,...
Read more >Stop / Enable / Disable Terminal services from command line
This happens when Terminal Services is disabled through registry hack. You can fix this by running the below registry change command.
Read more >Disabling and Enabling System Integrity Protection
Disable System Integrity Protection Temporarily · Restart your computer in Recovery mode. · Launch Terminal from the Utilities menu. · Run the command...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
feel free to try the pre-release 4.5.0, you should be able to turn off the terminal with
"jest.showTerminalOnLaunch": false
setting.@KevinBatdorf, you raised good points!
Not every javascript project, but those with a jest in node_modules will indeed activate the extension. I was a bit surprised that a project not using jest could still have jest in the node_module… Can you give us a bit more detail so we can see if we can improve the activation logic to avoid such false positive.
In any case, you convinced me that to treat “no test” as an error might not be the proper severity. I will change that to a warning in the next release.
I also agree with @jakemhiller that this is a great idea! 😃 With this visual cue, I think we could add a
jest.showTerminalOnError
setting, knowing the alert is not lost.@jakemhiller Just want to make sure we are on the same page, the errors triggered the show-terminal is not regular test errors but operation or configuration errors that prevented jest from running normally. These should be relatively rate but I do agree we could enhance it as mentioned above.