5 Written questions
5 Matching questions
- orthogonal array
- logic-driven testing
- a A device or storage area used to store data temporarily for differences in rates of data flow, time or occurrence of events, or amounts of data that can be handeld by the devices or processes involved in the transfer or use of the data. [IEEE 610]
- b A specification or software product that has been formally reviewed or agreed upon, that thereafter serves as the basis for further development, and that can be changed only through a formal change control process. [After IEEE 610]
- c A 2-dimensional array constructed with special mathematical properties, such that choosing any two columns in the array provides every pair combination of each number in the array.
- d The process of finding, analyzing and removing the causes of failures in software.
- e See white box testing. Testing based on an analysis of the internal structure of the component or system.
5 Multiple choice questions
- See false-pass result. A test result which fails to identify the presence of a defect that is actually present in the test object.
- The process of combining components or systems into larger assemblies.
- The testing activities that must be repeated when testing is re-started after a suspension. [After IEEE 829]
- A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria. [After IEEE 829]
- See interoperability testing. The process of testing to determine the interoperability of a software product.
5 True/False questions
capture/playback tool → A type of test execution tool where inputs are recorded during manual testing in order to generate automated test scripts that can be executed later (i.e. replayed). These tools are often used to support automated regression testing.
standard software → A statement of test objectives, and possibly test ideas about how to test. Test charters are used in exploratory testing. See also exploratory testing. An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests. [After Bach]
infeasible path → The ratio of the number of failures of a given category to a given unit of measure, e.g. failures per unit of time, failures per number of transactions, failures per number of computer runs. [IEEE 610]
frozen test basis → See test environment. An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test. [After IEEE 610]
test stage → (1) See test design specification. (2) The process of transforming general testing objectives into tangible test conditions and test cases.