20231031 - Unity Rollout Status Report
Current progress of Unity testing, development, and deployment.
RISKS
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
Confluence page for release cadence link here Unity Release Cadence and Process
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)
Kelsi is leading effort to define test cases for Land and Michael for Contract Management with Harish in QA.
For Unity-Midstream1&2
Bank formats
Fixed assets
GAPS
Release Notes (Jeff Gunter/Michael Ferrante actively working on)
Product team to release in 10.7.3(?)
Active projects versioning and communication
We are targeting to get the cadence rolled out once clients are all on 1099 code release so every client is on same version.
Rewrite SOC documentation for delivering patches, releases etcComplete (Erik to update names for org changes)
Erik distributing by 11/15
Pre Unity to Unity DB schema changes (client by client request)
Clients with replica DB’s need this level of detail for reporting/dashboards etc.
Unsure if Cognos would be affected
Internal Feedback/Questions
What is the game plan for unique features testing by QA in this continuous rollout?
Need land test cases for Dugan and QA to test them. In progress with Kelsi.
Vaibhav? to start analyzing column E of unity combined spreadsheet with the product team and QA
Are we going to skim pivotal features and create test cases based on that?
How are we looking to resolve the space issue?
Can we upgrade a few support and QA boxes?
Additional follow up email sent to Vaibhav and team with the continual issues with space that prevents productivity for most teams.
Internal email to remove various internal environments no longer in use. Ticket is now in CloudOps hands to action removal.
Current Status
LIVE CLIENTS
TERRA (Live 5/22) Green
GME (Live 5/22) Yellow
IKAV (Live 6/12) Yellow
Flywheel (Live 7/17) Green
Highpeak (Live 7/31) Yellow
King (Live 8/1) Green
Riverbend (Live 8/7) Yellow
Vital (Live 8/28) Yellow
In UAT
Mustang (services project thru 2024) - Mid/Trans Unity
2 open ticket
Legacy/Revenir(services project) - Upstream 1Selling their assets. Not expected to continue
AEC
Received UAT box for gap analysis project with Magnum Forge
SSO has been enabled
Jaybee
11 OPEN TICKETS
2 code change, 5 awaiting feedback, 1 support review, 1 engineering complete
Regression Testing
Mid/Trans
CHS - 2 in progress, still have 5 additional results sets to tie-out
Summit - 3 in progress, 6 to do, 4 total results sets to tie-out
Live clients' logged ticket count in backlog: 133
Dev queue: 53
Support queue: 39
Waiting on DevOps: 4
Waiting for Feedback (from client): 26
To Do: 11
Focus for Next Week
Mid/Trans Unity regression testing - @a user coordinating additional resources from Services
Determine how many clients we can take on internally for continuous and successful roll out of Unity
Need follow up meetings surrounding FR2.0 and land - material item. should be feature flag.
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.
Comprehensive and up-to-date check list of all tasks related to upgrades.
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 | Upstream: Jaybee(september), Dugan, Kosmos Mid/Trans: TRG, Superior January 2024 , CHS(ready as soon as chorus integration is complete) , EOG Q2 2024,Western Q2 2024 Targa mentioned Q32024 need messaging for reluctant clients |
