Add CI test step with Vitest - #7
Merged
Merged
Conversation
Run unit tests on pull requests and main pushes, and gate the Docker build/push on a green test job. Co-authored-by: Pile <pierre@kanta.fr>
PiLep
marked this pull request as ready for review
July 27, 2026 19:36
Resolve complementary conflicts by retaining Vitest tests alongside the npm audit gate, and regenerate the lockfile for Next 15 + Vitest. Co-authored-by: Pile <pierre@kanta.fr>
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.
Summary
npm testscript with unit tests for pure helpers (indicators,format,month,labels).testjob in.github/workflows/deploy.ymlthat runs on pull requests and pushes tomain.securityaudit job frommain; deploy now needs bothtestandsecurity.main(Next 15 / audit overrides) and regenerated the lockfile.Test plan
npm testlocally (39 tests passing)npm run auditlocally (0 vulnerabilities)testandsecurityjobs run on this PRbuildremains skipped on PRs and still runs after both gates onmain