[DevExpress Support Team: CLONED FROM T706240: Unit Testing - An unexpected error is raised when tests run for the second time]
Issue is still happening to me on VS2019 with 18.2.9
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Hi Dan,
Thank you for contacting us.
I tried to reproduce this issue but my attempts were unsuccessful. To determine what causes this problem, please provide us with a text error, detailed steps that lead to it and CodeRush log files located in the following folder: %localappdata%\CodeRush\Logs\
I am simply editing tests and running tests within the file CTRL+T,F
I am using MSTEST if it is relevant
attached is the diag log but I do not see anything in it (The status bar shows an unexpected error has occurred and no tests are actually ran)
Thank you for your clarification and providing the log file.
We use the Visual Studio test executor for the MSTest test framework. I have found a message reported by this executor in your log file:
2019.04.26 19:20:16.7464 Information: The active Tests Discovery was aborted.
There are some reports on the Visual Studio test runner with the same message:
"The active Tests Discovery was aborted"
Error in Test Discovery after upgrade to VS 2017 15.5
To determine what causes the issue (CodeRush or the Visual Studio test executor), please repeat your steps with the Visual Studio test runner and check if the issue persists.
The issue happens with mstest runner as well but I did notice that if I disable CR it does not happen (atleast within a few runs I made)
Thank you for informing us of your results. Please give us some time to examine how CodeRush can affect this issue.
Also, please check whether this issue is reproduced in Visual Studio 2017 on your side.