Creating a list of annotations allowed to treat package as annotated#1297
Creating a list of annotations allowed to treat package as annotated#1297lwasylow wants to merge 6 commits into
Conversation
Current issues is that any comment matching annotation --% is pushed into ut cache packages which causes exclusion from coverage reports.
…ture/issue_1278
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #1297 +/- ##
========================================
Coverage 95.04% 95.05%
========================================
Files 111 111
Lines 5369 5377 +8
Branches 33 33
========================================
+ Hits 5103 5111 +8
Misses 266 266
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…ture/issue_1278
Test Results 1 files 103 suites 2m 32s ⏱️ Results for commit 439d9be. ♻️ This comment has been updated with latest results. |
|
|
This is not the correct way to solve this problem. There was an actual issue (A bug) in the suite cache management (not annotation cache) I opened a separate PR to solve this problem. See #1313 |
Resolve #1278
Root problem is the issue that package is being treated as annotate which allows it to be pushed into cache_suite table.
The solution is the do not treat object as annotated if the
--%does not contain a valid annotation that is specified by framework.e.g. ignore comments like --%parameter
This will allow for greater flexibility for documenting.