20230614 - 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.
For Unity-Upstream2
We will need to have db loaded for each one to test regulatory in all the different states(8 total, possibly can exclude 2)
Bank formats
Land/Contract Management needs heavy regression (170/290 features were WPX)
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
Internal Feedback/Questions
No organization created in Jira for CHS Unity or Eagleclaw Unity. Are we not tracking in Jira? If not, why?
Are we regression testing upstream1 clients still? If yes, why?
Date commitment examples that we should be able to provide client; regression testing done by date X, environments created by date X, client testing to begin by date X, bug turnaround time commitments
3 main v10 clients (Terra/IKAV/GME), we're getting right back to versioning problems where each client has issues + their own set of issues, that need deploy at different times. Is there a reason we can’t get those stable before continuing to add more clients into the mix? (re: version approach in Risks)
Current Status
TERRA (Live 5/22)
Issues since go-live
Closed-10, Code Change in progress-4, Support Review-2, Waiting for feedback-3, Waiting on CloudOps-2
GME (Live 5/22)
Issues since go-live
Closed-7, Code Change in progress-2, Support Review-12, Waiting for feedback-1, Waiting on CloudOps-2
IKAV (Live 6/12)
Issues since go-live
Closed-3, Code Change in progress-2, Support Review-0, Waiting for feedback-0, Waiting on CloudOps-0
Flywheel (UAT)
3 open tickets(2 code change, 1 support review), 6 Closed
Rev and JIB testing at 50-60% complete
Vital
Client testing to begin 6/12
No issues reported
Riverbend
Client testing to begin 6/12
JIB this week
REV end of week first of next week
DO next week
No issues reported
Highpeak
Client testing to begin 6/12
Environment up as of today, 6/14
Waiting on DevOps to create Tuan user so he can smoke test and get Highpeak testing
Internal regression testing(QA)
Flywheel (High Risk)
no change from last week
Untested - 76, Pass - 69, Blocked - 1, N/A - 10, Unable to test - 3
Vital (Full Test Suite)
Only one new test case tested since last week
Untested - 501, Pass - 361, Fail - 18, Blocked -8 , N/A- 42, In-Progress- 2
Live clients' logged ticket count in backlog: 36
Dev queue: 12
Support queue: 24
Focus for Next Week
Continue Vital & Flywheel regression testing - QA
Mid/Trans Unity1 to begin regression testing - QA
Examine root cause for open tickets @a user and team
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 |

