Week 2 of 8
Who owns testing
Cloud ERP moves infrastructure and upgrades to the vendor. Testing stays with you. Sage Intacct updates every customer automatically each quarter and its pre-release checklist puts the review on the customer. Odoo tells customers to request an upgraded test database and test it before upgrading production. Acumatica says major upgrades need sandbox testing, customization validation and user training.
On-premises is ending too. Epicor has said its final on-premises Kinetic feature release is 2028.1, tentatively January 2028, with new features going to Epicor Cloud only. More teams are about to live on a vendor’s calendar for the first time.
This week: give every testing activity one accountable owner
- List the activities: unit, SIT, data import and migration, roles and permissions, performance, UAT, mock cutover, and regression for every vendor release.
- For each, name one accountable person: your team, the implementation partner, an ISV, or the vendor. Write "nobody" if that is the truth.
- Put ISV and partner regression in writing: who tests their add-on on each pre-release build, and how fast they fix it.
- Write the master test plan once, with numeric entry and exit criteria, and have the program director and business sponsor sign it.
Number of the week
Jan 2028
is Epicor’s tentative date for the final on-premises Kinetic feature release. After that, new features ship only to Epicor Cloud.
Source: Epicor press release (January 6, 2026)Use this week
- ERP Implementation Master Test Plan (Word) →
Test levels, owners, environments, entry and exit criteria and the post-go-live release plan, for any ERP vendor.
- TCoE Operating Model & RACI →
Testing activities against roles, with a check that every row has one accountable owner.
Next week: you cannot test everything every release. We rank your processes so you know what to test first.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.