Top 350+ Solved Software Testing and Quality Assurance (STQA) MCQ Questions Answer
Q. When testing principles are useful?
a. during testing
b. during execution
c. during review
d. throughout life-cycle
Q. End result of Software Requirement Analysis is ________
a. functional and behavioral
b. architectural and structural
c. usability and reliability
d. algorithmic and data structure
Q. The inputs for developing a test plan are taken from
a. project plan
b. business plan
c. support plan
d. none of the above
Q. Testing beyond normal operational capacity is __________
a. load testing
b. performance testing
c. stress testing
d. all of these
Q. Test wares are handed over to maintenance team during which phase?
a. test implementati on and execution
b. test closure activity
c. evaluating exit criteria and reporting
d. test analysis and design
Q. What are the criteria to decide the testing efforts?1. Time and budget2. Size of development team3. Size of testers4. Risk associated with project
a. 1, 3, 4
b. b. 1, 2, 3
c. 1, 4
d. 1, 3
Q. A chronological record of relevant details about the execution of tests is called as, a _______
a. test suite
b. test procedure
c. test data
d. test log
Q. Which of the following is not other name for structural testing?
a. white box testing
b. glass box testing
c. behavioral testing
d. none of the above
Q. In which of the following type of testing, testing is done without planning and documentation?
a. unit testing
b. retesting
c. ad hoc testing
d. regression testing
Q. When should company stop the testing of a particular software?
a. after system testing done
b. it depends on the risks for the system being tested
c. after smoke testing done
d. none of the above
Q. Who performs the Acceptance Testing?
a. software developer
b. end users
c. testing team
d. systems engineers
Q. Before handing over the software to the client, which testing is to be done in-house?
a. alpha
b. betta
c. gamma
d. theta
Q. Requirement Engineering is not concern with _.
a. requirement design
b. requirement elicitation
c. requirement analysis
d. requirement documentatio n