20230609 - Unity Rollout Status Report
Current progress of Unity testing, development, and deployment.
RISKS
Migration time
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 (Jeff Gunter actively working on)
Active projects versioning and communication
Internal project box alignment
Rewrite SOC documentation for delivering patches, releases etc
Current Status
TERRA (Live)
Bumpy start. Need to address why migration took 72 hours vs 36.
Wins: no critical issues and increased performance noticed by users
GME (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
IKAV (go-live cutover in progress)
100% complete on client testing
DB Migrate to begin this afternoon
longest step from Terra upgrade
Flywheel (UAT)
Only 2 open tickets(1 code change, 1 support review)
Currently, testing JIB and Revenue concurrently and ~40% complete
Vital
Client environment in their hands
No test cases completed at this time due to timing of 9.0.14 release. Testing scheduled to begin 6/12
Riverbend
Client testing to begin 6/12
Highpeak
Client testing to begin next week, waiting on confirmation that environment will be ready by Monday
Internal regression testing(QA)
Flywheel - Untested - 76, Pass - 69, Blocked - 1, N/A - 10, Unable to test - 3 (High Risk) -no change from last week
Vital - Untested - 502, Pass - 358, Fail - 18, Blocked -8 , N/A- 42, In-Progress- 4(Full Test Suite)
Live clients' logged ticket count in backlog: 17
Dev queue: 9
Support queue: 8
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 |

