next.js

c94fdefd - test utils: Include origin of failed `browser.*` in stack (#74553)

test utils: Include origin of failed `browser.*` in stack (#74553) i.e. the stack will now include the actual test util in the test that failed not just a single frame from util internals. New stack for e.g. a failed `waitForElementByCSS`: ```diff ● app dir - navigation with Suspense in nested layout › resolves data after client navigation to a nested layout with Suspense page.waitForSelector: Timeout 1000ms exceeded. Call log: - waiting for locator('[data-testid="nested-resolved"]') 423 | return this.chain(() => { 424 | return page > 425 | .waitForSelector(selector, { timeout, state: 'attached' }) | ^ 426 | .then(async (el) => { 427 | // it seems selenium waits longer and tests rely on this behavior 428 | // so we wait for the load event fire before returning at waitForSelector (lib/browsers/playwright.ts:425:10) + at BrowserInterface.chain (lib/browsers/base.ts:17:23) + at BrowserInterface.chain [as waitForElementByCss] (lib/browsers/playwright.ts:423:17) + at Object.waitForElementByCss (e2e/app-dir/navigation-layout-suspense/navigation-layout-suspense.test.ts:17:19) ``` Ideally we'd just display the stack starting by `at Object.waitForElementByCss` but that would mean passing a sync error from each `this.chain` callsite and this may actually hide internal errors and I'm not sure of the interaction with actual chaining e.g. `browser.waitForElementByCSS().click().waitForElementByCSS()`. This is improves readability of CI errors by a lot with minimal changes.