(improv): add suite compliance context to HTML reports - #801
Merged
chetan-rathore merged 1 commit intoSep 17, 2026
Merged
Conversation
- Add compact compliance tables to detailed DT and SR reports using run-specific requirement and compliance decisions. - Show requirement and compliance badges on suite summary cards, with Not Run placeholders for missing applicable suites and no invented outcomes or empty detailed report links. - Combine SBMR IB and OOB in one HTML view while preserving their identities, source results, and detailed compliance rows. Show the interface filter only when both interfaces have results. Include missing mandatory interfaces in the summary-card status. Show Not Compliant (Not Run) in the detailed compliance table. - Keep missing mandatory standalone checks visible as Not Compliant (Not Run), without changing raw JSON structures or test results. - Align BSA and SBSA failure summaries with top-level suite totals while preserving nested subtests in search and status filters. - Limit Recommended-entry exclusion to SR OS suite compliance so BSA and other suites retain their failures in compliance counts. Preserve the non-blocking behaviour of Recommended SR OS checks. - Validate DT/SR compliance, missing suites, IB/OOB grouping, data preservation, responsive layout, and print output with focused regression tests and browser checks. Signed-off-by: Ashish Sharma <ashish.sharma2@arm.com> Change-Id: Iba9d42ffc94c0c8b2a59c0ff5a4cf490e3a54e8d
chetan-rathore
approved these changes
Sep 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add compact compliance tables to detailed DT and SR reports using run-specific requirement and compliance decisions.
Show requirement and compliance badges on suite summary cards, with Not Run placeholders for missing applicable suites and no invented outcomes or empty detailed report links.
Combine SBMR IB and OOB in one HTML view while preserving their identities, source results, and detailed compliance rows. Show the interface filter only when both interfaces have results. Include missing mandatory interfaces in the summary-card status. Show Not Compliant (Not Run) in the detailed compliance table.
Keep missing mandatory standalone checks visible as Not Compliant (Not Run), without changing raw JSON structures or test results.
Align BSA and SBSA failure summaries with top-level suite totals while preserving nested subtests in search and status filters.
Limit Recommended-entry exclusion to SR OS suite compliance so BSA and other suites retain their failures in compliance counts. Preserve the non-blocking behaviour of Recommended SR OS checks.
Validate DT/SR compliance, missing suites, IB/OOB grouping, data preservation, responsive layout, and print output with focused regression tests and browser checks.
Change-Id: Iba9d42ffc94c0c8b2a59c0ff5a4cf490e3a54e8d