Passing parameters to cypress using cli

Hi,

Is There a way we can pass command line arguments to a cypress script in order to make it truly scalable .

To explain in detail , We have a script a.js That selects some values from list boxes(As of now these values are hardcode) . If there is a way we can parametrize these values , then the same script can be used to select multiple values

[must-git-good]

krishvv,

I’m pretty sure you can already achieve what you want here through the use of environment variables (which you can specify in the command line). While your use case is slightly different, see https://on.cypress.io/configuration-api#Usage for a general example.

We, for example, load up a bunch of different configurations depending on our environment. You can extend this beyond just route/visit. The note at the end of the page is especially important to remember…it’s just js, so you can make things as programmatically variable as you’d like.

So, loosely, in your case, you might have a cypress/config/ folder which contains (in .js or json, depending on your setup) a legalname.js, releaselevel.js, (etc). Which config context is invoked here is called (from the example above) from the cli when you open Cypress.

Then within that file you define variable that are different for each setup. So your code becomes:

it('.select() - select an option in a element', () => {
  cy.get(  ${Cypress.config('releaseVersion')}  )
    .select( ${Cypress.config('graphicsDriverOptions')} ) 
 })

Of course that’s just a general abstraction after a brief glance at what you need. But it should give an idea of how to accomplish what you want. It’s probably not the only solution, but it’s the one that seems to be the easiest ‘fit’ for your situation. Hope it helps.

[jennifer-shehane]

Issues in our GitHub repo are reserved for potential bugs or feature requests. This issue will be closed since it appears to be neither a bug nor a feature request.

We recommend questions relating to how to use Cypress be asked in our community chat. Also try searching our existing GitHub issues, reading through our documentation, or searching Stack Overflow for relevant answers.

Alternatively, signing up for any of you paid plans gives you access to our team for support via email. If you would like something higher touch, we also offer screen sharing and workshops with our premium support options.