test_output_2.txt

> test
> vitest run


 RUN  v4.0.18 C:/Users/heman/Downloads/form-engine-frontend

 ✓ src/App.test.tsx (1 test) 165ms
 ✓ src/hooks/use-mobile.test.ts (3 tests) 49ms
 ✓ src/lib/auth-client.test.ts (1 test) 23ms
 ✓ src/components/ui/badge.test.tsx (2 tests) 1028ms
     ✓ renders text content  775ms
 ✓ src/lib/utils.test.ts (7 tests) 12ms
 ✓ src/components/ui/button.test.tsx (5 tests) 3213ms
     ✓ renders children correctly  2524ms
     ✓ handles click events  402ms
 ✓ src/components/ui/complex-primitives.test.tsx (4 tests) 2613ms
       ✓ renders and status reflects change  2149ms
 ✓ src/components/Header.test.tsx (2 tests) 3265ms
     ✓ renders the logo  734ms
     ✓ opens and closes the mobile menu  2526ms
 ✓ src/components/fields/field-items.test.tsx (2 tests) 3325ms
     ✓ renders all field labels  984ms
     ✓ renders labels as buttons  2327ms
 ✓ src/components/ui/field.test.tsx (10 tests) 3442ms
       ✓ renders with vertical orientation by default  2589ms
 ✓ src/components/ui/input.test.tsx (5 tests) 4196ms
     ✓ renders correctly with initial value  3125ms
     ✓ updates value on change  873ms
stderr | src/components/app-sidebar.test.tsx > AppSidebar > renders the sidebar with correct title
An update to Transitioner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
An update to Transitioner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
An update to MatchesInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
An update to MatchesInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
An update to Transitioner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act

stderr | src/components/app-sidebar.test.tsx > AppSidebar > renders navigation links
An update to Transitioner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
An update to Transitioner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
An update to MatchesInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
An update to MatchesInner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act
An update to Transitioner inside a test was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://react.dev/link/wrap-tests-with-act

 ❯ src/components/app-sidebar.test.tsx (2 tests | 2 failed) 558ms
     × renders the sidebar with correct title 506ms
     × renders navigation links 36ms
 ✓ src/components/fields/field-preview.test.tsx (6 tests) 1729ms
     ✓ calls onRemove when the trash icon is clicked  1074ms
 ✓ src/components/ui/primitives.test.tsx (6 tests) 1363ms
       ✓ renders and handles toggle  1154ms
 ✓ src/components/editor-canvas.test.tsx (3 tests) 1847ms
     ✓ renders empty state when no fields are provided  1487ms
stdout | src/components/editor-sidebar-tabs.test.tsx > TabsLine > calls onFieldClick when a field is clicked
Field button clicked: text

 ✓ src/components/editor-sidebar-tabs.test.tsx (3 tests) 1952ms
     ✓ renders the initial tab (Fields) correctly  1335ms
     ✓ switches tabs correctly  421ms
 ✓ src/components/field-properties.test.tsx (5 tests) 2572ms
     ✓ renders with initial field values when open  1275ms
     ✓ updates state and calls onSave with new values  1037ms

⎯⎯⎯⎯⎯⎯⎯ Failed Tests 2 ⎯⎯⎯⎯⎯⎯⎯

 FAIL  src/components/app-sidebar.test.tsx > AppSidebar > renders the sidebar with correct title
TestingLibraryElementError: Unable to find an element with the text: Form Builder. 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>
    <div
      class="group/sidebar-wrapper has-data-[variant=inset]:bg-sidebar flex min-h-svh w-full"
      data-slot="sidebar-wrapper"
      style="--sidebar-width: 16rem; --sidebar-width-icon: 3rem;"
    />
  </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/app-sidebar.test.tsx:48:23
     46|             </SidebarProvider>
     47|         );
     48|         expect(screen.getByText('Form Builder')).toBeInTheDocument();
       |                       ^
     49|     });
     50| 

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/2]⎯

 FAIL  src/components/app-sidebar.test.tsx > AppSidebar > renders navigation links
TestingLibraryElementError: Unable to find an element with the text: Dashboard. 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>
    <div
      class="group/sidebar-wrapper has-data-[variant=inset]:bg-sidebar flex min-h-svh w-full"
      data-slot="sidebar-wrapper"
      style="--sidebar-width: 16rem; --sidebar-width-icon: 3rem;"
    />
  </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/app-sidebar.test.tsx:58:23
     56|             </SidebarProvider>
     57|         );
     58|         expect(screen.getByText('Dashboard')).toBeInTheDocument();
       |                       ^
     59|         expect(screen.getByText('Editor')).toBeInTheDocument();
     60|         expect(screen.getByText('Analytics')).toBeInTheDocument();

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/2]⎯


 Test Files  1 failed | 16 passed (17)
      Tests  2 failed | 65 passed (67)
   Start at  00:10:55
   Duration  17.66s (transform 22.78s, setup 62.58s, import 68.68s, tests 31.35s, environment 37.15s)