20230324 - 10.2 Rollout Status Report
Current progress of 10.2.0 testing, development, and deployment. Clients targeted are Terra, GME, and IKAV.
RISKS
Issue found with migration that could invalidate the GME and Terra testing databases.
Proposed solution that should allow us to keep existing databases and resolve issue.
Production Accounting tie-out still unresolved with effort going on almost 1 month.
JIB tie-out being held up by a posting issue. Based on data review JIB appears clean on GME and Terra.
IKAV regression has not started.
IKAV is slated for UAT in 1 week total. We will need to turn around any issues ASAP to achieve this kind of timeline.
Environmental issues delayed both GME and Terra UAT start dates.
Client reported issues that are data dependent 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.
OpenInvoice testing was done with Fake Server internally. API testing will only be done in UAT.
No GIS testing capabilities at this time.
Current Status
Internal IKAV environment is being migrated and expected to be available by Monday
Tie-out progress
Terra Production have differences and still in work per note in RISKS.
JIB is clean on GME and Terra appears to be as well. Last validation is waiting on a fix to the posting engine for the JIB JE.
Created 4 tie-out scripts (posted on Confluence) that can be used by our teams in services or QA to do future JIB validations for testing or implementation.
Revenue check file issue is now resolved. GME issue that was noted is related to migration issue listed in RISKS.
Migration issue is being resolved by Nathan with a temp solution that allows us to maintain existing migrated database to not interrupt Client testing.
Tickets completed - 9 stories for 18 points
Open tickets - 21 tickets (3 - “To Do”, 10 - “In Progress”, 4 - “In Review”)
To Do - 2 are performance/stability related, 1 is a cleanup task
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 |