20230517 - 10.2 Rollout Status Report
Current progress of Unity testing, development, and deployment. Current clients targeted are Terra, GME, IKAV, Vital, Flywheel.
RISKS
Need continuous performance optimization plan for GME and Terra after go-live
Unclear communication across teams targeting next phase of Unity Rollout
IKAV testing on Azure has experienced multiple issues that cannot be reproduced internally on functionality already passed internally and at other client UAT.
We are not able to identify the cause of issues yet whether environmental or data set driven.
Code freeze has not occurred(Vipul to opine)
1 critical for GME go-live; assuming no code change is needed but can’t confirm until refresh is complete
All Terra critical tickets have been resolved
Clients using EAG to test cause additional WES resource burden to validate issues.
Initial regression testing on Flywheel and Laredo have found multiple JIB issues that were previously thought resolved (could be dataset related but unknown at this time).
Establish upgrade procedures and version controls for live clients on a single code version.
Need agreement by all internal teams so that client communication is aligned.
Needs to be clearly communicate to clients so they understand the future process.
Need to confirm any risk associated with testing on one type of environment and going live on another.
Current Status
TERRA IS A GO
Cutover to officially begin 5/18 at 11pm. Vipul’s team has already started tasks behind the scenes.
IKAV Tie-out testing
Revenue company processes delayed due to environmental constraints. Will be done in parallel with IKAV UAT testing.
Functional regression
IKAV - 50 Untested, 2 Failed (no change)
Flywheel - Untested - 77, Pass - 69, Blocked - 1, N/A - 10, Unable to test - 3 (High Risk)
Vital - Untested - 642, Pass - 247, Fail - 12, Blocked - 7, N/A- 39, In-Progress- 3(Full Test Suite)
IKAV UAT
74% complete testing - 290 Pass, 13 Fails, 100 To Do
9 complete, 4 in code change
Client logged ticket count - total
GME - 4 code change, 5 complete, 2 awaiting feedback, 4 in review, 26 closed no action (39)
Terra - 4 code change, 14 complete, 4 support review, 13 close no action (35)
Flywheel UAT
Environment setup complete 5/10/23
One ticket reported and closed, user error.
Very little testing on client’s end this week so far
Focus for Next Week
Continue Vital & Flywheel regression testing - TBD QA resource & @a user coordinating
Riverbend UAT setups
Highpeak UAT discussions
IKAV OpenInvoice invoice sync testing with fake server - @a user coordinating
Focus on dev completion of issues across Scrum Teams - @a user coordinating
Monitor client UAT testing - @a user and CSMs coordinating
Finalize dates for Pilot Clients for future Unity Releases - @a user and @a user coordinating
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 | Regression testing dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10080 Release 10.2.0 Dashboard - https://wenergysoftware.atlassian.net/jira/dashboards/10077 |
