Manual and Automated Testing: What to Use When

    STASX EditorialNov 9, 20265 min read

    Custom Software and ERP

    Most teams need both. A practical guide to what each does well and how to build a sensible mix.

    Testing is how a team finds problems before customers do. People often treat manual and automated testing as rivals. In practice they do different jobs, and good teams use both.

    What manual testing is good at

    • New and changing features. It takes less effort to try something by hand than to write a script for something that will change next week.
    • Judgement. A person can tell when a screen feels confusing, looks wrong or takes too many steps.
    • Exploring. Testers who think like users try odd combinations that no script covers.
    • One off checks. If a check happens once or rarely, automating it is not worth the effort.

    What automated testing is good at

    • Repeated checks. The same steps run on every release, in minutes, without tiring.
    • Speed. Teams that release often get fast feedback instead of waiting for a long manual round.
    • Wide coverage. Many combinations of browsers, devices and data can be checked at once.
    • Protecting what works. Automated checks stop old problems from coming back.

    Where automation does not help

    Automated tests only check what someone told them to check. They do not notice a confusing screen. They also need care: if the product changes and the tests are not updated, they fail for the wrong reasons and people stop trusting them.

    A sensible mix

    1. Automate the checks that matter most and run every release: sign in, the main purchase or booking flow, key calculations.
    2. Test the connections between systems with automated checks on the interfaces, which are quick and stable.
    3. Keep people testing new features, usability and unusual situations.
    4. Add performance checks before busy periods or launches.
    5. Include accessibility checks so that everyone can use what you build.

    Starting small

    Do not try to automate everything at once. Pick the five to ten flows that would hurt most if they broke. Automate those first, run them on every release and keep them tidy. Add more as the team gains confidence.

    Make it part of how you build

    Testing works best when it runs alongside development, not at the end. Testers who join planning conversations catch unclear requirements early, and automated checks that run with every change give developers quick feedback.

    See our page on software testing and test automation, or tell us about your product and how often you release.

    • Software Testing
    • Test Automation
    • QA
    • Quality

    Share this article

    Have a question about this topic?

    Talk to the engineers behind the research.

    (+61) 406 267 743