What is the job of a Test Automation Engineer?
The job of a test automation engineer consists of writing programs that check, over and over and without manual effort, that an application or a website works as it should. It helps catch errors before they reach the people who use the product, and it lets the team make changes without having to check everything by hand each time.
A typical day mixes programming and review. The requirements of a new feature are read, automated tests are written or adjusted, the results of the overnight runs are reviewed, and someone works out why a test failed: sometimes the mistake is in the application and sometimes in the test itself. There are also short meetings with the people who build the product and with the rest of the quality team to agree on what is worth automating.
Typical tasks
- Writing automated tests that simulate the use of an application, a web page or an internal service.
- Maintaining existing tests when the product changes, so that they stay useful.
- Analyzing tests that fail and telling whether the problem is in the product or in the test.
- Connecting the tests to the systems that build and release the software, so that they run on their own after every change.
- Reporting the errors found with clear steps so that they can be reproduced.
- Agreeing with developers and with the quality team which cases are worth automating and which are checked by hand.
- Reviewing the code of other team members and documenting how the testing tools are used.
Subjects and content usually covered
- Programming in languages such as Python, Java or JavaScript.
- Data structures and basic algorithms.
- Databases and queries with SQL.
- Networks, web protocols and how application programming interfaces (APIs) work.
- Software engineering: the development life cycle, version control and working with agile methods.
- Fundamentals of software testing: types of tests, test case design and defect management.
- Test automation tools and continuous integration.
Usual duration and type of training
It depends on the route. An engineering or related university degree, such as computer science, information systems or software, usually takes 4 to 5 years. On top of that base, people often add courses or practice of their own in automated testing lasting 3 to 12 months. In some countries people also arrive from a technical program in programming lasting 2 to 3 years. The names of the qualifications and their length vary by country.
How you get there and what is usually required to practice
This is a job that people reach by several routes. The most common one is to study engineering or a related degree, such as computer science, information systems or software, and to start in a testing or development position. Others come from working as a manual tester, learning to program little by little, or from a junior programming job that leans toward quality.
A license to practice is not usually required. What job postings ask for is the ability to program, familiarity with some automation tool and an understanding of how software teams work. Some companies value software testing certifications and technical English for reading documentation. The first job is usually the hardest to get, and a portfolio of personal projects often helps to show what has been learned.
Skills that help
- Programming in an orderly way, so that other people can read and maintain the test code.
- Designing test cases that cover what matters, including unusual situations.
- Investigating the cause of a failure by following clues in logs, data and code.
- Writing clear and precise bug reports.
- Using version control and continuous integration tools.
- Communicating with development teams so that criticism of the product does not feel like a personal attack.
Career paths and job opportunities
- Software development companies and technology consultancies.
- Banks, insurers and other financial institutions with their own systems.
- E-commerce companies and online service businesses.
- Telecommunications and mobile technology companies.
- Technology departments of public bodies, health services or education.
- Freelance or project-based work for different clients.
What you are not always told
- Maintaining automated tests takes as much work as writing them: when the product changes, many of them break and have to be repaired.
- Part of the day goes into investigating failures that are not real errors but unstable tests or problems with the environment.
- As a release approaches, the pressure on quality increases, and the testing team is sometimes asked to say whether something is ready with little time.
- Many hours are spent in front of a screen, and the work can become repetitive if the team does not rotate roles.
- Not every error can be found automatically, and part of the job is explaining those limits to people who expect the tests to cover everything.
How the field is changing
Testing is increasingly built into the process of creating software, so tests run on their own after every change and the results reach the team quickly. Tools are appearing that help generate tests, repair the ones that break and spot patterns in failures, so the work is shifting from writing each step to reviewing, designing strategies and analyzing results. Testing of APIs, mobile apps and security is also gaining weight, and the job looks more and more like that of a developer.
Want to know if this is the right career for you?
Take the free vocational test with 5 scientific methods — CHASIDE, Holland, Big Five, MMMG and VAK — to get your personalized profile. You can also explore all university careers or learn about the scientific methodology.