Working branch: feature/test-automation-envs.
We are going to run smoke tests against PROD and DEV environments as implemented in #4526.
But for PROD we cannot provide credentials for copilotManagerRole user because it is a too powerful user.
We have to update smoke tests, so the cases which require copilotManagerRole would be skipped and would not run if we run tests against PROD env. But they would still run for other environments. To identify PROD env we would set env=prod inside connect-automation-config-prod.json file.
For local testing of this workflow you may to the next steps:
- copy
connect-automation-config-dev.json into connect-automation-config-prod.json and inside this file:
- set
"env": "prod"
- remove config for
copilotManagerRole
- run
npm run test:prod
All the smoke tests should work good, and only tests which depend on copilotManagerRole should be skipped. Other test should still run.