If you run Cucumber and standard Cypress you cannot use not tags

[PaulDotmatics]

Current behavior

If I have a test like

describe('My First Test', () => {
it('Does not do much!', () => {
expect(true).to.equal(true)
})
})

and also have cucumber scenarios if I run the suite with

cypress open -env TAGS='not @test'

then My first test wont appear in the run at all. If I dont pass -env TAGS='not @test' then they appear

Desired behavior

Should allow the use of not tags and still allow other tests to appear that arent cucumber scenarios

Test code to reproduce

describe('My First Test', () => {
it('Does not do much!', () => {
expect(true).to.equal(true)
})
})

Feature: duckduckgo.com
@test
Scenario: visiting the frontpage
When I visit duckduckgo.com
Then I should see a search bar

Versions

• Cypress version: 13.5.0
• Preprocessor version:19.1.0
• Node version:v20.5.0

[badeball]

I don't feel strongly about the behavior here and absence of other requirements, I'm inclined to agree. I've fixed this with v19.1.1.

[badeball]

I've sort of reverted 0b2702b and introduced an option to control this behavior. If you want negative expressions to include non-Cucumber specs, you now need to set filterSpecsMixedMode to "empty-set".