...
After every deployment to production:
Once the E2E test run against Staging environment to test the new changes and changes gets deployed to production, Smoke tests should be running after every change which gets deployed to production to make sure any new changes are not breaking the basic functionality of the application in Production and report will be sent to slack channel.
A new step will be required to add in Jenkins file after the code gets deployed to production to run test smoke test pack.Smoke test pack step has been added to Jenkins pipeline and running after any new changes get deployed to production to make sure any new deployment is not breaking basic functionality of the Production and sending smoke test report notification to notifications-e2e-test-results.
 |
Scheduled nightly job: A scheduled Jenkins job with a schedule to run against production every night will execute a smoke test pack. The test report will be sent in the Slack channel to notify the team like existing e2e test results.
Next Steps to follow: 1. Add smoke test pack in existing Jenkins pipeline to run against production after any changes pushed to production.
2. Create a separate Jenkins job so that test can be scheduled to run nightly.Test user creation with all required permission for productionjob (GithubActions) to run on a scheduled basis nightly. The ticket can be found herehttps://hee-tis.atlassian.net/browse/TISNEW-4766
User credentials: Smoke test user has been created and user credentials have been added to Jenkins to run test against production.
Github Repository: https://github.com/Health-Education-England/TIS-ADMINS-UI
...