Cypress configuration
Explanations about how Cypress is configured by Next Right Now, and how you can extend the default configuration.
Table of contents
When using MST tenancy
When you’re using a MST tenancy, you will have one Cypress config file per tenant, because each tenant has its own dedicated production app and domain. There is also another config file for development usage (local).
Update cypress/config-*.json and update the baseUrl so that it matches with their respective production url.
When not using MST tenancy
When you’re not using a MST tenancy, you will only have one Cypress config file. There is also another config file for development usage (local).
Update cypress/config-production.json and update the baseUrl so that it matches the project’s production url.
Cypress plans and pricing
Next Right Now doesn’t use a paid version of Cypress (no Dashboard available). We don’t use their infrastructure to host our tests, since they’re executed on GitHub Actions.
Therefore, you don’t have to pay for Cypress.
But, if you wish to benefit from the Cypress Dashboard and store your Cypress recordings then you might be interested in buying a Cypress plan.
If you buy a plan, you should set the
orgIdin all yourcypress/config-*.jsonso that recordings will be stored on your Cypress account, and can then be accessed through the Dashboard.Alternatively, you could also add it only to
cypress/config-customer-ci-cd.jsonif you only wish to track recordings performed through CI/CD, but not the local runs.