guru 99 manual testing interview questions

In this post, we see Software Testing Interview Questions. Our main focus is on questions asked in Real-World Based Manual Testing Interview Questions And Answers.

Before going ahead, let’s see some unavoidable Interview Questions such as Why did you choose Software Testing As Your Career. I don’t want to take much time of yours but I couldn’t move further without mentioning this inevitable question in an interview i.e., Tell Me About Yourself. Click on the link to get some ideas on how to answer general interview questions. So, Let’s move on to the actual post.

Manual Testing Interview Questions and Answers for Experience & Freshers

Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution. The planning involves the creation of a test charter, a short declaration of the scope of a short (1 to 2 hour) time-boxed test effort, the objectives and possible approaches to be used. The test design and test execution activities are performed in parallel typically without formally documenting the test conditions, test cases or test scripts. This does not mean that other, more formal testing techniques will not be used. For example, the tester may decide to use boundary value analysis but will think through and test the most important boundary values without necessarily writing them down. Some notes will be written during the exploratory-testing session so that a report can be produced afterward.

What is “use case testing”?

In order to identify and execute the functional requirement of an application from start to finish “use case” is used and the techniques used to do this is known as “Use Case Testing.”

Top Answers to Manual Testing Interview Questions


Before the launch of any product or software, testing is a must. You can use Automation Testing in most cases but not for all of them. This is where Manual Testing comes in and plays an important role in the field of software development. Our Manual Testing Interview Questions and Answers blog guides you to master this field through the carefully collated set of Manual Testing interview questions:

Mentioned below are the three categories into which this Manual Testing Interview Questions blog is classified: 1. Basic

Software Testing Interview Questions

According to ANSI/IEEE 1059 standard – A process of analyzing a software item to detect the differences between existing and required conditions (i.e., defects) and to evaluate the features of the software item. Learn more about Software Testing.

SDET Vs Test Engineer Vs Developer

Test Engineer SDET Developer
Test Engineer thinks only in the terms of pass or fail of a test case and how to break the software SDET knows system functional objectives as well as quality objectives Developer thinks how to develop a system and make a functionality work
Test Engineer works only for test life cycle, like design of test cases, and execution SDET is involved in Designing, development, and testing Developer is limited to Coding part and release to testing team
No coding knowledge is required Dynamic skill sets, like knowledge of quality and testing and good in coding too Only coding knowledge is required
Test Engineers know where repetitive work or simple data entry is present but they are not expected to minimize the repetitive tasks SDET understands automation needs, they can code and provide a solution to the team where repetitive kind of work is killing the time. They can design framework which can help testing team to reduce repetitive test cycle or simple data entry task. Developers don’t deal with such tasks
Test Engineers are not expected to reach up to code level and tune the performance Well aware of Performance tuning and security threats , they can suggest and reach to the code and suggest where application is poor in performance, plus they can optimize the code Developers are only expected to code the functionality which is expected by customer
  • Write test cases with end-users perspective
  • Write test steps in a simple way that anyone can follow them easily
  • Make the test cases reusable
  • Set the priority
  • Provide a test case description, test data, expected result, precondition, postcondition.
  • Write invalid test cases along with valid test cases
  • Follow proper naming conventions
  • Review the test cases regularly and update them if necessary.
  • Be practical while answering these kind of real time manual testing interview questions. You can say like it totally depends on the test case complexity and size. Some test cases have few test steps and some have more test steps.

    A sample answer is “In my previous project, we generally execute 30-40 simple test cases (like login functionality) per day, 10-20 medium test cases (like Assigning user roles) per day, and 5-10 complex test cases (complete purchase flow) per day.

    Same strategy applies here too. It depends totally on the complexity of the functionality.

    Before saying how many defects you detected in your last project, first start saying about the type of project you worked and how many test cases you executed. I have worked for an ecommerce website where I have executed overall of 200 test cases and found around 45 defects.

    Configuration management (CM) is a process of systems engineering to maintain system resources, computer systems, servers, software, and product’s performance in a consistent state. It helps to record all the changes made in the system and ensures that the system performs as expected even though changes are made over time.

    Some of the popular configuration management tools are Ansible, Chef, Puppet, Terraform, Saltstack, etc.

    Modification request (MR) in software development is used by clients to change the existing functionality of a software.

    Enhancement report (ER) in software development is used by clients to add a new feature in a software.

    If the software is so buggy, the first thing we need to do is to report the bugs and categories them based on Severity. If the bugs are critical bugs then it severely affects schedules and indicates deeper problems in the software development process. So you need to let the manager know about the bugs with proper documentation as evidence.

    Quality Assurance: Quality Assurance involves in process-oriented activities. It ensures the prevention of defects in the process used to make Software Applications. So the defects don’t arise when the Software Application is being developed.

    Quality Control: Quality Control involves in product-oriented activities. It executes the program or code to identify the defects in the Software Application.

    Now that you know what is Quality Assurance and what is Quality Control. As a software test engineer, you need to know the difference between Quality Assurance vs Quality Control.

    Check this post, where we clearly discussed QA vs QC in Testing.

    Verification is the process, to ensure that whether we are building the product right i.e., to verify the requirements which we have and to verify whether we are developing the product accordingly or not. Activities involved here are Inspections, Reviews, Walk-throughs. Click here for more details.

    Validation is the process, whether we are building the right product i.e., to validate the product which we have developed is right or not. Activities involved in this is Testing the software application. Click here for more details.

    Static Testing involves reviewing the documents to identify the defects in the early stages of SDLC. In static testing, we do code reviews, walkthroughs, peer reviews, and static analysis of a source code by using tools like StyleCop, ESLint, etc.,

    Dynamic testing involves the execution of code. It validates the output with the expected outcome.

    White Box Testing is also called as Glass Box, Clear Box, and Structural Testing. It is based on applications internal code structure. In white-box testing, an internal perspective of the system, as well as programming skills, are used to design test cases. This testing usually was done at the unit level. Click here for more details.

    Various white-box testing techniques are:

  • Statement Coverage
  • Decision Coverage
  • Condition Coverage
  • Multiple Condition Coverage
  • Black Box Testing is a software testing method in which testers evaluate the functionality of the software under test without looking at the internal code structure. This can be applied to every level of software testing such as Unit, Integration, System and Acceptance Testing. Click here for more details.

    Grey box is the combination of both White Box and Black Box Testing. The tester who works on this type of testing needs to have access to design documents. This helps to create better test cases in this process.

    Positive Testing: It is to determine what system supposed to do. It helps to check whether the application is justifying the requirements or not.

    Negative Testing: It is to determine what system not supposed to do. It helps to find the defects from the software.

    Test Strategy is a high-level document (static document) and usually developed by the project manager. It is a document that captures the approach on how we go about testing the product and achieve the goals. It is normally derived from the Business Requirement Specification (BRS). Documents like Test Plan are prepared by keeping this document as a base. Click here for more details.

    Test plan document is a document which contains the plan for all the testing activities to be done to deliver a quality product. Test Plan document is derived from the Product Description, SRS, or Use Case documents for all future activities of the project. It is usually prepared by the Test Lead or Test Manager.

  • Test plan identifier
  • References
  • Introduction
  • Test items (functions)
  • Software risk issues
  • Features to be tested
  • Features not to be tested
  • Approach
  • Items pass/fail criteria
  • Suspension criteria and resolution requirements
  • Test deliverables
  • Remaining test tasks
  • Environmental needs
  • Staff and training needs
  • Responsibility
  • Schedule
  • Plan risks and contingencies
  • Approvals
  • Glossaries
  • Test Suite is a collection of test cases. The test cases which are intended to test an application.

    Test Scenario gives the idea of what we have to test. Test Scenario is like a high-level test case.

    Test cases are the set of positive and negative executable steps of a test scenario which has a set of pre-conditions, test data, expected result, post-conditions and actual results. Click here for more details.

    An environment configured for testing. Test bed consists of hardware, software, network configuration, an application under test, other related software.

    Test Environment is the combination of hardware and software on which Test Team performs testing.


  • Application Type: Web Application
  • OS: Windows
  • Web Server: IIS
  • Web Page Design: Dot Net
  • Client Side Validation: JavaScript
  • Server Side Scripting: ASP Dot Net
  • Database: MS SQL Server
  • Browser: IE/FireFox/Chrome
  • Test data is the data that is used by the testers to run the test cases. Whilst running the test cases, testers need to enter some input data. To do so, testers prepare test data. It can be prepared manually and also by using tools.

    For example, To test a basic login functionality having a user id, password fields. We need to enter some data in the user id and password fields. So we need to collect some test data.

    A test harness is the collection of software and test data configured to test a program unit by running it under varying conditions which involves monitoring the output with the expected output.

    It contains the Test Execution Engine & Test Script Repository

    Test Closure is the note prepared before test team formally completes the testing process. This note contains the total no. of test cases, total no. of test cases executed, total no. of defects found, total no. of defects fixed, total no. of bugs not fixed, total no of bugs rejected etc.,

    Test Closure activities fall into four major groups.

    Test Completion Check: To ensure all tests should be either run or deliberately skipped and all known defects should be either fixed, deferred for a future release or accepted as a permanent restriction.

    Test Artifacts handover: Tests and test environments should be handed over to those responsible for maintenance testing. Known defects accepted or deferred should be documented and communicated to those who will use and support the use of the system.

    Lessons learned: Analyzing lessons learned to determine changes needed for future releases and projects. In retrospective meetings, plans are established to ensure that good practices can be repeated and poor practices are not repeated

    Archiving results, logs, reports, and other documents and work products in the CMS (configuration management system).

    Test coverage helps in measuring the amount of testing performed by a set of tests. Test coverage can be done on both functional and non-functional activities. It assists testers to create tests that cover areas which are missing.

    Code coverage is different from Test coverage. Code coverage is about unit testing practices that must target all areas of the code at least once. It is usually done by developers or unit testers.

  • Test Strategy
  • Test Plan
  • Effort Estimation Report
  • Test Scenarios
  • Test Cases/Scripts
  • Test Data
  • Requirement Traceability Matrix (RTM)
  • Defect Report/Bug Report
  • Test Execution Report
  • Graphs and Metrics
  • Test summary report
  • Test incident report
  • Test closure report
  • Release Note
  • Installation/configuration guide
  • User guide
  • Test status report
  • Weekly status report (Project manager to client)
  • The most common components of a defect report format include the following

  • Project Name
  • Module Name
  • Defect ID
  • Defect detected on
  • Defect detected by
  • Priority
  • Severity
  • Defect resolved on
  • Defect resolved by
  • FAQ

    How do I prepare for a manual tester interview?

    Basic Manual Testing Interview Questions
    1. Q1. How does quality control differ from quality assurance?
    2. Q2. What is Software Testing?
    3. Q3. Why is Software Testing Required?
    4. Q4. What are the two main categories of software testing?
    5. Q5. What is quality control? …
    6. Q6. What different types of manual testing are there?
    7. Q7. …
    8. Q8.

    What are the interview questions for QA?

    Basic Interview Questions
    • What do you understand by software testing? …
    • When should you stop the testing process? …
    • What do verification and validation mean in software testing? …
    • What is static testing? …
    • Define Black-box testing. …
    • What is a test plan and what does it include? …
    • What is meant by test coverage?

    Is manual testing easy?

    QA Interview Questions for Experienced
    • What do you understand about regression testing? …
    • Explain risk in the context of quality assurance. …
    • What do you understand about severity and priority of a defect in the context of quality assurance? …
    • What do you mean by quality audit in the context of quality assurance?

    Related Posts

    Leave a Reply

    Your email address will not be published.