dotCover and runsettings not working
Hi,
I've created a .runsettings file that defines the filters to include and exclude certain assemblies from the coverage report generated in Visual Studio, and also on the command line when running the tests with the vstest.console.exe CLI tool, an it does the filtering as expected.
I'm now trying to use this same settings file on a TeamCity build, but when I setup on my build the VSTest run configuration file, dotCover does not detect any executable code.
Versions:
- TeamCity Enterprise 2017.2.1 (build 50732)
- JetBrains dotCover Console Runner 2017.3.2. Build 111.0.20180201.111828
- Microsoft (R) Test Execution Command Line Tool Version 15.5.0
- Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter : 14.0.2303.1
dotCover error message:
No executable code was detected. The issue could be caused by one of the following:
- Include / exclude patterns are incorrect
- Assemblies are compiled without debugging information
- .pdb files are not available
- Visual Studio code coverage is enabled for MSTest
- .testrunconfig is used for MSTest and Visual Studio code coverage is not disabled (CodeCoverage section with enable="true" is present)
Unit tests step configuration:
Please sign in to leave a comment.
Hi,
while we would usually ask for the build log to have extra information on the error, parameters, etc, I'd like to point out that our requests for paths aren't absolute paths, but relative paths, which very often messes results of several tools. In your case, you are using %teamcity.build.workingDir% as the (start of the) run configuration file, so it might be messing with your setup. Please consider using a relative path to it, or the file selector on the right of the field.
If this doesn't help, please consider sending us the full build log using the Submit a request button on top of the page.
I've tried that, and it didn't worked. That was why I've added the full path.
I've submitted a request (1378021) with a build log of a test project that I've created just to reproduce the issue, and the actual test project solution.