You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When runsettings contains incorrect attribute (For e.g. name instead of friendlyName in dataCollectorRunSettings or LoggerRunSettings) and test is ran via VSTS, then VSTS hangs.
Steps to reproduce
In runsettings add LoggerRunSettings and add trx logger. Instead of mentioning friendlyName="trx", write name="trx" (which is incorrect)
Run test dll from vsts.
Test run hangs.
Expected behavior
Test Run should not hang
Actual behavior
Test run hangs.
The text was updated successfully, but these errors were encountered:
This issue is happening because SettingsException, TestPlatformeException, InvalidOperationException are eaten up by TestRequestManager and not forwarded to design mode client. Thus design mode doesn't know about the failure and keeps on waiting for test discovery/excution to complete.
Description
When runsettings contains incorrect attribute (For e.g. name instead of friendlyName in dataCollectorRunSettings or LoggerRunSettings) and test is ran via VSTS, then VSTS hangs.
Steps to reproduce
In runsettings add LoggerRunSettings and add trx logger. Instead of mentioning friendlyName="trx", write name="trx" (which is incorrect)
Run test dll from vsts.
Test run hangs.
Expected behavior
Test Run should not hang
Actual behavior
Test run hangs.
The text was updated successfully, but these errors were encountered: