300+ TOP MANUAL TESTING Interview Questions and Answers

MANUAL TESTING Interview Questions for freshers and experienced :-

1. 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 reuired conditions (i.e. bugs and defects) and to assess the highlights of the software at hand.

2. 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

3. Explain the tasks involved in planning and control.
Test planning comprises of the following major tasks:

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

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

5. What is Dynamic Testing?
Dynamic testing includes the process of execution of code. It validates and approves the output with the expected results.

6. 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.

7. 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.

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

9. Explain the tasks of test closure activities.
Test closure activities are endowed with the following major tasks:

• 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 acuire lessons for upcoming releases and ventures.

10. 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-reuisite – 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.

11. 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.

12. 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.

13. Why we need Localization Testing?
Localization testing generally deals with the functionality of application and GUI of the application.

14. 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.

15. 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 reuirements.
Manual Testing Interview uestions for Experienced

16. 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.

17. 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.

18. 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.

19. 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.

20. 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).

21. 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.

22. 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

23. 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.

24. Why we use decision tables?
The techniues of euivalence 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

25. 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.

26. Explain the term bug.
A bug is an error found while running a program. Bug fall into two categories: logical and syntax.
Senior Tester Interview Questions

27. Explain the difference between functional and structural testing.
Functional testing is considered to be behavioral or black box testing in which the tester verifies that the system or application functions according to specification.  Structural testing on the other hand is based on the code or algorithms and is considered to be white box testing.

28. Define defect density.
Defect density is the total number of defects per lines of code.

29. When is a test considered to be successful?
The purpose of testing is to ensure that the application operates according to the requirements and to discover as many errors and bugs as possible.  This means that tests that cover more functionality and expose more errors are considered to be the most successful.

30. What good bug tracking systems have you used?
This is a simple interview question about your experience with bug tracking.  Provide the system/systems that you are most familiar with if any at all.   It would also be good to provide a comparison of the pros and cons of several if you have experience. Bug tracking is the essence of testing process and is a must asked manual testing interview questions in any interview. Do not forget this.

31. In which phase should testing begin – requirements, planning, design, or coding?
Testing should begin as early as the requirements phase.

32. Can you test a program and find 100% of the errors?
It is impossible to fine all errors in an application mostly because there is no way to calculate how many errors exist.  There are many factors involved in such a calculation such as the complexity of the program, the experience of the programmer, and so on. This Manual testing interview questions is the most tricky questions considered by testers.

33. What is the difference between debugging and testing?
The main difference between debugging and testing is that debugging is typically conducted by a developer who also fixes errors during the debugging phase.  Testing on the other hand, finds errors rather than fixes them.  When a tester finds a bug, they usually report it so that a developer can fix it.

34. How should testing be conducted?
Testing should be conducted based on the technical requirements of the application.

35. What is considered to be a good test?
Testing that covers most of the functionality of an object or system is considered to be a good test.

36. What is the difference between top-down and bottom-up testing?
Top-Down testing begins with the system and works its way down to the unit level.  Bottom-up testing checks in the opposite direction, unit level to interface to overall system. Both have value but bottom-up testing usually aids in discovering defects earlier in the development cycle, when the cost to fix errors is lower.

37. Explain how to develop a test plan and a test case.
A test plan consists of a set of test cases. Test cases are developed based on requirement and design documents for the application or system. Once these documents are thoroughly reviewed, the test cases that will make up the test plan can be created.

38. What is the role of quality assurance in a product development lifecycle?
Quality assurance should be involved very early on in the development life cycle so that they can have a better understanding of the system and create sufficient test cases. However, QA should be separated from the development team so that the team is not able to build influence on the QA engineers.

39. What is the average size of executables that you have created?
This is a simple interview question about our experience with executables.  If you know the size of any that you’ve created, simply provide this info.

40. What version of the Oracle are you familiar with?
This is an interview question about experience.  Simply provide the versions of the software that you have experience with.

41. How is an SQL query executed in Oracle 8?
This is an interview question to check your experience with Oracle and you can simply provide the answer “from the command prompt.”  If you do not have Oracle experience, do not pretend and simply state that you have not worked on an Oracle database. Though this is a common manual testing interview questions, the answers can be different. Because if you have experience in other tools such as TOAD, SQL server etc, you can conveniently answer as per your experience.

42. Have you performed tests on the front-end and the back-end?
This is an interview question in which you should explain whether you performed testing on the GUI or the server portion of previous applications.

43. What is the most difficult problem you’ve found during testing?
This is a simple interview question in which you should provide an example. This is one of  most tricky manual testing interview questions as your answer will decide your job. You need to answer in such a way that your problem solving skills and your eagerness to learn new things, and your dedication towards the job will indicated by your answers.

44. What were your testing responsibilities at your previous employer?
This interview question is very likely being asked to verify your knowledge of your resume. Make sure that you know what is on your resume and that it is the truth.

45. What is Defect?

Non-conformance to requirements or functional / program specification

46. What is Dependency Testing?

Examines an application’s requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.

47. What is Depth Testing?

A test that exercises a feature of a product in full detail.

48. What is Dynamic Testing?

Testing software through executing it. See also Static Testing.

49. What is Emulator?

A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.

50. What is Endurance Testing?

Checks for memory leaks or other problems that may occur with prolonged

execution

51. What is End-to-End testing?

Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

52. What is Equivalence Class?

A portion of a component’s input or output domains for which the component’s behaviour is assumed to be the same from the component’s specification.

53. What is Equivalence Partitioning?

A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

54. What is Exhaustive Testing?

Testing which covers all combinations of input values and preconditions for an element of the software under test.

55. What is Functional Decomposition?

A technique used during planning, analysis and design; creates a functional hierarchy for the software.

54. What is Functional Specification?

A document that describes in detail the characteristics of the product with regard to its intended features.

55. What is Functional Testing?

Testing the features and operational behavior of a product to ensure they correspond to its specifications. Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions. or Black Box Testing.

56. What is Glass Box Testing?

A synonym for White Box Testing.

57. What is Gorilla Testing?

Testing one particular module, functionality heavily.

58. What is Gray Box Testing?

A combination of Black Box and White Box testing methodologies? testing a piece of software against its specification but using some knowledge of its internal workings.

59. What is High Order Tests?

Black-box tests conducted once the software has been integrated.

60. What is Independent Test Group (ITG)?

A group of people whose primary responsibility is software testing,

61. What is Inspection?

A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection).

62. What is Integration Testing?

Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

63. What is Installation Testing?

Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

64. What is Load Testing?

See Performance Testing.

65. What is Localization Testing?

This term refers to making software specifically designed for a specific locality.

66. What is Loop Testing?

A white box testing technique that exercises program loops.

67. What is Metric?

A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.

68. What is Monkey Testing?

Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.

69. What is Negative Testing?

Testing aimed at showing software does not work. Also known as “test to fail”. See also Positive Testing.

70. What is Path Testing?

Testing in which all paths in the program source code are tested at least once.

71. What is Performance Testing?

Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as “Load Testing”.

72. What is Positive Testing?

Testing aimed at showing software works. Also known as “test to pass”. See also Negative Testing.

73. What is Quality Assurance?

All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.

74. What is Quality Audit?

A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.

75. What is Quality Circle?

A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.

76. What is Quality Control?

The operational techniques and the activities used to fulfill and verify requirements of quality.

77. What is Quality Management?

That aspect of the overall management function that determines and implements the quality policy.

78. What is Quality Policy?

The overall intentions and direction of an organization as regards quality as formally expressed by top management.

79. What is Quality System?

The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.

80. What is Race Condition?

A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.

81. What is Ramp Testing?

Continuously raising an input signal until the system breaks down.

82. What is Recovery Testing?

Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions

83. What is Regression Testing?

Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.

84. What is Release Candidate?

A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).

85. What is Sanity Testing?

Brief test of major functional elements of a piece of software to determine if its basically operational.

86. What is Scalability Testing?

Performance testing focused on ensuring the application under test gracefully handles increases in work load.

87. What is Security Testing?

Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

88. What is Smoke Testing?

A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

89. What is Soak Testing?

Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.

90. What is Software Requirements Specification?

A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software/

91. What is Software Testing?

A set of activities conducted with the intent of finding errors in software.

92. What is Static Analysis?

Analysis of a program carried out without executing the program.

93. What is Static Analyzer?

A tool that carries out static analysis.

94. What is Static Testing?

Analysis of a program carried out without executing the program.

95. What is Storage Testing?

Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.

96. What is Stress Testing?

Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load.

97. What is Structural Testing?

Testing based on an analysis of internal workings and structure of a piece of software. See also White Box Testing.

98. What is System Testing?

Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

99. What is Testability?

The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.

100. What is Testing?

The process of exercising software to verify that it satisfies specified requirements and to detect errors. The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829). The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component. What is Test Automation? It is the same as Automated Testing.

101. What is Test Bed?

An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.

102. What is Test Case?

Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc. A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. Test Driven Development? Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.

103. What is Test Driver?

A program or test tool used to execute tests. Also known as a Test Harness.

104. What is Test Environment?

The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.

105. What is Test First Design?

Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.

106. What is Test Harness?

A program or test tool used to execute a tests. Also known as a Test Driver.

107. What is Test Plan?

A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.

108. What is Test Procedure?

A document providing detailed instructions for the execution of one or more test cases.

109. What is Test Script?

Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.

110. What is Test Specification?

A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.

111. What is Test Suite?

A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.

112. What is Test Tools?

Computer programs used in the testing of a system, a component of the system, or its documentation.

113. What is Thread Testing?

A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.

114. What is Top Down Testing?

An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.

115. What is Total Quality Management?

A company commitment to develop a process that achieves high quality product and customer satisfaction.

116. What is Traceability Matrix?

A document showing the relationship between Test Requirements and Test Cases.

117. What is Usability Testing?

Testing the ease with which users can learn and use a product.

118. What is Use Case?
The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.

119. What is Unit Testing?
Testing of individual software components.

120. how do the companies expect the defect reporting to be communicated by the tester to the development team. Can the excel sheet template be used for defect reporting. If so what are the common fields that are to be included who assigns the priority and severity of the defect
To report bugs in excel:
Sno. Module Screen/ Section Issue detail Severity
Prioriety Issuestatus
this is how to report bugs in excel sheet and also set filters on the Columns attributes.
But most of the companies use the share point process of reporting bugs In this when the project came for testing a module wise detail of project is inserted to the defect management system they are using. It contains following field
1. Date
2. Issue brief
3. Issue description (used for developer to regenerate the issue)
4. Issue status( active, resolved, on hold, suspend and not able to regenerate)
5. Assign to (Names of members allocated to project)
6. Priority(High, medium and low)
7. Severity (Major, medium and low)121. How do you plan test automation?1. Prepare the automation Test plan
2. Identify the scenario
3. Record the scenario
4. Enhance the scripts by inserting check points and Conditional Loops
5. Incorporated Error Handler
6. Debug the script
7. Fix the issue
8. Rerun the script and report the result

122. Does automation replace manual testing?