Release Notes V5.0.20

Enhancements

• Settings Enhancements: Application Settings is now available under Settings > Script Generation Settings. The panel groups configuration into collapsible sections, including Application Configuration, Silicon Grid, Timeouts & Retry Logic, Logging & Debugging, Notifications & Email Reporting, Visual Validation & Assertions, External Integrations, User Authentication & Security, and Custom Inputs. These settings are available for Web, Mobile, Desktop, Hybrid, and API automation types. To learn more, refer to Settings for Web, Mobile, Desktop and Hybrid Automation and Settings for API Automation.
• Update Customize Script with Latest Global Changes: Compare a project's customized script with the global script, selectively apply updated sections, or add missing global files so future generated scripts include the changes. Enable the project permission in Access Settings before using this feature. For details, see Customize scripts in Script Generation.
• Editing algoQA-generated scripts in VS Code and syncing changes: Open algoQA-generated scripts in VS Code, make the required changes to the scripts, object repository, custom actions, or customized script files, then review and sync those changes back to algoQA. After synchronization, review the scripts and run them as needed. API automation is not supported in this workflow. For details, see Open Scripts in VS Code and Sync Changes to algoQA.
• Page-name updates: When you change a control's page name, a confirmation pop-up indicates that other objects share the same page. Confirming the change updates the page name for all objects with the same page URL, without changing the URL. The update is reflected in the configuration and Object Repository. See Object Repository Feature.
• Scenario Outline handling for existing projects: When you use a Scenario Outline that already exists for an existing project in algoScraper, algoQA displays a prompt when you return to the platform to let you know. Change the Scenario Outline and update it to continue. To learn more, see Recording a Scenario Using the Offline Recorder, Creating a Project, and Auto Test Case Generation.
• Use AI toggle in algoScraper: Enable the Use AI toggle next to Ask AI to exclude unnecessary XPaths during scraping and reduce noise during scraping. For details, see algoScraper as an Extension for Web Applications.
• Dynamic XPath capture in algoScraper: algoScraper captures dynamic XPaths by default when collecting locators. For details, see Record a Scenario Using the Online Recorder and Scrape UI Using algoScraper.
• TypeScript Playwright execution report: Review pass and fail counts, feature and scenario result charts, and metadata such as the application version, environment, start and end times, duration, platform, parallelization, and execution location. Select a feature to see its execution duration and scenario outline details for that feature. For more information, see the TypeScript Playwright report.
• Auto-Healing for Web automation: Auto-Healing now supports common XPath issues in the Java Selenium framework for Web automation. For details, see Auto Healing.
• Auto-Healing for Desktop automation: Enhanced Auto-Healing is now available for the Python TestComplete framework. For details, see Auto Healing.