From 75a08426a3b16b66e2d5f20df29d99daa52117db Mon Sep 17 00:00:00 2001 From: Simon Holthausen Date: Thu, 25 Jul 2024 16:39:23 +0200 Subject: [PATCH] fix --- documentation/docs/05-misc/02-testing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/docs/05-misc/02-testing.md b/documentation/docs/05-misc/02-testing.md index 71c4ccfd07..b521c9915e 100644 --- a/documentation/docs/05-misc/02-testing.md +++ b/documentation/docs/05-misc/02-testing.md @@ -4,7 +4,7 @@ title: Testing Testing helps you write and maintain your code and guard against regressions. Testing frameworks help you with that, allowing you to describe assertions or expectations about how your code should behave. Svelte is unopinionated about which testing framework you use, so you can write unit tests, integration tests, and end-to-end tests using solutions like Vitest, Jasmine, Cypress and Playwright. -## Unit/Integration testing using Vitest +## Unit/Integration tests using Vitest Unit tests allow you to test small isolated parts of your code. Integration tests allow you to test parts of your application to see if they work together. If you're using Vite (including via SvelteKit), we recommend using [Vitest](https://vitest.dev/). @@ -17,7 +17,7 @@ npm install -D vitest jsdom Then adjust your `vite.config.js`: ```js -/// file: vitest.config.js +/// file: vite.config.js import { defineConfig } from 'vitest/config'; export default defineConfig({