Manual Testing Interview Questions

Manual Testing Interview Questions

We are getting so many emails and comments for sharing the manual testing interview questions. So in this post, we will share with you all the manual testing interview questions asked in an interview.

If you have to go through all those manual testing interview questions, you will get a clear picture of the type of questions most of the edit face in the interview. So we suggest you go through with all those questions and try to answer those questions.

Check: Software Testing Interview Questions

Before starting, you have prior knowledge about various manual testing or software testing concepts. Because in these manual testing interview questions, you may have seen that most of the questions come from fundamental concepts like test case development, different error guessing techniques, and black box techniques entering the complete testing process.

If you don’t have prior knowledge, we recommend you to follow the software testing tutorial or manual testing tutorial of software testing where we are trying to cover almost all the concepts of software testing or software engineering.

Top Manual Testing Interview Questions

Our team has put a lot of effort into getting those questions and preparing those interview questions for the manual tester. But still, if you noticed or found out some of the manual testing interview questions, let us know those questions in the comment section.

Mostly Asked Manual Testing Interview Questions

Following are some basic and advanced Top Manual Testing Interview Questions and answer for both beginner and experienced Manual Tester. We have focused on some manual testing concepts.

• What is Manual Testing?
• What is Regression Testing?
• What is JSON wire protocol?
• What is JSON?
• What is Automation Testing?
• What is Re-Testing?
• What is Smoke Testing?
• What is Functional Testing?
• What is Unit Testing?
• What is User Acceptance Testing?
• What is the F rule in Web Testing?
• What is the life cycle of Testing?
• What is Sanity testing?
• What tool is used for Manual Testing?
• What is Build?
• What is Release?
• What is Sprint in agile?
• What is Sprint Backlog?
• What is a Product backlog?
• What is the time limit of a sprint in Agile?
• What is Agile?
• What is the User story in Manual Testing?
• What is a Test case?
• What is Bug in Manual Testing?
• What is Epic?
• What is a Change request?
• What is an Enhancement Request?
• What are the types of bugs?
• What is static testing?
• What is Black box testing?
• What is white box testing?
• What is Test Plan?
• What are the contents of the Test Plan?
• What are Verification and validation?
• What are SDLC and STLC?
• What is Equivalent Testing?
• What is boundary testing?
• What is Dynamic Testing?
• What is the difference between static testing and dynamic testing?
• What is Integration testing?
• What is the top–bottom approach?
• What is the Bottom – Top approach?
• What is System Testing?
• How system Testing differs from UAT?
• What is Data-Driven Testing?
• What is Test Scenario?
• What is Test Case?
• What is Test Script?
• What is a defect?
• What is a Latent defect?
• What is Mutation testing?
• What is Risk Analysis?
• How we can eliminate risk?
• What is Grey Box Testing?
• What is Acceptance Testing?
• What is Non-Functional testing?
• What is Alpha Testing?
• What is Beta – Testing?
• What is the Difference Between Alpha Testing and Beta testing?
• What is Visual Testing?
• What is Decision Testing?
• What is Statement Testing?
• What is Branch Testing?
• What is Control Flow Testing?
• What is Data Flow Testing?
• What is Error Guessing?
• What is State Transition?
• What is Decision Table?
• What is Boundary value?
• What is Cause – Effect?
• What is SDLC?
• What is STLC?
• What is the Advantage of Manual Testing?
• What are the disadvantages of Manual testing?
• What is Code Redundancy?
• What is Bug Leakage?

Real-time Scenario Based Manual Testing Interview Questions

• If we are getting bugs in every builds what will be the first approach
  Ans:
  1. the First step will be to log the bugs.
  2. Will first test the critical and high priority test cases
  3. One person should start retesting the bugs and another person should start regression. Once the 1st guy has finished the retesting of bugs he can join you in regression.
  4. It seems a deployment issue or the environment of QA environment is different from Prod.
• if you need more time to complete any task and the given time is very less what will you do as a tester?
• you have 20 bugs and you need to fix it as well as u need to run the regression and you are only 2 people in a team how will you do it and which one you will give priority?
  if some function is working in the testing environment and the same is not working in production what will be your approach?
• Scenario-based questions … please suggest your approach
• A scenario 1000 links in the webpage and some links are open in a new tab and some links are open in a new window. How to handle this scenario.

Manual Testing Interview Questions

• What do you mean by automation testing or test automation?
• Are there any benefits of automation testing over manual testing?
• Selenium is a single testing tool, then why it is taken as a suite by professionals?
• What are selenium supporting testing types?
• Are there any drawbacks to the selenium testing tool?
• What do you understand by the term “Selenese”?
• How to identify web elements in Selenium?
• Explain the meaning of XPath in Selenium?
• How to count the number of elements on a page?
• Can you name the popular selenium tool used by large industries worldwide?
• Explain the waiting methods in selenium Web Driver?
• Where the implicit waiting method and explicit waiting method can be used in your script?
• Is there any technique to check either button is enabled on the page or not?
• Is there any technique to check either a particular element is visible on the page or not?
• Name the different types of drivers available in Web Driver?
• Name the different types of mobile testing drivers supported in Web Driver?
• Name the programming languages that are used by Web Driver to write the test cases?
• Do you know the difference between assert commands and verifying commands in Selenium Web Driver?
• Explain the difference between”/” and “//”in XPath Selenium Web Driver?
• Name the different types of annotations used in Selenium WebDriver?
• Which selenium technology is useful for distributed data processing?
• How will you check the result of text execution in Selenium IDE?
• How can you modify test cases in Selenium IDE?
• Explain the significance of JUnit in the Selenium testing tool?
• How to add meta-data in the JUnit selenium testing tool?
• How will you explain the difference between quit () and close () methods in Selenium?
• Why was the concept of the waiting method introduced in Selenium? Name the type of waits in Selenium?
• Is there any drawback of implementing implicit waits in Selenium?
• Why Selenium tools fail sometimes?
• Name the four parameters that have to be passed in Selenium?
• How to handle an Authentication Pop-up using Selenium WebDriver?
• The Selenium script runs in Chrome but not in IE. What can be done?
• What is the difference between ChromeOptions and Desired Capabilities?
• Is it possible to do responsive web design testing using Selenium?
• What is the need for database automation testing? Is it possible to perform database testing with Selenium?
• Why are assertions important in Selenium? What are the different types of assertions?
• What is a data-driven framework? How do data Providers help in data-driven testing?

Latest Manual Testing Interview Questions [09-12-2020]

• What are the preconditions to automate test cases?
• How you log the defects in your project?
• What is boundary value analysis?
• Suppose your manager gave you a task to complete in less time than what you have estimated for it. On that note what action you will take?
• What testplan includes?

Manual Testing Interview Questions

• What are the common problems with software automation?
• What are the key challenges of software testing?
• What is the role of QA in project development?
• Can you explain the V model in manual testing?
• Can u explain the structure of the bug life cycle?
• What is “bug leakage?” and what is “bug release?”
• Can you explain the waterfall model in manual testing?
• Can you explain to me the levels in the V model manual?
• What is the value of a testing group? How do you justify your work and budget?
• Why do u save .vbs in library files in qtp WinRunner?
• What is open beta testing? And it did at which end? What is the difference between open beta testing and beta testing?
• What’s the role of the CMM Level in Testing?
• What is the difference between scenarios and test cases?
• What is the Test case Life Cycle?
• What is the extension for the test script in Quick Test?
• How to write a test case with a minimum of 13 columns.
• How I can do GUI testing, what is its important content, plz tell me all the property of GUI testing?
• Can u explain the spiral binding model in manual testing developers looking to do= testing)
• Why do u use object spy in qtp?
• Why do need synchronization in qtp?
• Who are prepared use cases?
• Where do checkpoints store in qtp?
• When do we update mode in qtp?
• What type of testing questions will be asked for 2+ yrs exp people in an interview?
• What part of the testing phase is the most important part of testing in the cycle?
• What is a visual source safe?
• What is the virtual object and when will we use it?
• What is a virtual object and at what we will use the virtual object in qtp?
• What is virtual memory?
• What is unit testing?
• What is the model of spiral binding in manual testing? Can you explain spiral binding?
• What is the difference between properties and methods in qtp?
• What is the difference between smoke testing and sanitary testing?
• What is the difference between test scenarios and test strategy?
• What is the difference between build and release?
• What is the difference between usability testing and GUI?
• What is the difference between constant and parameter in qtp?
• What is the test strategy that will prepare that one? And what will be there in the test strategy?
• What are the test metrics?
• What is test development?
• What is the definition of the test life cycle?
• What is the Test case Life Cycle?
• What is a testbed?
• What is unit testing in the manual?
• What is a test plan who will prepare that one?
• How do you develop a test plan and schedule? Describe bottom-up and top-down approaches?
• What is system testing?
• What is the difference in writing the test cases for Integration testing and system testing?
• What are the application entry and exit criteria?
• What are SRS and BRS in manual testing?
• What is the Sanity Test, Adhoc Testing & Smoke Testing? When will you use the Above Tests?
• What is the V model in manual testing?
• What is the V model can u explain?
• What is a framework for what situations we will use?
• What is STLC how many phases are there can you explain them?
• What is the Review?
• What are alpha testing and beta testing?
• What is SRS and BRS document? Can you explain them briefly?
• What is stub and driver in manual testing?
• What is stress testing?
• What is standalone mode running in load runner?
• What is a reusable action in qtp?
• What is a regular expression and when we will use regular expression in qtp?
• What is the prototype model in manual testing?
• What is port testing?
• What is performance testing?
• What is the objective of actions in qtp?
• What is mean by GUI testing? What is mean by the client/Server? What is meant by a web-based application?
• What is integration testing?
• What is functional testing, system testing, data-driven testing?
• What is the framework in qtp?
• What is a fish model can you explain?
• What is the exact difference between Debugging & Testing?
• What is determination?
• What is debugging?
• What is compatibility testing?
• What is BUG Lifecycle?
• What is Black Box Testing?
• What are the roles of glass-box and black-box testing tools?
• What is FSO can you explain?
• What are the processes followed in your company for automation?
• What do you mean by Pilot Testing?
• What is AUT?
• What are the objectives of Low-level recording? What is Elapsed Time? When we use Update mode?
• What is the difference between per text mode and shared mode in qtp?
• What are the objectives of Utility objects?
• What are the objectives of debugging?
• Share a particular project where you have been able to learn enough skills to help with testing?
• What are GET TO, SETTO, and GET RO properties in QTP?
• The role of both QA & QC?
• How to test Microsoft Word 2003. What all the major areas to be tested, please explain.
• How to write a test case and bug report? Plz, explain with an example.
• How to do regression testing, and can give one or two examples on that in the same application?
• How to arrive in a Test case? And how to write the Test case in Email id? When we go for WinRunner and why we go for it?
• Explain to me the phases of STLC and explain each one briefly?
• Explain about Microsoft Six Rules Standard for User Interface testing?
• Difference between bug, error, and defect?
• How many modes of recording are there?
• Give an exact and appropriate definition of testing.
• How will you review the test case and how many types are there?

Manual Testing Interview Questions For Freshers

Here we have shared some of the most manual testing interview questions for the freshers. This question can be referred to by the testers who have recently completed their manual testing or manual testing concepts.

• Define software testing.
• What are the types of software testing?
• What is in mind while performing testing?
• Define manual testing.
• When do you start testing?
• When do you end testing?
• What are verification and validation?
• What are Branch Coverage and Decision Coverage?
• Define retesting.
• Define regression testing.
• What is the difference between retesting and regression testing?
• What is functional testing?
• What is nonfunctional testing?
• What is integration testing?
• What is system testing?
• What is module testing?
• What is system testing?
• What is end-to-end testing?
• What are the differences between system and end-to-end testing?
• What are the testing techniques?
• What are the testing methodologies?
• What is the boundary value analysis(BVA)? Explain with example.
• What is equivalence portioning(EA)? Explain with example.
• What is the decision table testing?
• What is the test case?
• What are the test scenarios?
• Difference between test case and test scenarios.
• What is the requirement traceability matrix? (RTM)?
• What is the first step to start the testing process?
• What is a test plan?
• What is the basic format of the test plan?
• What are the test objectives?
• What is the basic format of writing a test case?
• What is a bug?
• What is a defect?
• What is a fault?
• The difference between bug, defect, and fault?
• What are must present fields while raising a defect?
• What are the steps to reproduce while logging a defect?
• What is the defect life cycle?
• What are defect tracking tools?
• What is the severity and priority of the bug?
• Example of high severity and high priority.
• Example of low severity and low priority.
• Example of high severity and low priority.
• Example of low severity and high priority.
• Who decides the priority of bugs?
• Who decides the severity of the bug?
• What is bug leakage?
• What is a bug release?
• What are the differences between bug leakage and release?
• Define alpha testing and beta testing. Say to me the differences between alpha testing and beta testing?
• What is build?
• What is the software development life cycle(SDLC)?
• What is the software testing life cycle(STLC)?
• In which phase of SDLC, your works start?
• What is monkey testing?
• Explain the test driver and test stub with examples?
• What is the use case?
• What is a test strategy, and who prepares it?
• What is a test execution plan?
• What are Error guessing and Error seeding?
• What is compatibility testing?
• What are localization and global testing?
• What is mobile responsiveness testing?
• What is the statement coverage?
• What is branch coverage?
• What is static testing?
• What is dynamic testing?
• What is user acceptance testing?
• What is a testing environment?

Manual Testing Interview Questions For Experienced

Above, we have seen the manual testing interview questions for freshers. Now we have listed down some of the most asked manual testing interview questions for the experience. In this is Section, you have noticed some of the real-time and tricky manual testing interview questions. We have listed down interview questions for the experience of the testers who are already working somewhere and now want to switch their careers from one organization to another Organisation.

• How do you ensure if something is a bug?
• What is white box testing?
• What is black box testing?
• What is exploratory testing?
• What is SRS and BRS document?
• Explain the Validation and verification model.
• What is Concurrency Testing?
• What are the entry and exit criteria for testing?
• What is the difference between Functional Requirement and Non-Functional Requirement?
• Are severity and priority are related to each other. If yes, how?
• What is Concurrency Testing?
• What is the priority of the test case? How is it decided?
• What is root cause analysis?
• What do you understand by risk?
• What is called user interface testing?
• What is called user experience testing?
• What is the AUT(Application under test)?
• What is Ad-hoc testing?
• What is the difference between Software Testing and Quality Assurance (QA)?
• How to Test the water bottle?
• How to test the Google search engine?
• Write test cases in the pen.
• Write test cases on ATM.
• Write test cases of Lift.
• How is the test result made?
• What are the test conditions?
• What is smoke testing?
• What is sanity testing?
• Difference between smoke and sanity?
• What do you mean by Pilot Testing?
• What is the exact difference between Debugging & Testing?
• What is GAP ANALYSIS?
• How you deal if the requirement is not clear?
• How you estimate the time for testing?
• Why is Testing Necessary?
• What is the test deliverable?
• What is Agile Testing?
• What are agile methods?
• How will you decide which SDLC model is perfect for your AUT?
• What is a test suite?
• What is the top-bottom approach?
• What is the bottom-top approach?
• What are the challenges you face in manual testing?
• Why is testing required?
• What is a testbed?
• What is defect density?
• What is a blocker defect?

Manual Testing Interview Questions For 2 Years Experience

In this section, we are trying to put all the interview questions that can help a tester who has two years of experience. You can go through all of these interview questions and let us know it helps you in the interview or not.

•  What is state transition testing?
• What is a test harness? Why do we need a test harness?
•  How is monkey testing different from ad-hoc testing?
• Difference between positive and negative testing?
• What is the scrum?
• What is the sprint cycle?
• Why are testers needed when developers can do the same task?
• What are Independent Testing and its benefits?
• Why is test case review important? Who does it?
• What are the different test levels?
• What is the Latent defect?
• What is look and feel testing?
• Difference between use case and test case?
• How do you test the login feature of a web application?
• What are the types of applications?
• How to test a web-based application?
• How to test a standalone application?
• How to test the payment gateway?
• How to test an eCommerce application?
• You have been given 100 test cases of how you will start when you have given no time limit.
• You have been given 100 test cases of how you will start when you have given the time limit.
• How to check if the build is testable?
• What is grey box testing?
• What is the difference between the white box, black box, and grey-box testing?
• How you sign-off on the testing process?
• What is Testware?
• What is the difference between build and release?
• How can you do effective testing in less time?
• What is confirmation testing?
• How many test cases you can write in a day?
• How many test cases you can execute in a day?
• How will you decide you have enough test cases?
• What should be the mindset of a tester?
• How do you decide on test cases for the regression suite?
• How do you decide on the test case for the smoke test suite?
• How do you decide on the test case for the sanity test suite?
• What is a change request?
• The developer rejects your bug. How will you approach it?
• What is a Deferred Defect?
• How do you ensure 100 % requirement coverage while Execution?
• What are the things you consider when you are reviewing test cases?
• What are the base documents to write the test cases?
• What is meant by defect triage calls?
• You have been given a new project. How will you start?
• How to ensure your test cases are good?
• What is SLA?
• What is a test closure report?
• Write a test case on the water bottle.
• Why does software have bugs?
• What should you do after finding a bug?
• What are the attributes of a good Software QA engineer?
• You are testing functionality which sometimes passes and sometimes fails. How will you report it?
• You find the existing testing process is not up to mark in your current organization. How will you approach your manager to bring changes?
• What is the importance of a test plan?
• If you have ‘n’ requirements and you have less time, how do you prioritize the requirements?
• What types of testing you could perform on a web-based application?
• What types of testing you could perform on a standalone application?
• How do you find the regression scenarios if a defect is fixed?
• What are two of your strengths that you will bring to our QA/testing team?
• What do you like most about Quality Assurance/Testing?
• What do you like least about Quality Assurance/Testing?
• Will manual testing end in the future?
• Do you support automated testing? Why?
• When is a good time for system testing?
• What are the goals of manual testing?
• What is bidirectional traceability?
• What is the test server?
• Clients found a bug in a module in which you were tested. How will you handle this situation?
• Why is test data important?
• What is cross-browser testing?
• What is data-driven testing?
• What is the difference between Project Based Testing and Product Based Testing?
• What is the difference between Testing Methodology and Testing methods?
• What are the documents required to prepare a test plan?
• How does domain knowledge help in manual testing?
• Tell me about daily activities as a test engineer?
• Disadvantages of manual testing?
• What is the build duration?
• How can you report the defect using an excel sheet?
• If you have executed 100 test cases, every test case passed but apart from these test cases you found some defect for which test case is not prepared, them how you can report the bug?
•  If a bug has high severity then usually that is treated as a high priority, then why do priority given by test engineers/project managers and severity gave by testers?
• How would you say that a bug is 100% fixed?
• What are the different types of bugs we normally see in any of the projects?
• What is the difference between a Defect and an enhancement?
• If we found the bug in SRS or FRS, how to categorize that bug?

Manual Testing Interview Questions For 3 Years Experience

When our experience is more than three years, and also you want to continue your career as a manual tester, then in the time when we are going for an interview, we may expect some of the tough questions. So we have the plan to put those real-time and tricky manual testing interview questions below. You can follow those interview questions update us.

• What is the Requirement Traceability Matrix?
• What is the difference between Pilot and Beta testing?
• Describe how to perform Risk analysis during software testing?
• What is Silk Test?
• What is the difference between Master Test Plan and Test Plan?
• How to deal with not a reproducible bug?
• What is the difference between coupling and cohesion?
• What is the role of QA in project development?
• When do you choose automated testing over manual testing?
• What are the key challenges of software testing?
• What is the difference between QA, QC, and Software Testing?
• What is concurrent user hits in load testing?
• What is the difference between Front End Testing and Back End testing?
• What is Automated Testing?
• What is Testware?
• What is Exhaustive Testing?
• What is the Gray Box Testing?
• What is Integration Testing?
• What is Scalability Testing?
• What is the Software Requirements Specification?
• What is Storage Testing?
• What is Stress Testing?
• What is a Test Harness?
• Can you define a test driver and test stub?
• What is good design?
• What makes a good QA or Test manager?
• What are Manual scripted Testing and Manual Support testing?
• What are Fuzz testing, backward compatibility testing, and assertion testing?
• How does a client or server environment affect testing?
• What are the categories of defects?

Manual Testing Interview Questions and Answers

• Definition Software Testing
• Why the need for Testing
• If you send the software without testing what happens?
• Software Testing Life Cycle (STLC) Explain in Details
• Defect/Bug life cycle detail explains.
• Software Testing Life Cycle (STLC) & Describe Test Plan
• How you wrote a Test case in you are organization?
• How you identify the High-level scenario in your  application
• What is the Test design technique you used in you are organization like error guessing, Equivalence partition, Boundary value analysis?
• How you test and write Equivalence partition (EP) & Boundary value analysis (BVA) test cases
• What is the difference between Smoke & Sanity testing?
• What is the difference between Black box & White box testing?
• What is the difference between Retest & Regression Testing & with an example
• if you found a defect in the Production environment, then how you fix that issue?
• What is Integration Testing?
• What are System Testings?
• What is Treatability Matrix?
• In Defect, life cycle what  Differ means?
  Ans- If the release date is near and no time to fixes this Defect so these defects do not fix by the current release this will fix in future releases or the next release. That Defect is mentioned in Release Note. for customer understanding.
• What is the meaning of UAT Testing?
• What is the meaning of  UI Testing?
• What is the meaning of  Unit Testing?
• What is the meaning of Types of Testing?
  Ans-
  1. Functional Manual Testing- FT, IT, ST, AT all manual testing. Automation Testing- Selenium, QTP, etc
  2.Nonfunctional- Stress Testing, Load Testing, UI Testing, Web Testing, Security testing.
• What is Severity?
• What is  Priority?
  example- High Severity-Low priority.
  Ans- OK button click 100 times, then application crash High severity & this scenario rarely use low priority
  Low Severity- High priority
  Search Examples

Manual Testing Interview Questions And Answers For Experienced

Here as you can see, we tried to share some manual testing interview questions and answers, which can be helpful for both fresher and experience. We have prepared another post where we are trying to answer each of these manual testing interview questions.

• What is Integration Testing?
• What are Approaches/Methodologies/Strategies of Integration Testing?
  Answer:-The Software Industry uses a variety of strategies to execute Integration testing, viz.
  Big Bang Approach: Incremental Approach: which further divided into following
  Top-Down Approach
  Bottom-Up Approach
  Sandwich Approach – Combination of Top-Down and Bottom-Up
• What are the Entry and Exit Criteria?
• What is System Testing?
• What do you verify in System Testing?
• What are SDLC and STLC?
• What is Unit Testing, and why we do unit Testing, and when we do Unit Testing? and this black testing ya white testing?
• What are Smoke Testing and Sanity Testing, and why we do and when we do??
• What is the difference b/w Smoke Testing and Sanity Testing?
• What is Regression Testing? When we do Regression Testing? and why Regression Testing?
• Non – Functional Testing? Can you explain All Non – Functional Testing have you done Non – Functional Testing if you did explain which tool you have used?
• What is a test scenario? When we create Non – Functional Testing?
• What is a Test Case, and why we write the test case? Can you explain your Template of the Test Case?
• What is the difference between the Test Case and Test Scenario?
• What is the Traceability Matrix and Explain RTM? And Why, RTM?
• What is the Test technique?
• Can you explain Equivalence Partitioning & Boundary Value Analysis??
• What is Decision Table Testing?
• What is the Test Plan? Why Test Plan and who is creating the test plan and Explain Template of Test Plan?
• What are Defects?
• What is Defect Life Cycle?
• What is the difference b/w Defect and Bug and Error?
• Which mythology are you following? Explain
• Explain the Agile Testing Methodology?
• What is Scrum Testing??
• What is White Box Testing?
• What is Static Testing?
• What is Performance Testing? Explain j-meter??
• What is Load Testing??
• What is Stress Testing? Why Stress Testing? How to do Stress Testing ??
• What is Volume Testing? Why we do Volume Testing and how to do Volume Testing??
• What is Scalability Testing? Why we do Scalability Testing and How to do Scalability Testing??
• What is the difference b/w Test Plan V/s Test Strategy??
• What is the difference in Static VS Dynamic Testing?
• What is the difference between Re-testing VS Regression Testing?
• What is the difference between Quality Assurance VS Quality Control
• What is the difference b/w Verification v/s Validation in Software Testing??
• What is the difference b/w Positive VS Negative Testing??
• What is Security Testing, and why we do Security Testing and have you do Security Testing? Please explain how to do Security Testing?
• What is End to End Testing why we do End-to-End Testing and when we do End-to-End Testing can you give me a real example of End-to-End Testing?
• Explain Exploratory Testing??
• Explain Adhoc Testing ??
• What is the Pilot Testing??
• What is Endurance Testing??
• What is Grey Box Testing??
• What stub and Driver?
• What is beta testing??
• What is Alpha Testing?
• What is V-model?
• What is the waterfall model?
• Which tool are you using for rasing for the bug? Can you explain all the navigation Steps?

Selenium & Manual Interview Questions

Components of Selenium?
Ans:

Selenium IDE: Installs as an add-on in Mozilla. It only runs in Mozilla. Its got a strong feature of record and run. You can also extend IDE functionality with the help of user extensions. It supports regular extensions, loops if statements, and many other features. You can also parameterize your test cases using IDE. Selenium RC: This is the older version of selenium. It works on multiple browsers. RC can be implemented in any one of the programming languages mentioned above.

Webdriver: Webdriver is the new version of selenium. It also works on multiple browsers. Its removed many drawbacks and issues in Selenium RC. It also supports Android and iPhone Testing.

Grid: Grid is used to test cases parallel on multiple machines and browsers.

What is the test plan?
Ans: The Test Plan document derived from the Product Description, Software Requirement Specification SRS, or Use Case Documents. The Test Lead or Test Manager usually prepare the Test Plan document, and the focus of the document is to describe what to test, how to test when to test and who will do what test. It is common to have one Master Test Plan, which is a common document for the test phases and each test phase have their Test Plan documents. Typically Test Plan will have the following.

• Test Plan id
• Introduction
• Test items
• Features to be tested
• Features not to be tested
• Test techniques
• Testing tasks
• Suspension criteria
• Features pass or fail criteria
• Test environment (Entry criteria, Exit criteria)
• Test deliverable
• Staff and training needs
• Responsibilities
• Schedule

This is a standard approach to prepare test plan, but things can vary company-to-company.

What is the difference between agile methodology and other SDLC models?
Ans: Scrum is an innovative approach to getting work done efficiently. It is an iterative & incremental agile software development method. These iterations are time-boxed with various iterations & each iteration is called Sprint. The Sprint is a 2-4 week long & each sprint requires sprint planning estimation. According to the latest surveys, Scrum is the most popular agile project management methodology in software development. The term Scrum formed from Rugby. Scrum ideally used where highly emergent or rapidly changing requirements. Scrum worked on a self-organizing, cross-functional team. In the overall scrum team, no team leader assigns the task to the team. Rather whole scrum members work as a team & they decide the task on which they will work on. Also, the problem will be resolved by the team. Each Agile Development Scrum team having three core scrum roles: Product Owner, Scrum Master & The Team.

• Product Owner: The Product Owner is the person who represents the stakeholders and is the voice of the customer. The product owner writes the User Stories, ordered priorities, and add in the Product Backlog. It recommended that the Agile Scrum Master should not mix with the Product Owner; both members should be different as each member has its responsibilities.
• Scrum Master: The Scrum Master is a facilitation team leader who ensures that the team adheres to its chosen process and removes blocking issues to deliver the sprint deliverable/goal. Scrum Master is not a team leader but acts as a shield for the team from external interferences & also removes barriers. Scrum Master facilitates the daily scrums.
• The Team: The scrum development team is generally the size of 5-9 peoples with self-organizing and cross-functional skills who do actual work like Analysis, Design, Development, Testing, Documentation, etc. At the start of every Scrum Sprint, the team members are committed to delivering a few tasks from the Scrum Product Backlog. Over the sprint time-boxed the teamwork on developing, testing, integrating feature & end of the Sprint in the Sprint Review Meeting this functionality demoed to Product Owner & interested Stakeholders. In this meeting, they can give feedback, if any, on the developed product, which could influence the next sprint. The main artifact in the Agile Scrum project is the product itself. The team is working efficiently on the product to deliver the shippable product after the end of every sprint. The Product Backlog is a place where all requirements are ordered and written in the user story format. These user stories are ordered & prioritized by the Product Owner based on risk, business value, date needed, dependencies, etc. so that most valuable features picked in Sprint first.
• Product Backlog: The Product Backlog is an ordered & prioritized list of items that all need to include in the product. It is dynamic & during the project, items may add or delete from this list. All items ordered prioritized in this list. The highest priority items completed first.
• Sprint Backlog: In the sprint planning meeting, the team picks a list of User stories from Product Backlog. These selected items moved from the Product Backlog to Sprint Backlog. All sprint backlog user stories are discussed items from the product backlog and team member committed to complete the assigned task within Sprint Time boxed. Each user story divided into smaller, detailed tasks. Sprint team works together collaboratively to complete Sprint tasks.
• Daily SCRUM: The Daily SCRUM is not used as a problem-solving or issue resolution meeting. In the Daily SCRUM, each of the team members should answer three questions:
  What did you do yesterday?
  What will you do today?
  Are there any obstacles in your way? In the Daily, SCRUM team share the conflicts, obstacle or impediment faced in their tasks & any possible solutions on that. Daily, this meeting holds at the same time, same location hold by the Agile SCRUM team. Ideally, “The Daily SCRUM” is conducted in the morning, which helps to plan a task for the whole day. As an Agile process & Sprint is time-boxed, similarly Daily SCRUM meeting should be time-boxed to 15 minutes max. In this meeting, the discussion should be quick and relevant. The Scrum Master always helps to maintain the focus of the team on its Sprint goal.
• A Sprint Burndown: Sprint Burndown measures remaining Sprint Backlog items across the time of a Sprint. It is a very effective visual indicator to get the correlation between work remaining at any point of time & the actual progress of the team. Before the Daily SCRUM meeting, Sprint Burndown chart should be updated so it will help to understand the progress of Sprint daily & makes any adjustments if needed.
• Shippable Product: The end of the Sprint can turn into an increment of potentially shippable functionality hand over to the customer. This shippable functionality should be well-structured, well-written code, thoroughly tested, and user operation of the functionality documented. At the end of the Sprint, features committed in Sprint are demonstrated to all stakeholders & they provide valuable feedback to moving products in the correct direction.
• Sprint Retrospective: At the end of each Sprint Review and Retrospective meeting should be conducted to know what went good & bad in Sprint. Participants for this meeting are Team, SCRUM Master & Product Owner(Listener). This meeting also timeboxed to 2-3 hours. Using this approach, each team member is asked to identify specific things that the team should:
  Start doing
  Stop doing
  Continue doing
  Iterations are a key feature of the SCRUM process. In the next Sprint again, the team choose the chunk of User stories from the Product Backlog & Sprint cycle started with new Sprint goals again. These cycles are continued doing unless and until Product backlog finished or Deadline reaches or budget is used up. Agile SCRUM ensured that all high priority task ordered top in the Product backlog so those can get completed first before the project ends.
  

Explain the Bug Lifecycle?
Ans: Defect: A fault in a program, which causes the program to perform in an unintended or unanticipated manner. Defect Life Cycle (Bug Lifecycle) is the journey of a defect from its identification to its closure. The Life Cycle varies from organization to organization and governed by the software testing process, the organization or project follows and/or the Defect tracking tool being used.

Can you tell me about yourself? (For Experienced Candidates)
Ans: In my QA Or Testing career, I have been working on various system platforms and operating systems like Windows 95, Windows 2000, Windows XP, and UNIX. I have tested applications developed in Java, C++, Visual Basic, and so on. I have tested Web-based applications as well as client-server applications. As a QA person, I have written Test Plans, Test Cases, attended walkthrough meetings with the Business Analysts, Project Managers, Business Managers, and QA Leads. I have attended requirement review meetings and provided feedback to the Business Analysts. I have worked in different databases like Oracle and DB2, wrote SQL queries to retrieve data from the database. As far as different types of testing are concerned, I have performed Smoke Testing, Functional Testing, Backend Testing, Black Box Testing, Integration Testing, Regression Testing and UAT (User Acceptance Testing) Testing. I have participated in Load Testing and Stress Testing. I have written defects as they are found using Clear Quest and Test Director. Once the defects were fixed, retested them, and if the passed, closed them. If the defects not fixed, then I reopened them. I have also attended the defect assessment meetings as necessary. In the meantime, continuous interaction with developers was necessary. This is pretty much what I have been doing as a QA person.

How many Test cases can you execute at the time of doing Regression Testing?
Ans: It depends on how many test cases we have identified for doing regression testing, also depends on the timeframe within which we need to execute. If we are performing Unit Regression Testing on the application, then we are testing a particular feature in a form where that particular feature is not dependent upon the other features of the application. For example, If a help document has a defect and PDF file was not opening, then the tester will test only that defect why PDF file was not opening because it was not dependent upon the other part of the application again, if a developer did a mistake and type “Username” instead of typing “UserName” than the tester will test only the UserName function because it was not dependent upon the other parts of the application. In this case, I have to execute fewer test cases, i.e., 4-5 test cases per day are enough. Again, If we are performing Regional Regression Testing on the application, i.e., we are testing a particular feature in an application regionally where the features are dependent upon only some regions of that particular application, but not dependent upon the other regions of that particular application. For example, if the Compose feature has a defect and it was not working properly in Gmail Application, then it will cause an effect on the Inbox feature, Sent Item feature, Draft feature, Spam feature, and Trash feature only. As Username feature, Forgot Password feature, Help feature, and Settings feature are not dependent on the Compose feature. So, we can’t perform Regional Regression Testing on Username feature, Forgot Password feature, Help feature, and Settings feature. We will perform Regional Regression Testing only on Inbox feature, Sent Item feature, Draft feature, Spam feature, and Trash feature.

In this case, I have to execute a little bit number of test cases, i.e., 10-12 test cases per day are enough because at first, we have to identify the impacted regions. Then we perform Regional Regression Testing only on those regions. Again, If we are performing Full Regression Testing on the application, i.e., we go and test the whole application whenever the application changes or new features added. Here, we are re-executing the same test cases on different build and releases to ensure new features added or modification done has not introduced a defect in the older part of the application. For example, we have to perform Full Regression Testing on ICICI bank software because their entire business is dependent on that software. Again, if “wscript.exe” has any defect, then we have to perform Full Regression Testing on that because entire VB Scripting is dependent on “wscript.exe.” In this case, I have to execute the number of test cases, i.e., 15-20 test cases per day are enough.

How will you test the web application and client-server applications?
(OR)
What type of testing will you follow when you are testing web application and client-server application?
Ans: To test the web application, for example, to test Internet Explorer, Google Chrome, Mozilla Firefox, Opera, we are testing these websites’ functionality on different browsers. So, we have to perform Compatibility Testing here. To test the client-server application, for example, to test Yahoo Messanger, Tata Photon 3G Dongle, we require a dedicated client to access the server-side. So, we are testing the data flow between two features or modules. So, we have to perform Integration Testing here.

What is Project Testing and Product Testing?
(OR)
What is the difference between Project Testing and Product Testing?
Ans: Project testing defines that we are testing the developed software or application according to a specific client requirement or a customer requirement. In Project testing, we only test a part of the requirement document, which used in that particular project only. Product testing defines that we are testing the developed software or application according to the market demand or analysis(requirement) of multiple customers. Product testing, we test all the required documents used in the whole product.

How many types of defects have you found while testing the project in your current organization?
Ans: There are various ways in which we can classify. Below are some of the classifications:
(1) Severity Wise:
Major: A defect, which will cause observable product failure or departure from requirements.
Minor: A defect that will not cause a failure in the execution of the product.
Fatal: A defect that will cause the system to crash or close abruptly or affect other applications.
(2) Work product-wise:
SSD: A defect from System Study Document.
FSD: A defect from the Functional Specification Document.
ADS: A defect from Architectural Design Document.
DDS: A defect from the Detailed Design Document.
Source code: A defect from Source code.
Test Plan/Test Cases: A defect from Test Plan/Test Cases.
User Documentation: A defect from User manuals, Operating manuals.
(3) Error Wise:
Comments: Inadequate/incorrect/misleading or missing comments in the source code.
Computational Error: Improper computation of the formulae/improper business validations in code.
Data error: Incorrect data population/update in database.
Database Error: Error in the database schema/Design.
Missing Design: Design features/approach missed/not documented in the design document and hence, does not correspond to requirements.
Inadequate or sub-optimal Design: Design features/approach needs additional inputs for it to be complete Design features described does not provide the best approach (optimal approach) towards the solution required.
Incorrect Design: Wrong or inaccurate Design.
Ambiguous Design: The design feature/approach is not clear to the reviewer. It also includes the ambiguous use of words or unclear design features.
Boundary Conditions Neglected: Boundary conditions not addressed/incorrect.
Interface Error: Internal or external to application interfacing error, Incorrect handling of passing parameters, Incorrect alignment, incorrect/misplaced fields/objects, unfriendly window/screen positions.
Logic Error: Missing or Inadequate or irrelevant or ambiguous functionality in the source code.
Message Error: Inadequate/ incorrect/ misleading or missing error messages in the source code.
Navigation Error: Navigation not coded correctly in the source code.
Performance Error: An error related to the performance/optimality of the code.
Missing Requirements: Implicit/Explicit requirements are missed/not documented during requirement phase.
Inadequate Requirements: Requirement needs additional inputs for to be complete.
Incorrect Requirements: Wrong or inaccurate requirements.
Ambiguous Requirements: Requirement is not clear to the reviewer. It also includes the ambiguous use of words – e.g., Like, such as, maybe, could be, might, etc.
Sequencing/Timing Error: Error due to incorrect/missing consideration to timeouts and improper/missing sequencing in the source code.
Standards: Standards not followed like improper exception handling, use of E & D Formats, and project-related design/requirements/coding standards.
System Error: Hardware and Operating System-related error, Memory leak.
Test Plan/Cases Error: Inadequate/incorrect/ambiguous or duplicate or missing – Test Plan/ Test Cases & Test Scripts, Incorrect/Incomplete test setup.
Typographical Error: Spelling/Grammar mistakes in documents/source code.
Variable Declaration Error: Improper declaration/usage of variables, Type mismatch error in source code.
(4) Status Wise:
Open
Closed
Deferred
Cancelled
These are the major ways in which defects can be classified.

What is Test Release Document and Test Report Document?
Ans: Test Release Document is a document that covers all the testing related information like what are the features/module are tested and types of testing done on the product also what types of testing not done on the product, also what is the environment on which product is tested and all the release information related to that product.
Test Report Document is a document that covers no. of the pass, no. of fails, the percentage of pass and percentage of fail, etc.

What is the difference between Project and Product?
Ans:

• If the developed software or application developed according to the client requirement or a specific customer, then it is called a “Project,” otherwise, if the software or application is developed according to the market demand or analysis(requirement) for multiple customers, then it is called a “Product.”
• The project contains requirements about the Product and the different phases which is required to develop the Product, while the Product will be the results of the Project.
  
• Multiple processes form Project & Projects produces various Products, i.e, Process ->Project ->Product.

Why should you use Bi-Directional Traceability in your current Project?
(OR)
What is the difference between forwarding Traceability & Backward Traceability?
Ans: Bi-Directional Traceability contains both Forward & Backward Traceability.
(1) Forward Traceability, we can check that required documents are covered in which test cases? Or whether the required documents covered in the test cases or not?
Backward Traceability, we can see that test cases are mapped with which requirement document. This will help us in identifying if there are test cases that do not trace to any coverage item in which the test case is not required and should be removed (or maybe a specification like a requirement or two should add). This Backward Traceability is also very helpful if you want to identify that a particular test case is covering how many requirement documents.
(2) Forward Traceability Matrix ensures that we are Building the Right Product and Backward Traceability Matrix ensures that We the Building the Product Right.

What is the difference between Software Quality Assurance and Software Quality Control?
Ans:

• Software Quality Assurance is used to identify the Standards and Guidelines; whereas, and Software Quality Control is used to implement the Standards and Guidelines.
• Software Quality Assurance is Process-Oriented; whereas, Software Quality Control is Product Oriented.
• Software Quality Assurance is used to Prevent Problems, whereas Software Quality Control is used to Delete Problems.
• Software Quality Assurance needs Continuous Improvement for Audits, i.e., it Checks for Conformance; whereas, Software Quality Control is the Final Checkpoint before delivery.

Challenges faced using selenium Automation Testing
Ans: Dealing with pop-up windows

• Testing dynamic text or content
• How to go about testing Flash
• Capturing screenshots, either to file or in some form of the report
• Iteration of the test case, running it repeatedly with some minor change
• Data-Driven Testing, using suites of pre-cooked data or generating it on the fly
• Generating useful test status reports
• Setting up Remote Control
• Setting up Grid
• handling Alerts Popups
• Switching between windows
• Working with frames.
• Field validation
• How to identify dynamic objects.
• Xpath and CSS locators for identifying elements.
• File Upload/Download Using : Java-AutoIT-Selenium
• Handling Multiple Popup Windows.
• Switching with multiple Windows

Suppose I have 5 @Tests and 3 Tests are independent, but the 4th test is dependent on the 3rd Test, and the 5th test is dependent on 3rd, but it should execute only after the 4th test. How to plan my execution for the above scenario in Testng.
Ans: Normal priority will work. Suppose TC 3, TC 4, and TC 5 will have priorities as 3,4,5, respectively. TC 4 and 5 both are dependent on TC 3. By priority, TC 3 will execute before TC 4 and 5. Since TC 4 has priority higher den TC 5 so TC 4 will be executed, they are followed by  TC 5.

Searching Keywords: manual testing tutorial, automation testing interview questions, AUT in testing, manual testing, TCS software testing interview questions, what is software testing and its types, UI testing interview questions, automation testing interview questions, manual testing interview questions for freshers, manual testing interview questions and answers pdf, testing interview questions for experienced professionals with answers, manual testing interview questions and answers for experienced in Capgemini, scenario-based software testing interview questions and answers for experienced, manual testing interview questions and answers for freshers doc, practical testing interview questions

Final Words

I hope this massive list of manual testing interview questions will be a boost to your career because if you follow all those interview questions, then we are sure that you can face any interview questions.

But when you are attending the interview, I have to be confident while answering the interview because a simple no is better than giving some random non-answer and adding unnecessary details.

So wish you the very best of luck for your upcoming interview and let us know what type of interview questions you have faced in an interview. If that is not covered here, we will try to add all those missed interview questions in this list to be more helpful to the testing community.

the above manual testing interview questions are frequently asked in most of the interviews. So we request you to share in all the testing community so that you are indirectly helping other fellow testers. If you want to share your interview experience or interview process in which you have gone through the interview, you can write to us.