Manual Testing Interview Questions & Answers-PART3


Manual Testing Interview Questions Part-3

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. 




Followers