> For the complete documentation index, see [llms.txt](https://summerain-1.gitbook.io/summerain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://summerain-1.gitbook.io/summerain/archived-design-records/frontend-architecture/06-testing.md).

# 06 - Testing Strategy

> \[!WARNING] **Archived design record.** This page predates the completed V2 frontend and may contain obsolete versions, paths, or implementation status.

> Part of: [Frontend Architecture Design (Index)](/summerain/archived-design-records/frontend-architecture.md)

## Scope

**Vitest + React Testing Library:**

* Unit-test `lib/api.ts` (envelope unwrapping, CSRF injection, **logout on 401, disabled account on 4030, rate limiting on 429, and i18n error-code mapping**).
* Test each feature's `hooks.ts` with MSW-mocked endpoints to verify query and mutation behavior.

Write component tests for critical interactions: upload, infinite scrolling, form validation, visibility changes, reauthentication after a password change, and post-registration navigation.

## Trade-offs

Do not pursue exhaustive coverage. Prioritize the **API layer and authentication/query hooks** because they are central to system correctness and especially prone to regressions.

## Layered Quality Gates

* **pre-commit (local and fast):** `prettier --check` + `eslint` + `tsc --noEmit` (aligned with [08](/summerain/archived-design-records/frontend-architecture/08-coding-standards.md)).
* **CI (blocks merge and release):** all three checks above **plus `vitest run`**. Failing tests block merges, and release builds run the same test suite.

***

<- [05 Build and Deployment](/summerain/archived-design-records/frontend-architecture/05-build-and-deploy.md) · [Index](/summerain/archived-design-records/frontend-architecture.md) · Next: [07 Production Artifact Standards](/summerain/archived-design-records/frontend-architecture/07-production-standards.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://summerain-1.gitbook.io/summerain/archived-design-records/frontend-architecture/06-testing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.