Applitools

Applitools provides AI-powered visual testing that catches visual regressions (layout shifts, color changes, missing elements) that functional assertions miss. Integration pattern: add Applitools SDK alongside existing Selenium/Playwright/Cypress tests, call eyes.open() and eyes.checkWindow() to capture visual snapshots, and let Applitools compare against baselines. The Ultrafast Grid re-renders snapshots across browsers/viewports without re-running tests. For agents automating QA pipelines, Applitools adds a visual layer to functional test suites with minimal test code changes. REST API available for batch management and result retrieval. Confidence is docs-derived.

REST API at eyesapi.applitools.com. Resources: batches, test_results, branches, sessions. GET /api/v1/batches lists recent test batches. GET /api/v1/batches/{batchId}/results fetches test results in a batch (status: passed/failed/new/unresolved). PATCH /api/v1/batches/{batchId}/close closes a batch. Primary integration via SDK (not REST): import Applitools SDK for your framework, configure APPLITOOLS_API_KEY, call eyes.checkWindow() in test. Results available in Applitools Dashboard after test run. SDK submits snapshots to Applitools processing pipeline automatically.

API key auth: APPLITOOLS_API_KEY environment variable for SDK; same key as Authorization: Bearer for REST API calls. Keys from Applitools account settings → API Key. Team API keys available for shared CI environments. No OAuth2. Key rotation via Applitools dashboard. Team-level access: viewer (see results), tester (run tests), admin (manage team settings). Applitools Eyes cloud handles snapshot processing; no data stored client-side beyond the SDK session.

SDK errors on connectivity issues, invalid API key (401), or baseline access failure. REST API: standard HTTP status codes. 401 for invalid key, 404 for missing batch/test. Test result states: passed (matches baseline), failed (visual regression), new (no baseline yet — requires human approval), unresolved (AI uncertain). Batch close required for CI status gates. Applitools Cloud uptime at status.applitools.com. CI integration via JUnit XML output or direct batch status API polling.

applitools.com/docs provides SDK integration guides for all supported frameworks (Selenium, Playwright, Cypress, Appium, etc.), REST API reference, visual grid configuration, and CI/CD pipeline integration guides. Getting started requires an Applitools account (free Developer plan with limited steps). SDK installation is straightforward via npm/pip/Maven. Tutorials with popular frameworks available. Commercial support for Enterprise. Active developer community via Applitools Community Slack.