Question types

Start with

Question limit

of 667 available terms

Advertisement Upgrade to remove ads
Print test

5 Written questions

5 Matching questions

  1. configuration
  2. project
  3. false-pass result
  4. bebugging
  5. functional testing
  1. a A project is a unique set of coordinated and controlled activities with start and finish dates undertaken to achieve an objective conforming to specific requirements, including the constraints of time, cost and resources. [ISO 9000]
  2. b Testing based on an analysis of the specification of the functionality of a component or system. See also black box testing. Testing, either functional or non-functional, without reference to the internal structure of the component or system. Black-box test design technique Procedure to derive and/or select test cases based on an analysis of the specification, either functional or non-functional, of a component or system without reference to its internal structure.
  3. c A test result which fails to identify the presence of a defect that is actually present in the test object.
  4. d The composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.
  5. e See 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]

5 Multiple choice questions

  1. A portion of an input or output domain for which the behavior of a component or system is assumed to be the same, based on the specification.
  2. Tests aimed at showing that a component or system does not work. Negative testing is related to the testers' attitude rather than a specific test approach or test design technique, e.g. testing with invalid input values or exceptions. [After Beizer].
  3. A document reporting on any event that occurred, e.g. during the testing, which requires investigation. [After IEEE 829]
  4. A black box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle test cases are designed to cover each partition at least once.
  5. A high level document describing the principles, approach and major objectives of the organization regarding testing.

5 True/False questions

  1. risk identificationThe process of identifying risks using techniques such as brainstorming, checklists and failure history.


  2. FSee component. A minimal software item that can be tested in isolation.


  3. operational acceptance testingA white box test design technique in which test cases are designed to execute condition outcomes and decision outcomes.


  4. structural testingTesting to determine the security of the software product. See also functionality testing. The process of testing to determine the functionality of a software product.


  5. D...