Software Testing Quality Assurance Set 4
On This Page
This set of Software Testing and Quality Assurance (STQA) Multiple Choice Questions & Answers (MCQs) focuses on Software Testing Quality Assurance Set 4
Q1 | Test wares are handed over to maintenance team during which phase?
- test implementati on and execution
- test closure activity
- evaluating exit criteria and reporting
- test analysis and design
Q2 | 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. 1, 2, 3
- c. 1, 4
- d. 1, 3
Q3 | Who leads a formal review process?
- author
- moderator
- reviewer
- scribe
Q4 | A chronological record of relevant details about the execution of tests is called as, a _______
- test suite
- test procedure
- test data
- test log
Q5 | Non functional testing is performed only at system testing level. True or false.
- true
- false
Q6 | Which of the following is not other name for structural testing?
- white box testing
- glass box testing
- behavioral testing
- none of the above
Q7 | Which things are measured by software Test effectiveness?
- how many customer requirements are implemented in system?
- how well the customer specifications are achieved by the system?
- how much effort is put in developing the system?
- all of the above
Q8 | In which of the following type of testing, testing is done without planning and documentation?
- unit testing
- retesting
- ad hoc testing
- regression testing
Q9 | When should company stop the testing of a particular software?
- after system testing done
- it depends on the risks for the system being tested
- after smoke testing done
- none of the above
Q10 | ___________ refers to a different set of tasks ensures that the software that has been built is traceable to Customer Requirements.
- verification
- requirement engineering
- validation
- none of the above
Q11 | Who performs the Acceptance Testing?
- software developer
- end users
- testing team
- systems engineers
Q12 | Before handing over the software to the client, which testing is to be done in-house?
- alpha
- betta
- gamma
- theta
Q13 | Requirement Engineering is not concern with _.
- requirement design
- requirement elicitation
- requirement analysis
- requirement documentatio n
Q14 | When an expected result is not specified in test case template then _.
- we cannot run the test.
- it may be difficult to determine if the test has passed or failed.
- it may be difficult to repeat the test.
- we cannot automate the user inputs.
Q15 | End result of Software Requirement Analysis is _.
- functional and behavioral
- architectural and structural
- usability and reliability
- algorithmic and data structure
Q16 | Bug status is set to postpone due to _.
- priority of that bug may low.
- lack of time for the release.
- the bug may not be the major effect in the software.
- data may be unavailable.
Q17 | Which Testing is performed first?
- black box testing
- white box testing
- dynamic testing
- static testing
Q18 | Verification and Validation uses _.
- internal and external resources respectively.
- internal resources only.
- external resources only.
- external and internal resources respectively.
Q19 | Testing beyond normal operational capacity is _.
- load testing
- performance testing
- stress testing
- none
Q20 | The expected results of the software is _.
- only important in system testing
- only used in component testing
- most useful when specified in advance
- derived from the code.
Q21 | Test cases are created in which phase?
- test specification
- test planning
- test requirement
- test configuration
Q22 | 7n test cases are generated in which case of Boundary Value Analysis?
- worst case
- roust worst case
- critical fault assumption
- none
Q23 | Which testing cannot be performed on first build of the software?
- regression testing
- retesting
- a,b
- none
Q24 | Which testing is performed with Planning and Documentation?
- ad-hoc testing
- monkey testing
- fuzz testing
- end-to-end testing
Q25 | GUI means
- graphical user interface
- graphical user interaction
- graphics uniform interaction
- none