tests: add more unit tests to cover markdown related components #2467
jderochervlkAnnotations
5 errors and 3 warnings
|
Vitest
Process completed with exit code 1.
|
|
[chromium] __tests__/SidebarLayout_.test.jsx > sidebar category with active TOC renders entries:
__tests__/SidebarLayout_.test.jsx#L145
Error: strict mode violation: getByTestId('__vitest_0__').getByText('Overview') resolved to 2 elements:
1) <div class="hl-overline text-gray-80 mt-5">Overview</div> aka locator('div').filter({ hasText: /^Overview$/ })
2) <a data-discover="true" href="/docs/manual/introduction#overview" class="font-normal block text-14 text-gray-40 leading-tight hover:text-gray-80">Overview</a> aka getByRole('link', { name: 'Overview' })
❯ __tests__/SidebarLayout_.test.jsx:145:40
Caused by: Caused by: Error: Matcher did not succeed in time.
❯ __tests__/SidebarLayout_.test.jsx:145:2
|
|
[chromium] __tests__/DocsLayout_.test.jsx > desktop docs layout shows pagination (prev/next):
__tests__/DocsLayout_.test.jsx#L184
Error: strict mode violation: getByTestId('__vitest_0__').getByText('Introduction') resolved to 2 elements:
1) <a data-discover="true" href="/docs/manual/introduction" class="block py-1 md:h-auto tracking-tight text-gray-60 rounded-sm hover:bg-gray-20 hover:-ml-2 hover:py-1 hover:pl-2 ">Introduction</a> aka locator('#sidebar-content').getByRole('link', { name: 'Introduction' })
2) <a data-discover="true" href="/docs/manual/introduction" class="flex items-center text-fire hover:text-fire-70 border-2 border-red-300 rounded py-1.5 px-3">…</a> aka getByTestId('side-layout-children').getByRole('link', { name: 'Introduction' })
❯ __tests__/DocsLayout_.test.jsx:184:40
Caused by: Caused by: Error: Matcher did not succeed in time.
❯ __tests__/DocsLayout_.test.jsx:184:2
|
|
[chromium] __tests__/DocsLayout_.test.jsx > desktop docs layout highlights active nav item:
__tests__/DocsLayout_.test.jsx#L158
Error: strict mode violation: getByTestId('__vitest_0__').getByText('Installation') resolved to 2 elements:
1) <a data-discover="true" href="/docs/manual/installation" class="block py-1 md:h-auto tracking-tight text-gray-60 rounded-sm hover:bg-gray-20 hover:-ml-2 hover:py-1 hover:pl-2 bg-fire-5 text-red-500 leading-5 -ml-2 pl-2 font-medium block hover:bg-fire-70 ">Installation</a> aka getByRole('link', { name: 'Installation' }).first()
2) <a data-discover="true" href="/docs/manual/installation#installation" class="font-normal block text-14 text-gray-40 leading-tight hover:text-gray-80">Installation</a> aka getByTestId('Installation').getByRole('link', { name: 'Installation' })
❯ __tests__/DocsLayout_.test.jsx:158:43
Caused by: Caused by: Error: Matcher did not succeed in time.
❯ __tests__/DocsLayout_.test.jsx:158:2
|
|
[chromium] __tests__/ApiLayout_.test.jsx > desktop API layout shows sidebar categories and version select:
__tests__/ApiLayout_.test.jsx#L63
Error: strict mode violation: getByTestId('__vitest_0__').getByText('Belt') resolved to 3 elements:
1) <div class="hl-overline text-gray-80 mt-5">Belt</div> aka getByText('Belt', { exact: true })
2) <a data-discover="true" href="/docs/manual/api/belt/array" class="block py-1 md:h-auto tracking-tight text-gray-60 rounded-sm hover:bg-gray-20 hover:-ml-2 hover:py-1 hover:pl-2 ">Belt.Array</a> aka getByRole('link', { name: 'Belt.Array' })
3) <a data-discover="true" href="/docs/manual/api/belt/map" class="block py-1 md:h-auto tracking-tight text-gray-60 rounded-sm hover:bg-gray-20 hover:-ml-2 hover:py-1 hover:pl-2 ">Belt.Map</a> aka getByRole('link', { name: 'Belt.Map' })
❯ __tests__/ApiLayout_.test.jsx:63:36
Caused by: Caused by: Error: Matcher did not succeed in time.
❯ __tests__/ApiLayout_.test.jsx:63:2
|
|
Format
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Site_Checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Vitest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|