Repository navigation
Restructure the HTML report template and match the website theme #179
Description
The report template (src/main/resources/report-template.html, ~660 lines) holds all CSS, JS and markup in one file, and its look doesn't match seleniumboot.com.
Goal
- Split the template into a maintainable structure (separate CSS and JS sources, markup partials) that still builds into the single self-contained report file, so the report stays one file with no network needed.
- Align colours, typography and spacing with the website theme. Keep light and dark mode working.
Acceptance criteria
- The generated report is still one self-contained HTML file and works from
file://. - No behaviour change: tabs, filters, search, trend charts and failure panels work as before (existing report tests pass).
- Theme tokens live in one place.
Suggested by @PUSHPAK-JAISWAL.
Activity
codingkush commentedon Oct 20, 2026
Hi,
I would like to work on this issue. I can help restructure the HTML report template while keeping it self-contained and preserving the existing functionality. Could you please assign this issue to me, or let me know if there's anything specific I should consider before getting started?
shossain786 commentedon Oct 21, 2026
Thanks @codingkush, assigning this to you. A few things before you start:
master:report-template.htmlandHtmlReportGeneratorchanged in the last day (feat: feature added failure intelligence #177, Add flaky test trend line to report chart #185).file://, with light and dark mode intact.Comment here if anything is unclear.
codingkush commentedon Oct 21, 2026
Hi! @shossain786 I am preparing the JavaScript extraction as a separate, small PR, following your suggestion.
I tried to use the CSS extraction branch as the base for the JavaScript PR, but GitHub doesn't let me select that branch because it exists in my fork, not in the upstream repository.
Should I keep the JavaScript PR based on
masterand make it independent of the CSS changes, or would you prefer a different approach?I want to make sure both changes integrate cleanly without duplicating or losing changes.
shossain786 commentedon Oct 24, 2026
Thanks @codingkush, this is moot now: #192 and #193 are merged, so the CSS/JS split is done. Remaining work is #194. Please address the review comments there (
</nav>, balanced-tag test, chart font fallback, browser check) and I'll take another look.codingkush commentedon Oct 24, 2026
@shossain786 Done , Kindly review the changes
shossain786 commentedon Oct 24, 2026
Done in #192, #193 and #194. Thanks @codingkush for the clean split into small PRs and for turning the review fixes around quickly.
codingkush commentedon Oct 24, 2026
@shossain786 Thank you! Looking forward to contributing more to Selenium Boot.