Code and No-Code Journeys: The Maintenance Shortcut
0 likes36 views
This session focuses on avoiding the uphill battle of test maintenance by shifting to smarter, low-maintenance workflows. Session recording and more info at https://applitools.info/rtv. See examples of how teams are reducing brittle locator dependencies, improving test reliability, and cutting down on manual rework using visual AI.
Code and No-Code Journeys: The Maintenance Shortcut
- 1. The Maintenance Shortcut Code & No-Code Journeys: Heather Vercillo Product Team @ Applitools
- 3. Maintenance Challenges BRITTLE LOCATORS Tests rely on attributes like IDs, XPaths, or class names that change frequently. POOR ROOT CAUSE VISIBILITY When a test fails, engineers have to dig through logs, videos, and code to understand why. TEST FLAKINESS Tests fail intermittently due to timing, async elements, animation, or environment. ENVIRONMENT COMPLEXITY Teams must test across browsers, screen sizes, locales, and responsive layouts. EXCESSIVE MANUAL MAINTENANCE After every sprint, QA teams must update hundreds of tests manually.
- 4. Test flakiness comes from problems with interaction, not verification NoSuchElementException This small change from the dev team will fail the entire test case — even if nothing actually changed in the UI
- 5. Focus on less interaction
- 6. AI-based self-healing mechanisms understand and corrects UI changes like locator changes LIMIT TEST FLAKINESS
- 7. LLM assisted test authoring ✓ Automatic error correction Automatically corrects syntax and grammar mistakes ✓ Automatic step simplification Automatically splits complex steps to multiple simpler ones ✓ Automatic step disambiguation Automatically disambiguates step to clarify how the step will be executed LIMIT TEST FLAKINESS
- 8. AI accelerates cross browser and device testing Capture the entire UI with a single snapshot DOM & CSS sent to Applitools Ultrafast Test Cloud Applitools Visual AI analysis Parallel DOM Rendering . Firewall HANDLE ENVIRONMENT COMPLEXITY Applitools Ultrafast Test Cloud HTML CSS
- 9. What if only the Firefox-based test break?
- 10. Root Cause Analysis tools find what changed in minutes PINPOINT THE ROOT CAUSE
- 11. Group hundreds of updates — accept or reject in one click REDUCE MANUAL WORK
- 12. Ensure flexibility is built into your tool to reduce false positives REDUCE MANUAL WORK Exact ● Pixel-by-pixel comparison against the baseline and checkpoints ● Catches anomalies that aren’t visible to the human eye Increasing flexibility for testing Strict (default) Ignore colors Layout ● Visual comparison against the baseline and checkpoints that mimics a human eye ● Catches changes in graphics, text, fonts, and positions of elements ● Same as Strict but ignores differences in colors ● Catches changes in graphics, text, fonts, and positions of elements ● Ignores dynamic colors ● Visual comparison that identifies patterns of the page ● Catches changes in visual structure of a page, not the content, allowing content to change within an expected structure Dynamic ● Visual comparison that adapts to dynamic content ● Catches changes in structure, like layout or missing elements ● Ignores expected variations like personalized data, timestamps, dates, etc.
- 13. NO-CODE CODE INTEGRATE GIT CI/CD OPS Parallel Execution DESIGN AUTHOR VALIDATE EXECUTE ANALYZE AI-ASSISTED Find all-in-one tools that make your life easier Automated Maintenance Root Cause Analysis Dashboards & Reporting Insights & Optimizations Self-Healing Locators Functional Testing Visual Testing Accessibility Testing API Testing Cross Browser & Device Testing FULLY AUTONOMOUS SDKs Web Crawler Test Data Generation Natural Language Test Builder Codeless Recorder VISUAL AI & DATA VALIDATIONS INTELLIGENT INFRASTRUCTURE Website Testing AUT Web App Testing Native Mobile Testing Component Testing PDF & Doc Testing CONSOLIDATE TOOLING
- 14. Test Maintenance Impacts TEST RELIABILITY Provide confidence in test results QUALITY Contribute to overall quality COST Prevent costly rework down the line EFFICIENCY Reduce time and effort required for testing FEEDBACK LOOPS Quicker feedback on code changes
- 15. Real example of how focusing on maintenance improves testing overall
- 16. The Power of Visual AI: A Case Study from Peloton Visual AI let them to continually release UI updates to 3+ million subscribers with confidence, enabling them to validate hundreds of product showcase pages and views at scale across various languages and locales. The Journey with Applitools ● Applitools directly replaced Percy.io in all Peloton automated visual testing. ● Peloton makes heavy use of screen regions, A/B testing, and other Applitools features to release UI updates with full confidence, while targeting various localities worldwide. ● Peloton leverages Applitools within GitHub pipelines for PRs and release. Customer Since 2023 Use Cases Visual and native mobile testing for class scheduling, responsive filter menus, live data validation on interactive leaderboards Integrations GitHub, Playwright, Slack Customer Profile Before Applitools With Applitools They faced major challenges with Percy.io, as its pixel-based approach generated excessive false positives and negatives. This wasted time, eroded trust in test results, and also created a heavy maintenance burden and ultimately led them to abandon visual testing altogether. They dramatically reduced manual overhead from false positives and negatives by leveraging the precision of Applitools Visual AI, reducing test maintenance times and enabling the creation of thousands of automated tests. With reliable, AI-driven visual accuracy, they now catch issues early and uphold a higher standard of quality. ~130 ~78% 2,947 Hours Saved per Month on Checking False Positives/Negatives Reduction in Test Maintenance Time Automated Web and Mobile Tests Created
- 17. Questions? Sign up for a 14-day free trial of Applitools Autonomous https://applitools.info/bt5