Error: [vitest] No "getGoals" export is defined on the "@/api/goalAPI" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/api/goalAPI"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError node_modules/vitest/dist/chunks/execute._eQQfgI8.js:320:19 ❯ Object.get node_modules/vitest/dist/chunks/execute._eQQfgI8.js:388:22 ❯ fetchGoalList src/components/CreateNewTodo.tsx:38:28 ❯ src/components/CreateNewTodo.tsx:94:5 ❯ commitHookEffectListMount node_modules/react-dom/cjs/react-dom.development.js:23189:26 ❯ commitPassiveMountOnFiber node_modules/react-dom/cjs/react-dom.development.js:24970:11 ❯ commitPassiveMountEffects_complete node_modules/react-dom/cjs/react-dom.development.js:24930:9 ❯ commitPassiveMountEffects_begin node_modules/react-dom/cjs/react-dom.development.js:24917:7 ❯ commitPassiveMountEffects node_modules/react-dom/cjs/react-dom.development.js:24905:3 ❯ flushPassiveEffectsImpl node_modules/react-dom/cjs/react-dom.development.js:27078:3 This error originated in "src/components/CreateNewTodo.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "제목 입력 하기". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: [vitest] No "getGoals" export is defined on the "@/api/goalAPI" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/api/goalAPI"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError node_modules/vitest/dist/chunks/execute._eQQfgI8.js:320:19 ❯ Object.get node_modules/vitest/dist/chunks/execute._eQQfgI8.js:388:22 ❯ fetchGoalList src/components/CreateNewTodo.tsx:38:28 ❯ src/components/CreateNewTodo.tsx:94:5 ❯ commitHookEffectListMount node_modules/react-dom/cjs/react-dom.development.js:23189:26 ❯ commitPassiveMountOnFiber node_modules/react-dom/cjs/react-dom.development.js:24970:11 ❯ commitPassiveMountEffects_complete node_modules/react-dom/cjs/react-dom.development.js:24930:9 ❯ commitPassiveMountEffects_begin node_modules/react-dom/cjs/react-dom.development.js:24917:7 ❯ commitPassiveMountEffects node_modules/react-dom/cjs/react-dom.development.js:24905:3 ❯ flushPassiveEffectsImpl node_modules/react-dom/cjs/react-dom.development.js:27078:3 This error originated in "src/components/CreateNewTodo.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "제목 입력 하기". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: [vitest] No "getGoals" export is defined on the "@/api/goalAPI" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/api/goalAPI"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError node_modules/vitest/dist/chunks/execute._eQQfgI8.js:320:19 ❯ Object.get node_modules/vitest/dist/chunks/execute._eQQfgI8.js:388:22 ❯ fetchGoalList src/components/CreateNewTodo.tsx:38:28 ❯ src/components/CreateNewTodo.tsx:94:5 ❯ commitHookEffectListMount node_modules/react-dom/cjs/react-dom.development.js:23189:26 ❯ commitPassiveMountOnFiber node_modules/react-dom/cjs/react-dom.development.js:24970:11 ❯ commitPassiveMountEffects_complete node_modules/react-dom/cjs/react-dom.development.js:24930:9 ❯ commitPassiveMountEffects_begin node_modules/react-dom/cjs/react-dom.development.js:24917:7 ❯ commitPassiveMountEffects node_modules/react-dom/cjs/react-dom.development.js:24905:3 ❯ flushPassiveEffectsImpl node_modules/react-dom/cjs/react-dom.development.js:27078:3 This error originated in "src/components/CreateNewTodo.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "파일 업로드 하기". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: [vitest] No "getGoals" export is defined on the "@/api/goalAPI" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/api/goalAPI"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError node_modules/vitest/dist/chunks/execute._eQQfgI8.js:320:19 ❯ Object.get node_modules/vitest/dist/chunks/execute._eQQfgI8.js:388:22 ❯ fetchGoalList src/components/CreateNewTodo.tsx:38:28 ❯ src/components/CreateNewTodo.tsx:94:5 ❯ commitHookEffectListMount node_modules/react-dom/cjs/react-dom.development.js:23189:26 ❯ commitPassiveMountOnFiber node_modules/react-dom/cjs/react-dom.development.js:24970:11 ❯ commitPassiveMountEffects_complete node_modules/react-dom/cjs/react-dom.development.js:24930:9 ❯ commitPassiveMountEffects_begin node_modules/react-dom/cjs/react-dom.development.js:24917:7 ❯ commitPassiveMountEffects node_modules/react-dom/cjs/react-dom.development.js:24905:3 ❯ flushPassiveEffectsImpl node_modules/react-dom/cjs/react-dom.development.js:27078:3 This error originated in "src/components/CreateNewTodo.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "목표 기본 값으로 세팅하기". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: [vitest] No "getGoals" export is defined on the "@/api/goalAPI" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/api/goalAPI"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError node_modules/vitest/dist/chunks/execute._eQQfgI8.js:320:19 ❯ Object.get node_modules/vitest/dist/chunks/execute._eQQfgI8.js:388:22 ❯ fetchGoalList src/components/CreateNewTodo.tsx:38:28 ❯ src/components/CreateNewTodo.tsx:94:5 ❯ commitHookEffectListMount node_modules/react-dom/cjs/react-dom.development.js:23189:26 ❯ commitPassiveMountOnFiber node_modules/react-dom/cjs/react-dom.development.js:24970:11 ❯ commitPassiveMountEffects_complete node_modules/react-dom/cjs/react-dom.development.js:24930:9 ❯ commitPassiveMountEffects_begin node_modules/react-dom/cjs/react-dom.development.js:24917:7 ❯ commitPassiveMountEffects node_modules/react-dom/cjs/react-dom.development.js:24905:3 ❯ flushPassiveEffectsImpl node_modules/react-dom/cjs/react-dom.development.js:27078:3 This error originated in "src/components/CreateNewTodo.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "목표 기본 값으로 세팅하기". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: [vitest] No "getGoals" export is defined on the "@/api/goalAPI" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/api/goalAPI"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError node_modules/vitest/dist/chunks/execute._eQQfgI8.js:320:19 ❯ Object.get node_modules/vitest/dist/chunks/execute._eQQfgI8.js:388:22 ❯ fetchGoalList src/components/CreateNewTodo.tsx:38:28 ❯ src/components/CreateNewTodo.tsx:94:5 ❯ commitHookEffectListMount node_modules/react-dom/cjs/react-dom.development.js:23189:26 ❯ commitPassiveMountOnFiber node_modules/react-dom/cjs/react-dom.development.js:24970:11 ❯ commitPassiveMountEffects_complete node_modules/react-dom/cjs/react-dom.development.js:24930:9 ❯ commitPassiveMountEffects_begin node_modules/react-dom/cjs/react-dom.development.js:24917:7 ❯ commitPassiveMountEffects node_modules/react-dom/cjs/react-dom.development.js:24905:3 ❯ flushPassiveEffectsImpl node_modules/react-dom/cjs/react-dom.development.js:27078:3 This error originated in "src/components/CreateNewTodo.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "새 할 일 제출하기". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

Error: [vitest] No "getGoals" export is defined on the "@/api/goalAPI" mock. Did you forget to return it from "vi.mock"? If you need to partially mock a module, you can use "importOriginal" helper inside: vi.mock(import("@/api/goalAPI"), async (importOriginal) => { const actual = await importOriginal() return { ...actual, // your mocked methods } }) ❯ VitestMocker.createError node_modules/vitest/dist/chunks/execute._eQQfgI8.js:320:19 ❯ Object.get node_modules/vitest/dist/chunks/execute._eQQfgI8.js:388:22 ❯ fetchGoalList src/components/CreateNewTodo.tsx:38:28 ❯ src/components/CreateNewTodo.tsx:94:5 ❯ commitHookEffectListMount node_modules/react-dom/cjs/react-dom.development.js:23189:26 ❯ commitPassiveMountOnFiber node_modules/react-dom/cjs/react-dom.development.js:24970:11 ❯ commitPassiveMountEffects_complete node_modules/react-dom/cjs/react-dom.development.js:24930:9 ❯ commitPassiveMountEffects_begin node_modules/react-dom/cjs/react-dom.development.js:24917:7 ❯ commitPassiveMountEffects node_modules/react-dom/cjs/react-dom.development.js:24905:3 ❯ flushPassiveEffectsImpl node_modules/react-dom/cjs/react-dom.development.js:27078:3 This error originated in "src/components/CreateNewTodo.test.tsx" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "할 일 수정하기". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

AssertionError: expected "spy" to be called with arguments: [ 1 ] Received: Number of calls: 0 Ignored nodes: comments, script, style <html> <head /> <body> <div> <form class="flex flex-col gap-6" > <div> <h2 class="mb-3 font-semibold" > 제목 </h2> <label class="sr-only" for="title" > 할 일의 제목 </label> <input class="w-full rounded-xl bg-slate-50 px-6 py-3 focus:outline-none" id="title" maxlength="30" name="title" placeholder="할 일의 제목을 적어주세요" required="" value="" /> </div> <div> <h2 class="mb-3 font-semibold" > 자료 </h2> <div class="mb-3 flex gap-3" > <div class="flex w-fit cursor-pointer gap-[7px] rounded-md border p-2 bg-slate-100 text-black" style="pointer-events: none;" > <img alt="checkbox-icon" data-nimg="1" decoding="async" height="18" loading="lazy" src="/modal-unchecked.svg" style="color: transparent;" width="18" /> <span> 파일 업로드 </span> </div> <div class="flex w-fit cursor-pointer gap-[7px] rounded-md border p-2 bg-slate-100 text-black" > <img alt="checkbox-icon" data-nimg="1" decoding="async" height="18" loading="lazy" src="/modal-unchecked.svg" style="color: transparent;" width="18" /> <span> 링크 첨부 </span> </div> </div> <div class="flex h-[184px] w-full cursor-pointer items-center justify-center rounded-xl bg-slate-50" > <div class="text-center text-slate-400" > <div class="hover:underline" > <p> + </p> <p> 파일을 업로드해주세요 </p> </div> <label class="sr-only" for="file-upload" > 파일을 업로드해주세요 </label> <input class="absolute opacity-0" id="file-upload" type="file" /> </div> </div> </div> <div class="relative" > <h2 class="mb-3 font-semibold" data-testid="modal-heading" > 목표 </h2> <div class="flex w-full cursor-pointer justify-between rounded-xl bg-slate-50 px-[20px] py-3" > <p class="text-slate-400" > 목표를 선택해주세요 </p> <img alt="arrowdown-icon" data-nimg="1" decoding="async" height="24" loading="lazy" src="/modal-arrowdown.svg" style="color: transparent;" width="24" /> </div> </div> <button class="mb-6 mt-4 flex h-[50px] w-full items-center justify-center rounded-xl border bg-blue-400 py-3 text-base text-white hover:bg-blue-500 disabled:bg-blue-200" disabled="" type="submit" > 생성 하기 </button> </form> </div> </body> </html> ❯ src/components/CreateNewTodo.test.tsx:87:23 ❯ runWithExpensiveErrorDiagnosticsDisabled node_modules/@testing-library/dom/dist/config.js:47:12 ❯ checkCallback node_modules/@testing-library/d

TestingLibraryElementError: Unable to find an element with the text: 확인. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible. Ignored nodes: comments, script, style <body> <div> <form class="flex flex-col gap-6" > <div> <h2 class="mb-3 font-semibold" > 제목 </h2> <label class="sr-only" for="title" > 할 일의 제목 </label> <input class="w-full rounded-xl bg-slate-50 px-6 py-3 focus:outline-none" id="title" maxlength="30" name="title" placeholder="할 일의 제목을 적어주세요" required="" value="노래 선정" /> </div> <div> <h2 class="mb-3 font-semibold" > 자료 </h2> <div class="mb-3 flex gap-3" > <div class="flex w-fit cursor-pointer gap-[7px] rounded-md border p-2 bg-slate-100 text-black" style="pointer-events: none;" > <img alt="checkbox-icon" data-nimg="1" decoding="async" height="18" loading="lazy" src="/modal-unchecked.svg" style="color: transparent;" width="18" /> <span> 파일 업로드 </span> </div> <div class="flex w-fit cursor-pointer gap-[7px] rounded-md border p-2 bg-slate-100 text-black" > <img alt="checkbox-icon" data-nimg="1" decoding="async" height="18" loading="lazy" src="/modal-unchecked.svg" style="color: transparent;" width="18" /> <span> 링크 첨부 </span> </div> </div> <div class="flex h-[184px] w-full cursor-pointer items-center justify-center rounded-xl bg-slate-50" > <div class="text-center text-slate-400" > <div class="hover:underline" > <p> + </p> <p> 파일을 업로드해주세요 </p> </div> <label class="sr-only" for="file-upload" > 파일을 업로드해주세요 </label> <input class="absolute opacity-0" id="file-upload" type="file" /> </div> </div> </div> <div class="relative" > <h2 class="mb-3 font-semibold" data-testid="modal-heading" > 목표 </h2> <div class="flex w-full cursor-pointer justify-between rounded-xl bg-slate-50 px-[20px] py-3" > <p class="text-slate-400" > 목표를 선택해주세요 </p> <img alt="arrowdown-icon" data-nimg="1" decoding="async" height="24" loading="lazy" src="/modal-arrowdown.svg" style="color: transparent;" width="24" /> </div> </div> <button class="mb-6 mt-4 flex h-[50px] w-full items-center justify-center rounded-xl border bg-blue-400 py-3 text-base text-white hover:bg-blue-500 disabled:bg-blue-200" type="submit" > 생성 하기 </button> </form> </div> </body> ❯ Object.getElementError node_modules/@testing-library/dom/dist/config.js:37:19 ❯ node_modules/@testing-library/dom/dist/query-helpers.js:76:38 ❯ node_modules/@testing-library/dom/dist/query-helpers.js:52:17 ❯ node_modules/@testing-library/dom/dist/query-helpers.js:95:19 ❯ src/components/CreateNewTodo.test.tsx:100:34