# UnitTest number always 0

**URL:** <https://community.sonarsource.com/t/unittest-number-always-0/22439>\
**Category:** SonarQube Cloud\
**Tags:** azuredevops-services, dotnet\
**Created:** [April 1, 2020, 9:45am UTC](https://community.sonarsource.com/t/unittest-number-always-0/22439 "2020-04-01T09:45:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Alexandre\_Frigout](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/alexandre_frigout/32/151_2.png) [@Alexandre\_Frigout](https://community.sonarsource.com/u/Alexandre_Frigout)\
**Post date:** [April 2, 2020, 9:54am UTC](https://community.sonarsource.com/t/unittest-number-always-0/22439/2 "2020-04-02T09:54:21Z")

</div>

Hi,  
You should have a look at this guide: [[Coverage & Test Data] Generate Reports for C#, VB.net](https://community.sonarsource.com/t/coverage-test-data-generate-reports-for-c-vb-net/9871) for this issue.  
Alex.

---

_[View the full topic](https://community.sonarsource.com/t/unittest-number-always-0/22439)._
