What is the job of a Manual Tester?
The job of a manual tester consists of trying out a program, an app or a website the way a person would use it, in order to find errors before they reach the people who will use it. Whoever does this work checks that each function behaves as it was requested, writes down what fails and explains how to repeat the problem so that the development team can fix it.
A typical day starts by reading what has changed in the product and what each function is supposed to do. Then test cases are run: written steps that are followed one by one, comparing what happens with what should happen. When something fails, it is recorded with screenshots, the exact steps and the device or browser that was used. Fixes are tested again, and there are short meetings with developers and analysts to clear up questions.
Typical tasks
- Reading requirements and descriptions of features to understand how the product should behave.
- Designing and writing test cases with clear steps and expected results.
- Running the tests on different browsers, operating systems and devices.
- Recording the errors found with a precise description, screenshots and steps to repeat them.
- Checking that fixed errors are really resolved and that no new ones have appeared.
- Doing exploratory testing, using the product without a script to discover unexpected failures.
- Keeping the test documentation up to date and reporting progress to the rest of the team.
Subjects and content usually covered
- Software testing basics: types of tests, such as functional, regression, integration and acceptance testing.
- The software development life cycle and work methods, both agile and traditional.
- Designing test cases and techniques for choosing what to test.
- Using bug tracking and test management tools.
- Basic notions of databases and simple queries to check information.
- How websites, mobile apps and connections between systems work, in general terms.
- Clear technical writing for reporting errors.
Usual duration and type of training
There is no single length, because this is a job people reach by several paths. Courses specifically about software testing usually last 2 to 12 months. Technical programs in programming or computer systems usually last 2 to 3 years, and university degrees in computer science or information systems take 4 to 5 years. Many people start with a short course and learn the rest on the job. The length, the names of the qualifications and the way they are offered vary by country.
How you get there and what is usually required to practice
People can arrive from a degree or technical program in computing, information systems or related areas, but it is not required. Others come in from a short software testing course, from technical support or customer service for digital products, or from other areas where they knew the product well and later moved on to testing it.
In general no license or professional registration is required to practice. Things that are usually valued include knowing the types of tests, practice with bug tracking tools, a comfortable reading level of technical English and some portfolio or examples of written test cases. Private certifications in software testing exist, but how they are used and how much they count changes by company and by country. The first job is usually the hardest to get.
Skills that help
- Observing in detail and noticing small differences between what is expected and what happens.
- Following a procedure step by step and repeating it without skipping parts.
- Writing clear bug reports that another person can reproduce without asking questions.
- Thinking of unusual situations: empty data, very long texts, slow connections or actions done out of order.
- Explaining a problem to developers respectfully and with concrete data.
- Learning new tools and products quickly.
Career paths and job opportunities
- Software development companies and technology consultancies.
- Product teams in companies that have their own apps, such as banks, online stores and insurers.
- Video game and mobile app companies.
- Companies specialized in testing services that work for several clients.
- Public bodies and health or education organizations with their own systems.
What you are not always told
- Much of the work is repetitive: running the same cases again and again on every new version.
- When a delivery date gets close, testing tends to be left until the end and the time for it shrinks.
- Reporting errors all day can create tension with the people who develop the product, so the way they are communicated needs care.
- Some errors are hard to reproduce, and time is lost searching for the conditions in which they appear.
- The first job is usually the hardest to get, and prior experience is often asked for.
How the field is changing
Many repetitive tests are run by programs that automate them, so purely manual work is concentrated on what needs human judgment: exploratory testing and testing of how the product is used and felt. For that reason, in many teams people also pick up basics of automation, databases and reading code. Tools with artificial intelligence are also being added that help suggest test cases and write reports, although a person has to review their results. Agile teams often bring the person who tests in from the start of development and not only at the end.
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.