Manual Testing Interview Questions & Answers for Freshers and Experienced
Manual testing interview questions covering SDLC, STLC, test cases, bug life cycle, and testing techniques for QA roles.
Top Manual Testing Interview Questions for Freshers and Experienced Developers
Ace your QA interviews with manual testing questions covering testing fundamentals, test case design, defect life cycle, and real-world testing scenarios.
55 Questions3 PagesEasy · Medium · HardPage 1 of 3
1
What is the difference between the QA and software testing?
Answer
The role of QA (Quality Assurance) is to monitor the quality of the process to produce a quality of a product. While the software testing, is the process of ensuring the final product and check the functionality of final product and to see whether the final product meets the user’s requirement.
Did you know it?
2
What is Testware in manual testing?
Answer
Testware is the subset of software, which helps in performing the testing of application. It is a term given to the combination of software application and utilities which is required for testing a software package.
Did you know it?
3
What is Test case in manual testing?
Answer
Test case is a specific term that is used to test a specific element. It has information of test steps, prerequisites, test environment and outputs.
Did you know it?
4
What is a 'USE' case and what does it include?
Answer
The document that describes, the user action and system response, for a particular functionality is known as USE case. It includes revision history, table of contents, flow of events, cover page, special requirements, pre-conditions and post-conditions.
Did you know it?
5
What is validation and verification in software testing?
Answer
In verification, all the key aspects of software developments are taken in concern like code, specifications, requirements and document plans. Verification is done on the basis of four things list of issues, checklist, walk through and inspection meetings. Following verification, validation is done, it involves actual testing, and all the verification aspects are checked thoroughly in validation.
Did you know it?
6
What is the difference between white box, black box, and gray box testing?
Answer
Black box testing is a testing strategy based solely on requirements and specifications. Black box testing requires no knowledge of internal paths, structures, or implementation of the software being tested. White box testing is a testing strategy based on internal paths, code structures, and implementation of the software being tested. White box testing generally requires detailed programming skills.
In gray box testing this we look into the "box" being tested just long enough to understand how it has been implemented. Then we close up the box and use our knowledge to choose more effective black box tests.
Did you know it?
7
Does an increase in testing always improve the project?
Answer
No an increase in testing does not always mean improvement of the product, company, or project. In real test scenarios only 20% of test plans are critical from a business angle. Running those critical test plans will assure that the testing is properly done. The following graph explains the impact of under testing and over testing. If you under test a system the number of defects will increase, but if you over test a system your cost of testing will increase. Even if your defects come down your cost of testing has gone up.
Did you know it?
8
What is difference between Master Test Plan and Test Plan?
Answer
1.Master Test Plan contains all the testing and risk involved area of the application where as Test case document contains test cases. 2.Master Test plan contain all the details of each and every individual tests to be run during the overall development of application whereas test plan describe the scope, approach, resources and schedule of performing test. 3.Master Test plan contain the description of every tests that is going to be performed on the application where as test plan only contain the description of few test cases. during the testing cycle like Unit test, System test, beta test etc 4.Master Test Plan is created for all large projects but when it is created for the small project then we called it as test plan.
Did you know it?
9
What is bug life cycle?
Answer
Bug Life Cycle, again is the various stages through which it goes after it's discovered. So once the Quality Assurance Engineer discovers the bug, it's marked as "New", then the concerned authority will assign it to the developer where the status of the bug changes to 'Assigned', once the bug is assigned it's either 'fixed' or 'rejected'. In both the cases, the QAE will verify the bug and mark it as 'reopen' (if not fixed properly) or 'closed' if it no longer exists.
Did you know it?
10
What is smoke testing and what is sanity?
Answer
What would happen if you turn on a newly brought TV and you get smoke coming out of it? Smoke testing is basically to ensure that the basic functionality of the product (in TV's case, it should be displaying video when turned on) works fine. So you'll identify the most basic test cases you need to execute and perform them. Sanity testing is similar - which ensures that the system or product functions without any logical errors. If you are testing a calculator app; you may multiply a number by 9 and check whether the sum of the digits of the answer is divisible by 9.
Did you know it?
11
Mention the different types of software testing?
Answer
Unit testing
Integration testing and regression testing
Shakeout testing
Smoke testing
Functional testing
Performance testing
White box and Black box testing
Alpha and Beta testing
Load testing and stress testing
System testing
Did you know it?
12
What is data driven testing?
Answer
Data driven testing is an automation testing part, which tests the output or input values. These values are read directly from the data files. The data files may include csv files, excel files, data pools and many more. It is performed when the values are changing by the time.
Did you know it?
13
What is the difference between build and release?
Answer
Build: It is a number given to Installable software that is given to testing team by the development team. Release: It is a number given to Installable software that is handed over to customer by the tester or developer.
Did you know it?
14
What is bug leakage and bug release?
Answer
Bug release is when software or an application is handed over to the testing team knowing that the defect is present in a release. During this the priority and severity of bug is low, as bug can be removed before the final handover. Bug leakage is something, when the bug is discovered by the end users or customer, and missed by the testing team to detect, while testing the software.
Did you know it?
15
What is the difference between bug, defect and a error?
Answer
There's actually no difference between 'bug' and 'defect'. It's basically an unexpected behaviour of the software. 'Error' too would fall in the same category; but many times errors are well defined. For example - 404 error in HTML pages.
Did you know it?
16
Explain the steps for Bug Cycle?
Answer
1.Once the bug is identified by the tester, it is assigned to the development manager in open status. 2.If the bug is a valid defect the development team will fix it and if it is not a valid defect, the defect will be ignored and marked as rejected. 3.The next step will be to check whether it is in scope, if it is happen so that, the bug is not the part of the current release then the defects are postponed. 4.If the defect or bug is raised earlier then the tester will assigned a DUPLICATE status. 5.When bug is assigned to developer to fix, it will be given a IN-PROGRESS status. 6.Once the defect is repaired, the status will changed to FIXED at the end the tester will give CLOSED status if it passes the final test.
Did you know it?
17
Explain Structure-based testing techniques.
Answer
Structure-based testing techniques are also termed as white-box testing techniques.
These are dynamic techniques. They use the internal structure of the software to derive test cases. They are usually termed as 'white-box' or 'glass-box' techniques. They need you to have knowledge of how the software is implemented and how it works.
Did you know it?
18
Explain component testing.
Answer
Component testing is also termed as unit, module or program testing.
It looks for defects in the software and verifies its functioning.
It can be done in isolation from rest of the system depending on the context of the development life cycle and the system.
Mostly stubs and drivers are used to replace the missing software and simulate the interface between the software components in a simple manner.
The stub is called from the software component to be tested while a driver calls a component to be tested.
Did you know it?
19
What are decision tables? Why do we use them?
Answer
Decision tables are specification-based techniques which are more focused on business logic or business rules.
A decision table is useful in dealing with combinations of things like inputs.
This technique is sometimes also called as 'cause-effect' table as there exists an associated logic diagramming technique called 'cause-effect graphing' which is at times used to help derive the decision table.
The techniques of equivalence partitioning and boundary value analysis are usually applied to specific situations or inputs.
Did you know it?
20
Explain exploratory testing.
Answer
In exploratory testing approach testers are involved in minimum planning and maximum test execution.
The planning includes creation of a test charter, a short declaration of the scope of a short time-boxed test effort, the objectives and possible approaches to be used.
The test design and test execution are performed parallelly without any formal documentation of test conditions, test cases or test scripts. However, this does not imply that other more formal testing techniques will not be used.
