February 2019

A. Developers
B. Testers
C. Users
D. All of the mentioned

A. Test File Generator
B. Coverage Analyzer
C. Output Comparator
D. Test Harness System

A. Test/File Generator
B. Test Harness System
C. Test Archiving Systems
D. Coverage Analyzer

Explanation: The answer is self-explanatory.

A. alpha testing
B. beta testing
C. regression testing
D. none of the mentioned

Explanation: Beta testing is the last stage of testing, and normally can involve sending the product to beta test sites outside the company for real-world exposure or offering the product for a free trial download over the Internet.

A. Non-Code Source Statement
B. Non Comment Source Sentence
C. Non-Comment Source Statement
D. All of the mentioned

A. Code Inspector
B. Static Analyzer
C. Standard Enforcer
D. Coverage Analyzer

Explanation: A static analyzer operates from a pre-computed database o descriptive information derived from the source text of the program.

A. Static Analyzer
B. Code Inspector
C. Standard Enforcer
D. Both Code Inspector & Standard Enforcer

Explanation: A standard enforcer is just like a code inspector, except that the rules are generally simpler. Standard enforcer looks at only single statements while the static analyzer looks at whole programs.

A. Static Testing Tool
B. Dynamic Testing
C. Static & Dynamic Testing
D. None of the mentioned

Explanation: Static Testing tools are those that perform analysis of the the program without executing them at all.

A. data
B. case
C. variable
D. all of the mentioned

Explanation: It increases the scope for code inspection.

A. Acceptance testing
B. Regression testing
C. Equivalence partitioning
D. Quality assurance

Explanation: Equivalence partitioning is a software testing technique that divides the input data of a software unit into partitions of equivalent data from which test cases can be derived.