-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add unit tests for the telemetry module #471
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 but I think a ticket should be raised for filters falsy and empty arguments [T010]
fix if there is no ticket already.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I just noticed that two of the AppVeyor tests failed. It seems those two tests are in the describe block that uses the new |
Actually I already have a fix for that on my machine. I just wanted to get the unit tests merged first. So I will be posting a PR for that shortly. |
c7af7cd
to
18a7078
Compare
- cli.spec#028 superseded by telemetry.spec.T017-T019 - part of cli.spec#029 superseded by telemetry.spec.T020 - cli.spec#031-032 superseded by telemetry.spec.T022-T023
18a7078
to
fb6ce59
Compare
Haha, that was my first guess too. But it turned out that |
Codecov Report
@@ Coverage Diff @@
## master #471 +/- ##
=========================================
+ Coverage 79.68% 83.59% +3.9%
=========================================
Files 3 3
Lines 256 256
=========================================
+ Hits 204 214 +10
+ Misses 52 42 -10
Continue to review full report at Codecov.
|
Motivation and Context
The telemetry module had bad test coverage and I was about to start working on some improvements in that area. So I decided to first write some decent tests for it.
Description
It might seem odd that I also tested some aspects of our dependency
insight
, but in some cases it was not at all clear what exactly would be happening. So I decided to just add some tests for interesting cases.