github-actions[bot]
commented
1 year ago 
| Package | Line Rate | Health |
|---|---|---|
| src.Cache | 63% | ➖ |
| src.DataStream | 44% | ➖ |
| src.FileList | 67% | ➖ |
| src.Frame | 36% | ❌ |
| src.HttpServer | 42% | ➖ |
| src.ImageData | 28% | ❌ |
| src.ImageFitter | 83% | ✔ |
| src.ImageGenerators | 43% | ➖ |
| src.ImageStats | 72% | ➖ |
| src.Logger | 34% | ❌ |
| src.Main | 52% | ➖ |
| src.Region | 17% | ❌ |
| src.Session | 4% | ❌ |
| src.Table | 52% | ➖ |
| src.ThreadingManager | 67% | ➖ |
| src.Timer | 85% | ✔ |
| src.Util | 30% | ❌ |
| Summary | 32% (6028 / 18682) | ❌ |
Description
What is implemented or fixed? Mention the linked issue(s), if any. Following discussions at the F2F meeting, I removed the ICD test from the backend unit tests. Since this is a high-level test and has already been done independently by @acdo2002 in this GitHub repository. The backend unit test is supposed to focus on the correctness of basic functions or object functionalities. The priority is to improve the test coverages, especially on
ImageData,Region, andSessionparts.How does this PR solve the issue? Give a brief summary. This is just a clean-up of test codes. So no issue is related.
Are there any companion PRs (frontend, protobuf)? No.
Is there anything else that testers should know (e.g. exactly how to reproduce the issue)? The
TestICDis removed from unit tests.Checklist