What's new at Katalon: October 2026 release roundup 🎃

[nghi.phan]

What shipped in October

Release roundup · Oct 19–30, 2026. Treats from four product teams.

Happy Halloween, everyone @trust_level_1

Fresh from our product teams, here’s everything that shipped between October 19 and October 30. A few of these started as threads right here on the forum, so thank you.

Open the product you use below. Each section has short demo videos.

The 30-second version

	What’s new	Where
	Push test cases to Azure DevOps	True Platform
	Pick which Jira issue types count as defects	True Platform
	Katalon AI learns from drafts you discard	Katalon AI
	Charts and KPI tiles right inside the AI chat	Katalon AI
	Record and run tests on hybrid mobile apps	Studio 11.7.0
	BDD step definitions through MCP	Studio 11.7.0
	Import Postman environments	Studio 11.7.0

Pick your product

True Platform: ADO export, Jira defect types, and quality-of-life fixes

Push test cases to Azure DevOps

You could already import from ADO. Now it works the other way too. Go to Tests > Test Cases and export Cloud test cases as native ADO Test Cases. Create new ones, or sync to items that are already linked.

Map Jira defect types per project

Not every team files bugs as “Bug.” In each project integration, choose which Jira issue types TestOps treats as defects.

Testers then pick from those types in the Report Defect dialog.

Small things, big relief

• Add a test step or call a test case straight from View mode. No need to switch to Edit.
• Secrets can now be up to 48 KB, so long Jira API tokens finally fit.
• The new Mobile Browser picker shows the full browser and OS version list.
• Accessibility work (WCAG 2.1 AA) across Tests, Plans, Live Testing, Reports, Settings, and more.
• Imports and manual test processing are harder to stall when one batch goes wrong.

Katalon AI: learns from you, draws charts, explains failures

It learns from your feedback

Discard a generated test case draft and a Why discard? menu asks for the reason. Katalon AI can then suggest personal memories from your edits and discards.

You stay in control. Nothing changes until you accept a suggestion, and your memories stay personal. They never become project-wide rules on their own.

Charts right in the chat

Ask a data question and get charts, KPI tiles, and a table view inside the thread. Where Artifacts are on, the chart pages are saved there too.

Run with AI

The new Run with AI screen is on for everyone, with a Test Cloud environment picker in quick run.

Manual runs can target native Android apps on Test Cloud real devices, up to 5 cases in parallel.

• AI Sessions progress updates live. No more refreshing.
• Failed runs now tell you why: model service, quota, environment setup, or Katalon Tunnel.
• After the AI creates or changes something, you get a direct link to it.

Katalon Studio 11.7.0: hybrid mobile, BDD via MCP, Postman environments

Hybrid mobile app testing

Record and run tests on apps that mix native screens with embedded WebViews. Switch between native and WebView contexts, save WebView objects, and run it all in one flow.

Full BDD workflow through MCP

The Studio MCP Server adds a writeStepDefinition tool. AI-assisted authoring now goes all the way from feature steps to working step definitions.

Import Postman environments

Bring in a Postman environment file with your collection. Environment variables, even ones not stored in the collection, come across into your API project.

Also in 11.7.0

• Studio follows True Platform admin controls for AI and user-provided AI keys
• Faster startup, project reopening, and Test Case Browser search
• Smoother handling of large Object Repositories
• Dependency and security updates (Cucumber, Gradle, jsoup, embedded webdrivers, and more)
• Mobile recorder, self-healing, and WebView fixes
• TestRail legacy custom fields and Dynamic Test Suite retry fixes
• Accessibility and theme improvements

TrueTest: steadier replay and smarter filters

• Replay handles rich editors (like TinyMCE) and value-help inputs more reliably.
• The webdriver filter works the same way in User Sessions and Journey Map generation.
• Journey Map generation picks up where it left off if it gets interrupted.
• Search Applications Under Test by name in Account Settings.
• Accessibility fixes across tracking, configuration, and journey maps.

Knock knock

Knock on the door and see what you get. Usually it’s a treat from this release. Sometimes it’s a trick.

• Treat: Push test cases to Azure DevOps. Export Cloud test cases as native ADO Test Cases.
• Treat: Map your own Jira issue types as defects, per project.
• Treat: Katalon AI learns from the drafts you throw away.
• Treat: Charts and KPI tiles right inside the AI chat.
• Treat: Record and run tests on hybrid mobile apps in Studio 11.7.0.
• Treat: BDD step definitions, written through MCP.
• Treat: Bring your Postman environments into Studio.
• Treat: TrueTest Journey Map generation picks up where it left off.
• Trick: Your flaky test passed. Then failed. Then passed again.
• Trick: The locator changed while you were reading this.
• Trick: It works on my machine.
• Trick: Someone renamed the test suite final_FINAL_v2.

Trick or treat: guess the feature

Vote on each card. Every right answer puts a candy in your bag Answers and the top candy collectors are announced in this thread when the quiz closes on 2026-11-06T10:00:00Z.

Your Jira project uses a custom issue type called ‘Defect’, not ‘Bug’. TestOps keeps ignoring it. Which update fixes that?

• Jira defect type mapping
• Why discard?
• Postman environment import

You keep deleting the same kind of bad test case draft. The AI keeps writing it. Which update fixes that?

• Charts in the AI chat
• Why discard?
• Run with AI

Half your app is native, half is a WebView. Your recorder only sees one half. Which update fixes that?

• BDD through MCP
• Push to Azure DevOps
• Hybrid mobile testing

Your turn

Which update will you try first?

• Push test cases to Azure DevOps
• Custom Jira defect types
• Katalon AI learning from feedback
• Charts in Katalon AI chat
• Hybrid mobile testing in Studio
• BDD step definitions through MCP
• Postman environment import

What should we cover next in a deep-dive post or live session? (pick up to 3)

• ADO two-way sync walkthrough
• Setting up Katalon AI memories
• Hybrid mobile testing from scratch
• BDD + MCP in Studio
• Postman to Katalon migration

Tried something already? Hit a snag? Reply below with a screenshot. We read every post and pass it on to the product team.

Release notes: Katalon Studio 11.x · TrueTest. The pages for these releases are being added.

[arvind.choudhary]

I like that “Why discard?” captures the reason and doesn’t just record the discard.

[arvind.choudhary]

Hybrid mobile testing in Studio 11.7.0 is the one I’m most keen to try. Context switching between native and WebView is where a lot of mobile suites turn flaky: the context list isn’t ready when you ask for it, or the WebView hasn’t finished loading when the script switches. Being able to save WebView objects and run native and WebView steps in one flow should remove a lot of custom Groovy glue. Curious how the recorder handles apps with multiple WebViews on one screen, and whether the context-switch wait is configurable.

[arvind.choudhary]

Run with AI: failure reasons: Failed runs will now tell (model service, quota, environment setup, or Katalon Tunnel) is a big time saver. The first question after a red run is always whether it’s a product bug or an infrastructure problem. Sorting failures into those buckets before anyone digs in speeds up triage a lot. It would be even better if the same classification showed up in reports and trends, so teams can see how many failures are infra noise versus real defects over time.

[arvind.choudhary]

Thanks for the roundup, @nghi.phan and team.

[arvind.choudhary]

BDD step definitions through MCP: writeStepDefinition completes the BDD loop for MCP-assisted authoring. Generating feature steps was only half the job, because the step definitions are where the real maintenance lives. I’d like to know how it handles reuse: does it detect existing step definitions and reuse them, or create near-duplicates? Duplicate steps are the usual way Cucumber suites get messy over time.