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
Failed to Load RunSettings File #284
Comments
For Ms code coverage FCC will generate a runsettings file and add an msbuild property to the test proj file. Please can you check your proj file to see if the RunSettingsFilePath property is present or not. |
@tonyhallett Sorry for the severely delayed response on this. Yes I see where the entry is made in the Before the failure, it actually creates the csproj entry, and doesn't delete it because an exception is thrown. Then the next time I run my tests, they execute and afterwards the csproj entry is deleted. So every other test run fails for me. It's almost like the tests initially try to run before the csproj is updated. Also, I should note this appears to be happening with some projects and not others, which is very strange. Both unit tests projects are .NET 6 with the same packages installed. |
FYI: I've found this can occur when the file path to the generated *.runsettings file is longer than 260 characters. This isn't too difficult to make happen since FCC requires at least 96? characters for its naming scheme: |
Installed product versions
Description
I noticed that occasionally unit tests would just fail to run, even after executing via the VS UI. I then noticed an exception being thrown in the output window...
Steps to recreate
Current behavior
Will sometimes cause test to fail to run in visual studio
Expected behavior
Allow tests to run in visual studio
The text was updated successfully, but these errors were encountered: