Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 42 Next »

March / April 2023 - Initial ROFs Prod Release

Sprint

Due Date

Activity

Team Member

Status

Sprint 26 / 27

March 15th - March 29th

UAT Testing

Steve, Grace

Complete

Sprint 26 / 27

MAACE team - present (projected complete Monday March 27th)

Grace - WLM permissions for testing

Jugraj / MAACE

In Progress

  • Told we would have access by March 17

  • Update a/o March 22 - MAACE group is completing sync work before we can get access

  • New projected completion date March 27th - Jugraj will follow-up Tuesday March 28th. If not complete, we will escalate. We need the credentials to access.

Sprint 27

Monday March 20th

Troubleshoot and test URL

Jugraj / Cloud Team

Complete

  • URL fixed March 20

  • Jugraj has tested and it is working for him

  • Jugraj suggests that we can test URL during smoke testing

Sprint 27

March 21st

ACC / Prod API permissions

Jugraj / MAACE

Complete

  • Permissions granted March 21

Sprint 27/28

March 29th - April 5th

ACC / Prod API Testing

Jugraj

In Progress

  • Test the following:

    • Roles have permissions

    • Workflows with different roles

    • Ad-hoc testing

Sprint 27

March 24th - present

SCED set-up

Jugraj / MAACE Team

In Progress

  • MAACE has provided four endpoints

  • Troubleshooting performance issues with WLM devs

  • Meeting with MAACE team for March 29th - missing endpoints

Sprint 27

Monday March 27th - present

ROFs ACC environment set-up to RSIG SCED endpoints

Jugraj / Shu Zi (endpoint set-up on RSIG side)

In Progress

  • March 27th - ran into issues, and could not give RSIG SCED endpoints

  • We need to update in dev and test as well to be in sync

Sprint 27

Monday March 27th - Wednesday March 30th

Possible testing in RSIG when we give RSIG SCED.

RSIG ACC Testing

RSIG - Entai, Honglei and Ewa

Complete on RSIG side. But, RSIG should test again to make sure the TSB pop-up in ACC and Citrix once they have the SCED endpoints.

  • RSIG ACC deployment of desktop and Citrix are complete a/o March 22nd

  • Xu needs to add current UAT user list to ACC (not real email addresses for RSIs)

  • Estimated time to test

    • ACC - 2 days

    • Citrix - 0.5 days

Sprint 28

Wednesday March 29th

Sprint 28 - Start Date

ROFs Team

In Progress

Sprint 28

Wednesday March 29th

Submit RSIG prod ticket

RSIG - Entai

In Progress

  • Entai will submit RSIG prod ticket by end-of-day

Sprint 28

March 27th to present

Jugraj & Henry to troubleshoot so it can be done automatically vs manually on March 14th (time: 20 min)

Jugraj

In Progress

  • March 24th - Jugraj and Henry troubleshooting to see if manual deployment on release day can be automatic vs. manual

Sprint 28

Friday March 31st

Code Freeze

ROFs Team

In Progress

Sprint 28

Monday April 3rd

Prod sanity check - backend

Note: 255651 - split into tasks in PBI

ROFs Team

Not started

  • See prod sanity check below for details

Sprint 28

Monday April 3rd - Thursday April 6th

ACC Testing - backend and frontend

Note: split into tasks in PBI

ROFs Team

Not started

  • Let internal users know they might receive an email from ROFs

  • Create and follow test checklist

  • We will test in our ACC environment, but switch connection to RSIG UAT

Sprint 28

Friday April 7th

Holiday - Good Friday

ROFs Team

Holiday

Sprint 28

Monday April 10th

Holiday - Easter Monday

ROFs Team

Holiday

Sprint 29

Wednesday April 5th

Sprint 29 - Start Date

ROFs Team

Not Started

Sprint 30

Friday April 28th

Prod release day activities

Jugraj, ROFs Team

Not Started

Sprint 30

Monday May 1st

Release to users

Steve, Help Desk?

Not Started

  • Email to OPS users, letting them know ROFs is released and ready for use

March 28th - RSIG ACC Testing

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.

12:00pm (approx.)

Give RSIG team ROFs ACC non-SCED to RSIG ACC

Afternoon

Plan was to give RSIG team ROFs ACC SCED to RSIG ACC. We were unable to give them ROFs ACC SCED due to SCED issues.

From our understanding, the following was working in SCED:

  • Location mapping

  • Planned Location

  • Display ROFs data in pop-up window

  • RSIG workflow

The following is missing from SCED:

  • Letters - not working

    • A letter has been added to ROFs so workflow into RSIG can continue

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 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

  • 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

Do not test

  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 - 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 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 with Grace and Jugraj on March 30th

April 28th - Smoke Test

Checklist: Started with Jugraj on March 29th. Needs further review.

  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 Notification

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

April 28th - Prod Release Day Activities

RSIG Release Day Activities - Dev Team: https://dev.azure.com/transport-canada/DSD-RAIL-RSIG/_wiki/wikis/DSD-RAIL-RSIG.wiki/4334/Release-34-Release-Day-Workflow-Dev-Team

Item

Time (approx.)

Effort

Activity

Team Member

Details

Status

1.

9:00am

Switch connection string from training to prod

Jugraj

Not Started

2.

9:40am

Latest code pushed to prod branch

Jugraj

Coordinate with RSIG team at approx. 9:40am at the same time they do the quick test

Not Started

3.

[11:00am?]

20 min

Merge ACC branch with main branch

Jugraj

We can do our build after RSIG db is refreshed. Need to confirm with RSIG before proceeding.

Not Started

4.

[11:30am?]

20 min

Manually [or automatically] deploy from main branch

Jugraj

May be able to deploy automatically.

Not Started

5.

[1:00pm?]

30 min

Smoke test with users to verify release is error free

Steve, Grace

Not Started

6.

[3:00pm?] - After RSIG Smoke test?

[Can OPS use ROFs via RSIG db even though frontend is locked?]

Not Started

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.

Training - Manual

  • No labels