Skip to content

v3.2.4 broke timeout inheritance from describe when using test.extend() #8277

@jgoux

Description

@jgoux

Describe the bug

Prior to v3.2.4, when we define a timeout on any describe, the timeout is then inherited by test within the describe block(s), even when test is a custom one created with test.extend().

This is no longer true in v3.2.4.

Reproduction

https://stackblitz.com/edit/stackblitz-starters-znqdgkrg?file=index.test.js

Run :

npm test

Related discussion on Discord

https://discord.com/channels/917386801235247114/1391760237396099216

System Info

System:
    OS: macOS 15.5
    CPU: (8) arm64 Apple M3
    Memory: 303.13 MB / 24.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 24.1.0 - ~/.nvm/versions/node/v24.1.0/bin/node
    npm: 11.3.0 - ~/.nvm/versions/node/v24.1.0/bin/npm
    pnpm: 10.12.1 - ~/.nvm/versions/node/v24.1.0/bin/pnpm
    bun: 1.2.8 - /opt/homebrew/bin/bun
  Browsers:
    Chrome: 137.0.7151.122
    Safari: 18.5
  npmPackages:
    vitest: 3.2.3 => 3.2.3

(I'm stuck on 3.2.3 because of this)

Used Package Manager

pnpm

Validations

Metadata

Metadata

Assignees

No one assigned

    Labels

    p3-minor-bugAn edge case that only affects very specific usage (priority)

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions