21⟩ What is Code review?
A meeting at which software code is presented to project personnel, managers, users, customers, or other interested parties for comment or approval. Contrast with code audit, code inspection, code walkthrough.
Software QA
Home Testing Software QA
“Software QA Testing Interview Questions and Answers will guide us that Software QA is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software Testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. So learn more about Software QA with this Software QA Testing Interview Questions with Answers guide”
251 Software QA Questions And Answers
22⟩ Explain Glossary of Software QA/Testing?
A value derived by adding several qualities and dividing the sum by the number of these quantities.
23⟩ What is Affinity Diagram?
A group process that takes large amounts of language data, such as a list developed by brainstorming, and divides it into categories.
24⟩ What is Checksheet?
A form used to record data as it is gathered.
25⟩ What is Walkthrough?
Usually, a step-by-step simulation of the execution of a procedure, as when walking through code, line by line, with an imagined set of inputs. The term has been extended to the review of material that is not procedural, such as data descriptions, reference manuals, specifications, etc.
26⟩ What is Data Flow Analysis?
Consists of the graphical analysis of collections of (sequential) data definitions and reference patterns to determine constraints that can be placed on data values at various points of executing the source program.
27⟩ Explain Defect?
NOTE: Operationally, it is useful to work with two definitions of a defect:
1) From the producer’s viewpoint: a product requirement that has not been met or a product attribute possessed by a product or a function performed by a product that is not in the statement of requirements that define the product.
2) From the end user’s viewpoint: anything that causes end user dissatisfaction, whether in the statement of requirements or not.
28⟩ What is Usability?
"Usability" means ease of use; the ease with which a user can learn to operate, prepare inputs for, and interpret the outputs of a software product.
29⟩ What is Failure-directed Testing?
Testing based on the knowledge of the types of errors made in the past that are likely for the system under test.
30⟩ What is Incremental testing?
Incremental testing is partial testing of an incomplete product. The goal of incremental testing is to provide an early feedback to software developers.
31⟩ What is Flowchart?
A diagram showing the sequential steps of a process or of a workflow around a product or service. Formal Review: A technical review conducted with the end user, including the types of reviews called for in the standards.
32⟩ What is Hybrid Testing?
A combination of top-down testing combined with bottom-up testing of prioritized or available components.
33⟩ What is Operational Requirements?
Qualitative and quantitative parameters that specify the desired operational capabilities of a system and serve as a basis for deter-mining the operational effectiveness and suitability of a system prior to deployment.
34⟩ What is Class Level Methods?
As mentioned above, a class (and its operations) is the module most concentrated on in OO environments. From here it should expand to other classes and sets of classes. Just like traditional models are tested by starting at the module first and continuing to module clusters or builds and then the whole program
35⟩ What is OO Integration Testing?
This strategy involves testing the classes as they are integrated into the system. The traditional approach would test each operation separately as they are implemented into a class. In OO system this approach is not viable because of the "direct and indirect interactions of the components that make up the class"
. Integration testing in OO can be performed in two basic ways :
- Thread-based - Takes all the classes needed to react to a given input. Each class is unit tested and then thread constructed from these classes tested as a set.
- Uses-based - Tests classes in groups. Once the group is tested, the next group that uses the first group (dependent classes) is tested. Then the group that uses the second group and so on. Use of stubs or drivers may be necessary. Cluster testing is similar to testing builds in the traditional model. Basically collaborating classes are tested in clusters.
36⟩ Explain Basis Path Testing?
Basis path testing is a white-box technique. It allows the design and definition of a basis set of execution paths. The test cases created from the basis set allow the program to be executed in such a way as to examine each possible path through the program by executing each statement at least once.
To be able to determine the different program paths, the engineer needs a representation of the logical flow of control. The control structure can be illustrated by a flow graph. A flow graph can be used to represent any procedural design.
Next a metric can be used to determine the number of independent paths. It is called cyclomatic complexity and it provides the number of test cases that have to be designed. This insures coverage of all program statements.
37⟩ Explain Operational Testing?
Testing performed by the end user on software in its normal operating environment.
38⟩ What is Outputs?
Products, services, or information supplied to meet end user needs.
39⟩ What is Path Coverage Testing?
A test method satisfying coverage criteria that each logical path through the program is tested. Paths through the program often are grouped into a finite set of classes; one path from each class is tested.
40⟩ What is Policy?
Managerial desires and intents concerning either process (intended objectives) or products (desired attributes).
