Release Notes - Katalon True
October 28, 2026β
Enhancementsβ
- When scheduling a run with an environment your organization is not licensed to use, the error now names the missing license type.
- The Executions history shows browser icons for Samsung Internet and UC Browser Turbo sessions instead of a generic icon.
Fixes
- Azure DevOps test case imports now finish and display the imported cases instead of remaining at Processing after validation completes.
- Synchronization with an application lifecycle management (ALM) integration no longer starts overlapping syncs, and stalled sync tasks can recover instead of remaining stuck.
- Pushing test results to Xray no longer intermittently fails with a generic error when the configuration is valid. If a push fails, the error explains the cause.
- You can delete a ZIP repository after completed Run now executions when it has no schedule, instead of being blocked by references to those runs.
- Assigning the Account Admin role succeeds when licenses are available, instead of incorrectly reporting that the assignment exceeds the available licenses.
- Standalone sessions now leave Running when execution finishes, including when results and artifacts have already been imported.
- Long-running Playwright sessions on Katalon Test Execution Cloud no longer terminate unexpectedly after about five minutes.
- Results for Playwright tests annotated with
test.fail()now match the Playwright HTML report instead of showing the opposite status. - Stopping one Katalon Tunnel client no longer interrupts traffic for other clients that remain connected.
- The Plans > Releases list opens with the latest release dates first instead of the oldest releases.
October 22, 2026β
New featuresβ
Push test cases to Azure DevOpsβ
- What's new: Export test cases from a Cloud repository in Katalon True into Azure DevOps as native Azure DevOps Test Cases. Choose Fresh to create new cases or Linkage to update linked cases and create cases where no link exists.
- Why this matters: Teams working in Azure DevOps can use test cases authored in Katalon True without recreating them manually.
- How it works:
Each push is a one-time action, not an automatic sync. See Push test cases to Azure DevOps for requirements and steps.
Tell Katalon AI why you discard a generated test caseβ
- What's new: When you discard an AI-generated test case, a Why discard? menu opens. Pick a reason from the provided list, which then discards the case. The same menu opens from a row's discard icon, Retry discard, the detail pane, and bulk discard.
- Why this matters: Your reason stays with the discarded case, so Katalon AI can learn which kinds of cases your team does not want.
Memory suggestions from your edits and discards (early access)β
- What's new: Saved edits and reasoned discards of AI-generated test cases now produce memory suggestions. You do not need to explain the pattern in a chat message. Each suggestion appears in Personalization under Needs your review and states what it came from, for example the cases you discarded and the reason you picked.
- Why this matters: A correction you make in the test case list becomes a lesson you can review, such as a naming convention or a type of case to stop generating.
Nothing applies until you accept it. Open Personalization from the Katalon AI header, then accept, edit, or dismiss each suggestion. This feature is in early access and is being rolled out by organization.
Charts and dashboards in Katalon AI chat (early access)β
- What's new: Katalon AI can answer a data question with a chart page inside the chat, above its reply. For example, ask for a health dashboard for a week to get KPI tiles, an outcome bar chart, and a pass rate by platform chart. Each chart has a Table view toggle. The page is also saved under Artifacts. Charts work in the full Katalon AI page and in the side panel.
- Why this matters: Trend and breakdown answers are easier to read as charts, and you can check each chart against its table without leaving the conversation.
This feature is in early access and is being rolled out by organization. Pages larger than 2 MiB are not displayed. Links in a chart page open only http and https addresses, and Katalon AI asks before it opens another site.
New Run with AI interface with a TestCloud environment pickerβ
- What's new: The new Run with AI interface is now on for all users. In the Run with AI dialog, the Environment field opens a TestCloud picker for desktop browsers. Select the OS, then the browser, then the version. The run banner shows the selected browser.
- Why this matters: When you start Run with AI from a test list, you can choose the exact OS and browser for the run in the same dialog.
The choices depend on your TestCloud license:
- Licensed: Linux, Windows, or macOS with Chrome or Edge, stable versions only. The default is the newest stable Chrome on Linux.
- Unlicensed: Chrome on Linux or Windows, latest stable version only. The dialog shows a warning.
- If Katalon cannot read your license, the dialog shows Could not load license information and offers the unlicensed choices.
See Run with AI for the updated steps.
Enhancements
- After Katalon AI creates, moves, duplicates, or updates a test case, test suite, or folder, its reply ends with a direct link to the item, such as Open the test suite. Agents connected through the Katalon MCP server get the same link in the tool response. See Katalon True MCP Server.
- In Admin > Configurations > AI Services > Edit Account AI Key, each selector under Model per Capability Tier has a Search models input. Search matches the model name and model ID and ignores case. The saved model changes only when you select a model and save.
- Memory suggestions skip short-lived notes, do not suggest the same lesson twice, and keep the latest wording of a correction.
- Each Jira project integration can specify which issue types appear as defects in Report Defect, rather than recognizing only the Bug type. See Jira integration.
- Add Test Step and Call Test Case now start directly from View mode, entering Edit mode through the existing draft flow without a separate switch to Edit first.
- Secrets in Katalon True now accept values up to 48 KB, including longer API tokens.
- The new Mobile Browser Live Testing interface lists the remaining supported browser and OS versions, so you do not need to return to the old picker to select them.
- Test case detail panels use a consistent layout, and icon-only controls in test management have tooltips.
- Accessibility updates across Tests, Plans, Live Testing, Analytics, Project Settings, Account, and Get Started include accessible control names, layout reflow at 200% zoom, and clearer form errors.
Fixes
- An AI run now ends as Failed when the AI model service, the AI provider quota, or Katalon Tunnel fails. Before, the run could stay Running. Each test case shows the cause in the AI Verdict panel under Why this test case did not pass, with a Rerun button.
- In Executions > AI Sessions > Test Steps, step icons and counters now update while the run advances. You no longer need to refresh the page.
- When you rerun an AI test run that someone else started, the executor is now set to you. You can still change the executor to schedule the rerun for someone else. Manual test run reruns work the same way.
- When Save all fails for some AI-generated test cases, each failed row in the Katalon AI side panel shows the cause and a way to fix it. For a duplicate title, the row shows Needs changes with Rename and Change folder, and Katalon AI asks how you want to resolve the conflict.
- A draft that you ask Katalon AI to discard after a failed save now leaves the list. Other saved cases stay.
- The Azure DevOps result-push dialog restores your saved project, test plan, and test suite when the token has access. Insufficient access now shows a recovery message instead of an internal error.
- Report Defect now creates the Jira issue and links it to the test result instead of failing with Invalid Jira ID.
- Save & Create Another clears the previous test case's data before you enter the next case.
- Opening an execution from a notification now loads its details instead of leaving the page loading with Invalid time range.
- The breadcrumb in test case details returns to the page you opened the case from, including Test Cases or Test Suites.
- Xray result pushes preselect the last-used integration and parent story for each project. You can still change either selection.
- Edits to automated test case information now persist after saving and refreshing instead of reverting to the previous values.
- Reruns using an inactive tunnel now move to Error instead of remaining queued, and the log identifies the inactive tunnel.
- Sessions no longer remain at Created when a device is unavailable or the live-session limit is reached. Queued sessions also clear automatically after a Katalon Studio session-creation error.
- Katalon True MCP test case and folder writes no longer intermittently time out during concurrent Run with AI activity; failures return an actionable error.
- The Katalon Playwright reporter completes imports for specifications with duplicate
describetitles instead of leaving executions at Importing. The reporter package also includes TypeScript declarations so strict TypeScript builds no longer fail because declarations are missing.
Known issues
- If the AI runner restarts in the middle of a run, the run can stay open. Cancel the run and start it again.
- An AI run can stay Pending when startup planning fails.
October 15, 2026β
New featuresβ
Use separate Azure DevOps credentials for each projectβ
- What's new: Project admins can enter and rotate a personal access token (PAT) for their project's Azure DevOps integration when an account admin permits project-level credentials.
- Why this matters: Projects with different Azure DevOps access requirements no longer need to share one account-level credential.
- How it works:
See Azure DevOps integration for setup requirements and the Use project PAT option.
Track TestPak execution progressβ
- What's new: An always-visible TestPak summary shows live execution progress and counts for Passed, Blocked, Failed, and Skipped results.
- Why this matters: You can check progress and outcomes without opening each test case.
- How it works:
Personalize what Katalon AI learns from conversationsβ
- What's new: After a conversation becomes idle, Katalon AI can suggest a personal project memory based on a correction or preference you shared. A notification in a later chat and the Personalization panel let you review the suggestion, see the quote it came from, and accept, edit, or dismiss it. Project-wide agent rules suggested from chats appear under Needs your review in Project Settings > AI > Agent Rules, where a project admin can review them.
- Why this matters: Repeated guidance can become reusable project context while you control which personal memories and project rules take effect. Suggestions are not used until accepted.
Personal memories apply only to you within that project. Agent rules apply to the project after an admin accepts them. Suggestions appear after the conversation has been idle, rather than immediately.
Edit AI-generated test cases during reviewβ
- What's new: Edit a draft's title, description, pre-condition, priority, and steps directly in the Katalon AI side panel. You can add, remove, and reorder steps, or ask Katalon AI in chat to revise the selected case. If Katalon AI changes a case while you are editing it, choose whether to keep your changes or use its changes.
- Why this matters: You can correct generated cases before saving them without leaving the review flow or regenerating the whole set.
Select Full review in the review widget header to compare drafts with their source before saving.
Keep credentials out of AI answers and generated test stepsβ
Katalon AI redacts password values in its replies and generated content. When a test step needs a stored secret, it uses a Secret Hub reference such as <<PasswordName>> or asks you to create the secret. Generated test cases retain the requested secret reference instead of inserting its value.
Store the credential in Secret Hub and refer to its name when asking Katalon AI to generate login tests. If you explicitly enter a password into a step, it can still be stored in that step, so use a secret reference for sensitive values.
Choose a Tunnel when starting Run with AI from a testβ
The Run with AI dialog now offers a Tunnel or IP whitelisting choice when you start from the Test Case list, Test Suite list, or a test case page. You can start a test against an app on a private network without navigating to Executions first.
Enhancements
- Katalon AI and agents connected through the Katalon MCP server can start a run from an existing TestPak, either as a manual run or a hosted Katalon AI session, and receive a link to the run.
- The Full review link is now in the header of the AI-generated test case review widget.
- Export uses your selected test cases or the current filtered view, including cases in selected folders and their subfolders. See Export test cases.
- When you leave a test case mid-edit, you can recover the unsaved draft when you enter Edit mode again without replacing the latest saved version.
- After you push an automated test run result to Azure DevOps or Xray, the integration result on the Test Run page updates without a manual refresh.
- Breadcrumb links support opening destinations in a new tab, with consistent navigation across modules.
- Accessibility updates across Home, Plans, Analytics, Executions, Project Settings, and Account include keyboard access to the Plans timeline, accessible names for icon controls, and clearer color contrast.
Changesβ
- The Katalon Studio download entry has moved from the sidebar to the user menu.
Fixes
- Open the review page in Katalon AI's test-generation reply opens the generated drafts. If a review link cannot be created, the reply directs you to the review panel.
- Save all and Discard all now complete as a batch for large sets of AI-generated test cases, avoiding partial saves caused by timeouts.
- Future-dated manual test runs now schedule successfully and their details page loads instead of showing Unexpected Application Error.
- Run with AI executes test cases containing Call Test Case steps instead of failing on the referenced cases.
- The Analytics & Trends dashboard returns its AI-generated briefing instead of failing, and multi-project dashboards load in the EU environment instead of showing an access error.
- Large test suite lists scroll to the final test cases instead of cutting off the bottom of the list.
- The version indicator and Update version button stay aligned when a test case has a long name.
- Organizations with only a Private Device license can open the environment selector and schedule a test run instead of being asked to obtain another license.
- Runs using Sauce Labs devices no longer intermittently fail at startup because the Sauce Connect tunnel is not yet reachable.
- The Android live stream no longer flickers black during execution, allowing Spy Object capture to work.
- True Parallel and Standalone executions leave Running when they finish or encounter an error. Standalone session usage also clears when execution ends instead of blocking later runs.
- License assignment in the new Live Desktop interface now works consistently with the previous interface.
- The Tester filter in the requirements list no longer crashes the page. Requirement breadcrumbs also reflect whether you opened the requirement from Releases or Timeline.
- Deleting a test case with a missing linked integration now shows an actionable message instead of a raw error. Adding tags to a Git test suite without a configured PAT also explains which credential you need to configure.
- The Azure DevOps import wizard lets you create a destination folder without leaving the wizard.
- Updating a repository waits for a confirmed sync instead of creating blank duplicate test cases from a stale repository state.
- The Test Cases system-field count excludes deleted cases and archived repositories instead of counting them as active cases.
- Audit Trail records test case and suite creation through imports, ZIP uploads, Git integration, and repository refresh, as well as defect linking and unlinking. Requirement sync produces one consolidated activity entry instead of one entry per item.
October 8, 2026β
New featuresβ
Update a test case during a manual executionβ
- What's new: The run owner can explicitly update a test case in an active TestPak execution to its latest version. Results and evidence for unchanged steps are retained.
- Why this matters: Testers can use a corrected test case without restarting the whole execution or losing completed work.
See Manage test case versions and the demo below for the updated workflow.
Compare test case versionsβ
- What's new: Compare two versions side by side to see changes to test case details and steps. Each version card also shows a short change summary.
- Why this matters: Reviewers can see what changed before choosing a version to execute or restore.
See Manage test case versions and the demo below for more details.
Push manual results to the intended Azure DevOps or Xray executionβ
- Azure DevOps: Select the target Test Suite when configuring a result push. Katalon resolves the corresponding Test Point for the suite and configuration instead of sending results to the root suite's point.
- Xray: If the mapped Jira project offers the Sub Test Execution issue type, select it in the Xray configuration. When pushing a result, choose its parent story and, optionally, an existing Sub Test Execution.
Attach files to defect reportsβ
The Create bug flow now accepts documents, PDFs, videos, and log files in addition to images. These files are attached to the resulting Jira or Azure DevOps issue. The Jira defect form also supports more required field types, including Team.
Review AI-generated test cases beside their sourceβ
Full review now shows the source used to generate test cases, including a requirement, pasted text, an uploaded document or image, or an issue read through MCP. For uploaded files, Open original opens the file and Download saves it. You can check each draft against its source before saving.
Manage Test Suite folders in Katalon Cloudβ
You can rename, move, duplicate, and delete Test Suite folders, using the same folder operations available for Test Case folders.
Enhancementsβ
- Project Settings > AI > Knowledge Base groups its status, last update, and counts of indexed content in one view.
- The test case Activities tab identifies the person who requested a Katalon AI edit and labels the action via Katalon AI.
- Files attached in Katalon AI chat are read by Katalon AI without browser-side conversion, improving handling of complex files such as multi-sheet spreadsheets.
- Katalon AI's Progress, Artifacts, and Test cases side-panel sections open automatically when they contain items.
- Links to test cases and other resources returned by Katalon AI or the MCP server use the workspace's production host.
- Dashboard table cells can link directly to their underlying records when configured, making it easier to investigate a test run from a dashboard.
- The automated test run creation dialog shows the full OS and browser configuration instead of clipping its label.
- Test result details show versioned test management fields again.
- Home and Executions include accessibility improvements to keyboard focus, labels, error identification, zoom reflow, motion controls, and ARIA behavior.
- Live Testing restores the selected app, configuration, URL, environment, and private or local testing settings after a session. Accounts with a private device pool can select Private Devices in the new Mobile Browser and Mobile App Live Testing interface.
- The Parallel Sessions page shows queued sessions alongside running sessions for the Private Devices license type.
- The self-hosted agent rule builder shows Agent name and Hostname as the available matching conditions.
Fixesβ
- When an account admin explicitly turns AI off, the server rejects Katalon True AI requests from that account before calling a model provider.
- Asking Katalon AI to read or summarize a requirement no longer creates test cases unless you request generation.
- Test case generation recovers when Katalon AI mistakenly looks for its built-in generation tool in the MCP catalog.
- Cross-project dashboards load on the first selection without requiring a refresh.
- Mark all as read in notifications no longer intermittently times out.
- Repository resync no longer times out while cleaning up orphaned Test Suites.
- PDF attachments preview in defect reports, and Azure DevOps attachment names display separately.
- Azure DevOps Test Cases with Shared Steps now import those steps.
- The Jira add-on maps Skipped and Blocked test result statuses correctly.
- Git repositories and folders in the Tests tree load on the first click; the tree also remembers the last selected repository.
- Accepted AI-generated test cases save successfully instead of failing with a create error.
October 1, 2026β
New featuresβ
Project context settings for Katalon AIβ
- What's new: Project Settings > AI now brings together three sources that Katalon AI reads before it answers or acts in a project.
- Knowledge Base: Project data and uploaded documents.
- Agent Rules: Project-wide standards for AI agents.
- Project Memory: Personal preferences for the project.
- MCP & Skills: AI client connections and reusable testing workflows.
- Why this matters: Katalon AI can use shared project standards, personal preferences, project data, uploaded documents, and connected AI-agent workflows while respecting existing permissions.
See AI settings for setup instructions and details.
Review files created by Katalon AI in chat side panelβ
- What's new: Files created or saved by Katalon AI now appear as cards at the end of its replies, making them easy to find and open without using the collapsed side pane. HTML files open as rendered previews in the artifact panel, including charts, with Expand, Show source, and Download options. Files larger than 10 MB can be downloaded for viewing.
- Why this matters: You can review Katalon AI's output directly in the conversation where you requested it.
- How it works: Ask Katalon AI to create or export a file, then select its card to open it in chat.
Enhancementsβ
- Katalon AI test case generation from requirements is more reliable: follow-up questions now appear on Requirement Detail, recommended choices are labeled, generation recovers from transient tool errors, and Refresh no longer fails in the test case side widget.
- The live execution video appears faster, lags less, and keeps playing when you expand it.
- Katalon AI and MCP clients can search test cases under a folder and all its subfolders, so a parent folder no longer reports a false zero.
- Long snake_case test case names wrap in the Katalon AI side rail instead of overflowing the chat layout.
- The Project AI permission reads AI instead of Knw in the permission matrix and role previews. Existing roles keep working.
September 24, 2026β
New featuresβ
Test case versions and activitiesβ
- What's new: Test case authoring now uses intentional Save and Save & publish actions instead of auto-save. The revamped details page includes Versions and Activity tabs, version status, author and source attribution, historical views, restore, discard-working-changes, activity filters, and unsaved-change protection.
- Why this matters: You can control when changes become versions, audit test-case history, and restore earlier content without overwriting it.
- How it works: Use the header save controls to create a draft or publish a major version. Open Versions or Activity to review history, restore a version, filter activity, or discard working changes.
Mixed web and mobile-native test runsβ
- What's new: An automated test run can include suites configured for Desktop & Mobile Browser, Mobile Native App, or Web Services.
- Why this matters: Teams can run mixed web and mobile-native coverage together without splitting it into separate runs.
- How it works: Configure the test type on each suite when you're configuring the test; the run-level Test Run Type selector is no longer required.
Automatically select an available self-hosted agentβ
- What's new: Schedules and automated runs can select an available self-hosted agent automatically, with optional operating system, agent name, and hostname rules.
- Why this matters: Runs are less dependent on one pinned agent and can use available capacity at trigger time.
- How it works: Select Auto-select available agent and add rules when needed.
Run-level test data in custom chartsβ
- What's new: The custom chart builder now includes a Test Runs dataset with run identity, method, status, duration, executor, release, sprint, build, and source fields.
- Why this matters: You can chart pass/fail trends and duration at run level.
- How it works: Choose Test Runs in the custom chart builder and select the fields to visualize.
Potential conflicts in Katalon AI responsesβ
- What's new: When Katalon AI generates test cases or analyzes a requirement using your project's AI knowledge base, the response now ends with a Potential conflicts section. Each conflict names the requirement clause and the source that contradicts it, marks whether that source is a declared link or a document retrieved from the knowledge base, and suggests a fix. When nothing conflicts, the section says None found and lists what it checked, for example a PRD and related requirements.
- Why this matters: A requirement that says one thing while a PRD in your knowledge base says another used to produce test cases built on whichever version the model picked, and you found out in review or in a failed run. Now the disagreement is named, with both sources, before you save any drafts.
- How it works: Upload your PRDs and specs to the project's AI knowledge base, then ask Katalon AI to generate test cases for a requirement or analyze its readiness. Read the Potential conflicts section before you save the drafts, fix the conflict at its source, and regenerate if needed. The section only informs you; Katalon AI takes no action on it. If the knowledge base is empty, rebuilding, failed, or out of date, the response says it could not check. See Review potential conflicts.
Acceptance Criteria and other Jira-mapped fields in Katalon AIβ
- What's new: Katalon AI now reads every custom field that your Jira integration's Requirement fields mapping brings into a requirement, including Acceptance Criteria, Steps to Reproduce, and mapped fields of any type, such as text, checklist, and option. It uses those values when it answers questions about a requirement, generates test cases, and asks clarification questions during requirement analysis. Access is read-only; Katalon AI does not write back to Jira.
- Why this matters: Acceptance Criteria is where most teams write the testable part of a story. Previously, a requirement could show a full checklist on screen while Katalon AI answered that it had no acceptance criteria recorded, and test generation worked from the description alone. Generated test cases now trace to the criteria your team agreed on.
- How it works: Map the fields in your Jira integration, then ask Katalon AI a question such as
What are the acceptance criteria for requirement ABC-123?to get the checklist with its completion state. Test generation and requirement analysis pick up the same fields automatically. See Use Jira-mapped requirement fields.
MCP tools for recording and reviewing test resultsβ
- What's new: The Katalon True MCP server adds the
update_test_resultstool with two modes. Manual record writes case and step status, actual-result notes, and evidence for a manual test run, without ending the run or changing the test case. Automated review changes the status of one result in a completed automated run; you supply the status you expect the result to have now, and a result already in the target status is left unchanged. - Why this matters: MCP clients could read test results but not write them, so an agent that ran a manual check in Claude Code or Codex had to hand the outcome to a person for data entry. Now the agent records the result, with its evidence, where it belongs.
Enhancementsβ
- Test case custom fields and tags are available as filters across filterable TestOps views, including Automation Progress Analysis.
- Azure DevOps imports now map Automation Status to the True Platform test case.
- TestCloud Applications now supports automatic failure of stuck uploads, OS and status filters, broader search, sortable and resizable columns, an Uploaded By column, clearer tooltips, and a sticky action column.
- TestCloud
openBrowsernow forwards standard and vendor WebDriver capabilities alongsidekatalon:options. - Empty suites release reserved execution quota after completion.
- Test-case versions record actor and source, including AI attribution.
- Agents that build test runs over MCP with
create_test_runnow send canonical values downstream, for exampleDESKTOP_AND_MOBILE_BROWSERwhen you ask for "desktop and mobile browser", so display values no longer reach scheduling and fail there. The helper toolsbuild_scheduleandbuild_run_configurationare described as local builders that create nothing, and a wrong or legacy field name returns an error that names the field to send. find_test_cases_by_requirementnow acceptsrequirement_id, the requirement's internal ID in Katalon True Platform, alongside the ALM key and the external issue ID. Agents that already hold a requirement record can list its linked test cases without looking up the Jira key first. Supply exactly one identifier; zero or more than one returns a validation error.- Knowledge-base document ingestion now handles large and concurrent uploads reliably.
Fixesβ
- Jira-synced sprints and releases now load promptly in Plans > Timeline.
- Large test case imports now complete successfully, including imports with large volumes of content.
- Valid root folders now load correctly in the repository.
- Inactive Azure DevOps integrations are no longer selected automatically.
- Test-case rows-per-page preferences now persist when navigating between pages.
- When test-case versioning is disabled, automation test cases can be duplicated, moved, and deleted.
- Linux Chrome Playwright sessions now connect and execute successfully.
- AI Runner now completes logins where the email OTP is six single-digit boxes in one group. Previously, the runner stopped with "email OTP target is ambiguous" before calling your OTP provider, and the login never completed. The runner now treats the group as one OTP target, fills the fresh code, and continues, without storing the code or credentials.
- Katalon AI now reads the automation status field directly, both when reading a test case and when filtering. Previously, it inferred automation status from test type or incomplete data, for example answering "Automated 10, Manual 10" for cases spread across four automation statuses.
- Katalon AI now reports generated test cases as saved when the save succeeds, and saves still in progress resolve to their final result. Previously, it could say "No test cases were created" while the cases landed in the right folder moments later, and teams re-ran generation and created duplicates.
- Agent rules CSV exports now escape double quotes, so every exported rule imports into another project. Previously, a rule such as
Use the "Smoke" suitesplit into the wrong columns on import and was skipped.
Changesβ
- The
search_external_tool_opsandrun_external_skilltools are no longer listed or callable for MCP clients connecting to Katalon True Platform. Connector actions inside Katalon AI chat, such as reading an Azure DevOps work item, keep working. If an external agent or script called either tool, remove that call.
Known limitationsβ
- A generated draft can occasionally fail to save. When it does, the draft stays in the review panel behind a Save (1) button; click it to save the draft.
- Links returned by MCP write tools, such as
create_test_run, are still relative. Absolute links cover read tools in this release.
September 17, 2026β
New featuresβ
Configurable Jira requirement-field mappingβ
- What's new: You can map any Jira field, including Acceptance Criteria, Steps to Reproduce, and custom fields, into the Requirements view.
- Why this matters: Testers can use structured requirement content even when it is not stored in Jiraβs Description field.
- How it works: Configure the Jira requirement-field mapping for the fields your team wants to display.
Restore a previous test-case version as the latestβ
- What's new: Restoring an older version creates a new latest version while preserving the complete history.
- Why this matters: You can recover earlier content without overwriting the audit trail.
- How it works: Choose Restore from a historical version.
Enhancementsβ
- Defect Report now has the same rich-text editor as manual test steps, including inserted and uploaded images.
- The repository pane now guides users to set up a Git personal access token when a write credential is missing.
- Test-suite tag changes now commit to the linked Git repository.
- The Import ADO Test Cases dialog now explains when no ADO integration is configured and links to Settings > Integrations.
- Scanned automation test cases now record an author based on the Git commit identity.
Fixesβ
- Large-volume and large-content imports now complete instead of failing with a generic invocation error.
- Push dialogs now exclude inactive ADO integrations and select an active integration by default.
- Jira-synced sprint and release data now appears within the complex-API service-level objective.
September 10, 2026β
New featuresβ
Cross-project dashboardsβ
- What's new: Dashboards are now a top-level destination, with an all-project view by default and a template gallery for creation.
- Why this matters: You can monitor and report across projects without first entering a specific project or building every dashboard from a blank canvas.
- How it works: Go to the Cross-project view to access the one list of custom dashboards from every project you can access. Each row shows its owning Project and links to that projectβs existing dashboard route.
Import Azure DevOps test casesβ
- What's new: You can import Azure DevOps test cases directly into a Katalon Cloud folder, including names, descriptions, steps, expected results, status, and priority.
- Why this matters: This removes the CSV-export step when teams bring Azure DevOps-authored tests into Katalon True Platform.
- How it works: Make sure you have Azure DevOps integration enabled. Then, navigate to Tests > + Create and select the option Import ADO Test Cases.
Choose your AI agentβ
- What's new: Katalon True Platform now presents a choice between Katalon AI and your own agent in the product.
- Why this matters: Teams can use their preferred agent approach in the same workflow.
Tags for execution workβ
- What's new: You can add and query tags on test suites, test runs, and test resultsβnot only on test cases.
- Why this matters: Teams can group, find, and report on executions without copying the same tag across many individual test cases.
Enhancementsβ
Enhancements
- Test-case CSV and Word exports now include customizable-field values. Word exports embed step images inline instead of presenting them as attachments.
- Sort order, filters, rows per page, and column layout now remain in place while you navigate folders and modules in Test Cases, Test Suites, Test Runs, and Reports.
- Katalon AI Runner can now handle email one-time passwords during login steps.
- Katalon AI connectors now support Azure DevOps personal access token authentication for MCP connections.
- Knowledge-base work is more actionable with project-level ingestion controls, public knowledge-base ingestion, and clearer file-upload and processing feedback. [TODO: verify final user-visible scope with PM]
Changesβ
- Folder, test-case, and test-suite names now accept common special characters, including parentheses, commas, periods, hyphens, underscores, plus signs, ampersands, equals signs, and apostrophes.
- New manual test suites open with a default name, and requirement mapping no longer shows Test Management work-item types that cannot be mapped.
August 27, 2026β
Enhancementsβ
- In Project Configuration, Feature Areas, Test Types, and Tags now show usage counts and can be renamed or merged.
- Playwright runs triggered from Katalon True Platform now use the existing Katalon Tunnel or IP Allowed List selection when testing private applications. You do not need to reconfigure your tunnel or allowed list.
August 19, 2026β
New featuresβ
Manual test cases versioningβ
- What's new: Manual test cases now have fixed major and minor version history with Draft and Published states. You can select a version when creating a run, see the retained version on the run record, and restore a previous version from Change History.
- Why this matters: You can preserve an auditable history of test case changes and run tests against a specific version without overwriting earlier content.
- How it works: Changes are retained as versioned snapshots. Open Change History to review, compare, or restore an earlier version, and select the required version when creating a test run. Watch the demo video or see Manage manual test case versions for details.
Enhancementsβ
Enhancements
- Executions on Linux environments now provide network logs for troubleshooting network activity.
August 12, 2026β
Enhancementsβ
- Word and CSV test case exports now preserve attachments. Supported attachments appear inline where the export format supports them, and the delivered ZIP includes an
attachments/directory alongside the exported file. Files that cannot be resolved remain visibly marked. - Audit trails now record folder, test suite, test run, rerun, schedule, tag, and custom field actions with the actual actor and populated change details.
- You can now create folders for test suites and rename a test case or test suite inline from its details view.
- Before a multi-test AI run, you can choose one shared browser profile or separate isolated profiles.
- Content fetched from connected apps remains available when Katalon AI Assistant generates test scenarios.
- Katalon AI Assistant answers now appear progressively instead of arriving all at once.
- AI session results now have clearer empty states, status and duration summaries, and appropriately enabled Re-run and Create defect actions.
Fixesβ
Fixes
- Returning to a file-upload conversation now restores its first message instead of leaving the conversation loading indefinitely.
- Image-only PDF artifacts now provide more complete content for AI-assisted test case suggestions.
- Reselecting an execution environment no longer prevents a Run with AI execution from using its selected private tunnel.
August 6, 2026β
New featuresβ
Updated Test Case list and detailsβ
- What's new: The Test Cases workspace now has a compact filter bar that keeps filters applied as you navigate. Test Case IDs have their own column, test type icons appear next to test case names, and a new toggle lets you hide child folders. The test case details page now places Description and Pre-condition side by side, centers the steps table and rich-text toolbar, organizes Linkages, Run history, and Change History into tabs, and moves metadata into a collapsible Additional Information sidebar. You can also edit assignee, priority, status, and automation status directly from the list or details page.
- Why this matters: You can find and update test cases faster without losing your filter context or opening a separate edit form.
Existing bookmarks and shared URLs continue to work because test case IDs and routes have not changed.
Run AI-assisted tests on Windows environments (early access)β
- What's new: Run with AI now supports Windows (Chrome) in early access, in addition to the default Linux (Chrome) environment. Select an environment when starting a run from the Test Case list, Test Suite list, or Test Case details page. If the configured environment is not supported, select a supported environment for the current execution. This feature is being rolled out by organization.
- Why this matters: You can run AI-assisted tests on Windows when your application requires a Windows environment.
Video recording is not yet supported for Windows runs. Step results and screenshots remain available, and the Video tab displays a not-supported message. See Run a manual test with AI.
Shared test steps with Call Test Caseβ
- What's new: A test case can now call another test case, allowing you to reuse shared steps. Add call steps manually or ask the AI Assistant to add them to existing test cases. This feature is being rolled out by organization.
- Why this matters: You can maintain shared flows, such as login, in one test case. Updates apply everywhere that test case is called.
Enhancementsβ
Enhancements
- The test case detail breadcrumb and the browser tab title now show the test case name instead of the raw ID.
Fixesβ
Fixes
- The AI Assistant now returns an exact "requirement not found" error for an unknown requirement ID or key instead of a message about project membership.
- The test case count reported by the AI Assistant now matches the number of test cases generated and saved.
- Test cases generated from a requirement now follow the requirement's story order when ordered output is requested.
- AI test scenario generation no longer fails when the optional priority field is omitted.
- Auto Sequence runs no longer fail intermittently with "The AI service is temporarily unavailable."
- Updating schedules in bulk with the AI Assistant no longer duplicates existing Test Suite Configurations.
- The AI Assistant now reports the current status of an in-progress AI run instead of inferring the status from the conversation.
- Looking up an unknown requirement ID or key now returns a not-found response instead of an internal server error.
- Figma context requests now retrieve a specific node when possible and provide retry guidance when a request is rate-limited.
- Personal Preferences no longer cause unrelated read-only Katalon AI Assistant requests to create test cases.
August 5, 2026β
New featuresβ
Run and manage Playwright tests in True Platformβ
- What's new: You can connect and import a compatible Playwright project into Katalon True Platform, discover its tests, suites, and profiles, and select a suite and profile to run and review.
- Why this matters: Teams using Playwright can bring supported projects into their Katalon testing workflow without recreating their test structure.
Configure email reports for automated runsβ
- What's new: You can configure an Email Report for an ad-hoc or scheduled automated run, select role-based, individual, or external recipients, and optionally customize the subject.
- Why this matters: Run results can be delivered automatically to the stakeholders who need them.
- How it works:
See Configure email report for a test run.
Enhancementsβ
Enhancements
- Call Test Case steps now let you record pass or fail results during a manual run.
- In Plans > Timeline, you can scroll and zoom the Gantt view and use its grab cursor and scrollbar to navigate the timeline.