Manual or Automated Testing? What to Automate First

Muhammad Ilyas
October 16, 2026
Two engineers working on code at monitors

Teams often treat test automation as all or nothing. Either everything is tested by hand before each release, or someone sets out to automate the whole app and gives up halfway. The useful answer sits in between: automate the checks you repeat on every release, and keep people on the work that needs judgment.

Key takeaways

  • Automate stable, repeated, high-value flows such as login, checkout and core forms.
  • Keep exploratory testing, new features and visual review manual.
  • Start small, run the suite on every change, and fix flaky tests quickly.

What is the difference?

Manual testing means a person follows steps and judges the result. Automated testing means code runs those steps and checks the result, usually on every change. Manual testing finds unexpected problems. Automated testing makes sure old problems do not come back.

What to automate first

  1. Critical user journeys. Sign up, log in, search, add to cart, checkout, submit a form.
  2. Anything involving money or permissions. Pricing rules, discounts, refunds, role-based access.
  3. Integrations. Checks that data sent to your CRM, payment provider or accounting tool arrives correctly.
  4. Bugs that came back before. If a bug returned once, a test should guard it.

What to keep manual

  • Exploratory testing of new features, where a tester tries things nobody planned for.
  • Usability and visual review. Code can confirm a button exists, not that the page makes sense.
  • Features still changing every week. Automating them too early means rewriting tests constantly.

A simple way to start

  • Write a short list of the ten flows that must never break.
  • Automate those with an end-to-end tool such as Playwright or Cypress.
  • Add unit tests for business rules as developers touch that code.
  • Run the suite automatically on every pull request and before every release.
  • Treat a flaky test as a bug. If people learn to ignore failures, the suite stops helping.

FAQ

Is automated testing worth it for a small app?

For a small app with a few key flows, a handful of automated end-to-end tests usually pays off quickly because they run on every change at no extra effort.

Can automated tests replace QA engineers?

No. Automation repeats known checks. QA engineers decide what to test, find the unexpected and judge whether the product works for real users.

What should we test on mobile apps?

Core journeys on a small set of real devices that match your users, plus automated tests for business logic and the API the app depends on.

Next step

Our QA and software testing services combine manual and automated testing for web and mobile apps, and we can help you set up a first automated suite that your team can maintain. Testing is one part of keeping software healthy; see what a maintenance plan should cover.

Post Views38 View(s)
ABOUT THE AUTHOR
Muhammad Ilyas
CTO at Techholds

I have spent 14 years in software. I started as a developer, then led teams, then ran delivery for projects with 20 or more engineers. I have built SaaS platforms, web and mobile products, CRM systems and AI agents for companies across the US, Canada, Europe and the Middle East.

At Techholds I lead every client project from the first call to handover, whether it is an AI pilot, a mobile app, a web application or a business system. I am the person you talk to about scope, timelines and results. There is no sales team in between.

Let's connect and work together on your company's digital transformation.

Talk to an engineer about this

A straight answer from an engineer, with no sales team in between.

Related guides

All guides

Still not sure?

Talk to the engineer who would work on your project. Same answers, faster, and specific to your setup.

CONTACT US

Tell us about your project

TALK TO AN EXPERT

Tell us what you are working on