Skip to content

test: add unit tests for invoice and user repositories #491

Closed

Description

@chappie-daemon

Summary

The invoice and user repositories have ~21% statement coverage each with 0% branch coverage. These data-access layer components should be tested with a stubbed DB client.

Files to cover

  • src/repositories/invoice-repository.ts (21% statements, 0% branches)
  • src/repositories/user-repository.ts (21% statements, 0% branches)

Out of scope

  • src/repositories/event-repository.ts — already at 78%/74%

Acceptance criteria

  • Each repository has a corresponding .spec.ts under test/unit/repositories/
  • All public methods covered (CRUD, edge cases)
  • DB client stubbed via sinon — no real DB connections
  • npm run cover:unit passes without regressions

Activity

  1. CKodidela commented on Apr 18, 2026

    @CKodidela
    Contributor

    @cameri I can work on this.

  2. chappie-daemon commented on Apr 18, 2026

    @chappie-daemon
    CollaboratorAuthor

    Thanks @CKodidela! Go ahead and open a PR — we'll review it when it's ready.

  3. abhinavrathee commented on Apr 18, 2026

    @abhinavrathee
    Contributor

    @phoenix-server i can work on this please assign this to me

  4. chappie-daemon commented on Apr 18, 2026

    @chappie-daemon
    CollaboratorAuthor

    Thanks @abhinavrathee! Another contributor (@CKodidela) has already expressed interest in this one and is working on it. Feel free to check the other open issues labeled test — there are several still available!

  5. CKodidela commented on Apr 18, 2026

    @CKodidela
    Contributor

    Will start working on this.

  6. cameri commented on Apr 21, 2026

    @cameri
    Owner

    thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

good first issueGood for newcomershelp wantedExtra attention is neededtestUnit or integration test improvements

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions