groombook/app
Archived
13
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Set up unit testing infrastructure #39

New Issue
Closed
opened 2026-03-18 01:40:28 +00:00 by ghost · 0 comments
ghost commented 2026-03-18 01:40:28 +00:00 (Migrated from github.com)
Copy Link
Copy Source

Summary

The repo has Vitest configured but zero test files exist. We need proper testing infrastructure before features accumulate without coverage.

Tasks

  • Install @testing-library/react and @testing-library/jest-dom in apps/web
  • Set up test database fixture (test docker-compose or in-memory setup) for apps/api
  • Write initial unit tests for existing API route handlers
  • Write initial component tests for existing web pages
  • Remove passWithNoTests: true from vitest configs once tests exist
  • Configure coverage thresholds in vitest config
  • Update CI test job to include database service if needed for integration tests

Context

Tests should be written alongside features going forward. This issue covers bootstrapping the test infrastructure and writing initial tests for existing code.

## Summary The repo has Vitest configured but zero test files exist. We need proper testing infrastructure before features accumulate without coverage. ## Tasks - [ ] Install `@testing-library/react` and `@testing-library/jest-dom` in `apps/web` - [ ] Set up test database fixture (test docker-compose or in-memory setup) for `apps/api` - [ ] Write initial unit tests for existing API route handlers - [ ] Write initial component tests for existing web pages - [ ] Remove `passWithNoTests: true` from vitest configs once tests exist - [ ] Configure coverage thresholds in vitest config - [ ] Update CI `test` job to include database service if needed for integration tests ## Context Tests should be written alongside features going forward. This issue covers bootstrapping the test infrastructure and writing initial tests for existing code.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working
 documentation
Improvements or additions to documentation
 duplicate
This issue or pull request already exists
 enhancement
New feature or request
 feature
New feature
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 invalid
This doesn't seem right
 question
Further information is requested
 wontfix
This will not be worked on
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ai-review (AI Review) gb_barkley (Barkley Trimsworth) cpfarhood (Chris Farhood) ci (Continuous Integration [bot]) gb_flea (Flea Flicker) flux (Flux CD) admin (Gitea Admin) gb_lint (Lint Roller) renovate (Mend Renovate) gb_pawla (Pawla Abdul) gb_scrubs (Scrubs McBarkley) gb_shedward (Shedward Scissorhands) gb_dogfather (The Dogfather)
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: groombook/app#39
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?