#4445 closed defect (fixed)
new coverage test is not working properly
| Reported by: | lochel | Owned by: | sjoelund.se |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Testing Framework | Version: | |
| Keywords: | ThermoSysPro | Cc: | ptaeuber |
Description
The latest results from the new coverage test are a bit strange. It seems to miss the impact on the ThermoSysPro and probably other libraries as well: 2017-06-12 11:16:56 to 2017-06-13 03:48:54
ThermoSysPro went up by 3 tests due to that specific commit.
Change History (4)
comment:1 Changed 7 years ago by sjoelund.se
comment:2 Changed 7 years ago by sjoelund.se
I think the following commits should partially fix the problem (not really a problem with the report generation, but some old way we renamed dates that caused this odd behaviour when there was no new OM version):
Do not change dates of library test runs
Add script for cleaning out empty omcversion dates
Do not add entries if we run no test
I have not been able to verify it though. Hopefully it doesn't mess with the overview.html report generation (it seems we no longer depend on all libraries having the same date despite being run on different dates; I could be wrong though).
We then also need a commit for handling the report generation when a library was not updated in the latest run (happens when there is no OM commit, but libraries are bumped).
comment:3 Changed 7 years ago by sjoelund.se
- Resolution set to fixed
- Status changed from new to closed
comment:4 Changed 7 years ago by sjoelund.se
- Milestone Future deleted
It seems this is due to no test being run at the previous date, causing no changes to be possible for this one (since it cannot find any library). I think I'll need a slower SQL statement here, and possibly some better filtering to not generate reports or SQL entries when no test was run.