Quality

What to automate first: a pragmatic guide to test automation

Automating everything is expensive and brittle. Start where automation pays back fastest, and keep humans where they add the most value.

GloryTekSystems team12 Sept 2026 2 min read

An engineer working on code in a contemporary office

Test automation pays back when the same checks run often and reliably. It disappoints when teams try to automate everything at once, or automate the wrong things first.

Start with the test pyramid

Fast, cheap unit tests at the base; API and integration tests in the middle; a thin layer of end-to-end UI tests at the top. Most of your automated checks should sit low in the pyramid, where they are quick to run and rarely flaky.

Automate these first

  • Smoke tests for the journeys that make you money: sign-up, checkout, payments
  • API tests for business rules, which are stable and fast
  • Regression checks for bugs that have escaped before
  • Data-heavy checks that are tedious and error-prone by hand

Keep these manual, for now

  • Features that are still changing every sprint
  • Exploratory testing and usability
  • One-off migrations and rarely used admin screens

Make the suite trustworthy

A flaky suite is worse than no suite, because people learn to ignore it. Quarantine flaky tests quickly, run the suite on every pull request, and treat test code with the same care as product code.

Written by the GloryTekSystems team

Our engineers and consultants write about what they see in real projects. Have a question about your own systems?

Ask us
GloryTek assistantQuick answers · automated

Hi, I’m the GloryTek assistant. Ask me about our services, pricing, timelines or industries.

Popular pages

↑↓ to move to open Esc to close