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. fault seeding
  2. status accounting
  3. confirmation testing
  4. changeability
  5. Test Point Analysis (TPA)
  1. a See re-testing. Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.
  2. b The capability of the software product to enable specified modifications to be implemented. [ISO 9126] See also maintainability. The ease with which a software product can be modified to correct defects, modified to meet new requirements, modified to make future maintenance easier, or adapted to a changed environment. [ISO 9126]
  3. c A formula based test estimation method based on function point analysis. [TMap]
  4. d An element of configuration management, consisting of the recording and reporting of information needed to manage a configuration effectively. This information includes a listing of the approved configuration identification, the status of proposed changes to the configuration, and the implementation status of the approved changes. [IEEE 610]
  5. e 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]

5 Multiple choice questions

  1. The representation of selected behavioral characteristics of one physical or abstract system by another system. [ISO 2382/1]
  2. A form of state transition testing in which test cases are designed to execute all valid sequences of N+1 transitions. [Chow] See also state transition testing. A black box test design technique in which test cases are designed to execute valid and invalid state transitions.
  3. 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]
  4. The calculated approximation of a result (e.g. effort spent, completion date, costs involved, number of test cases, etc.) which is usable even if input data may be incomplete, uncertain, or noisy.
  5. See defect report. A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function. [After IEEE 829]

5 True/False questions

  1. error seedingSee fault seeding.error seeding tool: See fault seeding tool. 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]

          

  2. black-box test design techniqueSee experienced-based test design technique. Procedure to derive and/or select test cases based on the tester's experience, knowledge and intuition.

          

  3. storage testingSee resource utilization testing. The process of testing to determine the resource-utilization of a software product. See also efficiency testing. The process of testing to determine the efficiency of a software product.

          

  4. test data preparation toolA type of test tool that enables data to be selected from existing databases or created, generated, manipulated and edited for use in testing.

          

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