Skip to main content
Skip table of contents

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

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

Current Status

  1. TERRA (Live)

    1. Bumpy start. Need to address why migration took 72 hours vs 36.

    2. Wins: no critical issues and increased performance noticed by users

  2. GME (Live)

    1. Migration was very quick(completed 11pm Friday night)

    2. EAG began testing Sunday. Critical items showed up in Prod causing resource constraints around the clock for 3 days specific to GME

    3. Prod down 5/24 @ 1:05pm

  3. IKAV (go-live cutover in progress)

    1. 100% complete on client testing

    2. DB Migrate to begin this afternoon

      1. longest step from Terra upgrade

  4. Flywheel (UAT)

    1. Only 2 open tickets(1 code change, 1 support review)

    2. Currently, testing JIB and Revenue concurrently and ~40% complete

  5. Vital

    1. Client environment in their hands

    2. No test cases completed at this time due to timing of 9.0.14 release. Testing scheduled to begin 6/12

  6. Riverbend

    1. Client testing to begin 6/12

  7. Highpeak

    1. Client testing to begin next week, waiting on confirmation that environment will be ready by Monday

  8. Internal regression testing(QA)

    1. Flywheel - Untested - 76, Pass - 69, Blocked - 1, N/A - 10, Unable to test - 3 (High Risk) -no change from last week

    2. Vital - Untested - 502, Pass - 358, Fail - 18, Blocked -8 , N/A- 42, In-Progress- 4(Full Test Suite)

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

    1. Dev queue: 9

    2. Support queue: 8

Focus for Next Week

  1. Continue Vital & Flywheel regression testing - TBD QA resource

  2. Examine root cause for open tickets @a user

  3. Focus on dev completion of issues across Scrum Teams - @a user coordinating

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.