20230802 - 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.
Need standard timeline of deploying latest branch, there is a calendar that a few have seen internally and gme/terra have seen
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)
For Unity-Midstream1
Bank formats
Fixed assets
Resource constraints internally
Chris Peterson(M33) assisting in who and how to target on initial call. Continued discussion scheduled 7/10
Services to begin assisting Midstream regression testing to meet Aug1 deadline
Micah, Blake, Ryan putting together Midstream specific test cases
GAPS
Release Notes (Jeff Gunter/Michael Ferrante actively working on)
Need process put in place to combine deltas as new clients onboard to Unity
Active projects versioning and communication
Internal project box alignment
Rewrite SOC documentation for delivering patches, releases etc
Internal Feedback/Questions
Is there a way to create a dashboard in JIRA for clients on unity to know which code version is in their prod? who should own that creation? Vinay is creating
We have decided on next client targets and scheduling meeting for broader audience to weigh in why or why not. (Total 20 clients)
Timeline needed for midstream unity 2 merge.
Mustang is a new client that will need Summit’s contract management code. No timeline is set still on mid1. can’t just do summit due to targa and some others lined up for future rollout
Environments down due to start/stop mechanism across multiple clients
Terra has had 2 fatals(apply do, do journal), IKAV 1 fatal(WHB)
Current Status
LIVE CLIENTS
TERRA (Live 5/22) Yellow
GME (Live 5/22) Yellow
IKAV (Live 6/12) Green
Flywheel (Live 7/17) Green
Highpeak (Live 7/31) Yellow
King (8/1) Green
Riverbend (UAT-GO LIVE TARGET 8/3) Green
2 open tickets-both in support review and not go-live critical
Vital (UAT-GO LIVE TARGET 8/11) Yellow
24 open tickets(12 code change, 12 support review)
client requested 6 old tickets be moved to Vital Unity organization that increased ticket count
Internal regression testing(QA)
Upstream(Jaybee DB)
Functional high risk: total = 133 (Untested - 127, Pass - 5, Fail-1)
Midstream
Eagleclaw (will not be our first midstream client on unity)
total = 509(Untested - 60, Pass - 414, Fail-35)
Transportation
CHS
73 test cases Untested.
Live clients' logged ticket count in backlog: 69
Dev queue: 9
Support queue: 48
Waiting on DevOps: 4
Waiting for Feedback (from client):7
Assigned to reporting team: 1
Focus for Next Week
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.
Important Links | Regression testing dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10080 Release 10.2.0 Dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10077 |
Clients in upgrade pipeline | Jaybee, TRG |

