Tosca 26.1 adds AI chat inside Tosca Commander, manual to automation (including pulling in qTest manual tests), requirement to automation from a Jira requirement, co-create and autonomous automation modes, debug/fix/rerun, and self-healing scripts that adapt when the application or interface changes. These run on the Tosca MCP server and Knowledge Base MCP, already live for supported on-prem versions.
Key Takeaways
- 01
Tosca 26.1 adds AI chat, manual to automation, requirement to automation, co-create and autonomous automation modes, debug/fix/rerun, and self-healing scripts inside Tosca Commander.
- 02
The Tosca MCP server and Knowledge Base MCP that these features depend on are already live for supported on-prem versions.
- 03
An on-prem upgrade to 26.1 delivers AI through a connected cloud tenant without moving infrastructure, generally a 10 to 14 week project.
- 04
A full migration to Tosca Cloud generally runs 12 to 22 weeks and removes the need for future upgrade projects.
- 05
Merito is an authorized Tricentis reseller and services partner, listed as a Certified Solution Partner in the Tricentis partner directory. It can deliver the readiness, upgrade, and AI enablement work whether the engagement is quoted by Tricentis or by Merito.
Tosca 26.1 AI Capabilities Explained | On-Prem vs. Cloud Upgrade Paths: transcript and chapter notes
Tosca 26.1 is out, and it brings the first wave of AI capability into Tosca Commander. Chris Carpenter, COO at Merito, walks through what shipped, why it matters for testing teams right now, and the two upgrade paths available to Tosca customers.
What's in this video
Development teams have been AI-enabled for a while, and that has pushed more code, faster, onto testing teams that are often still running things manually. Tosca 26.1 is built to close that gap. The release includes AI chat inside Tosca Commander, manual to automation, requirement to automation, co-create and autonomous automation modes, debug, fix and rerun, and self-healing scripts, all built on the Tosca MCP server and Knowledge Base MCP, which are already live for supported on-prem versions.
Two paths forward
Upgrading to 26.1 on-prem keeps your infrastructure exactly where it is and delivers AI through a connected cloud tenant, generally a 10 to 14 week project. Moving to Tosca Cloud is a longer project, generally 12 to 22 weeks, and gets you automatic updates and scaling with no capacity planning. These are general ranges. Your actual timeline depends on account size and complexity.
If Tricentis reaches out to you about this upgrade, you can ask for Merito as your delivery partner on their paper, or we can quote it directly on ours. Merito is an authorized Tricentis reseller and services partner, listed as a Certified Solution Partner in the Tricentis partner directory, and runs the readiness call, scopes the work, and delivers the implementation and AI enablement either way.
Learn more about how Merito delivers Tosca: Tricentis Tosca
Chapters
0:00 Open 0:43 Agenda 1:22 Why We're Here 3:45 The AI Capabilities 12:02 Your Path Forward 14:40 Timeline 17:14 Next Steps 19:17 Close
Frequently Asked Questions
Tosca 26.1 AI Capabilities Explained | On-Prem vs. Cloud Upgrade Paths: questions and answers
Consultation request
Book a consultation with Merito
Use this form to talk through the workflow, platform fit, and delivery priorities behind this video with a Merito specialist.
Discovery
Turn the video into a working plan
Use the conversation to translate what you saw here into a practical next step for your team.
Alignment
Get the right specialist involved
We route the request to the team best suited for platform strategy, implementation, quality, or AppSec delivery work.
Get Started
Secure intake workflow
The request is protected by reCAPTCHA Enterprise and processed through Merito's standard consultation flow.