Smoke Testing approach

Objective:

The objective of performing smoke testing is to ensure that the most important features of the TIS Admins-UI are working as expected. It's non-exhausting testing with a very limited number of test cases will be executed against the prod environment to verify that the critical functionality of the system is working fine. Example: User Login to TIS with the login Credentials and verify that TIS Admin UI has launched successfully and GUI is responding.

Smoke Testing Scope for TIS:
A test pack with a limited number of tests to verify the basic functionalities are working fine will be executed. The test pack will not be creating any data in the database and will only be verifying the application basic functionalities by executing below feature scenarios:

1. User can log in to TIS successfully with test user credentials

2. TIS ADMIN-UI GUI has launched successfully with data

3. User can navigation to multiple components of TIS including (People, Post, programme, Assessment, Curriculum, speciality-group)

4. Components GUI is loaded successfully with table data

5. Smart search with table data is displayed for all components

6. pagination is displayed with table data

7. Column sorting and filtering is available on table headers

8. Apply and remove column sorting to sort the table records

9. Apply and remove column Filtering to filter the table records

10. User can click and view on a table record

'./e2e/authorise/authorise.spec.ts',
'./e2e/app/**/*.spec.ts',
'./e2e/assessments/assessments.component.spec.ts',
'./e2e/tcs/people/people.component.spec.ts',
'./e2e/tcs/curriculum/curriculum.component.spec.ts',
'./e2e/tcs/post/post.component.spec.ts',
'./e2e/tcs/programme/programme.component.spec.ts',
'./e2e/tcs/specialty-group/specialty-group-list.component.spec.ts'

Out of scope:
Any tests which can make any changes in the database including creating/delete/edit/upload operation across TIS Admin UI.

Environment to run against: Production

The process to run smoke tests in Jenkins pipeline:

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.

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.

Github Repository: https://github.com/Health-Education-England/TIS-ADMINS-UI