Skip to main content
Skip table of contents

20230721 - Unity Rollout Status Report

Current progress of Unity testing, development, and deployment.

RISKS

  1. Migration time

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

  3. 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)

  4. For Unity-Midstream1

    1. Bank formats

    2. Fixed assets

  5. Resource constraints internally

    1. Chris Peterson(M33) assisting in who and how to target on initial call. Continued discussion scheduled 7/10

    2. Services to begin assisting Midstream regression testing to meet Aug1 deadline

      1. Micah, Blake, Ryan putting together Midstream specific test cases

GAPS

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

    1. Need process put in place to combine deltas as new clients onboard to Unity

  2. Active projects versioning and communication

  3. Internal project box alignment

  4. Rewrite SOC documentation for delivering patches, releases etc

Internal Feedback/Questions

  1. Flywheel said “transition was surprisingly smoothe” and appreciative of that success

  2. We create new Prod environments for cutover. Do we do this as well for their non-Prod? If not, what’s the risk?

    1. What’s our pattern as Flywheel did not require new box?

Current Status

  1. TERRA (Live 5/22) Yellow

    1. Issues since go-live (49)

      1. only 2 reported this week.

  2. GME (Live 5/22) Yellow

    1. Issues since go-live (54)

  3. IKAV (Live 6/12) Green

    1. Issues since go-live (64)

  4. Flywheel (Live 7/17) Green

    1. 1 issue reported this week

  5. Vital (UAT-GO LIVE TARGET 8/11) Yellow

    1. 21 open tickets(11 code change, 9 support review, 1 waiting on DevOps)

    2. client requested 6 old tickets be moved to Vital Unity organization that increased ticket count

  6. Riverbend (UAT-GO LIVE TARGET 8/3) Green

    1. 3 open tickets (all in support review)

  7. Highpeak (UAT- GO LIVE TARGET 7/28) Yellow

    1. 12 open tickets(6 code change, 6 support review)

  8. Internal regression testing(QA)

    1. Upstream

      1. Phase 2 has not started. Jaybee will likely be test database

    2. Midstream

      1. Eagleclaw (will not be our first midstream client on unity)

        1. 96.23% complete (High risk)

        2. 234 test cases Untested

    3. Transportation

      1. CHS

        1. 73 test cases Untested.

  9. Live clients' logged ticket count in backlog: 69

    1. Dev queue: 9

    2. Support queue: 48

    3. Waiting on DevOps: 4

    4. Waiting for Feedback (from client):7

    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

    2. Micah to examine list of prospects and provide analysis to cross functional teams and get sign off on timing.

  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.

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, AEC

JavaScript errors detected

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

If this problem persists, please contact our support.