You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Code coverage apparently requires debug(?) build with full non-portable PDBs, so switch to Build Debug -> Test & Coverage -> Build Release -> Deploy sequence? There're no parallel builds on free AppVeyour plan, so no point in separating build jobs even if it's possible. Symbol Packages for .NET Standard libraries are probably supposed to contain portable PDBs, so there's no way around double build, I guess.
Could also be a good time to find out why the heck only 1 set of tests is executed on AppVeyor instead of 6 ( { XAML, No-XAML } x { Core 1.1, Core 2.0, .NET 4.6 } ).
P. S. Coveralls to CodeCov is like SensioLabs Insight to Scrutinizer. Don't bother with it. Not worth the badge. Well, maybe. If it's one line of code in the build script.
The text was updated successfully, but these errors were encountered:
Add CodeCov badge. As a bonus, it shows pretty diagrams of code coverage.
Use example CodeCov C# repository as an example.
Code coverage apparently requires debug(?) build with full non-portable PDBs, so switch to Build Debug -> Test & Coverage -> Build Release -> Deploy sequence? There're no parallel builds on free AppVeyour plan, so no point in separating build jobs even if it's possible. Symbol Packages for .NET Standard libraries are probably supposed to contain portable PDBs, so there's no way around double build, I guess.
Could also be a good time to find out why the heck only 1 set of tests is executed on AppVeyor instead of 6 ( { XAML, No-XAML } x { Core 1.1, Core 2.0, .NET 4.6 } ).
Related:
P. S. Coveralls to CodeCov is like SensioLabs Insight to Scrutinizer. Don't bother with it. Not worth the badge. Well, maybe. If it's one line of code in the build script.
The text was updated successfully, but these errors were encountered: