Test: adapt unit tests after Vitest update

The assertion `toContain` can no longer be used to check if an object is a subset of another object. The closest equivalent is `toMatchObject`. See: https://github.com/vitest-dev/vitest/releases/tag/v1.0.0 RISDEV-0000
digitalservicebund · Dec 18, 2023 · 30b46dd · 30b46dd
1 parent b06430c
commit 30b46dd
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/frontend/test/composables/useCaseLawMenuItems.spec.ts b/frontend/test/composables/useCaseLawMenuItems.spec.ts
@@ -10,7 +10,9 @@ describe("useCaseLawMenuItems", () => {
     const menuItems = useCaseLawMenuItems(documentNumber, route)
 
     for (const menuItem of menuItems.value) {
-      expect(menuItem.route.params).toContain({ documentNumber: "fake-number" })
+      expect(menuItem.route.params).toMatchObject({
+        documentNumber: "fake-number",
+      })
     }
   })
 

diff --git a/frontend/test/composables/useNormMenuItems.spec.ts b/frontend/test/composables/useNormMenuItems.spec.ts
@@ -10,7 +10,7 @@ describe("useNormMenuItems", () => {
     const menuItems = useNormMenuItems(guid, route)
 
     for (const menuItem of menuItems.value) {
-      expect(menuItem.route.params).toContain({ normGuid: "fake-guid" })
+      expect(menuItem.route.params).toMatchObject({ normGuid: "fake-guid" })
     }
   })