NAME

Question Types


Start With


Question Limit

of 667 available terms

Advertisement Upgrade to remove ads

5 Written Questions

5 Matching Questions

  1. blocked test case
  2. error tolerance
  3. re-testing
  4. interoperability testing
  5. data flow testing
  1. a A test case that cannot be executed because the preconditions for its execution are not fulfilled.
  2. b The process of testing to determine the interoperability of a software product. See also functionality testing. The process of testing to determine the functionality of a software product.
  3. c A white box test design technique in which test cases are designed to execute definition and use pairs of variables.
  4. d The ability of a system or component to continue normal operation despite the presence of erroneous inputs. [After IEEE 610].
  5. e Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.

5 Multiple Choice Questions

  1. 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).
  2. See 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.
  3. ...
  4. A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified work loads, or with reduced availability of resources such as access to memory or servers. [After IEEE 610] See also performance testing, load testing. The process of testing to determine the performance of a software product.
  5. A tool that supports the validation of models of the software or system [Graham].

5 True/False Questions

  1. LCSAJ testingA white box test design technique in which test cases are designed to execute LCSAJs.

          

  2. bugSee 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.

          

  3. input domainA type of peer review that relies on visual examination of documents to detect defects, e.g. violations of development standards and non-conformance to higher level documentation. The most formal review technique and therefore always based on a documented procedure. [After IEEE 610, 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.

          

  4. installation guideSupplied instructions on any suitable media, which guides the installer through the installation process. This may be a manual guide, step-by-step procedure, installation wizard, or any other similar process description.

          

  5. migration testingTesting 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].

          

Create Set