Foundations for Test Automation Engineers
Test automation foundations are the decisions made before writing any scripts. They cover why to automate, such as faster feedback and repeatable regression checks, and what not to automate, such as one-off or highly unstable checks. Preparation includes choosing candidates by risk and value, setting up test data and environments and estimating return on investment.
Stage: Strategy · Part of the Test Automation Engineer roadmap · Last reviewed 19 November 2026
What to learn in Foundations
- State the goals and limits of test automation for a project
- Select test cases to automate using risk, frequency and stability criteria
- Estimate return on investment and maintenance cost of an automation effort
- Plan test data and environment needs before writing scripts
- Explain the testing pyramid and where automated tests belong
Foundations interview questions
Which tests should you automate first?
Start with tests that are repeated often, cover critical business flows, are stable and deterministic, and are tedious or error-prone by hand, such as regression and smoke checks. Leave exploratory testing, rapidly changing features and one-off checks for manual work.
Can automation replace manual testing?
No. Automation is excellent at fast, repeatable verification of known behaviour, but it only checks what it was written to check. Human exploratory testing finds usability problems and unexpected defects. A good strategy uses both, with automation covering regression.
Where Foundations fits in the Test Automation Engineer roadmap
Foundations belongs to the Strategy stage (beginner level), which takes about 30 hours. Why and what to automate.
Other units in this stage
Back to the full Test Automation Engineer roadmap