From c284983b4b8b26b7bc19ec6ac9c659e1dcae860b Mon Sep 17 00:00:00 2001 From: MartinBraquet Date: Mon, 4 Aug 2025 10:16:24 +0200 Subject: [PATCH] Update dev docs --- docs/development.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/docs/development.md b/docs/development.md index f70ef107..3b25cbd2 100644 --- a/docs/development.md +++ b/docs/development.md @@ -19,4 +19,17 @@ Then update the database: ```bash npx prisma migrate dev --name add-some-profile-variable -``` \ No newline at end of file +``` + +### Cover with tests + +Best Practices + +* Test Behavior, Not Implementation. Don’t test internal state or function calls unless you’re testing utilities or very critical behavior. +* Use msw to Mock APIs. Don't manually mock fetch—use msw to simulate realistic behavior, including network delays and errors. +* Don’t Overuse Snapshots. Snapshots are fragile and often meaningless unless used sparingly (e.g., for JSON response schemas). +* Prefer userEvent Over fireEvent. It simulates real user interactions more accurately. +* Avoid Testing Next.js Internals . You don’t need to test getStaticProps, getServerSideProps themselves—test what they render. +* Use jest.spyOn() for Internal Utilities . Avoid reaching into modules you don’t own. +* Don't test just for coverage. Test to prevent regressions, document intent, and handle edge cases. +* Don't write end-to-end tests for features that change frequently unless absolutely necessary. \ No newline at end of file