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. bespoke software
  2. cause-effect decision table
  3. elementary comparison testing
  4. Software Fault Tree Analysis (SFTA)
  5. branch testing
  1. a See Fault Tree Analysis (FTA). A technique used to analyze the causes of faults (defects). The technique visually models how logical relationships between failures, human errors, and external events can combine to cause specific faults to disclose.
  2. b Software developed specifically for a set of users or customers. The opposite is off-the-shelf software.
  3. c See decision table. A table showing combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects), which can be used to design test cases.
  4. d A white box test design technique in which test cases are designed to execute branches.
  5. e A black box test design technique in which test cases are designed to execute combinations of inputs using the concept of condition determination coverage. [TMap]

5 Multiple choice questions

  1. A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. [Gilb and Graham, IEEE 1028] See also peer review. A review of a software work product by colleagues of the producer of the product for the purpose of identifying defects and improvements. Examples are inspection, technical review and walkthrough.
  2. See recoverability testing. The process of testing to determine the recoverability of a software product.
  3. Testing using input values that should be rejected by the component or system. See also error tolerance. The ability of a system or component to continue normal operation despite the presence of erroneous inputs. [After IEEE 610].
  4. A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process. [After IEEE 829]
  5. A type of test tool that enables data to be selected from existing databases or created, generated, manipulated and edited for use in testing.

5 True/False questions

  1. cyclomatic complexityThe capability of the software product to be upgraded to accommodate increased loads. [After Gerrard]

          

  2. test conditionSee coverage. The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test suite.

          

  3. structurebased testingSee white-box testing. Testing based on an analysis of the internal structure of the component or system.

          

  4. systemComputer instructions and data definitions expressed in a programming language or in a form output by an assembler, compiler or other translator. [IEEE 610]

          

  5. big-bang testingSee exhaustive testing.A test approach in which the test suite comprises all combinations of input values and preconditions.

          

Create Set