5 Written questions
5 Matching questions
- configuration testing
- structured walkthrough
- test plan
- condition combination testing
- test execution phase
- a See portability testing. The process of testing to determine the portability of a software product.
- b A document describing the scope, approach, resources and schedule of intended test activities. It identifies amongst others test items, the features to be tested, the testing tasks, who will do each task, degree of tester independence, the test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process. [After IEEE 829]
- c See multiple condition testing. A white box test design technique in which test cases are designed to execute combinations of single condition outcomes (within one statement).
- d The period of time in a software development life cycle during which the components of a software product are executed, and the software product is evaluated to determine whether or not requirements have been satisfied. [IEEE 610]
- e See walkthrough. 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]
5 Multiple choice questions
- A feature or characteristic that affects an item's quality. [IEEE 610]
- An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test. [After IEEE 610]
- See interoperability testing. The process of testing to determine the interoperability of a software product.
- Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions.
- A white box test design technique in which test cases are designed to execute LCSAJs.
5 True/False questions
exception handling → 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.
equivalence partition → A portion of an input or output domain for which the behavior of a component or system is assumed to be the same, based on the specification.
software life cycle → A grid showing the resulting transitions for each state combined with each possible event, showing both valid and invalid transitions.
functional requirement → A requirement that specifies a function that a component or system must perform. [IEEE 610]
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. See also incident management tool. A tool that facilitates the recording and status tracking of incidents. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of incidents and provide reporting facilities.