Skip to main content
Skip table of contents

20230707 - 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

GAPS

  1. Release Notes (Jeff Gunter actively working on)

  2. Active projects versioning and communication

  3. Internal project box alignment

  4. Rewrite SOC documentation for delivering patches, releases etc

Internal Feedback/Questions

  1. JIB close monitored closely by SME(Donnita) and time improvements were monumental(4+hours down to 48 minutes with more entries added that prior run).

    1. “I want to let you and W support team know that JIB close went a lot smoother and faster this month compared to the last three previous months.  I sure appreciate not having to stay up late trying to close JIB this month.  Thank you again for your support.” -GME user

  2. Division Order module had many challenges this week

    1. Duplicates

    2. Missing DOs in approval workflow

    3. TIK

    4. historical data cleanup needed

  3. Consistent Open Invoice issues

    1. WEDEVOPS-14017 (Vital UAT sync fatal)

    2. WEDEVOPS-14580 (Terra Prod missing invoices after code deploys)

    3. WEDEVOPS-146613 (IKAV prod sync fatal)

    4. WEDEVOPS-14484 (GME acquistion environment sync fatal) - RESOLVED 7/7

Current Status

  1. TERRA (Live 5/22) Yellow

    1. Issues since go-live (48)

      1. Closed-29, Code Change in progress-2, Support Review-10, Waiting for feedback-1, Waiting on CloudOps-3

  2. GME (Live 5/22) Red

    1. Issues since go-live (44)

      1. Closed-22, Code Change in progress-4, Support Review-14, Waiting for feedback-2, Waiting on CloudOps-2

  3. IKAV (Live 6/12) Green

    1. Issues since go-live (49)

      1. Closed-23, Code Change in progress-4, Support Review-16, Waiting for feedback-5, Waiting on CloudOps-1

  4. Flywheel (UAT) Green

    1. 4 open tickets(3 support review, 1 waiting on cloudops)

    2. Rev and JIB testing at 70% complete

  5. Vital (UAT) Yellow

    1. 7 open tickets(4 code change, 2 support review, 1 waiting on DevOps)

    2. potentially move to upstream phase 2, discussing go-live timeline next week

  6. Riverbend (UAT) Green

    1. 2 open tickets (both in support review)

  7. Highpeak (UAT) Yellow

    1. 8 open tickets (all in 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

        1. 96% complete (High risk)

        2. 15% complete remaining test cases(492 untested)

    3. Transportation

      1. N/A

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

    1. Dev queue: 15

    2. Support queue: 44

    3. Waiting on DevOps: 6

    4. Waiting for Feedback (from client):10

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

  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.