--env doesn't work when using globbing/filename expansion in --spec

Is this a Feature or Bug?

Bug

Current behavior:

cypress run --env foo=bar --spec=cypress/integration/**/*.js

does not add foo to the environment variables (cy.env('foo') returns undefined). It works though if I don’t use globs in the spec path.

Desired behavior:

I want to be able to use globbing/filename expansion in the --spec argument and also pass in an environment variable using --env.

Use case: I’m running the same tests on two different projects (using data-cy props) that implement basically the same thing, but one has additional routes. (Yes, I know this is painful to maintain, but it’s a three year old codebase and tests are the first step to start refactoring).

Workaround:

This works:

CYPRESS_foo=bar cypress run --spec=cypress/integration/**/*.js

I’m ok with that workaround but thought I’d leave this here FYI.

Versions

cypress@2.1.0, latest Chrome, macOS 10.13.4

[brian-mann]

Quote your --spec argument or use equals.

--spec=foo or --spec 'foo'

[simonhaenisch]

Thanks for that info, that’s what I needed to know…

According to isaacs/node-glob#glob-primer this syntax works:

--env foo=bar --spec='cypress/integration/@(dir1|dir2)/**/*.js'