Skip to main content
Skip table of contents

20230210 - 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. Effort for VEF has stopped. Open issues are still being resolved unless data dependent. We are continuing to use the environment for UI testing and the tracker has been updated to remove untested test cases.

  2. All environments are active with additional databases for Tie Outs being created (e.g. data prior to Revenue processes being run for 1 to 1 comparison).

  3. Testing is over 57% complete with High Risk ~60% complete.

  4. Tickets completed - 25 stories for 33 points

  5. Open tickets - 39 tickets (20 - “To Do”, 11 - “In Progress”, 8 - “In Review”)

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. Code dependent bug resolution still does not have a quick turnaround time.

    1. Only 14 stories completed with code changes.

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

  3. Deploy failure caused environments to be down almost a complete work day for India resources.

  4. Jenny will be on PTO through end of the month starting next Friday.

  5. OpenInvoice testing will have to be done with Fake Server internally.

  6. 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 (Frank returned from PTO).

  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.