add dockerfile

Dockerfile

@@ -0,0 +1,9 @@
+FROM node:18
+
+WORKDIR /app
+
+COPY . .
+
+RUN yarn
+
+CMD [ "yarn", "test" ]

README.md

@@ -0,0 +1,15 @@
+https://github.com/vitest-dev/vitest/issues/3077#issuecomment-1867306736
+
+```sh
+docker build . -t vitest
+docker run -it -v ./src:/app/src vitest /bin/bash
+```
+
+Play with configs, my findings:
+1. It is more likely to hang when test cases failed. (not sure, you can try comment & uncomment `data-testid="message"` in Message.tsx)
+2. Node 18/19 will hang, while it seems that there are no issues with version 20+.
+3. Setting `globals: true` and using the global vitest function increases the possibility of hanging.
+4. The higher count of tests, the higher the chance of hanging.
+
+
+

src/Message.test.tsx

@@ -1,6 +1,6 @@
 import { cleanup, render, screen } from "@testing-library/react";
 import Message from "./Message";
-import { describe, it, expect, beforeEach } from "vitest";
+// import { describe, it, expect, beforeEach } from "vitest";
 
 beforeEach(cleanup);
 
@@ -23,5 +23,5 @@ describe(
       expect(messageElement.innerHTML).toBe("<b>test</b> abc");
     });
   },
-  { repeats: 200 }
+  { repeats: 500 }
 );

src/Message.tsx

@@ -5,7 +5,7 @@ const dompurify = DOMPurify();
 const SystemMessage = ({ text }: { text: string }) => {
   return (
     <div
-      // data-testid="message"
+      data-testid="message"
       dangerouslySetInnerHTML={{ __html: dompurify.sanitize(text) }}
     />
   );

vite.config.ts

@@ -4,7 +4,7 @@ import { defineConfig } from "vitest/config";
 export default defineConfig({
   plugins: [react()],
   test: {
-    // globals: true,
+    globals: true,
     setupFiles: ["./src/setupTests.ts"],
     environment: "jsdom",
   },