From 05d8e2b6ec35907b3c125e28338a28927e1745db Mon Sep 17 00:00:00 2001 From: NM3214 Date: Sat, 18 Jul 2026 03:58:19 +0300 Subject: [PATCH] Fixed wording in part5c --- src/content/5/en/part5c.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/5/en/part5c.md b/src/content/5/en/part5c.md index f671dc48e7b..4356920f00b 100644 --- a/src/content/5/en/part5c.md +++ b/src/content/5/en/part5c.md @@ -856,7 +856,7 @@ In the previous part of the course material, we wrote integration tests for the So far all of our tests for the frontend have been unit tests that have validated the correct functioning of individual components. Unit testing is useful at times, but even a comprehensive suite of unit tests is not enough to validate that the application works as a whole. We could also make integration tests for the frontend. Integration testing tests the collaboration of multiple components. It is considerably more difficult than unit testing, as we would have to for example mock data from the server. -We chose to concentrate on making end-to-end tests to test the whole application. We will work on the end-to-end tests in the last chapter of this part. +We chose to concentrate on making end-to-end tests to test the whole application. We will work on the end-to-end tests in the next chapter of this part. ### Snapshot testing