5 Written questions
5 Matching questions
- time behavior
- test report
- post-execution comparison
- cause-effect analysis
- a See performance. The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate. [After IEEE 610]
- b See test summary report. A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria. [After IEEE 829]
- c Acronym for Computer Aided Software Engineering.
- d Comparison of actual and expected results, performed after the software has finished running.
- e See cause-effect graphing. A black box test design technique in which test cases are designed from cause-effect graphs. [BS 7925/2]
5 Multiple choice questions
- The percentage of decision outcomes that have been exercised by a test suite. 100% decision coverage implies both 100% branch coverage and 100% statement coverage.
- The process of identifying risks using techniques such as brainstorming, checklists and failure history.
- The number of independent paths through a program. Cyclomatic complexity is defined as: L - N + 2P, where - L = the number of edges/links in a graph - N = the number of nodes in a graph - P = the number of disconnected parts of the graph (e.g. a called graph and a subroutine) [After McCabe]
- A meeting at the end of a project during which the project team members evaluate the project and learn lessons that can be applied to the next project.
- Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled. [ISO 9000]
5 True/False questions
test execution tool → A type of test tool that is able to execute other software using an automated test script, e.g. capture/playback. [Fewster and Graham]
informal review → A review not based on a formal (documented) procedure.
efficiency testing → The process of testing to determine the efficiency of a software product.
impact analysis → The assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements.
status accounting → See white box testing.Testing based on an analysis of the internal structure of the component or system.