Google News
logo
Manual Testing Interview Questions
Manual Testing is the process of manually testing software for defects. Manual testing is a software testing process in which test cases are executed manually without using any automated tool. All test cases executed by the tester manually according to the end user's perspective. It ensures whether the application is working, as mentioned in the requirement document or not. Test cases are planned and implemented to complete almost 100 percent of the software application.
A test plan stores all possible testing activities to ensure a quality product. It gathers data from the product description, requirement, and use case documents.
 
The test plan document includes the following :
 
* Testing objectives
* Test scope
* Testing the frame
* Environment
* Reason for testing
* Deliverables
* Risk factors
* Criteria for entrance and exit
Quality control is the process of running a program to determine if it has any defects, as well as making sure that the software meets all of the requirements put forth by the stakeholders. Quality assurance is a process-oriented approach that focuses on making sure that the methods, techniques, and processes used to create quality deliverables are applied correctly.
Manual testing’s strengths are :
 
* It’s cheaper
* It’s great for testing UI’s
* It’s perfect for ad hoc testing
* It’s ideal for testing minor changes
* You get visual feedback that’s accurate and quick
* Testers don’t have to know anything about automation tools
The testing activity ends when the testing team completes the following milestones.
 
Test case execution : The successful completion of a full test cycle after the final bug fix marks the end of the testing phase.
 
Testing deadline : The end date of the validation stage also declares the closure of the validation if no critical or high-priority defects remain in the system.
 
Code Coverage(CC) ratio : It is the amount of code concealed via automated tests. If the team achieves the intended level of code coverage (CC) ratio, then it can choose to end the validation.
 
Mean Time Between Failure (MTBF) rate : Mean time between failure (MTBF) refers to the average amount of time that a device or product functions before failing. This unit of measurement includes only operational time between failures and does not include repair times, assuming the item is repaired and begins functioning again. MTBF figures are often used to project how likely a single unit is to fail within a certain period of time
Quality control is a product-oriented approach of running a program to determine if it has any defects, as well as making sure that the software meets all of the requirements put forth by the stakeholders.
Some types of testing are conducted by software developers and some by specialized quality assurance staff. Here are a few different kinds of software testing, along with a brief description of each.

Type Description
Unit Testing A programmatic test that tests the internal working of a unit of code, such as a method or a function.
Integration Testing Ensures that multiple components of systems work as expected when they are combined to produce a result.
Regression Testing Ensures that existing features/functionality that used to work are not broken due to new code changes.
System Testing Complete end-to-end testing is done on the complete software to make sure the whole system works as expected.
Smoke Testing A quick test performed to ensure that the software works at the most basic level and doesn’t crash when it’s started. Its name originates from the hardware testing where you just plug the device and see if smoke comes out.
Performance Testing Ensures that the software performs according to the user’s expectations by checking the response time and throughput under specific load and environment. 
User-Acceptance Testing Ensures the software meets the requirements of the clients or users. This is typically the last step before the software is live, i.e. it goes to production.
Stress Testing Ensures that the performance of the software doesn’t degrade when the load increases. In stress testing, the tester subjects the software under heavy loads, such as a high number of requests or stringent memory conditions to verify if it works well.
Usability Testing Measures how usable the software is. This is typically performed with a sample set of end-users, who use the software and provide feedback on how easy or complicated it is to use the software. 
Security Testing Now more important than ever. Security testing tries to break a software’s security checks, to gain access to confidential data. Security testing is crucial for web-based applications or any applications that involve money. 
Test coverage is a quality metric to represent the amount (in percentage) of testing completed for a product. It is relevant for both functional and non-functional testing activities. This metric is used to add missing test cases.
We need software testing for the following reasons :

* Testing provides an assurance to the stakeholders that the product works as intended.
 
* Avoidable defects leaked to the end-user/customer without proper testing adds a bad reputation to the development company.
 
* Defects detected earlier phase of SDLC results in lesser cost and resource utilization of correction.
 
* Saves development time by detecting issues in an earlier phase of development.
 
* The testing team adds another dimension to the software development by providing a different viewpoint to the product development process.
Black box Testing : The strategy of black box testing is based on requirements and specification. It requires no need of knowledge of internal path, structure or implementation of the software being tested.
 
White box Testing : White box testing is based on internal paths, code structure, and implementation of the software being tested. It requires a full and detail programming skill.
 
Gray box Testing : This is another type of testing in which we look into the box which is being tested, It is done only to understand how it has been implemented. After that, we close the box and use the black box testing.

Black box testing Gray box testing White box testing
Black box testing does not need the implementation knowledge of a program. Gray box testing knows the limited knowledge of an internal program. In white box testing, implementation details of a program are fully required.
It has a low granularity. It has a medium granularity. It has a high granularity.
It is also known as opaque box testing, closed box testing, input-output testing, data-driven testing, behavioral testing and functional testing. It is also known as translucent testing. It is also known as glass box testing, clear box testing.
It is a user acceptance testing, i.e., it is done by end users. It is also a user acceptance testing. Testers and programmers mainly do it.
Test cases are made by the functional specifications as internal details are not known. Test cases are made by the internal details of a program. Test cases are made by the internal details of a program.