Nested .only is ignored

[Floriferous]

Current behavior:

When a describe with a .only contains an it with a .only as well, it ignores the second one and runs the full test suite.

Desired behavior:

The nested it should be the only test that is run.

Steps to reproduce: (app code and test code)

// Both tests are being run
describe.only('suite', () => {
  it('should not run this test');

  it.only('should only run this test');
})

Versions

Cypress 3.1.5

[flotwig]

The second .only will be superseded by the first .only. Cypress is based on Mocha 2.x, and before Mocha 3, only one .only can be used at a time:

Previous to v3.0.0, .only() used string matching to decide which tests to execute; this is no longer the case. In v3.0.0 or newer, .only() can be used multiple times to define a subset of tests to run
https://mochajs.org/#exclusive-tests

If you want to run only that one test case, use the it.only. If you only want to run that describe, use the describe.only.

[Floriferous]

Okay, and what is preventing cypress from using mocha v3?

…

On 25 Mar 2019, at 21:33, Zach Bloomquist ***@***.***> wrote: The second .only will be superseded by the first .only. Cypress is based on Mocha 2.x, and before Mocha 3, only one .only can be used at a time: Previous to v3.0.0, .only() used string matching to decide which tests to execute; this is no longer the case. In v3.0.0 or newer, .only() can be used multiple times to define a subset of tests to run https://mochajs.org/#exclusive-tests If you want to run only that one test case, use the it.only. If you only want to run that describe, use the describe.only. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[flotwig]

@Floriferous It would be a potentially breaking change for existing users. Cypress will upgrade to Mocha v5.2.0 as part of the next major release, v4.0 v5.0: #2703