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

[MTP] TestNodeOutputMessage / TestNodeErrorMessage #4915

Open
thomhurst opened this issue Feb 4, 2025 · 2 comments
Open

[MTP] TestNodeOutputMessage / TestNodeErrorMessage #4915

thomhurst opened this issue Feb 4, 2025 · 2 comments
Labels
Area: MTP Belongs to the Microsoft.Testing.Platform core library Needs: Attention 👋

Comments

@thomhurst
Copy link
Contributor

Currently, as far as I'm aware there isn't a way to stream output to IDEs? There are standard output and error messages properties that you can attach to a test node when it completes.

Would it make sense to be able to publish a new message for output or error, containing the test node id and the message. Then the ide can subscribe to it and append them to the output window. This way hanging or long running tests can show output which can be useful to the user.

@Youssef1313
Copy link
Member

Messages sent through output device should be forwarded to the IDE, at least starting from #4178. Could you try with latest 1.5.3 and let us know?

@Youssef1313 Youssef1313 added Needs: Author Feedback Area: MTP Belongs to the Microsoft.Testing.Platform core library and removed Needs: Triage 🔍 labels Feb 5, 2025
@thomhurst
Copy link
Contributor Author

Ah I'll take a look.

Unfortunately I need to wait for Rider to release a fix before I can upgrade users as something in 1.5.0 onwards broke test discovery: https://youtrack.jetbrains.com/issue/RSRP-499756/Package-Microsoft.Testing.Platform.MSBuild-1.5.0-breaks-test-discovery

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: MTP Belongs to the Microsoft.Testing.Platform core library Needs: Attention 👋
Projects
None yet
Development

No branches or pull requests

2 participants