click below
click below
Normal Size Small Size show me how
ISTQB F.L 2.1 - 2.2
ISTQB Foundation Level Glossary
Question | Answer |
---|---|
Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled. | Verification |
Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled. | Validation |
A framework to describe the software development life cycle activities from requirements specification to maintenance. | V-model |
A group of test activities that are organized and managed together. | Test level |
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. | Off-the-shelf software |
A development life cycle where a project is broken into a series of __________. | Incremental development model |
The testing of individual software ___________. | Component testing |
A skeletal or special-purpose implementation of a software component, used to developor test a component that calls or is otherwise dependent on it. It replaces a called component. | Stub |
A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system. | Driver |
The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions. | Robustness |
Testing to determine the __________ of the software product. | Robustness testing |
The process of combining components or systems into larger assemblies. | Integration |
Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. | Integration testing |
The process of testing an integrated ______ to verify that it meets specified requirements. | System testing |
A condition or capability needed by a user to solve a problem or achieve an objective that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document. | Requirement |
A requirement that specifies a function that a component or system must perform. | Functional requirement |
A requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability. | Non-functional requirement |
An ___________ containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test. | Test environment |
Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the __________ criteria and to enable the user, customers or other authorized entity to determine whether or not to _ | Acceptance testing |
Simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site, but outside the development organization. _____ _______ is often employed for off-the-shelf software as a form of internal acceptanc | Alpha testing |
Operational testing by potential and/or existing users/customers at an externalsite not otherwise involved with the developers, to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes. | Beta testing |
A way of developing software where the test cases are developed, and often automated, before the software is developed to run those test cases. | Test driven development |