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. item transmittal report
  2. test level
  3. reliability growth model
  4. cause-effect analysis
  5. key performance indicator
  1. a A group of test activities that are organized and managed together. A test level is linked to the responsibilities in a project. Examples of test levels are component test, integration test, system test and acceptance test. [After TMap]
  2. b See cause-effect graphing. A black box test design technique in which test cases are designed from cause-effect graphs. [BS 7925/2]
  3. c See performance indicator. A high level metric of effectiveness and/or efficiency used to guide and control progressive development, e.g. lead-time slip for software development. [CMMI]
  4. d A model that shows the growth in reliability over time during continuous testing of a component or system as a result of the removal of defects that result in reliability failures.
  5. e See release note. A document identifying test items, their configuration, current status and other delivery information delivered by development to testing, and possibly other stakeholders, at the start of a test execution phase. [After IEEE 829]

5 Multiple choice questions

  1. The component or system to be tested. See also test item. The individual element to be tested. There usually is one test object and many test items. See also test object. A reason or purpose for designing and executing a test.
  2. See defect density. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms, e.g. lines-of-code, number of classes or function points).
  3. The capability of the software product to enable the user to operate and control it. [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 description of a component's function in terms of its output values for specified input values under specified conditions, and required non-functional behavior (e.g. resource utilization).
  5. Deviation of the component or system from its expected delivery, service or result. [After Fenton]

5 True/False questions

  1. outcomeAcronym for Computer Aided Software Testing. See also test automation.The use of software to perform or support test activities, e.g. test management, test design, test execution and results checking.

          

  2. Software Failure Mode Effect, and Criticality Analysis (SFMECA)A black box test design technique in which test cases are designed based on boundary values. See also boundary value. An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either side of an edge, for example the minimum or maximum value of a range.

          

  3. capture/replay toolA tool that supports operational security.

          

  4. migration testingA black box test design technique where test cases are selected, possibly using a pseudo-random generation algorithm, to match an operational profile. This technique can be used for testing non-functional attributes such as reliability and performance.

          

  5. branch condition coverageThe percentage of combinations of all single condition outcomes within one statement that have been exercised by a test suite. 100% multiple condition coverage implies 100% condition determination coverage.