Test Configuration data leaking into configuration for describe.only & it.only blocks

[emilyrohrbough]

Current behavior

@davidmunechika discovered the test configuration was not applying correctly for single suite/test execution. When Cyress starts, the runner normalize's the mocha runnables, which is where we determine the expected test configuration. When the runner filters for a suite or test that has marked as the only one that should run, the runner re-normalizes the mocha runnables. At this point, the test configuration has been formatted with the invocation details to determine where the configuration has been passed if the configuration fails its validation.

Desired behavior

The test configuration should not leak the testConfigList or unverifiedTestOverrides data onto the configuration when a suite or test is marked as the only block to execute.

Test code to reproduce

describe('my suite', () => {
  describe.only('my nested suite', () => {
    it('my test', () => {
      expect(Cypress.config('testConfigList')).to.be.undefined
      expect(Cypress.config('unverifiedTestConfig')).to.be.undefined
    })
  })
})

describe('my suite', () => {
  it.only('my test', () => {
    expect(Cypress.config('testConfigList')).to.be.undefined
    expect(Cypress.config('unverifiedTestConfig')).to.be.undefined
  })
})

Cypress Version

9.0.0

Other

No response

[cypress-bot]

The code for this is done in cypress-io/cypress#18961, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 9.1.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v9.1.0, please open a new issue.