Week 8 of 8
Release Reports, toggles and automation
After go-live the work changes shape. Every month there is a maintenance update to triage; every April and October a feature release to regress. Infor’s Release Report is the input: read it, decide what affects you, and turn that into test scope before the update reaches production.
Feature toggles help, with a deadline. On M3, a toggled feature has a transition period of at least six months, and the feature list shows the update that will switch it on for you. Test it before you switch it on, and certainly before Infor does.
This week: set up the update routine that runs all year
- Triage every Release Report item against your process list: affects us yes, no or to decide. Any "yes" without a test is a gap.
- Track each feature toggle with its forced-activation update and an owner. Flag anything inside 60 days that is untested (example threshold).
- Automate the Critical processes from your Week 2 ranking first, and the ION flows from Week 4. They run in every cycle.
- Measure three things per update: critical-process coverage, regression cycle time and defects that escaped to production.
Number of the week
6 months
minimum transition period for a toggled M3 feature before it is forced on.
Source: Infor M3 documentation, Manage featuresUse this week
- Infor CloudSuite Update Regression Plan →
Release calendar, Release Report triage, toggle countdown and scope rules in one workbook.
- Automation Prioritization Scorecard →
Score which tests to automate first, with your own weights.
- Guide: testing Infor CloudSuite updates →
The full routine, with every source cited.
That is the playbook. From next week you will get a weekly roundup of new statistics, guides and templates from The Sign-Off Table.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.