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. input value
  2. walkthrough
  3. intake test
  4. test result
  5. impact analysis
  1. a An instance of an input. See also input. A variable (whether stored within a component or outside) that is read by a component.
  2. b A step-by-step presentation by the author of a document in order to gather information and to establish a common understanding of its content. [Freedman and Weinberg, 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.
  3. c See result. The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and communication messages sent out.
  4. d The assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements.
  5. e A special instance of a smoke test to decide if the component or system is ready for detailed and further testing. An intake test is typically carried out at the start of the test execution phase. See also smoke test. A subset of all defined/planned test cases that cover the main functionality of a component or system, to ascertaining that the most crucial functions of a program work, but not bothering with finer details. A daily build and smoke test is among industry best practices.

5 Multiple choice questions

  1. See Failure Mode and Effect Analysis (FMEA). A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence. See also Failure Mode, Effect and Criticality Analysis (FMECA).
  2. Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a result of the changes made. It is performed when the software or its environment is changed.
  3. A risk related to management and control of the (test) project, e.g. lack of staffing, strict deadlines, changing requirements, etc. See also risk. A factor that could result in future negative consequences; usually expressed as impact and likelihood.
  4. 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.
  5. Two or more single conditions joined by means of a logical operator (AND, OR or XOR), e.g. 'A>B AND C>1000'.

5 True/False questions

  1. failureA test is deemed to fail if its actual result does not match its expected result.

          

  2. Software Fault Tree Analysis (SFTA)See quality attribute. A feature or characteristic that affects an item's quality. [IEEE 610]

          

  3. confidence testSee smoke test. A subset of all defined/planned test cases that cover the main functionality of a component or system, to ascertaining that the most crucial functions of a program work, but not bothering with finer details. A daily build and smoke test is among industry best practices.

          

  4. process improvementA program of activities designed to improve the performance and maturity of the organization's processes, and the result of such a program. [CMMI]

          

  5. debuggingA tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute programs step by step, to halt a program at any program statement and to set and examine program variables.

          

Create Set