Code coverage checks and reports

[hsubramanianaks]

This PR is for generating code coverage reports via c8 library and uploading them via codecov github action here

Sample Code Cove report

https://app.codecov.io/github/hsubramanianaks/vscode-bridge-to-kubernetes/commit/32888d1f7e1a2ef1ff5f3e5ddbd93c242092e6b9/tree/src/clients

Also PR comment will be generated by codecov stating Code Coverage reports here

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (main@5783704). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #62   +/-   ##
=======================================
  Coverage        ?   63.37%           
=======================================
  Files           ?       23           
  Lines           ?     1977           
  Branches        ?       72           
=======================================
  Hits            ?     1253           
  Misses          ?      724           
  Partials        ?        0           

Flag	Coverage Δ
unittests	63.27% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

[Tatsinnit]

💡🙏 Thank you so much for this, Here is my 2 cents: please note some key points if we plan to make this codecov public that we stay true to the actual reality and future plans around it for how to. I guess this is great place where we can learn for various other project which might have similar issue aka well developed and matured and since they were legacy the codecov was not the initial thinking process. ☕️

Like:

• What is the current whole repo level coverage number?
  * Answer the whole repo is +63% which is not bad: Details link here

Reference to the codecov for this work

[Tatsinnit]

💡 Just as a note: I see this kind of really solves the mystery for me, essentially all these tests already existed, and upon adding the test runner and coverage we get 63% coverage for free, which is a win! 🐴🚀🔔

[hsubramanianaks]

💡🙏 Thank you so much for this, Here is my 2 cents: please note some key points if we plan to make this codecov public that we stay true to the actual reality and future plans around it for how to. I guess this is great place where we can learn for various other project which might have similar issue aka well developed and matured and since they were legacy the codecov was not the initial thinking process. ☕️

Like:

• What is the current whole repo level coverage number?
  • Answer the whole repo is +63% which is not bad: Details link here

Reference to the codecov for this work

@Tatsinnit thanks for your thoughts. My thought was to add this code cov at least not to reduce the existing 63% for future upcoming PR's and add a work item to increase the coverage for existing unit tests and for files which are missing unit test cases. I agree lot of this was well developed and matured but there is also lot of code which is legacy and some parts of it is not used. we can use this opportunity to refactor them and remove unused/dead code, also learn more in depth about this vscode extension. Please let me know your thoughts further on this and also how other extensions are achieving the same.

[bfoley13]

Nice to see you were able to use the codecov here as well!