20230524 - Unity Rollout Status Report
Current progress of Unity testing, development, and deployment. Current clients targeted are Terra, GME, IKAV, Vital, Flywheel.
RISKS
Need continuous performance optimization plan for GME and Terra after go-live
Outstanding critical items getting addressed on latest version(IKAV)
Migrations
IKAV Prod-if similar to Terra, could run into downtime during business hours
IKAV UAT-needs latest GME migration
Terra-needs latest GME migration
Establish upgrade procedures and version controls for live clients on a single code version.
Need agreement by all internal teams so that client communication is aligned.
Needs to be clearly communicate to clients so they understand the future process.
Need to confirm any risk associated with testing on one type of environment and going live on another.
GAPS
Release Notes
Active projects versioning and communication
Current Status
TERRA IS LIVE
Bumpy start. Need to address why migration took 72 hours vs 36.
Wins: no critical issues and increased performance noticed by users
GME IS LIVE
Migration was very quick(completed 11pm Friday night)
EAG began testing Sunday. Critical items showed up in Prod causing resource constraints around the clock for 3 days specific to GME
Prod down 5/24 @ 1:05pm
Internal regression testing(QA)
Flywheel - Untested - 77, Pass - 69, Blocked - 1, N/A - 10, Unable to test - 3 (High Risk) -no change from last week
Vital - Untested - 577, Pass - 305, Fail - 15, Blocked - 7, N/A- 39, In-Progress- 3(Full Test Suite)
IKAV UAT
83% complete testing - 319 Pass, 10 Fails, 68 To Do
13 complete, 4 in code change
Live clients' logged ticket count in backlog: 19
Dev queue: 8
Support queue: 11
Flywheel UAT
Only 2 tickets reported and already closed. One due to user error, the other DevOps procedure for SSO
17 - Pass, 55 - Untested (currently on JIB and Rev)
Future Process Improvements
Build RACI matrix for future efforts for transparency of responsibilities across teams.
Add automation for the “easy” wins like UI testing to eliminate almost 30% of the testing effort.
Continue to build out test cases for regression testing across the application.
Add expected results to compare against for testers with limited functional knowledge.
Have defined performance testing with PROD comparable environments to provide better expectations to clients when taking code.
Add code test coverage to eliminate lost functionality with future merges or code changes.
During current round of testing multiple issues have re-emerged after originally fixed.
Notes |
|
|---|---|
Important Links | Regression testing dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10080 Release 10.2.0 Dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10077 |

