Description

Fixes #6226

Related #7188

const test = baseTest.extend({
  name: 'Vladimir',
  action: ({ name }, use) => use(`${name} is typing`)
})

describe('default behaviour', () => {
  test('Vladimir is typing', ({ action }) => {
    expect(action).toBe('Vladimir is typing')
  })
})

describe('custom behaviour', () => {
  test.scoped({ name: 'Hiroshi' }) // all tests in this suite inherit the value

  test('Hiroshi is typing', ({ action }) => {
    expect(action).toBe('Hiroshi is typing')
  })
})

describe('custom behaviour', () => {
  test.scoped({ name: 'Ari' }) // all tests in this suite inherit the value

  test('Ari is typing', ({ action }) => {
    expect(action).toBe('Ari is typing')
  })
})

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.