codecov[bot]
commented
2 years ago Codecov Report
Merging #1085 (465c05a) into master (1a8e7e7) will increase coverage by
0.19%. The diff coverage is50.00%.
@@ Coverage Diff @@
## master #1085 +/- ##
==========================================
+ Coverage 63.66% 63.85% +0.19%
==========================================
Files 130 133 +3
Lines 9494 9539 +45
Branches 1505 1513 +8
==========================================
+ Hits 6044 6091 +47
+ Misses 2288 2277 -11
- Partials 1162 1171 +9 | Flag | Coverage Δ | |
|---|---|---|
| fhem | 55.75% <50.00%> (+0.25%) |
:arrow_up: |
| modules | 63.85% <50.00%> (+0.19%) |
:arrow_up: |
| perl | 90.59% <ø> (+0.21%) |
:arrow_up: |
| unittests | 63.85% <50.00%> (+0.19%) |
:arrow_up: |
Flags with carried forward coverage won't be shown. Click here to find out more.
| Impacted Files | Coverage Δ | |
|---|---|---|
| FHEM/lib/SD_ProtocolData.pm | 100.00% <ø> (ø) |
|
| FHEM/14_SD_WS.pm | 65.59% <50.00%> (+0.05%) |
:arrow_up: |
| t/FHEM/14_SD_WS07/09_parseDatat.t | ||
| t/FHEM/10_SD_GT/00_load.t | 100.00% <0.00%> (ø) |
|
| t/FHEM/14_SD_BELL/00_load.t | 100.00% <0.00%> (ø) |
|
| t/FHEM/14_BresserTemeo/09_parseDatat.t | 80.00% <0.00%> (ø) |
|
| t/FHEM/14_SD_BELL/09_parseDatat.t | 80.00% <0.00%> (ø) |
|
| FHEM/lib/SD_Protocols.pm | 79.56% <0.00%> (+0.10%) |
:arrow_up: |
| FHEM/00_SIGNALduino.pm | 64.19% <0.00%> (+0.44%) |
:arrow_up: |
:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more
elektron-bbs
sidey79
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
[ ] Bugfix (please link issue)
[x] Feature enhancement
[ ] Documentation update
[ ] Unittest enhancement
[ ] other
What is the current behavior? (You can also link to an open issue here, if this describes the current behavior) No correct evaluation of the additional sensors.
What is the new behavior (if this is a feature change)? fixed packet length mode 18 byte new ground/earth sensor for humidity and temperature, indoor sensor for humidity and temperature
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) no
Other information: