Skip to content

Frontend testing guide #573

Closed
Closed

Description

@codebestia

Write apps/web/docs/testing.md: the web app's Vitest setup, Testing Library conventions, and the browser APIs that must be faked — IndexedDB via fake-indexeddb, WebCrypto, service worker registration, and the socket client.

Acceptance criteria:

  • Documents the runner config, setup files and how to run a single test
  • Documents the fake-indexeddb pattern and the requirement to reset databases between tests so key material does not leak across cases
  • Documents how WebCrypto-dependent code is tested, including round-trip encrypt/decrypt as the meaningful assertion
  • Documents the socket-client mocking pattern for component tests

Activity

  1. alade-dev commented on Aug 27, 2026

    @alade-dev

    @alade-dev has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hi, I would love to work on this issue.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @alade-dev to this issue.

  2. promisszn commented on Aug 30, 2026

    @promisszn
    Contributor

    @promisszn has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

    Hi, I'd like to work on this issue. I'll write apps/web/docs/testing.md covering the Vitest setup, Testing Library conventions, and the browser API fakes (IndexedDB via fake-indexeddb, WebCrypto, service worker registration, socket client), documenting the runner config, the fake-indexeddb reset-between-tests requirement, the WebCrypto round-trip encrypt/decrypt test pattern, and the socket-client mocking pattern for component tests. I'll cross-check the doc against the actual test setup files before opening a PR.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @promisszn to this issue.

  3. drips-wave commented on Aug 30, 2026

    @drips-wave

    Congratulations, @promisszn! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

    🧑‍💻 @promisszn: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  4. added a commit that references this issue on Aug 30, 2026
    ca440c8
  5. github-actions commented on Aug 30, 2026

    @github-actions

    Closed by #595, merged into dev.

  6. drips-wave commented on Aug 30, 2026

    @drips-wave

    This issue has been completed by @promisszn as part of the Stellar Wave Program's 8th Wave 🥳

    😎 @promisszn: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

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

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions