Process completed with exit code 1.

Process completed with exit code 1.

4) [default] › tests\request\response-pane-update-when-focused.spec.ts:30:7 › Response pane updates when focused and request is re-sent › Response pane shows new response after re-send with Cmd+Enter while focused in response Error: locator.click: Target page, context or browser has been closed Call log: - waiting for getByRole('button', { name: 'Discard All and Remove' }) - locator resolved to <button type="button">…</button> - attempting click action 2 × waiting for element to be visible, enabled and stable - element is not stable - retrying click action - waiting 20ms 2 × waiting for element to be visible, enabled and stable - element is not stable - retrying click action - waiting 100ms - waiting for element to be visible, enabled and stable - element is not stable - retrying click action - waiting 500ms - waiting for element to be visible, enabled and stable - element was detached from the DOM, retrying at tests\utils\page\actions.ts:30 28 | if (hasDiscardButton) { 29 | // Drafts modal - click "Discard All and Remove" > 30 | await page.getByRole('button', { name: 'Discard All and Remove' }).click(); | ^ 31 | } else { 32 | // Regular modal - click the submit button 33 | await page.locator('.bruno-modal-footer .submit').click(); at D:\a\bruno\bruno\tests\utils\page\actions.ts:30:76 at closeAllCollections (D:\a\bruno\bruno\tests\utils\page\actions.ts:12:3) at D:\a\bruno\bruno\tests\request\response-pane-update-when-focused.spec.ts:27:5

4) [default] › tests\request\response-pane-update-when-focused.spec.ts:30:7 › Response pane updates when focused and request is re-sent › Response pane shows new response after re-send with Cmd+Enter while focused in response "afterAll" hook timeout of 30000ms exceeded. 24 | }); 25 | > 26 | test.afterAll(async ({ page }) => { | ^ 27 | await closeAllCollections(page); 28 | }); 29 | at D:\a\bruno\bruno\tests\request\response-pane-update-when-focused.spec.ts:26:8

3) [default] › tests\preferences\default-collection-location\default-collection-location.spec.js:62:7 › Default Location Feature › Should use default location in Create Collection modal Error: expect(received).toBe(expected) // Object.is equality Expected: true Received: false 79 | 80 | const inputValue = await collectionLocationInput.inputValue(); > 81 | expect(inputValue.endsWith(EXPECTED_PATH_SUFFIX)).toBe(true); | ^ 82 | 83 | // cancel the collection creation 84 | await page.locator('.bruno-modal').getByRole('button', { name: 'Cancel' }).click(); at D:\a\bruno\bruno\tests\preferences\default-collection-location\default-collection-location.spec.js:81:55

2) [default] › tests\environments\import-environment\collection-env-import.spec.ts:10:7 › Collection Environment Import Tests › should import collection environment from file Error: Timed out 5000ms waiting for expect(locator).toHaveValue(expected) Locator: locator('input[name="4.name"]') Expected string: "postBody" Received: <element(s) not found> Call log: - expect.toHaveValue with timeout 5000ms - waiting for locator('input[name="4.name"]') 59 | await expect(page.locator('input[name="2.name"]')).toHaveValue('apiKey'); 60 | await expect(page.locator('input[name="3.name"]')).toHaveValue('postTitle'); > 61 | await expect(page.locator('input[name="4.name"]')).toHaveValue('postBody'); | ^ 62 | await expect(page.locator('input[name="5.name"]')).toHaveValue('secretApiToken'); 63 | await expect(page.locator('input[name="5.secret"]')).toBeChecked(); 64 | await envTab.hover(); at D:\a\bruno\bruno\tests\environments\import-environment\collection-env-import.spec.ts:61:56

1) [default] › tests\runner\collection-run-report\collection-run-report.spec.ts:23:7 › Collection Run Report Tests › CLI: Run collection and generate JUnit report Error: A snapshot doesn't exist at D:\a\bruno\bruno\tests\runner\collection-run-report\collection-run-report.spec.ts-snapshots\cli-junit-report-default-win32.xml, writing actual. 40 | // Snapshot the normalized XML 41 | const normalizedJunitReport = normalizeJunitReport(junitReportContent); > 42 | expect(normalizedJunitReport).toMatchSnapshot('cli-junit-report.xml'); | ^ 43 | }); 44 | }); 45 | at D:\a\bruno\bruno\tests\runner\collection-run-report\collection-run-report.spec.ts:42:35

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, actions/upload-artifact@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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/

15 passed (1.9m)