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 wm-automation-config-prod.json file.
For local testing of this workflow you may to the next steps:
copy wm-automation-config-dev.json into wm-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 tests should still run.
Do the same as we did for Connect App in this issue https://github.com/appirio-tech/connect-app/issues/4527
Working branch:
feature/test-automation-2
.We are going to run smoke tests against PROD and DEV environments as implemented in https://github.com/topcoder-platform/work-manager/issues/1231.
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 setenv=prod
insidewm-automation-config-prod.json
file.For local testing of this workflow you may to the next steps:
wm-automation-config-dev.json
intowm-automation-config-prod.json
and inside this file:"env": "prod"
copilotManagerRole
npm run test:prod
All the smoke tests should work good, and only tests which depend on
copilotManagerRole
should be skipped. Other tests should still run.