NAME

Question types


Start with


Question limit

of 667 available terms

Advertisement Upgrade to remove ads
Print test

5 Written questions

5 Matching questions

  1. test progress report
  2. defect based test design technique
  3. robustness
  4. R
  5. specification
  1. a The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions. [IEEE 610] See also error-tolerance, fault-tolerance. The ability of a system or component to continue normal operation despite the presence of erroneous inputs. [After IEEE 610].
  2. b A document summarizing testing activities and results, produced at regular intervals, to report progress of testing activities against a baseline (such as the original test plan) and to communicate risks and alternatives requiring a decision to management.
  3. c ...
  4. d A procedure to derive and/or select test cases targeted at one or more defect categories, with tests being developed from what is known about the specific defect category. See also defect taxonomy. A system of (hierarchical) categories designed to be a useful aid for reproducibly classifying defects.
  5. e A document that specifies, ideally in a complete, precise and verifiable manner, the requirements, design, behavior, or other characteristics of a component or system, and, often, the procedures for determining whether these provisions have been satisfied. [After IEEE 610]

5 Multiple choice questions

  1. See conversion testing. Testing of software used to convert data from existing systems for use in replacement systems.
  2. The set of generic and specific conditions for permitting a process to go forward with a defined task, e.g. test phase. The purpose of entry criteria is to prevent a task from starting which would entail more (wasted) effort compared to the effort needed to remove the failed entry criteria. [Gilb and Graham]
  3. The capability of the software product to enable the user to understand whether the software is suitable, and how it can be used for particular tasks and conditions of use. [ISO 9126] See also usability. The capability of the software to be understood, learned, used and attractive to the user when used under specified conditions. [ISO 9126]
  4. A high level document describing the principles, approach and major objectives of the organization regarding testing.
  5. The use of software, e.g. capture/playback tools, to control the execution of tests, the comparison of actual results to expected results, the setting up of test preconditions, and other test control and reporting functions.

5 True/False questions

  1. cause-effect graphA graphical representation of inputs and/or stimuli (causes) with their associated outputs (effects), which can be used to design test cases.

          

  2. test loggingSee fault seeding. [Abbott] The process of intentionally adding known defects to those already in the component or system for the purpose of monitoring the rate of detection and removal, and estimating the number of remaining defects. [IEEE 610]

          

  3. static code analysisAnalysis of source code carried out without execution of that software.

          

  4. performance indicatorA high level metric of effectiveness and/or efficiency used to guide and control progressive development, e.g. lead-time slip for software development. [CMMI]

          

  5. instrumentationSee test procedure specification. A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test script. [After IEEE 829]

          

Create Set