You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 setenv=prod
insideconnect-automation-config-prod.json
file.For local testing of this workflow you may to the next steps:
connect-automation-config-dev.json
intoconnect-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 test should still run.The text was updated successfully, but these errors were encountered: