Recruiter's Glossary

Examples: Usability Testing • Risk Assessment • Security Testing

Manual Testing

Term from Quality Assurance industry explained for recruiters

Manual Testing is a fundamental way of checking if software works correctly, where real people physically try out the software to find problems before it reaches customers. Unlike automated testing where computers run the checks, manual testers click through applications, type in data, and verify everything works as expected - similar to how an actual user would use the product. It's like having a thorough inspector who examines a house room by room before the new owners move in. Companies often use both manual testing and automated testing together to ensure their software is high quality.

Examples in Resumes

Performed Manual Testing of web applications across multiple browsers and devices

Created detailed test cases and executed Manual Testing for a healthcare portal

Led Manual Testing efforts for new features and bug verification

Conducted Manual QA Testing of mobile applications

Typical job title: "Manual Testers"

Also try searching for:

QA Tester Quality Assurance Tester Manual QA Engineer Software Tester Test Analyst Quality Analyst

Where to Find Manual Testers

Online Communities

Professional Networks

Learning Resources

Example Interview Questions

Senior Level Questions

Q: How would you plan a testing strategy for a large e-commerce website?

Expected Answer: A senior tester should describe creating a comprehensive test plan, prioritizing critical features like checkout and payments, coordinating with different teams, managing test schedules, and balancing manual and automated testing needs.

Q: How do you mentor junior testers and maintain testing standards?

Expected Answer: Should discuss creating testing guidelines, reviewing test cases, training on best practices, and helping junior testers develop their skills while ensuring consistency in testing approach across the team.

Mid Level Questions

Q: What information do you include in a bug report?

Expected Answer: Should mention including steps to reproduce, expected vs actual results, screenshots, environment details, and severity level. Should also discuss how to write clear, actionable bug reports.

Q: How do you decide what to test when you have limited time?

Expected Answer: Should explain risk-based testing approach, prioritizing critical features, understanding business impact, and focusing on areas most likely to affect users.

Junior Level Questions

Q: What is the difference between positive and negative testing?

Expected Answer: Should explain that positive testing checks if features work with valid inputs, while negative testing tries to break the system with invalid inputs to ensure proper error handling.

Q: How do you write a test case?

Expected Answer: Should describe including test ID, description, prerequisites, test steps, expected results, and pass/fail criteria in a clear, organized manner.