Conversation
…am/piq into bug/data_range
3c80676 to
60509eb
Compare
Codecov Report
@@ Coverage Diff @@
## master #195 +/- ##
==========================================
+ Coverage 95.32% 95.34% +0.01%
==========================================
Files 26 26
Lines 1777 1784 +7
==========================================
+ Hits 1694 1701 +7
Misses 83 83
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
Let's merge this first, then #184 |
|
Yes, I need to add data range tests to PieAPP before merge. |
I will add my review now and revise tomorrow evening after the data range tests for the PieAPP will be added. Then we can merge 😄 |
snk4tr
left a comment
There was a problem hiding this comment.
I like the PR a lot. Only small remarks from my side.
|
|
||
|
|
||
| @pytest.mark.parametrize( | ||
| "data_range", [128, 255], |
There was a problem hiding this comment.
General remark to all the series of tests: could you add more options of the data_range values if it is not too computationally heavy? It would be very interesting to see what happens if data_range is 1.0, <1.0 (for instance 0.5) of some weird huge number like 3000.
|
@snk4tr Ready to be merged |
|
Kudos, SonarCloud Quality Gate passed!
|
Closes #194 and #196
Proposed Changes
data_rangeProgres