The document defines key terms related to software testing:
- Acceptance testing is formal testing conducted by users to determine if a system meets requirements.
- Integration testing checks for defects at interfaces between integrated components or systems.
- Requirements specify functions a component must perform or conditions needed to solve problems.
- Validation confirms requirements for an intended use have been fulfilled while verification confirms specified requirements have been met.
The document defines key terms related to software testing:
- Acceptance testing is formal testing conducted by users to determine if a system meets requirements.
- Integration testing checks for defects at interfaces between integrated components or systems.
- Requirements specify functions a component must perform or conditions needed to solve problems.
- Validation confirms requirements for an intended use have been fulfilled while verification confirms specified requirements have been met.
The document defines key terms related to software testing:
- Acceptance testing is formal testing conducted by users to determine if a system meets requirements.
- Integration testing checks for defects at interfaces between integrated components or systems.
- Requirements specify functions a component must perform or conditions needed to solve problems.
- Validation confirms requirements for an intended use have been fulfilled while verification confirms specified requirements have been met.
The document defines key terms related to software testing:
- Acceptance testing is formal testing conducted by users to determine if a system meets requirements.
- Integration testing checks for defects at interfaces between integrated components or systems.
- Requirements specify functions a component must perform or conditions needed to solve problems.
- Validation confirms requirements for an intended use have been fulfilled while verification confirms specified requirements have been met.
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1/ 8
Istqb F.l.
Glossary Chapter 2
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 ______ the system.
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-theshelf software as a form of internal acceptance testing.
Alpha testing
Operational testing by potential and/or
existing users/customers at an external site 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
The testing of individual software
c__________.
Component testing
A software component or test tool that
replaces a component that takes care of the control and/or the calling of a
Driver
component or system. A ___________ that specifies a function that a component or system must perform.
Functional requirement
A development life cycle where a
project is broken into a series of __________.
Incremental development model
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
A ___________ that does not relate
to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability.
Non-functional requirement
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 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
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 ro________
of the software product.
Robustness testing
A skeletal or special-purpose implementation of a software component, used to develop or test a component that calls or is otherwise dependent on it. It replaces a called component.
Stub
The process of testing an integrated
______ to verify that it meets specified requirements.
System 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
An ___________ containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.
Test environment
A group of test activities that are
organized and managed together.
Test level
Confirmation by examination and
through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.
Validation
Confirmation by examination and
through provision of objective evidence that specified requirements have been fulfilled.
Verification
A framework to describe the software
development life cycle activities from requirements specification to maintenance.
V-model
A group of test activities aimed at
testing a component or system focused on a specific test objective, i.e. functional test, usability test, regression test etc.
Test type
Testing based on an analysis of the
specification of the f____________ of a component or system.
Functional testing
Testing, either functional or nonfunctional, without reference to the
internal structure of the component or system.
Black-box testing
Procedure to derive and/or select test
cases based on an analysis of the specification, either functional or nonfunctional, of a component or system without reference to its internal structure.
Black-box test design technique
The capability of the software product
to provide functions which meet stated and implied needs when the software is used under specified conditions.
Functionality
The process of testing to determine
the f____________ of a software product.
Functionality testing
The capability of the software product
to interact with one or more specified components or systems.
Interoperability
The process of testing to determine
the i_______________ of a software product.
Interoperability testing
Attributes of software products that
bear on its ability to prevent unauthorized access, whether accidental or deliberate, to programs and data.
Security
Testing to determine the s_______ of
the software product.
Security testing
A type of performance testing
conducted to evaluate the behavior of a component or system with increasing ____, e.g. numbers of parallel users and/or numbers of transactions, to determine what ____ can be handled by the component or system.
Load testing
The degree to which a system or
component accomplishes its designated functions within given constraints regarding processing time and throughput rate.
Performance
The process of testing to determine
Performance testing
the pe_________ of a software
product. See also efficiency testing. Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements.
Stress testing
The process of testing to determine
the r__________ of a software product.
Reliability testing
The capability of the software to be
understood, learned, used and attractive to the user when used under specified conditions.
Usability
Testing to determine the extent to
which the software product is understood, easy to learn, easy to operate and attractive to the users under specified conditions.
Usability testing
The capability of the software product
to provide appropriate performance, relative to the amount of resources used under stated conditions.
Efficiency
The process of testing to determine
the e_________ of a software product.
Efficiency testing
The ease with which the software
product can be transferred from one hardware or software environment to another.
Portability
The process of testing to determine
Portability testing
the po_________ of a software
product. Testing based on an analysis of the internal structure of the component or system.
White-box testing (structural testing)
An analysis method that determines
which parts of the software have been executed, _______ by the test suite and which parts have not been executed.
Code coverage
Procedure to derive and/or select test
cases based on an analysis of the internal structure of a component or system.
White-box test design technique
Modification of a software product
after delivery to correct defects, to improve performance or other attributes, or to adapt the product to a modified environment.
Maintenance
Testing the changes to an operational
system or the impact of a changed environment to an operational system.
Maintenance testing
The ease with which a software
product can be modified to correct defects, modified to meet new requirements, modified to make future maintenance easier, or adapted to a changed environment.
Maintainability
The process of testing to determine
the m______________ of a software
Maintainability testing
product. The assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements.
