Chapter 2 Testing throughout the software development life cycle Flashcards
Sequential development modeld
A type of devlopment life cycle model in which a complete system is developed in a linear way of several discrete and successive phases with no overlap between them.
Test level (test stage)
A specific instantiation of a test process.
Commercial off-the-shelf (COTS)
A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered mto man customers in identical format.
Test objective
A reason or purpose for designing and executing a test.
Test basis
The body of knowledge used as the basis for test analysis and design.
Test object
The component or system to be tested.
Test environment (test bed, test rig)
An environment containing hardware, instrumentation, simulators, software tools and other support elements needed to conduct a test.
Component testing (module testing, unit testing)
The testing of individual harware or software components.
Integration testing
Testing performed to expose defectgs in the interfaces and in the interactions bewteen integrated components or systems.
Component integration testing (link testing)
Tsting performed to expose defects in the interfaces and interactions between integrated components.
System integration testing
Testing the combination and interaction of systems.
System testing
Testing an integrated system to verify that it meets specified requirements.
Acceptance testing
Formal testing with respect ot user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to dtermine whether or not to accept the system.
User acceptance testing
Acceptance testing conducted in a real or simulated operational environement by intended users focusing on their needs, requirements and business processes.
Operation acceptance testing (production acceptance testing)
Operational testing int the acceptance test phase, typically performed in a operation environement by and/or systems administration staff focusing on operational aspects, for example recoverability, resource-behavviour, installability and technical compliance.
Contractual acceptance testing
Acceptance testing conducted to verify whether a system satisfies its contractual requirements.
Regulatory acceptance testing
Acceptance testing conducted to verify whether a system conforms to relevant laws, policies and regulations.
Alpha testing
Simulated or actual operationl teting conducted in the developer’s test envrironment, by roles outside the development organisation.
Beta testing (field testing)
Simulated or actula operational testing conducted at an external site, by roles outside the development organisation.
Test type
A group of test acivities based on specific test objectives aimed at specific characteristics of a component or system.
Functional testing
Testing conducted to evaluate the compliane of a component or system with functional requirements.
Non-functional testing
Testing conducted to evaluate the compliance of a component or system with the non-functional requirements.
White box testing
Testing based on an analysis of the internal structure-based of the component or system.
Conformation testing
Dynamic testing conducted after fixing defects with the objective to confirm that failures caused by those defects do not occur anymore.
Regression testing
Testing of a previously tested component or system following modification to ensure that defects have not been introduced or have been uncovered in unchanged areas of the software as a result of the changes made.
Maintenance testing
Testing the changes to an operational system or the impact of a changed environment to an operational system.
Impact analysis
The identification of all work products afected by a change, including an estimate of the resources needed to accomplish the change.