Skip to content

Allow custom stdout/stderr streams for test output#324

Merged
connor4312 merged 1 commit intomicrosoft:mainfrom
DanTup:allow-custom-output-streams
Feb 24, 2026
Merged

Allow custom stdout/stderr streams for test output#324
connor4312 merged 1 commit intomicrosoft:mainfrom
DanTup:allow-custom-output-streams

Conversation

@DanTup
Copy link
Contributor

@DanTup DanTup commented Feb 24, 2026

This will allow callers to capture the output (for example to filter out unnecessary VS Code/electron output to keep results cleaner) rather than it being written directly to the processes stdout/stderr.

See #132

(cc @connor4312 - I did not update any versions or changelog because it wasn't clear what the process for that is, but let me know if I should 🙂)

This will allow callers to capture the output (for example to filter out unnecessary VS Code/electron output to keep results cleaner) rather than it being written directly to the processes stdout/stderr.

See microsoft#132
@connor4312 connor4312 enabled auto-merge (squash) February 24, 2026 18:05
@connor4312
Copy link
Member

thanks!

@vs-code-engineering vs-code-engineering bot added this to the February 2026 milestone Feb 24, 2026
@connor4312 connor4312 merged commit d1e23bc into microsoft:main Feb 24, 2026
2 checks passed
@DanTup
Copy link
Contributor Author

DanTup commented Feb 25, 2026

@connor4312 np, thanks for reviewing!

What is the release process here? The last few releases look ad-hoc but I noticed this one is assigned to a milestone (though it's the only thing in it). This isn't a request to release, it'd just be useful for me to have an idea of when I can use this (without checking back frequently). Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants