What is your view on AI-based and self-healing test automation tools in 2026?
What the interviewer wants to hear
- They can speed up writing tests and suggest locators
- Self-healing can hide real UI regressions if not reviewed
- Generated tests still need good assertions and human review
- Good test design and stable locators still matter
- Evaluate on reliability, transparency, cost and lock-in
Model answer
AI tools are genuinely useful now. Coding assistants and tools like Playwright's code generation and agent features can draft tests, suggest locators and explain failures, which saves time. Self-healing locators can reduce maintenance when a button's ID changes. But I treat them as helpers, not replacements for test design. A self-healing tool that silently picks a different element can hide a real regression, so every heal must be logged and reviewed. AI-generated tests often click through flows with weak assertions, so they need human review to check that they verify meaningful behaviour. The basics still matter most: testable apps with stable test IDs and roles, independent tests, and the right pyramid. When evaluating a tool, I look at how transparent its decisions are, whether tests stay as readable code in our repo, flakiness in a real trial, cost and vendor lock-in.
Can you answer it under time pressure?
Take a timed hard round and get scored on every answer.
More hard Automation Test Engineer questions
- Design a test automation strategy for a product with 15 microservices, a web app and a mobile app.
- Your regression suite has grown to 3 hours. How do you bring feedback time under 15 minutes?
- What does testing in production mean, and how would you do it safely?
- Developers keep changing the UI and breaking your tests. How do you fix this at the team level, not just in your code?
- How do you measure whether your test automation is healthy and worth the investment?
- Your company has 2,000 Selenium tests and wants to move to Playwright. How would you plan the migration?
- The E2E suite fails on about 30% of runs and developers now ignore it. How do you turn this around?
- How do you design automated tests for an event-driven microservices system where services talk through a message broker?
- Your product adds an AI assistant built on a large language model. Its answers vary between runs. How would you automate testing for it?