Skip to content

Conversation

@drognanar
Copy link
Member

Fixes the issue that if starting sessions fails, vstest console will not receive a completion event, thus will keep waiting on the StartSession call indefinitely.

Copy link
Member

@Evangelink Evangelink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to setup some test to capture this case and avoid regressions?

@drognanar
Copy link
Member Author

Added a unit test and updated the previous Verify that was moved

{
// Note: StartTestSession will invoke the HandleStartTestSessionComplete event
// if the test session is started successfully. If it is not started, we need
// to invoke the event here.
Copy link
Member

@nohwnd nohwnd Feb 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can the comment also explain why we need to do that, please?

Copy link
Member

@Evangelink Evangelink left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From what I can grasp lgtm.

This was referenced Nov 12, 2025
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