AI Visual Comparison in Perforce Perfecto 26.5 identifies meaningful mobile screen changes against a baseline, giving release owners a more direct control for catching user-facing regressions before production. Combined with expanded device, framework, audio, and administration support, the release addresses the practical work of sustaining trustworthy mobile regression coverage at enterprise scale.
Prioritize visual defects that affect users
AI Visual Comparison compares a mobile test-result screenshot with a baseline image and describes meaningful differences between the two screens. The command is designed to fail tests when it detects critical issues, including missing UI elements or changed values, rather than treating every small visual variation as a release-blocking defect. It supports mobile testing only; tablet and web tests are outside this feature's scope.
For a large release program, this creates a useful control around high-value customer journeys such as payment confirmation, account changes, claims submission, or regulated disclosures. Teams can apply the comparison to screens where a missing amount, consent field, or call-to-action creates revenue, compliance, or customer-service risk.
For day-to-day quality engineering, visual checks can reduce the manual screenshot review that follows a mobile regression run. Testers can focus triage on differences that have a material effect on the customer experience, while developers receive clearer evidence of what changed on the device.
Install applications within AI User Actions
AI User Actions now supports installing a mobile application on a device. Teams can accept default instrumentation settings or provide instrumentation instructions during the interaction.
The change supports more self-contained test workflows. A release team can include application installation as part of a scripted quality path, which helps reduce dependency on separate preparation steps and makes the sequence of test setup more repeatable across release candidates.
A mature team could use this capability when validating a new build against a targeted device set after a deployment pipeline completes. Test engineers spend less time switching between setup activities and test actions, and the recorded workflow carries more context for audit and troubleshooting.
Keep scheduled test results visible to the right people
Scheduled jobs can now send email notifications to additional recipients without changing job ownership or permissions. Previously, notification delivery was limited to the job creator.
This supports release governance because the people accountable for readiness can receive evidence from recurring regression, smoke, or device-availability jobs. A release manager, product owner, security lead, and service owner can be informed from the same scheduled execution while access rights remain controlled.
In practice, a team running overnight mobile regression can route notifications to the release channel's owners without transferring the job to a shared account. The original test owner keeps accountability for configuration, while stakeholders get timely status for decision-making.
Make Scriptless authoring match the selected test environment
Legacy Scriptless Mobile commands are now available only when creating tests for real mobile devices. When a user selects desktop web or virtual devices, unsupported commands are hidden and the test cannot run until the device type changes.
Restricting incompatible commands at authoring time helps protect test-suite quality. It prevents teams from investing in test flows that cannot execute on the chosen platform, reducing avoidable failures and misleading coverage reports during a release cycle.
For testers, the interface provides earlier guidance about what the selected environment can support. That shortens the feedback loop between test design and execution, particularly for teams maintaining mixed real-device, virtual-device, and desktop-web portfolios.
Extend Android audio coverage across real-world paths
Perfecto 26.5 expands Android real-device audio testing across major input and output paths without Bluetooth. Supported output scenarios include voice and VoIP calls, media playback, app sounds and notifications, voice-assistant responses, and accessibility audio. Voice and VoIP scenarios require the Android voice feature to be enabled; the other output scenarios require it to be disabled. Audio input support includes voice and VoIP calls.
Audio defects frequently appear only after device-level integration, where application behavior interacts with operating-system audio routing, calls, notifications, and accessibility services. Teams delivering banking, healthcare, communications, media, travel, or customer-support applications can test these paths as part of end-to-end release evidence rather than treating audio as a late manual verification task.
For an engineer validating a mobile meeting or call workflow, the same automation approach can cover Android voice input and output without Bluetooth setup. That simplifies test preparation and improves consistency across repeated runs. Teams that need voice-call audio testing must enable the Android voice feature in their Perfecto cloud with Perfecto Support.
Strengthen certificate handling and identity administration
Web certificate upload and edit dialogs now include a dedicated Password field. This separates certificate passwords from non-secure fields and supports a cleaner operational process for teams managing authenticated web-testing environments.
The release also requires email-based usernames for newly created users. The user-management interface labels the field as Email (used as username), and API-created usernames must use email format. For API updates, the email parameter remains present but read-only. External identity-provider tenants can continue using non-email usernames when their IdP configuration supports that approach.
These changes matter to security and platform owners because test platforms often contain access to pre-production applications, certificates, device clouds, and test data. Clearer credential handling and a consistent user identifier support access reviews, incident investigations, and deprovisioning processes.
For administrators, email-based usernames make account ownership easier to interpret in routine user-management work. The dedicated certificate password field also reduces ambiguity when testers configure protected web environments for validation.
Update Quantum and virtual-device automation deliberately
Quantum 3.2.2 is available with fixes for security vulnerabilities in several Maven dependencies, updated Selenium and Appium Java Client components, device-availability enhancements, Android secure-screen instrumentation improvements, and an AXE integration fix. Teams running Quantum tests on virtual devices must specify the appiumVersion capability and should assess compatibility with changes introduced in Quantum 3.0.0 before upgrading.
Framework updates should be treated as governed engineering work, not merely a dependency refresh. Security remediation has clear value, while compatibility checks protect critical regression suites from unexpected execution changes that can delay a release.
A practical adoption pattern is to run a representative set of business-critical tests against Quantum 3.2.2 in a controlled branch, compare pass rates and device behavior, then promote the upgrade after owners resolve variance. The required Appium capability should be standardized in shared configuration so teams do not get inconsistent virtual-device results.
Keep device coverage aligned with current platforms
Perfecto 26.5 adds real-device support for iOS 26.5, 18.7.9, 16.7.16, and 15.8.8. iOS 26.x real devices require a cloud with HSS 2.0 and macOS Sequoia. The release also provides virtual-device support for iOS 26.5 in all regions at full capacity. Applications compiled only for Intel x86_64 cannot run on virtual devices using iOS 26.4 or later; an ARM64 build is required.
The release adds Android 16 and Android 17 Beta 4 emulator coverage for new Pixel, Galaxy, foldable, and tablet models. The default Android emulator is now a Pixel 9 running Android 15. Virtual-device automation uses Appium 2.19 by default, and Appium 3.3 is also supported.
Current platform coverage is a release-risk issue, especially when mobile operating-system adoption changes rapidly or a business supports a broad device population. Product and engineering leaders can use these additions to update their risk-based device matrix, concentrating testing on the operating systems and form factors that matter to their customers.
For practitioners, the new emulators make it practical to validate responsive behavior, foldable layouts, and current Android versions before physical-device demand rises. iOS teams should make ARM64 build readiness part of their simulator adoption checks, since Intel-only builds will not run on the relevant virtual-device versions.
Refresh browser validation for web journeys
Perfecto 26.5 supports Google Chrome 148 Stable, Chrome 149 Beta, and Microsoft Edge 148 Stable on Windows and Mac machines.
Browser support helps enterprise teams maintain coverage for web journeys that sit alongside their mobile applications, including account onboarding, administration portals, and service workflows. Testing current stable versions provides release evidence for the browsers most likely to be used by employees and customers, while beta coverage can expose compatibility risks earlier in browser release cycles.
For a cross-channel quality team, these additions enable targeted smoke tests for browser-specific issues without changing the wider test strategy. Teams can reserve deeper regression for stable browser versions and use beta runs as an early-warning signal for upcoming changes.
How Merito helps
Merito helps organizations buy, implement, govern, and renew Perforce Perfecto in ways that fit established QA, DevOps, and security operating models. For Perfecto 26.5, Merito can assess which changes affect existing test suites, device coverage, cloud configuration, identity controls, and release reporting.
Recommended next steps include:
- Run a pilot of AI Visual Comparison on high-risk mobile customer journeys.
- Review Android audio requirements, including cloud configuration for voice-call scenarios.
- Validate Quantum, Appium, and ARM64 compatibility before broad virtual-device upgrades.
- Update scheduled-job notification lists, certificate procedures, and user-administration standards.
The release gives leaders specific opportunities to improve release evidence while reducing avoidable test maintenance and setup work. Merito provides the technical and governance support to turn those capabilities into an adopted operating practice, rather than a set of features that remain unused after upgrade.
Merito is an authorized Perforce reseller and services partner. Our Perforce Perfecto team can scope licensing, sizing, and rollout for 26.5, and our enterprise upgrade services help you plan and validate the upgrade with minimal disruption to release schedules.