test/development/app-dir/use-cache-custom-handler-dev/use-cache-custom-handler-dev.test.ts - canary - githubmirror/next.js

test/development/app-dir/use-cache-custom-handler-dev/use-cache-custom-handler-dev.test.ts
121 строка5 KB
Hendrik Liebau
[test] Unflake `use-cache-custom-handler-dev` tests (#97187)
10 часов назад
10 часов назадb93ed4f
import { nextTestSetup } from 'e2e-utils'
import { retry, waitFor } from 'next-test-utils'

describe('use-cache-custom-handler-dev', () => {
  const { next, skipped } = nextTestSetup({
    files: __dirname,
  })

  if (skipped) {
    return
  }

  // Reads the rendered cache value over HTTP instead of through the browser. A
  // dev page reload costs seconds on a CI runner, almost all of it downloading
  // and evaluating the dev bundle, which keeps a retried read from fitting in
  // its budget. The value is server-rendered, so a plain request observes the
  // same cache state for a fraction of the cost.
  async function readCachedValue(pathname: string): Promise<string> {
    const $ = await next.render$(pathname)
    const value = $('#value')

    // Without this the callers, which all assert that the value changed, would
    // accept the empty string that a missing element yields.
    if (value.length === 0) {
      throw new Error(`Found no cached value in the HTML of ${pathname}.`)
    }

    return value.text()
  }

  it('shows the Cold cache badge on a cold load but not on a warm reload through a slow custom handler', async () => {
    const browser = await next.browser('/cold-badge')

    // Cold load: the cache misses and fills while streaming, so the cold
    // verdict is reported and (once the dev overlay's socket connects) the
    // badge appears.
    await browser.elementById('value')
    await retry(async () => {
      expect(await browser.hasElementByCss('[data-cold-cache-badge]')).toBe(
        true
      )
    })
    expect(
      await browser
        .elementByCss('[data-cold-cache-badge] [data-issues-open]')
        .text()
    ).toBe('Cold cache')

    // Warm reload: the built-in front serves the entry in a microtask, so the
    // read isn't pending at a staged render boundary and no cold verdict is
    // reported - even though the custom handler's own `get` is slow. Without
    // the front, that slow `get` would make this a phantom cold miss. An
    // absence can't be retried on, so wait out the replay window, then assert
    // it never appeared.
    await browser.refresh()
    await browser.elementById('value')
    await waitFor(500)
    expect(await browser.hasElementByCss('[data-cold-cache-badge]')).toBe(false)
  })

  it('serves a short-expire value warm through a custom handler and re-warms it on each reload', async () => {
    const browser = await next.browser('/expire-zero', {
      waitHydration: false,
      // Do not wait for "load"; inspect the page as it streams in.
      waitUntil: 'commit',
    })

    // Cold load: the custom handler misses, the value generates and is written
    // through to both the backing handler and the dev-only in-memory front. We
    // wait for the streamed-in element without waiting for "load".
    const coldValue = await browser
      .elementByCss('#value', { waitUntil: false })
      .text()
    expect(coldValue).toBeDateString()

    // Warm reload: served fast from the front, whose minimum retention keeps
    // the short-`expire` entry. The custom handler's slow `get` isn't on the
    // critical path, and the short `expire` no longer evicts the front entry on
    // every read, so the same cached value shows.
    await browser.refresh({ waitUntil: 'commit' })
    expect(
      await browser.elementByCss('#value', { waitUntil: false }).text()
    ).toBe(coldValue)

    // Each warm read re-executes the cache function in the background and
    // writes through to the backing, so reads converge to a fresh value. More
    // than one read is needed, because the regeneration that the previous one
    // started has not been written yet.
    await retry(async () => {
      expect(await readCachedValue('/expire-zero')).not.toBe(coldValue)
    })
  })

  it('stops serving a front-cached entry after the backing cache is purged out-of-band', async () => {
    const browser = await next.browser('/purged')

    // Cold load: the custom handler misses, the value generates and is written
    // through to both the backing handler and the dev-only in-memory front.
    const coldValue = await browser.elementById('value').text()

    // Warm reload: served from the front. Its real cache life keeps it
    // shell-eligible, so the same cached value shows immediately.
    await browser.refresh()
    expect(await browser.elementById('value').text()).toBe(coldValue)

    // Purge the backing handler out-of-band. The front still holds the entry,
    // so it would keep serving the stale value indefinitely if the tiered
    // handler didn't evict it.
    await next.fetch('/purge')

    // The reconcile can only evict the front entry once it has observed the
    // backing miss, so the read that observes it still serves the front copy
    // one last time. Reads converge on a freshly generated value instead of
    // serving the purged copy forever. How many reads that takes is not fixed:
    // the reconcile runs in the background, so a read that lands before it
    // finishes still gets the front copy.
    await retry(async () => {
      expect(await readCachedValue('/purged')).not.toBe(coldValue)
    })
  })
})