5 Written questions
5 Matching questions
- configuration management
- error guessing
- standard software
- operational environment
- a See test comparator.A test tool to perform automated test comparison of actual results with expected results.
- b A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made, and to design tests specifically to expose them.
- c Hardware and software products installed at users' or customers' sites where the component or system under test will be used. The software may include operating systems, database management systems, and other applications.
- d A discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item, control changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements. [IEEE 610]
- e See off-the-shelf software. A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to many customers in identical format.
5 Multiple choice questions
- The process of testing to determine the recoverability of a software product. See also reliability testing. The process of testing to determine the reliability of a software product.
- See white box testing. Testing based on an analysis of the internal structure of the component or system.
- A test management task that deals with the activities related to periodically checking the status of a test project. Reports are prepared that compare the actuals to that which was planned. See also test management. The planning, estimating, monitoring and control of test activities, typically carried out by a test manager.
- A program point at which the control flow has two or more alternative routes. A node with two or more links to separate branches.
- A form of state transition testing in which test cases are designed to execute all valid sequences of N+1 transitions. [Chow] See also state transition testing. A black box test design technique in which test cases are designed to execute valid and invalid state transitions.
5 True/False questions
configuration control board (CCB) → A group of people responsible for evaluating and approving or disapproving proposed changes to configuration items, and for ensuring implementation of approved changes. [IEEE 610]
finite state machine → Testing based on an analysis of the specification of the functionality of a component or system. See also black box testing. Testing, either functional or non-functional, without reference to the internal structure of the component or system. 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.
test estimation → See test procedure specification. A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test script. [After IEEE 829]
failure mode → A framework to describe the software development life cycle activities from requirements specification to maintenance. The V-model illustrates how testing activities can be integrated into each phase of the software development life cycle.
risk → ...