Context: For all other functionality that either spans multiple epics, or doesn’t fall neatly within an epic, the following stories were tested to ensure full coverage of acceptance criteria and user feedback.
Story reference (enter name & ticket link)/EPIC | Expected outcome | Actual outcome | Comments | Last updated date | |
|---|---|---|---|---|---|
| 1 | Checking Hotjar E21: Upgrading of Revalidation |
When functionality is enable in hotjar e.g. for feedback then when a user logs in, they should see the enabled hotjar functionality | |||
| 2 | https://hee-tis.atlassian.net/browse/TISNEW-4015 E21: Upgrading of Revalidation | ||||
| 3 | https://hee-tis.atlassian.net/browse/TISNEW-4791 E21: Upgrading of Revalidation | ||||
| 4 | https://hee-tis.atlassian.net/browse/TISNEW-5487 E21: Upgrading of Revalidation | ||||
| 5 | https://hee-tis.atlassian.net/browse/TISNEW-5171 E21: Upgrading of Revalidation | ||||
| 6 | https://hee-tis.atlassian.net/browse/TISNEW-4212 E21: Upgrading of Revalidation | ||||
| 7 | https://hee-tis.atlassian.net/browse/TISNEW-5159 E21: Upgrading of Revalidation | ||||
| 8 | https://hee-tis.atlassian.net/browse/TISNEW-2792 E21: Upgrading of Revalidation | ||||
| 9 | https://hee-tis.atlassian.net/browse/TISNEW-4020 E21: Upgrading of Revalidation | ||||
| 10 | https://hee-tis.atlassian.net/browse/TISNEW-4035 E21: Upgrading of Revalidation | ||||
| 11 | https://hee-tis.atlassian.net/browse/TISNEW-4034 E21: Upgrading of Revalidation | ||||
| 12 | https://hee-tis.atlassian.net/browse/TISNEW-4036 E21: Upgrading of Revalidation | ||||
| 13 | https://hee-tis.atlassian.net/browse/TISNEW-3923 E21: Upgrading of Revalidation | ||||
| 14 | https://hee-tis.atlassian.net/browse/TISNEW-3962 E21: Upgrading of Revalidation | ||||
| 15 | https://hee-tis.atlassian.net/browse/TISNEW-4141 E21: Upgrading of Revalidation | ||||
| 16 | https://hee-tis.atlassian.net/browse/TISNEW-4120 E21: Upgrading of Revalidation | ||||
| 17 | https://hee-tis.atlassian.net/browse/TISNEW-4153 E21: Upgrading of Revalidation | ||||
| 18 | https://hee-tis.atlassian.net/browse/TISNEW-4152 E21: Upgrading of Revalidation | ||||
| 19 | https://hee-tis.atlassian.net/browse/TISNEW-4371 E21: Upgrading of Revalidation | ||||
| 20 | https://hee-tis.atlassian.net/browse/TISNEW-4404 E21: Upgrading of Revalidation | ||||
| 21 | https://hee-tis.atlassian.net/browse/TISNEW-4424 E21: Upgrading of Revalidation | ||||
| 22 | https://hee-tis.atlassian.net/browse/TISNEW-4488 E21: Upgrading of Revalidation | ||||
| 23 | https://hee-tis.atlassian.net/browse/TISNEW-4060 E21: Upgrading of Revalidation | ||||
| 24 | https://hee-tis.atlassian.net/browse/TISNEW-4449 E21: Upgrading of Revalidation | ||||
| 25 | https://hee-tis.atlassian.net/browse/TISNEW-4054 E21: Upgrading of Revalidation | ||||
| 26 | https://hee-tis.atlassian.net/browse/TISNEW-3963 E21: Upgrading of Revalidation | ||||
| 27 | https://hee-tis.atlassian.net/browse/TISNEW-4521 E21: Upgrading of Revalidation | ||||
| 28 | https://hee-tis.atlassian.net/browse/TISNEW-4785 E21: Upgrading of Revalidation | ||||
| 29 | https://hee-tis.atlassian.net/browse/TISNEW-5393 E21: Upgrading of Revalidation | ||||
| 30 | https://hee-tis.atlassian.net/browse/TISNEW-5421 E21: Upgrading of Revalidation | ||||
| 31 | https://hee-tis.atlassian.net/browse/TISNEW-4480 E21: Upgrading of Revalidation | ||||
| 32 | https://hee-tis.atlassian.net/browse/TISNEW-4370 E21: Upgrading of Revalidation | ||||
| 33 | https://hee-tis.atlassian.net/browse/TISNEW-5502 E21: Upgrading of Revalidation | ||||
| 34 | https://hee-tis.atlassian.net/browse/TISNEW-5661 E21: Upgrading of Revalidation | ||||
| 35 | https://hee-tis.atlassian.net/browse/TISNEW-5789 E21: Upgrading of Revalidation | ||||
| 36 | Test User Login https://hee-tis.atlassian.net/browse/TISNEW-4619
|
A user created in keycloak with reval user permissions should be able to log into the revalidation module | |||
| 37 | Reval user Login https://hee-tis.atlassian.net/browse/TISNEW-4750 Reval - User management |
A user with the reval role should be able to log into the revalidation module |
| ||
| 38 | https://hee-tis.atlassian.net/browse/TISNEW-5602 Reval - User management | ||||
| 39 | Google Analytics | When users are using reval - data of the activity is sen’t to the TIS GA account | Production Envrionment only, may be part of TIS | ||
| 40 | Log out | When the user selects logout from the menu, they are taking to the page which displays the option to login with TIS | |||
| 41 | Navigation from Admins UI | As a user logged into TIS Admins UI, when I click on revldation on the menu, I am taken to revalidation. When I am logged into Revalidation, when I click on people, posts or admin I am taken to TIS Admins UI A browser back button can take a user back to the previous page regardless if TIS or Reval | |||
| 42 | Cookie timeout period | If a logged in user has left the browser tab open for longer than the timeout period, they should automatically be logged out | |||
| 43 | Searching https://hee-tis.atlassian.net/browse/TISNEW-4470 https://hee-tis.atlassian.net/browse/TISNEW-5263 | As a user, I can use the search box to enter a search string and when I press enter or click the search magnifying glass I get a search result based on GMC number or trainee name As a user, I can clear my search by using the burger menu and selecting the clear all text. Once this is pressed, anything in the search box should be removed | NR To be covered under their EPICs | ||
| 44 | Refresh button | When the refresh button is pressed, the table view of data is changed | |||
| 45 | Pagination | when the next arrorw is pressed, the view of the data changes | |||
| 46 | https://hee-tis.atlassian.net/browse/TISNEW-5720 Revalidation Infrastructure and Ops | Saving some $ when we stop using GMC mock if not required | |||
| 47 | https://hee-tis.atlassian.net/browse/TISNEW-4641 Revalidation Infrastructure and Ops | Separate the old world applications from the new world applications when the lift and shift migration is done | |||
| 48 | https://hee-tis.atlassian.net/browse/TISNEW-5137 Revalidation Infrastructure and Ops | There should be no white screen when users are accessing https://stage-revalidation.tis.nhs.uk/concerns | |||
| 49 | https://hee-tis.atlassian.net/browse/TISNEW-4640 Revalidation Infrastructure and Ops | Import Azure VHDs in to AWS in the ability to lift and shift and can start an EC2 instance from it | |||
| 50 | https://hee-tis.atlassian.net/browse/TISNEW-4732 Revalidation Infrastructure and Ops | Create an area where github actions can access Artifact storage S3 | |||
| 51 | https://hee-tis.atlassian.net/browse/TISNEW-4639 Revalidation Infrastructure and Ops | Create Elasticsearch cluster and it running as an AWS service | |||
| 52 | https://hee-tis.atlassian.net/browse/TISNEW-4638 Revalidation Infrastructure and Ops | Production data available in AWS to fully test application behaviour inside AWS | |||
| 53 | https://hee-tis.atlassian.net/browse/TISNEW-4891 Revalidation Infrastructure and Ops | Sonarcloud installed to track code smells | |||
| 54 | https://hee-tis.atlassian.net/browse/TISNEW-4890 Revalidation Infrastructure and Ops | Sentry installed to identify errors | |||
| 55 | https://hee-tis.atlassian.net/browse/TISNEW-2754 E1: Application layout and performance | ||||
| 56 | https://hee-tis.atlassian.net/browse/TISNEW-2761 E1: Application layout and performance | ||||
| 57 | https://hee-tis.atlassian.net/browse/TISNEW-2639 E1: Application layout and performance | ||||
| 58 | https://hee-tis.atlassian.net/browse/TISNEW-2648 E1: Application layout and performance | ||||
| 59 | https://hee-tis.atlassian.net/browse/TISNEW-226 E1: Application layout and performance | ||||
| 60 | https://hee-tis.atlassian.net/browse/TISNEW-1820 E1: Application layout and performance | ||||
| 61 | https://hee-tis.atlassian.net/browse/TISDEV-4951 E1: Application layout and performance | ||||
| 62 | https://hee-tis.atlassian.net/browse/TISDEV-6236 E1: Application layout and performance | ||||
| 63 | https://hee-tis.atlassian.net/browse/TISDEV-6286 E1: Application layout and performance | ||||
| 64 | https://hee-tis.atlassian.net/browse/TSNR-816 E1: Application layout and performance | ||||
| 65 | https://hee-tis.atlassian.net/browse/TISNEW-1981 E1: Application layout and performance | ||||
| 66 | https://hee-tis.atlassian.net/browse/TISNEW-2224 E1: Application layout and performance | ||||
| 67 | https://hee-tis.atlassian.net/browse/TISNEW-2225 E1: Application layout and performance | ||||
| 68 | https://hee-tis.atlassian.net/browse/TISNEW-2662 E1: Application layout and performance | ||||
| 69 | https://hee-tis.atlassian.net/browse/TISNEW-2767 E1: Application layout and performance | ||||
| 70 | https://hee-tis.atlassian.net/browse/TISNEW-3177 E1: Application layout and performance | ||||
| 71 | https://hee-tis.atlassian.net/browse/TISNEW-3185 E1: Application layout and performance | ||||
| 72 | https://hee-tis.atlassian.net/browse/TISNEW-5656 E1: Application layout and performance | ||||
| 73 | https://hee-tis.atlassian.net/browse/TISNEW-5668 E1: Application layout and performance | ||||
| 74 | https://hee-tis.atlassian.net/browse/TISNEW-5336 E2: Administer Revalidation | ||||
| 75 | https://hee-tis.atlassian.net/browse/TISNEW-2605 E2: Administer Revalidation | ||||
| 76 | https://hee-tis.atlassian.net/browse/TISNEW-2160 E2: Administer Revalidation | ||||
| 77 | https://hee-tis.atlassian.net/browse/TISNEW-407 E2: Administer Revalidation | ||||
| 78 | https://hee-tis.atlassian.net/browse/TISDEV-4796 E2: Administer Revalidation | ||||
| 79 | https://hee-tis.atlassian.net/browse/TISDEV-3726 E2: Administer Revalidation | ||||
| 80 | https://hee-tis.atlassian.net/browse/TISNEW-1786 E2: Administer Revalidation | ||||
| 81 | https://hee-tis.atlassian.net/browse/TSNR-757 E2: Administer Revalidation | ||||
| 82 | https://hee-tis.atlassian.net/browse/TSNR-784 E2: Administer Revalidation | ||||
| 83 | https://hee-tis.atlassian.net/browse/TSNR-733 E2: Administer Revalidation | ||||
| 84 | https://hee-tis.atlassian.net/browse/TISNEW-1784 E2: Administer Revalidation | ||||
| 85 | https://hee-tis.atlassian.net/browse/TSNR-20 E2: Administer Revalidation | ||||
| 86 | https://hee-tis.atlassian.net/browse/TISNEW-2202 E2: Administer Revalidation | ||||
| 87 | https://hee-tis.atlassian.net/browse/TISNEW-2414 E2: Administer Revalidation | ||||
| 88 | https://hee-tis.atlassian.net/browse/TISNEW-4705 Data Quality |
Role/Permission Testing - Ade findings as at 30/11/2020
Still finding it difficult to test for “See All local offices / designated bodies” or “See only Local Office/Designated Body” as this depends on the designated body codes assigned to each role. You can only see what is added to you as a user.
HEE Admin Revalidation Role seems to be over-lay for all the new reval roles, without this role you can’t access reval.
If you have HEE Admin Revalidation Role as an over-lay irrespective of any other new roles you will be able to do the following:
Recommendations: Manage users / Permissions, read, write/edit/create and submit.
Concerns: Manage users / Permissions, read, write/edit/create and save concerns.
Connections: Read/View only.
Role | Expected: Access to reval | Actual: Access to reval | Expected: Recommendation | Actual: Recommendation | Expected: Concern | Actual: Concerns | Expected: Connections | Actual: Connections | Comments |
Without HEE Admin Revalidation Role | No Access | No access | No access | No access | No access | No access | No access | No access | Looks like an over-layer for all Reval roles. Error received: "Please contact administrator for access" |
HEE Admin Revalidation Role without any other Reval Role | Access | Access |
|
|
|
|
|
| There is a ticket to resolve the concerns |
All Reval Roles without HEE Admin Revalidation Role | No Access | No Access | No Access | No Access | No Access | No Access | No Access | No Access | Error received: "Please contact administrator for access" |
HEE Admin Revalidation Role with RevalSiteAdmin Role | Access | Access |
|
| Read/ view only |
|
|
| There is a ticket to resolve the concerns |
HEE Admin Revalidation Role with RevalSuperAdmin Role | Access | Access |
|
|
|
|
|
| Got to the point to submit to GMC and got this error "Error: Fail to submit recommendation: Missing / Invalid Responsible Officer GMC reference number" though the FE is showing Error: Fail to submit recommendation: Missing / Invalid Responsible Officer GMC re....... instead of a full massage. A ticket will be raised |
HEE Admin Revalidation Role with RevalTISAdmin1 Role | Access | Access |
|
|
|
|
|
| Got to the point to submit to GMC and got this error "Error: Fail to submit recommendation: Missing / Invalid Responsible Officer GMC reference number" though the FE is showing Error: Fail to submit recommendation: Missing / Invalid Responsible Officer GMC re....... instead of a full massage. A ticket will be raised |
HEE Admin Revalidation Role with RevalTISAdmin2 Role | Access | Access |
|
|
|
|
|
| Got to the point to submit to GMC and got this error "Error: Fail to submit recommendation: Missing / Invalid Responsible Officer GMC reference number" though the FE is showing Error: Fail to submit recommendation: Missing / Invalid Responsible Officer GMC re....... instead of a full massage. A ticket will be raised |
HEE Admin Revalidation Role with RevalTISAdmin3 Role | Access | Access |
|
|
|
|
|
| There is a ticket to resolve the concerns https://hee-tis.atlassian.net/browse/TISNEW-4919 |
0 Comments