Top 30 Manual Testing Interview Questions & Answers for Fresher

Manual Testing is a procedure done to discover the imperfections. In this strategy, the analyser assumes a vital part of the end client and checks all highlights of the application to guarantee the conduct of the application. The Manual Testing is an essential kind of testing which finds the bugs in the application under test. It is preparatory testing, must be completed before the beginning of automating the experiments and furthermore needs to check the plausibility of mechanization testing.

You must be thinking that in today’s digital era why do we need manual testing. Trust me when I say this that manual testing is equally important as automated testing because you can test whatever you want at any time you want. You can perform random tests which are not possible for automated testing. This is why manual testing is and will always be a need. This, in turn, means there would always be vacancies for the individuals who are into manual testing. In case you are about to sit for an interview for the job role requiring manual testing skills then I am sure you would benefit from this blog. We have collated the most commonly asked questions in an interview session based on manual testing to help you in your interview preparation.

Manual Testing Interview Questions

• What is Software Testing?
• Explain the procedure for manual testing.
• Explain the tasks involved in planning and control.
• What is Static Testing?
• What is Dynamic Testing?
• What is use case testing?
• What is the difference between Positive and Negative Testing?
• What is a test case?
• Explain the tasks of test closure activities.
• Can you list down a few characteristics of a test case?
• How will you define a critical bug?
• What is Endurance Testing?
• What is Path Testing?
• Why we need Localization Testing?
• What is the difference between Validation and Verification?
• What is a Test Harness?
• What is a Test Closure?
• What is Top-Down Approach?
• What is the Bottom-Up Approach?
• Is it true that we can do system testing at any stage?
• What are the Experience-based testing techniques?
• When is it ideal that the testing is stopped?
• Explain the concept of semi-random test cases?
• Why we use decision tables?
• Why is it that the boundary value analysis provides good test cases?
• What is test coverage?
• Explain the concept of defect cascading?
• What is the Regression testing?

Manual Testing Interview Questions and Answers  

For a person who is looking to attend an interview on manual testing recently, here are some of the most standard interview questions and answers that will surely help you in the right way. At this juncture, we have a built-in list of the top frequently asked questions along with answers to help Fresher and the experienced people to crack this interview. 

Q1). What is Software Testing?

If we go by the ANSI/IEEE 1059 standards software testing is a procedure of breaking down software to distinguish the contrasting characteristics among the existing software conditions and the required conditions (i.e. bugs and defects) and to assess the highlights of the software at hand.

Q2). Explain the procedure for manual testing.

The manual testing process comprises of the following-

• Planning and Control
• Analysis and Design
• Implementation and Execution
• Evaluating exit criteria and Reporting
• Test Closure activities

Q3). Explain the tasks involved in planning and control.

Test planning comprises of the following major tasks:

• To fix the scope and the number of risks and ascertain the goals of testing.
• To govern the test method.
• To execute the test policy and/or the test tactics. 

Q4). What is Static Testing?

Static Testing includes the process of exploring the records to recognize the imperfections in the very early stages of SDLC.

Q5). What is Dynamic Testing?

Dynamic testing includes the process of execution of code. It validates and approves the output with the expected results.

Q6). What is the difference between Positive and Negative Testing?

Positive Testing	Negative Testing:
It is done to figure out what a framework is expected to do. It checks whether the application is defending the necessities it was built for or not.	It is to figure out what framework has been tuned to not do. It finds the deformities from the product.

Q7). What is use case testing?

The use case testing uses the use case to assess the application. So that, the tester can inspect all the functionalities of the application. Use case testing can cover a whole application.

Q8). What is a test case?

A test case is ideally used to test the conformance of a developed application in consonance with its requirement stipulations. It is a set of settings with pre-requisites, input values and predictable results in a recognized form.

Q9). Explain the tasks of test closure activities.

Test closure activities are endowed with the following major tasks:

Read: Top 20 QTP Interview Questions and Answers

• To see which strategic deliverable are really delivered and to safeguard that all incident reports have been successfully resolved.
• To confirm and document the test ware such as writings, testing environments, etc. for future reuse.
• To deliver the test ware to the maintenance team. They will give sustenance to the software.
• To assess how the testing actually went and acquire lessons for upcoming releases and ventures.

Q10). Can you list down a few characteristics of a test case?

A test case can have the following attributes-

• Test Case Id – An exceptional identifier for the test case.
• Test Summary – Online comments or summary for each of the test cases.
• Description – A Comprehensive narrative of the test case.
• Precondition or pre-requisite – A set of fundamentals that must be charted before implementing the test steps.
• Test Steps – Comprehensive steps for carrying out the test case.
• Expected result – The estimated result in the direction to pass the test.
• Actual result – The actual result received after having done the execution of the test steps.
• Test Result – Pass/Fail to stand of the test execution.
• Automation Status – Identifier for automation – whether the given application is mechanized or not.
• Date – The date of the test execution.
• Executed by – Name of the person performing the test case.

Q11). How will you define a critical bug?

A critical bug is a bug that has got the tendency to affect a majority of the functionality of the given application and the application cannot be distributed to the end client deprived of the procedure of fixing that bug. It is different from a blocker bug as it doesn’t essentially disturb or block the testing of other parts of the given application.

Q12). What is Endurance Testing?

In this type of testing, we test the application's behavior in contrast to the load and stress put on over an application for a long period of time.

Q13). Why we need Localization Testing?

Localization testing generally deals with the functionality of application and GUI of the application.

Q14). What is Path Testing?

Path testing is a testing in which tester guarantee that each path of the application should be affected at least once. In this testing, all the paths in the program’s source code are tested in any case once for sure.

Q15). What are Validation and Verification?

Verification	Validation
Progression of assessing work-products of a growth phase to control whether they fulfill the stated necessities for that stage.	The process of evaluating software during or at the end of the development process to determine whether it specified requirements.

Manual Testing Interview Questions for Experienced 

Q16). What is a Test Harness?

A test harness is the gathering of software along with the test information arranged to test a program unit by running it under changing conditions which include checking the input values with the expected yield.

Q17). What is a Test Closure?

Test Closure is the note arranged before the test group formally finishes the testing procedure. This note contains the aggregate no. of experiments, total no. of experiments executed, total no. of imperfections discovered, add total no. of imperfections settled, total no. of bugs not settled, total no of bugs rejected and so forth.

Q18). What is Top-Down Approach?

Testing happens from top-to-bottom. High-level state modules are tested first and after that low-level modules and lastly incorporating the low-level modules to a high-level state to guarantee the framework is working as it is expected to. Stubs are utilized as an impermanent module if a module isn't prepared for integration testing.

Q19). What is the Bottom-Up Approach?

It is an opposite of the Top-Down Approach. Testing happens from base levels to high-up levels. The lowest level modules are tried first and afterward high-level state modules and lastly coordinating the high-level state modules to a low level to guarantee the framework is filling in as it has been proposed to. Drivers are utilized as a transitory module for incorporation testing.

Q20). Is it true that we can do system testing at any stage?

No. The system testing must start only if all units are in place and are working properly. Though, it ought to happen before the UAT (User Acceptance testing).

Q21). What are the Experience-based testing techniques?

Inexperienced based methods, individuals’ information, abilities and foundation knowledge are prime supporters of the test conditions and experiments. The experience of both technical, as well as business, is vital, as they convey alternate points of view to the test examination and configuration process. Because of past involvement with comparable frameworks, they may have bits of knowledge into what could turn out badly, which is exceptionally valuable for testing purposes.

Read: Top 20 Frequently Asked Regression Testing Interview Questions & Answers

Q22). When is it ideal that the testing is stopped?

It depends on the level of risks associated with the system being tested. There are some criteria bases on which it is ok to stop testing.

• Closing date (Testing, Release)
• Test budget has been exhausted
• Bug rate fall below the definite level
• Test cases finished with assured percentage passed
• Alpha or beta periods for testing ends
• Reporting of code, functionality or necessities are met to a stated point

Q23). Explain the concept of semi-random test cases?

Semi-random test cases are those test cases which we get when we perform arbitrary experiments and do proportionality parceling to those experiments; it evacuates repetitive experiments, along these lines giving us semi-random test cases.

Q24). Why we use decision tables?

The techniques of equivalence dividing and boundary value analysis are regularly connected to the particular circumstances or sources of info. Nonetheless, if distinctive combinations of sources of info result in various actions being taken, this can be more difficult to indicate utilizing comparability apportioning and limiting esteem investigation, which has got a tendency to be more centered around the UI.

The other two determinations based methods, choice tables, and state change testing are more centered around business rationale or business rules. A choice table is a decent method to manage blends of things (e.g. inputs). This procedure is once in a while additionally alluded to as a ’cause-impact’ table. The purpose behind this is there is a related rationale charting system called ’cause-impact diagramming’ which was some of the time used to help determine the decision table 

Q25). Why is it that the boundary value analysis provides good test cases?

This is for the reason that errors are often made during the program design of the different cases near the ‘edges' of the array of values. 

Q26). What is test coverage?

Test coverage assesses in some specific way the quantity of testing completed by a regular set of tests (derived in some other way, e.g. using requirement-based methods). Everywhere we can tally things and can tell whether or not each of those things has been verified by some test, then we can measure coverage.

Q27). Explain the concept of defect cascading?

Defect cascading is a defect which is triggered by a different defect in the same application. In this one, defect beseeches the other defect in the application. When a defect is extant in any stage but is not recognized, hide to other stages without getting noted. This will affect in an upsurge in the number of defects.

Q28). What is the Regression testing?

Regression testing checks that alteration in code has not affected the operational functionality.