Unit Tests #5645
regexowlAnnotations
4 errors and 3 warnings
|
src/test/Components/ImagesTable/ImagesTable.test.tsx > Images Table > render ImagesTable:
src/test/Components/ImagesTable/ImagesTable.test.tsx#L22
Error: expect(element).not.toBeInTheDocument()
expected document not to contain element, found <div
class="pf-v6-c-content"
data-ouia-component-id="OUIA-Generated-Content-4"
data-ouia-component-type="PF6/Content"
data-ouia-safe="true"
data-pf-content="true"
>
Image builder is a tool for creating deployment-ready customized system images: installation disks, virtual machines, cloud vendor-specific images, and others. By using image builder, you can create these images faster than with manual procedures because it eliminates the specific configurations required for each output type.
</div> instead
❯ src/test/Components/ImagesTable/ImagesTable.test.tsx:22:28
|
|
src/test/Components/ImagesTable/ImagesTable.test.tsx > Images Table > render ImagesTable:
src/test/Components/ImagesTable/ImagesTable.test.tsx#L22
Error: expect(element).not.toBeInTheDocument()
expected document not to contain element, found <div
class="pf-v6-c-content"
data-ouia-component-id="OUIA-Generated-Content-3"
data-ouia-component-type="PF6/Content"
data-ouia-safe="true"
data-pf-content="true"
>
Image builder is a tool for creating deployment-ready customized system images: installation disks, virtual machines, cloud vendor-specific images, and others. By using image builder, you can create these images faster than with manual procedures because it eliminates the specific configurations required for each output type.
</div> instead
❯ src/test/Components/ImagesTable/ImagesTable.test.tsx:22:28
|
|
src/test/Components/ImagesTable/ImagesTable.test.tsx > Images Table > render ImagesTable:
src/test/Components/ImagesTable/ImagesTable.test.tsx#L22
Error: expect(element).not.toBeInTheDocument()
expected document not to contain element, found <div
class="pf-v6-c-content"
data-ouia-component-id="OUIA-Generated-Content-2"
data-ouia-component-type="PF6/Content"
data-ouia-safe="true"
data-pf-content="true"
>
Image builder is a tool for creating deployment-ready customized system images: installation disks, virtual machines, cloud vendor-specific images, and others. By using image builder, you can create these images faster than with manual procedures because it eliminates the specific configurations required for each output type.
</div> instead
❯ src/test/Components/ImagesTable/ImagesTable.test.tsx:22:28
|
|
src/test/Components/ImagesTable/ImagesTable.test.tsx > Images Table > render ImagesTable:
src/test/Components/ImagesTable/ImagesTable.test.tsx#L22
Error: expect(element).not.toBeInTheDocument()
expected document not to contain element, found <div
class="pf-v6-c-content"
data-ouia-component-id="OUIA-Generated-Content-1"
data-ouia-component-type="PF6/Content"
data-ouia-safe="true"
data-pf-content="true"
>
Image builder is a tool for creating deployment-ready customized system images: installation disks, virtual machines, cloud vendor-specific images, and others. By using image builder, you can create these images faster than with manual procedures because it eliminates the specific configurations required for each output type.
</div> instead
❯ src/test/Components/ImagesTable/ImagesTable.test.tsx:22:28
|
|
Cockpit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Unit Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|
|
Service Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
|