Skip to main content
Skip table of contents

20230317 - 10.2 Rollout Status Report

Current progress of 10.2.0 testing and development with target of 2/28 completion. Clients being tested against are VEF, Terra, and GME.

Current Status

  1. Internal deadline for completing regression testing and providing clients UAT env was 3/15

  2. IKAV regression testing was slated for 3/15 or early and we have not begun

  3. Tie-outs in progress

    1. Terra Production and Revenue Allocated results have differences and still in progress

    2. Both GME and Terra Revenue Asset and Company processes are tied out through to financials

      1. Differences are due to minor rounding issues

    3. Only one known JIB issue is in progress, but we have not loaded clean JIB databases yet to do full run without other QA testing interference

      1. Ran through JIB on GME with mid-month database and validating results now with SME

      2. Terra JIB specific database should be loaded this weekend

  4. Revenue check remittance file is missing details and still in progress

  5. OpenInvoice testing with fake server complete and passed

  6. Testing is ~95% complete with High Risk ~99% complete

  7. Tickets completed - 23 stories for 51 points

  8. Open tickets - 21 tickets (5 - “To Do”, 7 - “In Progress”, 7 - “In Review”)

    1. To Do - 3 are performance related, 1 UAT environmental, 1 related to background task

  9. Another round of performance testing (~10-15 users at once) was performed on 3/13

Focus for Next Week

  1. Begin IKAV regression testing - @a user coordinating

  2. Continued JIB Tie-Outs for GME and Terra - @a user coordinating

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

  4. Monitor client UAT testing - @a user and CSMs coordinating

RISKS

  1. JIB will have to be tied out manual as a client would. Direct comparison is not possible as improved logic changes will not allow for a 1 to 1 tie out.

  2. Client reported issues that are data dependent may require db refreshes to internal environments.

    1. Currently this can take a full day or more for Terra and GME.

    2. Resources on COLO are strained and cannot support additional instances of large clients.

  3. We have no specific performance metrics and yet clients have expectations of improved performance with v10.

  4. OpenInvoice testing was done with Fake Server internally.

  5. No GIS testing capabilities at this time.

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 beginning in earnest next week

  2. We have a dedicated v10 team with 4 engineers.

  3. Additional resources are coming from other sprint teams who lack priority stories.

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

Important Links

Full details around testing provided here - Testing Tracker - v10.2 Test Metrics

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

** High Risk Functional Tests are being done for eac client uniquely. This count represents triplicate of the number of tests. One set per client.

JavaScript errors detected

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

If this problem persists, please contact our support.