fix: resolve vscode type errors inside utils tests (anuraghazra#4585)

alexandr-garbuzov · qwerty541 · web-flow · commit a97ab2dc7a1a · 2025-10-16T20:18:28.000+03:00
Co-authored-by: Alexandr &lt;qwerty541zxc@gmail.com&gt;
diff --git a/tests/utils.test.js b/tests/utils.test.js
@@ -2,7 +2,7 @@
 
 import { describe, expect, it } from "@jest/globals";
 import { queryByTestId } from "@testing-library/dom";
-import "@testing-library/jest-dom";
+import "@testing-library/jest-dom/jest-globals";
 import { encodeHTML, renderError } from "../src/common/utils.js";
 import { parseBoolean } from "../src/common/ops.js";
 
@@ -34,19 +34,19 @@ describe("Test utils.js", () => {
   it("should test renderError", () => {
     document.body.innerHTML = renderError({ message: "Something went wrong" });
     expect(
-      queryByTestId(document.body, "message").children[0],
+      queryByTestId(document.body, "message")?.children[0],
     ).toHaveTextContent(/Something went wrong/gim);
     expect(
-      queryByTestId(document.body, "message").children[1],
-    ).toBeEmptyDOMElement(2);
+      queryByTestId(document.body, "message")?.children[1],
+    ).toBeEmptyDOMElement();
 
     // Secondary message
     document.body.innerHTML = renderError({
       message: "Something went wrong",
       secondaryMessage: "Secondary Message",
     });
     expect(
-      queryByTestId(document.body, "message").children[1],
+      queryByTestId(document.body, "message")?.children[1],
     ).toHaveTextContent(/Secondary Message/gim);
   });
 });
