20230303 - 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
Internal deadline for completing regression testing was 3/1 and we have now passed that date.
Tie-outs in progress
GME asset level completed
Terra Production and Revenue Allocated results have difference with issues logged
Terra Revenue Value results have additional records but no value difference
Both GME and Terra Apply DO have differences with issue logged
Blocking downstream Revenue Company process testing
JIB issues have been logged but we have not loaded the specific JIB tie-out databases because we are stuck on Revenue tie-out
Testing is over 89% complete with High Risk ~99% complete.
Tickets completed - 33 stories for 68 points (double the effort from previous week)
Turnaround on tickets has increased across all teams.
Open tickets - 51 tickets (18 - “To Do”, 15 - “In Progress”, 18 - “In Review”)
Stress testing performed 3/2/23, Vipul addressing performance
RISKS
Updated compare tool being used to compare large datasets for company level processes.
We have no performance metrics and yet clients have expectations of improved performance with v10.
Many 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.
This is across QA and CX Services SMEs.
Only 18 of 35 stories completed with code changes(2/17)
Only 16 of 22 stories completed with code changes(2/24)
Only 14 of 33 stories completed with code changes(3/3)
OpenInvoice testing will have to be done with Fake Server internally.
No GIS testing capabilities at this time.
Future Process Improvements
Build RACI matrix for future efforts for transparency of responsibilities across teams.
Add automation for the “easy” wins like UI testing to eliminate almost 30% of the testing effort.
Continue to build out test cases for regression testing across the application.
Add expected results to compare against for testers with limited functional knowledge.
Have defined performance testing with PROD comparable environments to provide better expectations to clients when taking code.
Add code test coverage to eliminate lost functionality with future merges or code changes.
During current round of testing multiple issues have re-emerged after originally fixed.
In the 20 weeks since Flywheel went live with v10, this is the bug count for clients whose code is in v10.2.0
Client | Number of Bugs | |
|---|---|---|
Flywheel | 4 | *after 3 weeks of stabilizing release |
GME | 11 | |
IKAV | 21 | |
Laredo | 10 | |
Surge | 15 | |
Terra | 14 |
Notes |
|
|---|---|
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.