Skip to main content
Skip table of contents

20231013 - Unity Rollout Status Report

Current progress of Unity testing, development, and deployment.

RISKS

  1. Establish upgrade procedures and version controls for live clients on a single code version.

    1. Need agreement by all internal teams so that client communication is aligned.

    2. Needs to be clearly communicate to clients so they understand the future process.

    3. Need to confirm any risk associated with testing on one type of environment and going live on another.

    4. Need standard timeline of deploying latest branch, there is a calendar that a few have seen internally and gme/terra have seen

  2. For Unity-Upstream2

    1. We will need to have db loaded for each one to test regulatory in all the different states(8 total, possibly can exclude 2)

    2. Bank formats

    3. Land/Contract Management needs heavy regression (170/290 features were WPX)

  3. For Unity-Midstream1&2

    1. Bank formats

    2. Fixed assets

GAPS

  1. Release Notes (Jeff Gunter/Michael Ferrante actively working on)

    1. Product team to release in 10.7.1

  2. Active projects versioning and communication

    1. We are targeting to get the cadence rolled out once clients are all on 1099 code release so every client is on same version.

  3. Rewrite SOC documentation for delivering patches, releases etc

    1. Complete (Erik to update names for org changes)

    2. Erik distributing week of 10/16/23

  4. Pre Unity to Unity DB schema changes (client by client request)

    1. Clients with replica DB’s need this level of detail for reporting/dashboards etc.

    2. Unsure if Cognos would be affected

Internal Feedback/Questions

  1. What is the game plan for unique features testing by QA in this continuous rollout?

    1. need land test cases for Dugan and QA to test them

    2. Vaibhav? to start analyzing column E of unity combined spreadsheet with the product team and QA

  2. How are we looking to resolve the space issue?

    1. Can we upgrade a few support and QA boxes?

    2. Additional follow up email sent to Vaibhav and team with the continual issues with space that prevents productivity for most teams.

  3. Superior added to pipeline below. We have no internal knowledge of volume balancing to even create test cases for QA. Nathan did a lot of the unique coding in data prep logic related to volume balancing. potential suggestion: upgrade regular environment, figure out volume balancing piece after and maybe get it in one instance. Need internal feedback on this suggestion

Current Status

  1. LIVE CLIENTS

    1. TERRA (Live 5/22) Yellow

    2. GME (Live 5/22) Yellow

    3. IKAV (Live 6/12) Red

    4. Flywheel (Live 7/17) Green

    5. Highpeak (Live 7/31) Yellow

    6. King (Live 8/1) Green

    7. Riverbend (Live 8/7) Yellow

    8. Vital (Live 8/28) Yellow

  2. In UAT

    1. Mustang (services project Aug2023) - Mid/Trans 1

      1. 2 open ticket

    2. Legacy/Revenir(services project) - Upstream 1

      1. Selling their assets. Not expected to continue

    3. AEC

      1. Received UAT box for gap analysis project with Magnum Forge

      2. claiming no access to their UAT due to SSO not configured. This was not originally outlined in their request and taking longer than expected to get setup.

    4. Jaybee

      1. 13 OPEN TICKETS

        1. 7 code change, 3 awaiting feedback, 3 waiting on cloudops

  3. Regression Testing

    1. Mid/Trans -CHS (UI done with automation)

      1. Total Executed Failed Pass To Do
        98 94 13 81 4

      2. 37 bugs logged

        1. 10-not started, 1-QA, 2-On Hold, 24-Passed

  4. Live clients' logged ticket count in backlog: 109 (trending down!)

    1. Dev queue: 42

    2. Support queue: 38

    3. Waiting on DevOps: 2

    4. Waiting for Feedback (from client):26

    5. Assigned to reporting team: 1

Focus for Next Week

  1. Mid/Trans Unity1 regression testing - @a user coordinating additional resources from Services

  2. Determine how many clients we can take on internally for continuous and successful roll out of Unity

    1. Need follow up meetings surrounding FR2.0 and land - material item. should be feature flag.

  3. Examine root cause for open tickets @a user and team

Future Process Improvements

  1. Build RACI matrix for future efforts for transparency of responsibilities across teams.

  2. Add automation for the “easy” wins like UI testing to eliminate almost 30% of the testing effort.

  3. Continue to build out test cases for regression testing across the application.

    1. Add expected results to compare against for testers with limited functional knowledge.

  4. Have defined performance testing with PROD comparable environments to provide better expectations to clients when taking code.

  5. Add code test coverage to eliminate lost functionality with future merges or code changes.

    1. During current round of testing multiple issues have re-emerged after originally fixed.

  6. 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

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.