Question types

Start with

Question limit

of 667 available terms

Advertisement Upgrade to remove ads
Print test

5 Written questions

5 Matching questions

  1. time behavior
  2. CASE
  3. test report
  4. post-execution comparison
  5. cause-effect analysis
  1. 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]
  2. 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]
  3. c Acronym for Computer Aided Software Engineering.
  4. d Comparison of actual and expected results, performed after the software has finished running.
  5. 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

  1. 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.
  2. The process of identifying risks using techniques such as brainstorming, checklists and failure history.
  3. 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]
  4. 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.
  5. 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

  1. test execution toolA type of test tool that is able to execute other software using an automated test script, e.g. capture/playback. [Fewster and Graham]


  2. informal reviewA review not based on a formal (documented) procedure.


  3. efficiency testingThe process of testing to determine the efficiency of a software product.


  4. impact analysisThe assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements.


  5. status accountingSee white box testing.Testing based on an analysis of the internal structure of the component or system.