exercise corrections

Author: kettanaito

.vscode/extensions.json

@@ -2,6 +2,7 @@
 	"recommendations": [
 		"dbaeumer.vscode-eslint",
 		"esbenp.prettier-vscode",
-		"neotan.vscode-auto-restart-typescript-eslint-servers"
+		"neotan.vscode-auto-restart-typescript-eslint-servers",
+		"qwtel.sqlite-viewer"
 	]
 }

exercises/02.context/02.problem.automatic-fixtures/README.mdx

@@ -6,12 +6,13 @@ Your custom fixtures can introduce side effects that run before and after the fi
 import fs from 'node:fs'
 import os from 'node:os'
 import path from 'node:path'
+import { test as testBase } from 'vitest'
 
 interface Fixtures {
-	createMockFile: (content: string, filename: string) => Promise<void>
+	createMockFile: (content: string, filename: string) => Promise<string>
 }
 
-test.extend({
+const test = testBase.extend<Fixtures>({
 	async createMockFile({}, use) {
 		// 1. Prepare.
 		const temporaryDirectory = await fs.promises.mkdtemp(

exercises/03.assertions/04.problem.retryable-assertions/README.mdx

@@ -6,7 +6,7 @@ In Promise-based APIs, that expectation is neatly abstracted behind the `async`/
 
 ```ts nonumber
 const response = await fetch('/api/songs')
-await expect(response.json()).toEqual(favoriteSongs)
+await expect(response.json()).resolves.toEqual(favoriteSongs)
 ```
 
 > While fetching the list of songs takes time, that eventuality is represented as a Promise that you can `await`. This guaratees that your test will not continue until the data is fetched. Quite the same applies to reading the response body stream.