5 Written Questions
5 Matching Questions
- root cause analysis
- test process
- stress testing
- scripting language
- a ...
- b A programming language in which executable test scripts are written, used by a test execution tool (e.g. a capture/playback tool).
- c 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.
- d The fundamental test process comprises test planning and control, test analysis and design, test implementation and execution, evaluating exit criteria and reporting, and test closure activities.
- e An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes, it is hoped that the likelihood of defect recurrence will be minimized.
5 Multiple Choice Questions
- See maintainability testing. The process of testing to determine the maintainability of a software product.
- 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]
- A chronological record of relevant details about the execution of tests. [IEEE 829]
- See defect management tool. A tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of defects and provide reporting facilities.
- A test design technique in which a model of the statistical distribution of the input is used to construct representative test cases. See also operational profile testing. Statistical testing using a model of system operations (short duration tasks) and their probability of typical use. [Musa]
5 True/False Questions
maturity → Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data. [ISO 9126] See also functionality. The capability of the software product to provide functions which meet stated and implied needs when the software is used under specified conditions. [ISO 9126]
system of systems → Multiple heterogeneous, distributed systems that are embedded in networks at multiple levels and in multiple domains interconnected addressing large-scale inter-disciplinary common problems and purposes.
installation wizard → Supplied software on any suitable media, which leads the installer through the installation process. It normally runs the installation process, provides feedback on installation results, and prompts for options.
branch condition coverage → See condition coverage.The percentage of condition outcomes that have been exercised by a test suite. 100% condition coverage requires each single condition in every decision statement to be tested as True and False.
incremental testing → A black box test design technique in which test cases are designed based upon the definition of the input domain and/or output domain.