---
title: "Discussion on \"The State of Test Automation Maintenance: What QA Engineers Actually Say\" | Hashnode"
description: "Discussion on \"The State of Test Automation Maintenance: What QA Engineers Actually Say\". Test automation was supposed to make QA teams faster.\nIn practice, many QA engineers describe a messier tradeoff: automation gives teams coverage, repeatability, and release confidence, but it also cr"
url: "https://hashnode.com/posts/the-state-of-test-automation-maintenance-what-qa-engineers-actually-say/6a2d3b2f72a2370e3d5ab9af"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The State of Test Automation Maintenance: What QA Engineers Actually Say](https://quash.hashnode.dev/the-state-of-test-automation-maintenance-what-qa-engineers-actually-say?utm_source=hashnode&utm_medium=feed)

Test automation was supposed to make QA teams faster. In practice, many QA engineers describe a messier tradeoff: automation gives teams coverage, repeatability, and release confidence, but it also cr

Jun 13 · 14 min read · quash.hashnode.dev  
Read the article

## Written by

[Quash Bugs](https://hashnode.com/@quash)

@quash · Bengaluru, India

  
[View profile](https://hashnode.com/@quash)

Tests That Don't Break When Your App Does

Quash is the mobile testing platform QA teams actually adopt. Describe your testing intent in plain language; Quash generates and runs tests on real devices with no scripts, no locators to maintain, and no setup. It's purpose-built for QA professionals, not repurposed from a developer tool. Tests survive UI changes, integrate with your existing stack, and keep QA in control. Less time fixing tests every sprint. More time on the testing only a human can do.

## Responses 1

Markdown supported · ⌘↵ to post

[Mikhail Golikov](https://hashnode.com/@golikovichev)

[Jun 13](https://hashnode.com/posts/the-state-of-test-automation-maintenance-what-qa-engineers-actually-say/6a2d3b2f72a2370e3d5ab9af/comment/6a2de31173117c915f41aceb)

This matches my experience more than most automation writing. The line that lands hardest is "did the product break, or did the test break" - on a backend serving seven teams, as the only QA, that investigation was eating more of my week than writing the tests ever did.

The flaky-as-trust-risk framing is right. Once people start re-running a red build by reflex, the suite has already lost. What helped me was refusing to label anything "flaky" as a category and instead forcing a class on every failure: timing, selector drift, data state, environment, or a real regression. A bucket you cannot name is usually one you have stopped reading.

On AI as a junior QA that still needs review, agreed, and the review cost is real and recurring. A generated test that nobody on the team can debug six weeks later is not coverage, it is debt with a green checkmark.

Question on your maintenance model: when a test survives a UI change without edits, how do you confirm it still asserts the original intent and did not quietly degrade into a weaker check that just happens to pass?
