Teams can review accessibility findings alongside functional test results in the same test session, without switching tools or manually exporting data. This creates one review workflow with audit-ready evidence.

This video shows the product integration between Digital.ai Testing and Deque, and how easy it is to review and act on accessibility findings captured directly in the same test report.

👉 Video Overview

Earlier this year, we announced support for Android 17 Beta to help teams validate applications ahead of the official release. With Android 17 now stable, teams can continue testing on real devices using the released version of the OS. 

Teams can run manual and automated tests against real Android 17 hardware to validate functionality, performance, accessibility, and security-hardened applications. 

For teams that started testing on Android 17 Beta, GA devices are now available to continue validation. For teams beginning Android 17 testing now, real devices are available immediately. 

Watch the overview video: https://digital.ai/resource-center/videos/android-17-official-release/

New Features

Natively Built-In Accessibility Reports – Accessibility scan results, powered by Deque Axe, are now available directly within generated test reports, alongside functional test results in the same test session—creating one review workflow with audit-ready evidence.

Android 17 Support – Earlier this year, we announced support for Android 17 Beta to help teams validate applications ahead of the official release. Now, with the support for Android 17 official release, teams can test on the latest OS version to validate compatibility and uncover issues before they reach users.


Integrations & Ecosystem

Digital.ai Testing MCP Server – The MCP Server connects AI agent directly to your testing platform, turning natural language into real platform actions across administration, analysis, and test execution.

WebdriverIO MCP Server Support - We now support the WebdriverIO MCP Server, enabling AI agents to connect WebdriverIO workflows to real browsers and mobile devices on the Digital.ai Testing platform.


26.6 also includes important platform improvements and bug fixes focused on stability, reliability, and overall testing experience, along with a few deprecation notices to help you prepare for upcoming changes.

👉 Read the full 26.6 Release Notes

If you use Deploy and have ideas, challenges, or repetitive tasks where AI-assisted workflows could help, we’d love to hear from you.

💬 Leave a comment here, and we’ll reach out to schedule a short discovery session.

Our company is moving to feature releases. Does anyone have any best practices to naming of planning levels?

Thanks,

With Digital.ai Deploy 26.1, large artifact handling has been improved.
Deploy can now handle artifacts of 2 GB or larger more efficiently by using a streaming approach instead of loading the full artifact into memory.

Why does this matter?

Because deployment reliability is not only about the deployment logic itself. Sometimes, a deployment can be correctly configured but still run into problems because the package is large and difficult to process efficiently.

This improvement helps reduce memory pressure and makes large artifact deployments more resilient, especially for teams working with bigger packages or running multiple deployments in parallel.

This may be especially relevant if your teams deploy:

large application archives
folder-based deployment packages
generated enterprise bundles
packages with many nested files
multiple large artifacts in parallel

• How do you currently manage large deployment artifacts?

• Do you split packages, tune memory settings, use external storage, or rely on the deployment platform to handle large artifacts automatically?

For technical details, check the Deploy 26.1 documentation.

Ask Release brings AI assistance directly into Release, helping teams get faster answers, understand release status more easily, identify potential issues, and reduce the manual effort involved in managing complex release processes.

Instead of spending time searching through releases, tasks, and status details, teams can simply ask questions and get useful insights in context. The goal is simple: help release teams move faster, make better decisions, and focus more on delivery.

If you are using the trial version or Release SaaS, you can try Ask Release today. Support for on-premises users is coming soon.

Learn more in the blog post:
https://digital.ai/catalyst-blog/ask-release-leverage-ai-to-streamline-devops/

Also new in this release: protection engine selection. You can now enable or disable individual engines independently, and choose which engine versions to run — useful for aligning protection configuration with your CI/CD pipeline or controlling when you adopt newly released engines.

One important note: the Android and iOS Native protection engines have been updated to a new Digital.ai-developed engine. AppAware is not yet supported on the new engine — support is planned for a future release.

Full release details are available in the download.

This release brings several exciting updates:

Now Supporting iOS 27 Beta – Test against iOS 27 Beta on real devices from Day Zero (June 8th). Teams can perform manual and automated testing across functional, performance, accessibility, and hardened application testing before the public release reaches users.

Support for Apple CarPlay Instrument Cluster – Automotive testing now extends beyond the main CarPlay display to include the Instrument Cluster. As teams begin automating CarPlay applications, cluster validation often remains a manual process. This gap is now closed by bringing the Instrument Cluster into the automated testing workflow.

Share Test Evidence Securely – Test results don't stay in QA. Developers, product teams, and external stakeholders all need visibility into testing outcomes. Secure sharing allows teams to share individual test results through protected links, making collaboration easier than ever.


26.5 also includes important platform improvements and bug fixes focused on stability, reliability, and overall testing experience.

Read the full 26.5 Release Notes

A question worth asking at the start of every beta season: how much time does your team actually have between "beta available" and "public release reaching users"?

For iOS, that window tends to close fast. And iOS upgrade rates mean issues that slip through don't stay contained for long.

Digital.ai Testing supports iOS 27 Beta on real devices — no additional configuration required, so teams can start validation now.

Read more →