Closed sidey79 closed 1 year ago
Merging #1123 (9b79dfd) into master (a609452) will decrease coverage by
0.08%
. The diff coverage isn/a
.
@@ Coverage Diff @@
## master #1123 +/- ##
==========================================
- Coverage 65.55% 65.47% -0.09%
==========================================
Files 141 138 -3
Lines 9871 9856 -15
Branches 1558 1558
==========================================
- Hits 6471 6453 -18
- Misses 2158 2161 +3
Partials 1242 1242
Flag | Coverage Δ | |
---|---|---|
fhem | 57.69% <ø> (-0.12%) |
:arrow_down: |
modules | 65.47% <ø> (-0.09%) |
:arrow_down: |
perl | 90.17% <ø> (-0.17%) |
:arrow_down: |
unittests | 65.47% <ø> (-0.09%) |
:arrow_down: |
Flags with carried forward coverage won't be shown. Click here to find out more.
Impacted Files | Coverage Δ | |
---|---|---|
FHEM/10_SD_Rojaflex.pm | 70.73% <0.00%> (-1.22%) |
:arrow_down: |
t/FHEM/14_Hideki/00_load.t | ||
t/FHEM/14_BresserTemeo/00_load.t | ||
t/FHEM/41_OREGON/00_load.t |
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
[ ] Bugfix (please link issue)
[ ] Feature enhancement
[ ] Documentation update
[x] Unittest enhancement
[ ] other
What is the current behavior?
Installtion of fhem is used via not future proof variant of installing gpg key.
Tested perl versions are not the mainly used ones as from fhem statistics
prove tests should not run for our intermediate temp branch for merging changed and controls file
What is the new behavior (if this is a feature change)?
Installtion of fhem is done via reusable action (setup-fhem) which handles this also for the future.
Perl Versions under test are updated to [ '5.24', '5.28','5.32' ]
prove tests are opted out for branches with the name /push-action//
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Removed some old files which are not used for a long time