5 Written Questions
5 Matching Questions
- non-functional test design techniques
- problem report
- specification-based technique
- input domain
- exception handling
- a See black box test design technique. Procedure to derive and/or select test cases based on an analysis of the specification, either functional or non-functional, of a component or system without reference to its internal structure.
- b Procedure to derive and/or select test cases for nonfunctional testing based on an analysis of the specification of a component or system without reference to its internal structure. See also black box test design technique. Procedure to derive and/or select test cases based on an analysis of the specification, either functional or non-functional, of a component or system without reference to its internal structure.
- c The set from which valid input values can be selected. See also domain. The set from which valid input and/or output values can be selected.
- d See defect report. A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function. [After IEEE 829]
- e Behavior of a component or system in response to erroneous input, from either a human user or from another component or system, or to an internal failure.
5 Multiple Choice Questions
- See compliance testing. The process of testing to determine the compliance of the component or system.
- Procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system.
- Acronym for Computer Aided Software Testing. See also test automation.The use of software to perform or support test activities, e.g. test management, test design, test execution and results checking.
- A white box test design technique in which test cases are designed to execute decision outcomes.
- 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).
5 True/False Questions
path → A sequence of events, e.g. executable statements, of a component or system from an entry point to an exit point.
bottom-up testing → An incremental approach to integration testing where the lowest level components are tested first, and then used to facilitate the testing of higher level components. This process is repeated until the component at the top of the hierarchy is tested. See also integration testing. Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.
migration testing → See conversion testing. Testing of software used to convert data from existing systems for use in replacement systems.
debugging tool → A tool for seeding (i.e. intentionally inserting) faults in a component or system.
keyword driven testing → A scripting technique that uses data files to contain not only test data and expected results, but also keywords related to the application being tested. The keywords are interpreted by special supporting scripts that are called by the control script for the test. See also data driven testing. A scripting technique that stores test input and expected results in a table or spreadsheet, so that a single control script can execute all of the tests in the table. Data driven testing is often used to support the application of test execution tools such as capture/playback tools. [Fewster and Graham]