Menu

1 / 4

AI-Assisted QA with GitHub Actions

DEV Community: cicd·Paul Newell·15 days ago
#yzD5O43A
#devtocicd#devto#dev#dashboard#github
Reading 0:00
15s threshold

The pipeline already knows how healthy the project is. It just never tells anyone.

Nobody Reads CI Logs

Every push to main on my side project produces a pile of reports. Vitest JSON for unit and component tests. A Playwright report across three browser projects. Coverage. Type coverage. Lighthouse runs. Bundle size. Eval results. Then the run goes green, the artifacts expire after 90 days and nobody looks at any of it again.

As a QA Engineer, that bothers me more than it should.

So the last job in the pipeline now turns those reports into a page. One HTML file, built from the run's own artifacts, published to GitHub Pages next to the app it describes.

It's live here: https://newell-paul.github.io/sprint-scout/dashboard/

The App

The app is SprintScout, a browser-only planner that times cycling segment attempts to the wind.

https://newell-paul.github.io/sprint-scout/

It has some strict rules: no server, no accounts, no API keys, no request the rider didn't ask for.

The dashboard had to live by the…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.