Actions
Architecture #23084
closedRemove constraint on component name pattern for matching reports
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Fix check:
To do
Regression:
No
Description
We use to match compoenent name and value pattern for matching between expected reports and actual reports.
Then, in 7.X, we added reportid which allows to better match reports and give more flexibility.
In 8.0, we want to only have match on reportid for the reports having it, and keep the old matching scheme only for report withtout reportid (== 0).
This means that component name in expected report and actual report can be totally different.
See linked issues for history / context.
Actions