Skip to main content
Skip table of contents

20230621 - 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)

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. WEMAIN-11141 and WEMAIN-11144

    1. Not an issue pre-v10

Current Status

  1. TERRA (Live 5/22) Yellow

    1. Issues since go-live

      1. Closed-15, Code Change in progress-4, Support Review-6, Waiting for feedback-1, Waiting on CloudOps-1

  2. GME (Live 5/22) Yellow

    1. Issues since go-live

      1. Closed-13, Code Change in progress-2, Support Review-12, Waiting for feedback-1, Waiting on CloudOps-2

  3. IKAV (Live 6/12) Green

    1. Issues since go-live

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

  4. Flywheel (UAT) Green

    1. 6 open tickets(3 code change, 3 support review), 7 Closed

    2. Rev and JIB testing at 70% complete

  5. Vital (UAT) Yellow

    1. 4 open tickets(3 supprt review, 1 waiting on DevOps)

    2. potentially move to upstream phase 2

  6. Riverbend (UAT) Green

    1. 1 reported issue

  7. Highpeak (UAT) Yellow

    1. One critical issue reported

  8. Internal regression testing(QA)

    1. Flywheel (High Risk)

      1. no change from last week

      2. Untested - 76, Pass - 69, Blocked - 1, N/A - 10, Unable to test - 3

    2. Vital (Full Test Suite)

      1. Only one new test case tested since last week

      2. Untested - 501, Pass - 361, Fail - 18, Blocked -8 , N/A- 42, In-Progress- 2

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

    1. Dev queue: 13

    2. Support queue: 24

Focus for Next Week

  1. Continue Vital & Flywheel regression testing - QA

  2. Mid/Trans Unity1 to begin regression testing - QA

  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.

Notes

  1. Terra and GME UAT is ongoing

  2. IKAV UAT kicked off 4/24

  3. We have a dedicated v10 team with 3 engineers.

  4. Additional resources are available from other sprint teams as needed.

    1. Upstream, DO/Land, and Regulatory team are taking stories as capacity allows.

Important Links

Regression testing dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10080

Release 10.2.0 Dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10077

JavaScript errors detected

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

If this problem persists, please contact our support.