Software Testing Interview Questions – Part 15
101. Explain Concurrency Testing.
Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.
102. What is Application Programming Interface or API?
A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.
103. What is Basic Block?
A sequence of one or more consecutive, executable statements containing no branches.
104. What is Accessibility Testing?
Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).
105. What is Glass Box Testing?
A synonym for White Box Testing. A white box testing technique that exercises program loops.
106. What is Backus-Naur Form?
A metalanguage used to formally describe the syntax of a language.
107. 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).
108. 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.
109. Explain Data Driven Testing.
Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.
110. Explain Functional Testing.
1) Testing the features and operational behavior of a product to ensure they correspond to its specifications.
2) 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. Block Box testing nothing but Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.