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
RunSettingsFilePath in csproj #312
Comments
When FCC generates the runsettings it is necessary to write to the proj file. FCC does attempt to remove this element. It is possible to supply your own runsettings. |
I'd forgotten I'd enabled the ms code coverage thing. I've turned it off and it now works without updating the csproj. |
There is a difference between ms and 'old style' though. Ms is immediate and collects from the tests you select. Old style runs all tests after the ones you select finish. I will look at storing the csproj and overwriting with it instead. |
@tonyhallett, it should use a relative path instead of an absolute one. That way the files can be pushed to git and shared between developers. the autogenerated config should search from the base path of the project with the option to enter an absolute path. |
@UkeHa FCC_removes.mp4The generated runsettings is generated in your bin folder which is not checked in. |
@tonyhallett I can see that for the most part the csproj amendment is removed at the end of the test run. However, I think there must be an edge case somewhere as it does occasionally get left behind - I've seen this a few times across different projects. As an aside if a test fails (I just threw an exception in there) the setting is not removed (it did get removed once the test passes). |
Installed product versions
Description
Every csproj file gets a local path based RunSettingsFilePath, which ends up getting checked into git and breaks the build.
Steps to recreate
Open solution, build and run tests.
Current behavior
This gets added to every csproj:
<RunSettingsFilePath>C:\dev\MyProjectetc\bin\Debug\net6.0\fine-code-coverage\coverage-tool-output\MyProject.UnitTests-fcc-mscodecoverage-generated.runsettings</RunSettingsFilePath>
Expected behavior
csproj files should not be modified when testing.
The text was updated successfully, but these errors were encountered: