microsoft / microsoft/vscode-dotnettools
Option to close test terminal after test run completes
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Describe the feature you'd like
The current behaviour when running tests via the dev kit is that a terminal starts running that runs the build / test commands.
I would like an configuration option to set that terminal to close after the test run complets, the reason for this is that when using test containers the Ryuk container responsible for closing down other containers remains open until the terminal is closed.
Running tests multiple times in a row leads to several zombie Ryuk containers being spawned waiting for that terminal to close, if I can configure C# Dev kit to close that terminal (rather than be reused) it would avoid that problem.
Alternatives considered
No response
Environment Information
Windows 11
Docker Desktop
I am running a dotnet core project via Visual Studio Dev Containers, in that project I have integration tests creating postgres database using the TestContainers library.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how C# Dev Kit creates and reuses the terminal for build and test commands, then inspect the configuration entry points for test execution. Done means a user-configurable option closes the test terminal after completion and repeated TestContainers runs no longer leave Ryuk containers waiting for the terminal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, docker, postgres, vscode
- Domain
- databases, devtools, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100