Automate Software Testing with AI

Test Automator is a broad test-automation-engineering skill spanning Test-Driven Development, AI-powered testing, and the full modern testing stack. On TDD it covers red-green-refactor cycle automation, both Chicago School (state-based) and London School (interaction-based, mock-driven) approaches, property-based TDD, BDD integration, TDD kata practice, and cycle-time and test-growth metrics tracking. On tooling it spans self-healing AI test automation (Testsigma, Testim, Applitools), cross-browser automation (Playwright, Selenium), mobile (Appium, XCUITest, Espresso), API testing (Postman/Newman, REST Assured, Karate), performance testing (K6, JMeter, Gatling), contract testing (Pact, Spring Cloud Contract), accessibility testing (axe-core, Lighthouse), and low-code platforms (Katalon Studio, Ghost Inspector, Mabl, Ranorex, TestComplete, BrowserStack/Sauce Labs cloud execution).

Use it for test-automation strategy and implementation work: designing a test pyramid, building CI/CD pipeline test integration (Jenkins, GitLab CI, GitHub Actions, containerized test environments), setting up performance or load testing, managing test data (synthetic generation, anonymization, GDPR-aware handling), or applying TDD from writing the first failing test through refactoring safety nets. It is not for tasks outside test automation itself, or when a different domain or tool is what's actually needed - in those cases, or when required inputs, permissions, or success criteria are missing, the skill calls for clarifying first rather than guessing.

Input: a testing goal - a framework choice, a CI/CD integration, a TDD cycle, a performance benchmark - plus its constraints. Output: a test strategy and, for detailed implementation, a pointer to resources/implementation-playbook.md for concrete examples. Its response approach runs requirements analysis through framework selection, scalable automation implementation, CI/CD integration, monitoring and reporting setup, and ongoing maintenance planning; its TDD-specific approach is the classic loop - write a failing test, verify it fails for the right reason, implement the minimal code to pass, confirm the pass, refactor with the test suite as a safety net, and track cycle-time and test-growth metrics throughout.

Draws on a wide named tool ecosystem across categories: AI-powered and self-healing testing (Testsigma, Testim, Applitools), UI and browser automation (Playwright, Selenium WebDriver), mobile (Appium, XCUITest, Espresso), API (Postman, Newman, REST Assured, Karate), performance (K6, JMeter, Gatling), contract testing (Pact, Spring Cloud Contract), accessibility (axe-core, Lighthouse), reporting (Allure, ExtentReports, TestRail), and cloud execution (BrowserStack, Sauce Labs) - alongside CI/CD platforms (Jenkins, GitLab CI, GitHub Actions) and containerized test environments (Docker, Kubernetes).

Test automation engineers and quality engineering teams designing or scaling a testing strategy - whether that's introducing TDD discipline (Chicago or London school), building an AI-assisted self-healing UI test suite, wiring performance and contract testing into CI/CD, or standing up test data management and reporting across microservices and multiple environments.