flndrn-dev c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
..
components c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
config c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
features c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
lib c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
pages c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
setup c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
unit c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
README.md c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
fixtures.ts c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
helpers.tsx c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja
vitestSetup.ts c5aa765f6b feat(studio): fork supabase studio + rebrand to briven (phases 0-5.1) 3 hónapja

README.md

UI Testing Notes

Rules

  • All tests should be run consistently (avoid situations whereby tests fails "sometimes")

  • Group tests in folders based on the feature they are testing. Avoid file/folder based folder names since those can change and we will forget to update the tests.

Examples: /logs /reports /projects /database-settings /auth

Custom Render and Custom Render Hook

customRender and customRenderHook are wrappers around render and renderHook that add some necessary providers like QueryClientProvider, TooltipProvider and NuqsTestingAdapter.

Generally use those instead of the default render and renderHook functions.

import { customRender, customRenderHook } from 'tests/lib/custom-render'

customRender(<MyComponent />)
customRenderHook(() => useMyHook())

Mocking API Requests

To mock API requests, we use the msw library.

Global mocks can be found in tests/lib/msw-global-api-mocks.ts.

To mock an endpoint you can use the addAPIMock function. Make sure to add the mock in the beforeEach hook. It won't work with beforeAll if you have many tests.

beforeEach(() => {
  addAPIMock({
    method: 'get',
    path: '/api/my-endpoint',
    response: {
      data: { foo: 'bar' },
    },
  })
})

API Mocking Tips:

  • Keep mocks in the same folder as the tests that use them
  • Add a test to verify the mock is working

This will make debugging and updating the mocks easier.

test('mock is working', async () => {
  const response = await fetch('/api/my-endpoint')
  expect(response.json()).resolves.toEqual({ data: { foo: 'bar' } })
})

Mocking Nuqs URL Parameters

To render a component that uses Nuqs with some predefined query parameters, you can use customRender with the nuqs prop.


customRender(<MyComponent />, {
  nuqs: {
    searchParams: {
      search: 'hello world',
    },
  },
})

<Popover> vs <Dropdown>

When simulating clicks on these components, do the following:

// for Popovers
import userEvent from '@testing-library/user-event'
await userEvent.click('Hello world')

// for Dropdowns
import clickDropdown from 'tests/helpers'
clickDropdown('Hello world')