Question types

Start with

Question limit

of 667 available terms

Advertisement Upgrade to remove ads
Print test

5 Written questions

5 Matching questions

  1. hazard analysis
  2. performance testing tool
  3. fault
  4. N-switch coverage
  5. re-testing
  1. a The percentage of sequences of N+1 transitions that have been exercised by a test suite. [Chow]
  2. b Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.
  3. c A technique used to characterize the elements of risk. The result of a hazard analysis will drive the methods used for development and testing of a system. See also risk analysis. The process of assessing identified risks to estimate their impact and probability of occurrence (likelihood).
  4. d See defect. A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g. an incorrect statement or data definition. A defect, if encountered during execution, may cause a failure of the component or system.
  5. e A tool to support performance testing and that usually has two main facilities: load generation and test transaction measurement. Load generation can simulate either multiple users or high volumes of input data. During execution, response time measurements are taken from selected transactions and these are logged. Performance testing tools normally provide reports based on test logs and graphs of load against response times.

5 Multiple choice questions

  1. 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.
  2. The capability of the software product to avoid unexpected effects from modifications in the software. [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. An element of storage in a computer that is accessible by a software program by referring to it by a name.
  4. A systematic evaluation of software acquisition, supply, development, operation, or maintenance process, performed by or on behalf of management that monitors progress, determines the status of plans and schedules, confirms requirements and their system allocation, or evaluates the effectiveness of management approaches to achieve fitness for purpose. [After IEEE 610, IEEE 1028]
  5. A skilled professional who is involved in the testing of a component or system.

5 True/False questions

  1. Software Fault Tree Analysis (SFTA)A form of static analysis based on the definition and usage of variables.


  2. horizontal traceabilityThe tracing of requirements for a test level through the layers of test documentation (e.g. test plan, test design specification, test case specification and test procedure specification or test script).


  3. configuration testingTesting performed to expose defects in the interfaces and in the interactions between integrated components or systems. See also component integration testing, system integration testing. Testing performed to expose defects in the interfaces and interaction between integrated components.


  4. design-based testingAn approach to testing in which test cases are designed based on the architecture and/or detailed design of a component or system (e.g. tests of interfaces between components or systems).


  5. predicted outcomeSee expected result. The behavior predicted by the specification, or another source, of the component or system under specified conditions.