Skip to main content
Skip table of contents

20230224 - 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. Databases required for tie-outs (revenue and JIB) identified. Revenue tie-outs in progress

    1. GME asset level completed

    2. Terra Revenue asset too large, needs compare tool

    3. Terra Production asset in progress

  2. Reallocating resources from VEF tie out boxes that are no longer needed.

  3. Testing is over 84% complete with High Risk ~95% complete.

  4. Tickets completed - 22 stories for 38 points (half of the effort from previous week)

  5. Turnaround on tickets has decreased across all teams.

  6. Open tickets - 36 tickets (16 - “To Do”, 11 - “In Progress”, 9 - “In Review”)

  7. Stress testing performed 2/23/23, Vipul addressing performance

Focus for Next Week

  1. Continued UI & functional testing - @a user & @a user coordinating

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

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

RISKS

  1. Performing Tie Outs with large data sets are going to be difficult and time consuming and this effort is really just beginning. We should have updated compare tool by next week.

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

  3. Almost half the stories closed were closed because there was no code related bug. The reasons fall into 3 major categories: environmental issues (resources and configs), incorrect in-app setup, lack of functional knowledge by tester.

    1. This is across QA and CX Services SMEs.

    2. Only 18 of 35 stories completed with code changes(2/17)

    3. Only 16 of 22 stories completed with code change(2/24)

  4. OpenInvoice testing will have to be 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.

Notes

  1. UI case counts was reduced to ~400 from ~760 after @a user reviewed and removed duplicates and irrelevant modules for given clients.

  2. SMEs from the CX team are assisting in functional testing with @a user updating the tracker based on their testing.

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

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

    1. Upstream and Regulatory team are both 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 each 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.