For CloudSuite customers, biannual releases and monthly releases mean tackling the same questions every time: what has changed, and what does it mean for our business processes? Answering them usually involves hours of reading release notes, comparing them against your configuration, and testing the flows that matter before anything reaches production.
This blog draws on our recent webinar on how AI-powered automated regression testing can help you during release season and beyond. It covers what the release brings, how our release agent narrows the focus, the AI features that power Fortest – our automated regression testing product, and the questions our audience asked along with the answers from our specialists.
What the October release brings
Infor describes the 2026.10 release as built to execute. AI is moving beyond recommendations to completing routine work within approval workflows, bringing people in where judgment is needed.
Industry AI Agents are expanding across ERP, finance, supply chain, customer service, analytics, and HR. For M3-based CloudSuites, these include a Financial Accounting Agent to support reconciliation and a Configuration Agent for M3 configuration and feature settings.
AI is also becoming part of the tools people already use. M3 H5 gains natural language search, XtendM3 extension code can be reviewed with AI, and Infor GenAI Assistant now draws on a Public Knowledge Hub of product documentation, user guides, and release reports available to all customers. Infor Velocity Suite brings agents, process mining, automation, and governance together in one offering.
Strengthened governance is also part of the full release package. Infor is extending AI governance within Infor Governance, Risk, and Compliance, helping organizations manage AI initiatives alongside traditional business risks while ensuring agent and human actions are traceable and auditable.
With more AI-driven capabilities entering the ERP environment, each release also brings changes that need to be assessed and validated. A structured approach to release readiness is therefore essential.
How our release agent helps
Once a release lands, the first job is finding out what affects your system, and that is what Fortest’s release agent does.
This is how it works:
- Collects the release: Pulls the M3 release report from the portal each month.
- Extracts each tenant: Captures the IOS Vault footprint for each customer.
- Runs AI impact analysis: An AI model matches the release to each footprint.
- Generates two reports: An analyst deep-dive and a customer dashboard.
- Reviews & publishes: Validates the findings, sets severity and shares them with the customer.
- Tracks & improves: Logs findings in Jira through to closure and feeds learnings back to the build team.
The dashboard shows how many release items are coming your way and how many affect your applications. It breaks these down into the components affected, defects fixed, and enhancements delivered. It also shows severity from high to medium, the split between defects and enhancements, and a summary by functional area such as finance, maintenance, and sales. Instead of reading every note, your team sees what matters to them.
The analysis then goes to the automation team, so they know exactly where to focus. The release agent is available as an add-on for CloudSuite customers.
The AI inside Fortest: Testing what matters after a release
Once you know what is impacted, you need to test it. Even though Infor tests its own releases, your configurations, master data and integrations make your processes different, so end-to-end regression testing of your own flows still matters. Fortest applies AI in four ways:
Recording through a web extension: The extension opens as a side panel beside your application. As a tester works through a scenario, it captures each action along with the relevant element information. Testers can add parameters and assertions so the generated automation has the right inputs and validations. Passwords and other sensitive values are captured as parameters, so they are not exposed to the agent or written into the generated script.
AI code generation: The recording is turned into an executable script, which is pushed to an Azure project repository and brought into the Fortest execution manager. Fortest is built on reusable libraries and prebuilt Infor test cases, and the AI speeds up script creation on top of that.
Self-healing: After a release, a script can fail because a UI element has changed, even though nothing is actually broken. Fortest identifies these failures, heals the script, and asks the user to verify the change before it continues. Teams can then concentrate on real defects.
The execution manager: Runs can be scheduled in parallel or in sequence, planned in a calendar view, and reviewed through a module-level heatmap. Screenshots from each run support the go or no-go decision.
Looking ahead, the roadmap includes a documentation agent that turns scenarios and screenshots into user manuals, along with load testing.
Answering some frequently asked questions on Fortest
Do you only test Infor components, or can Fortest work across multiple systems?
Any flow that is web or API-based can be automated, so a scenario can start in one system, pass through others and finish back in M3. One recent customer scenario, for example, began by bringing orders down from an e-commerce website into the testing flow.
In the case of this customer, order files were dropped to a location and picked up by an EDI interface, a customer order was created in M3, and the flow moved on to shipment creation, an external tracking application and, finally, invoicing in M3. Along the way, Fortest holds on to values such as the customer order number created at the start so it can verify them later in the flow. It also uses parameterized data files, so the same script can run across many iterations.
Do you archive the testing evidence?
Yes, some customers need to give testing evidence to their auditors as regulatory requirements, and Fortest reports are used as compliance documents. Each run produces a detailed report, with screenshots of key steps, passing and failing, depending on preference. These can be downloaded and stored.
Does Fortest support other ERPs?
Yes, Fortest is ERP agnostic. We currently support businesses on Infor M3 and Microsoft Dynamics 365 Business Central. Because Fortest records real user scenarios and automates any web or API–based flow, the same approach applies regardless of the ERP you run.
Release readiness, simplified
Every release brings new capability and new risk. Knowing what applies to your environment, and proving it works before go-live, turns an update into an advantage. Release season comes around twice a year, but monthly releases keep arriving in between. With the release agent showing you where to look and Fortest automating the checks, your team spends less time reading and re-testing, and more time on work that moves the business forward.
Watch the full webinar and talk to our team to see how Fortest can help you during this release season.
