It was almost three years ago that checkstyle started recording coverage on codecov.io using a similar setup to what I’m going to showcase here. We run tests from those test.hxml files rather than using munit’s command line tool. Each project has a test.hxml that references both libraries and enables coverage macros. Let me get you covered - at least some of you.įormatter, tokentree and checkstyle all use munit and mcover to run tests and collect coverage results.
Now that there is a test explorer for VSCode you probably wonder is there a way to somehow show coverage results in VSCode?
I think the MSDN page needs updating.Edit: I’ve updated the title to indicate post contains a solution despite the question mark This had me stumped for a while, but I'm glad it's fixed. It turns out the regular expression parser is being confused by the non-escaped dots (cheers Grin), so I need to do this instead. Make sure the tests ran, required binaries were loaded, had matching symbol files, and were not excluded through custom settings. runsettings file:īut instead of basking in the glory of a 100% code coverage score, I get the following error:Įmpty results generated: No binaries were instrumented. Following the guide over at the MSDN suggests that you can do the following in a. The alternative is to exclude the whole assembly. You can apply the attribute to every test class, and that works fine, but is a right faff with lots of tests. The only problem I've discovered with this is by default the Code Coverage tool will analyse all projects in the solution including the test projects themselves, which score 0% coverage and skews your solution stats. I keep tests in their own projects, named after the assembly they are testing, but with ".Tests" bunged on the end. I recently started playing with Visual Studio's code coverage analysis tool to show me where my unit testing is insufficient.
0 kommentar(er)
