Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve test output handling #17

Closed
hbenl opened this issue Aug 8, 2021 · 1 comment
Closed

Improve test output handling #17

hbenl opened this issue Aug 8, 2021 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@hbenl
Copy link
Contributor

hbenl commented Aug 8, 2021

Test adapters can send output from tests to Test Explorer and this converter will pass those messages to the native testing API using vscode.TestRun.appendOutput(). But I can't find these messages anywhere in the UI, only the messages sent to vscode.TestRun.failed() or vscode.TestRun.errored().
Furthermore, output sent to Test Explorer can be associated with a running test, but the native testing API doesn't seem to support that (except for error messages). This can be very useful because you don't have to wade through all messages from a test run to find the messages from a particular test.

@connor4312
Copy link
Member

appendOutput strings are shown in the Test Output, which can be seen using the Test: Show Output command, also accessible via the ctrl+; ctrl+o chord or via the "terminal" icon in the test explorer view.

output sent to Test Explorer can be associated with a running test, but the native testing API doesn't seem to support that (except for error messages

That's requested in microsoft/vscode#129201 and should come this month. Closing this as a dupe of that one 🙂

@connor4312 connor4312 added the duplicate This issue or pull request already exists label Aug 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants