top of page

Manual Testing Interview Questions (5-10 years) - Practical situational questions

Updated: Aug 12, 2021

Welcome to the compilation of important manual testing interview questions.

Please consider the following note from the author -

  • Our aim is not only to give direct answers but also to make readers understand the basic and important concept of software testing, hence they can counter any questions asked during interviews.

  • In case any reader has any other questions, do leave a comment and we will try to explain the concept. Enjoy learning. :)

Following are important manual testing interview questions -

  1. Work Breakdown Structure

  2. 3 Point Estimation

  3. Function Point Analysis

  4. Delphi Technique

  5. Agile Estimation

    1. Planning poker

    2. T-Shirt Sizing

  6. Test Case Point Analysis

  7. Historical Data-based

A test plan is a detailed document that describes the test scope, objectives, goals, estimations, resources required and enlists the responsibilities of the testing team members. The test plan acts as a blueprint to conduct software testing in a project. It also contains risks and contingency planning.

Components of test plan in software testing

Components of test plan
Components of test plan

Test Strategy vs Test Plan
Test Strategy vs Test Plan

Performance Testing is a non-functional testing technique performed to determine the quality attributes of the system such as speed, stability, reliability, scalability, response time, and resource usage of a software application under a particular workload. The goal is to measure and improve the performance of the system. It examines multiple indicators such as browser, page, and network response times, server query processing time to help identify software performance.

Types of performance testing
Types of performance testing

Steps to approach manual testing

  1. Create a testing plan - A test plan document is prepared which acts as a guide in the testing process to have the complete test coverage.

  2. Requirement clarification - Testers review the requirements and raise queries with business analysts for requirement clarification.

  3. Write test scenarios - Post getting all queries resolved and understanding the requirements, the tester creates the high-level test scenarios ensuring all requirements are covered and maintains a requirement traceability matrix.

  4. Write test cases - Then detailed test cases are written, self-descriptive steps that testers will execute while testing. Please following an engineered approach to write test cases using Test Case Design Techniques. Test steps are written keeping in mind that they should be understandable to anyone who even doesn't have any prior knowledge of software functionality.

  5. Test case review - Test cases are reviewed by peers, dev, and BA ensuring no testing scenario is missed in the test cases.

  6. Execute tests -The tester then plays the role of an end-user whereby they test the application's features to ensure correct behaviour. The tester follows a written test plan that leads them through numerous test cases.

Steps to approach automation testing

  1. Identify automation candidates - While writing manual test cases, identify test cases to automate. These are priority 1 and priority 2 test cases and will require testing multiple times throughout the life cycle of the product.

  2. Bifurcate test cases based on tech stack - Bifurcate which tech layer these test cases belong to - DB, API, or UI? This will help to identify which automate tool needs to be selected.

  3. Calculate ROI - Decide if automation will give a return over manual testing in a longer duration.

  4. Select tool - Identify the correct tool for automation based on factors such as the tech layer of test cases, skill set in the team, budget, etc.

  5. Automate the test cases - Develop scripts with proper test validation points.

  6. Validate the automation coverage - Validate if automation scrips are covering all intended functionalities to be tested and good to replace manual testing.

  7. Reporting - Automation reports should give a clear picture of the automation run.

  8. Maintenance - Maintain and enhance the automation script as per change in functionality.

1,117 views0 comments


bottom of page