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
Internal deadline for completing regression testing and providing clients UAT env was 3/15
IKAV regression testing was slated for 3/15 or early and we have not begun
Tie-outs in progress
Terra Production and Revenue Allocated results have differences and still in progress
Both GME and Terra Revenue Asset and Company processes are tied out through to financials
Differences are due to minor rounding issues
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
Ran through JIB on GME with mid-month database and validating results now with SME
Terra JIB specific database should be loaded this weekend
Revenue check remittance file is missing details and still in progress
OpenInvoice testing with fake server complete and passed
Testing is ~95% complete with High Risk ~99% complete
Tickets completed - 23 stories for 51 points
Open tickets - 21 tickets (5 - “To Do”, 7 - “In Progress”, 7 - “In Review”)
To Do - 3 are performance related, 1 UAT environmental, 1 related to background task
Another round of performance testing (~10-15 users at once) was performed on 3/13
RISKS
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.
Client reported issues that are data dependent may require db refreshes to internal environments.
Currently this can take a full day or more for Terra and GME.
Resources on COLO are strained and cannot support additional instances of large clients.
We have no specific performance metrics and yet clients have expectations of improved performance with v10.
OpenInvoice testing was 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.
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.