Page Comparison

...

March 28th - RSIG ACC Testing - Complete

Morning

Meeting held with RSIG and ROFs team. RSIG team determined it was ok to give ROFs ACC non-SCED to RSIG ACC in the morning so they can start testing, and provide them with ROFs ACC SCED in the afternoon. We have been using ROFs ACC non-SCED to test in QA.

...

March 29 to April 5 - ACC / PROD API Testing

Checklist: Reviewed with Jugraj, and marked as complete on March 29th

Test the following:

• Roles have permissions

• Workflows with different roles

• Ad-hoc testing

April 3rd to April 5th - ACC Testing

Backend testing

Checklist: Reviewed with Jugraj, and marked as complete on March 29th.

1. Check connection string in Key Vault

2. Check correct groups in app settings

3. Check if correct users are added to the groups - prod

4. Check if all the API permissions are configured for the groups

5. RSIG db - need to make sure the users main emails match with the Microsoft login emails

6. Check the correct API endpoints are set up

Frontend testing

Checklist: Will review Reviewed with Grace and Jugraj on April 3rd, and marked as Complete

1. Task Dashboard:

   1. Check TSB occurrences from overnight feed appear in “Pending Review” tab at top of table (if still mapped to RSIG training) - ask Jugraj if feed will be in ACC next week

   2. Run a date range search

   3. Run a few other ad-hoc searches

   4. Run a search in FR, searching for occurrences using FR translated criteria

2. TSB Data:

   1. Check a few TSB occurrences to make sure correct TSB data is appearing (from Jeff’s morning email - if still mapped to RSIG trainingUAT - need to confirm with Jugraj)

3. Location Mapping:

   1. Search for yard, spur, subdivision, crossing in the search tab Warning: Do not map a location

   2. Map a few locations including search and select a few different location types

4. Manager Review:

   1. Test “Requested By”

      1. Select “No” for the first question

      2. Test “Requested By” dropdown menu

      3. Warning: Do not Save!!!

5. Take a quick look at other tabs to see if FR translation is appearing

April 6th - Prod Sanity Check (backend and frontend)

RSIG Environments - Emails

QA

• Real emails: RSIG/ROFs team members

• Fake emails: All other RSIG contacts outside of RSIG/ROFs team members

• ROFS is using [TR157_GEN_INDIV_EMAIL_ADDRESS_ROFS_ROFS] for authentication and users in this table have their real email listed

• Fake email:  RSIG-PISF-test@tc.gc.cal

UAT

...

Real emails: RSIG/ROFs team members

1. 1. Complete a few Manager Reviews including:

      1. No Action Required

      2. Assigning RSI

      3. Required by Manager

      4. Reopen

      5. Reassign

2. Inspection Notification:

   1. Select a railway and railway officer

   2. Change railway and railway officer

   3. Create letter, add CC and appendix

   4. Send email - Caution: Double-check to make sure CC emails are not real

   5. Check letter received in email and make sure it can be edited

   6. Test letter pop-up window, download letter, Info Received pop-up window, Railway Officer pop-up window

   7. Test all fields in Inspection Notification tab

   8. Test validation and different scenarios

3. TSB Planned Location

   1. Create Planned Location

   2. If possible, test to make sure the Planned Location is going to the 2023-2024 fiscal year

4. Test steps 1-6 in French

April 6th - Prod Sanity Check (backend and frontend)

RSIG Environments - Emails

QA

• Real emails: RSIG/ROFs team members

• Fake emails: All other RSIG contacts outside of RSIG/ROFs team members

• ROFs ROFS is using [TR157_GEN_INDIV_EMAIL_ADDRESS_ROFS_ROFS] for authentication RSIG has team members listed in [TR157_GEN_INDIV_EMAIL_ADDRESS]and users in this table have their real email listed

• Fake email:  RSIG-PISF-test@tc.gc.cal

• Refer to DevOps ticket 252541

Required to start

...

ACC / Prod API permissions are granted and tested

...

UAT

• Real emails: RSIG/ROFs team members

• Fake emails: All other RSIG contacts outside of RSIG/ROFs team members

• ROFs is using [TR157_GEN_INDIV_EMAIL_ADDRESS] for authentication

• RSIG has team members listed in [TR157_GEN_INDIV_EMAIL_ADDRESS]

• Fake email:  RSIG-PISF-test@tc.gc.cal

• Refer to DevOps ticket 252541

Required to start

1. ACC / Prod API permissions are granted and tested

2. SCED endpoints are ready and tested

3. Check to make sure live emails will not go out

...

1. Location Mapping

2. Planned Location

3. Send emails in Inspection Notification - DO NOT SEND EMAILS as they are live?

Backend testing

Checklist: Reviewed with Jugraj, and marked as complete on March 29th

1. Check connection string in Key Vault

2. Check correct groups in app settings

3. Check if correct users are added to the groups - prod

4. Check if all the API permissions are configured for the groups

5. RSIG db - need to make sure the users main emails match with the Microsoft login emails

6. Check the correct API endpoints are set up

April 14th - Prod Frontend Testing

Checklist: Reviewed with Jugraj and Grace, and marked as complete on March 30th

1. Task Dashboard:

   1. Check TSB occurrences from overnight feed appear in “Pending Review” tab at top of table (if still mapped to RSIG training)

   2. Run a date range search

   3. Run a few other ad-hoc searches

   4. Run a search in FR, searching for occurrences using FR translated criteria

2. TSB Data:

   1. Check a few TSB occurrences to make sure correct TSB data is appearing (from Jeff’s morning email - if still mapped to RSIG training)

3. Location Mapping:

   1. Search for yard, spur, subdivision, crossing in the search tab Warning: Do not map a location

4. Manager Review:

   1. Test “Requested By”

      1. Select “No” for the first question

      2. Test “Requested By” dropdown menu

      3. Warning: Do not Save!!!

5. Take a quick look at other tabs to see if FR translation is appearing

April 28th - Smoke Test

Checklist: Started with Jugraj on March 29th. Needs further review. Finished review with Grace on March 31. Marked as complete.

1. Test URL

2. Complete a few searches on the dashboard, testing out the following filters (does not need to be in combination):

   1. Run a date range search

   2. Run a few other searches

3. Open up a few records in “Pending Review” [I don’t think there will be any records in “Pending Review”? Perhaps historical instead?]

4. Select a record and compare the data in the TSB tab with the daily email

5. Jeff / Cary - perhaps Map a location for a historical record - if this won’t ruin OPS analytics

6. In Manager Review:

   1. Complete a Manager Review for a historical occurrence that does not require further follow-up?

   2. Check only - Reopen the occurrence and check the ‘Assign To’ and the ‘Requested By’ list to make sure it is accurate

7. DO NOT complete an Inspection Notificationcompare the data in the TSB tab with the daily email

8. DO NOT complete Location Mapping or Manager Review

RSIG Release 33 Smoke Test: https://docs.google.com/spreadsheets/d/1PVZJTDb89otTOUIQd1xXcPH20KENyeAPjPz6yGiv-4I/edit#gid=0

...

May 1st - RSIG Release day - External

• Include ROFs release in the RSIG email

Training - In-person

Training - can happen one week before the release.

• Record one EN training and they are available - Jeff can run it. If not possible to record, then individual regional sessions in their language.

• Record one FR training and they are available - Jeff can run it. If not possible to record, then individual regional sessions in their language.

...

May 1st - RSIG Release day - External

• Include ROFs release in the RSIG email from helpdesk