Test
ISTQB Fundamentals - Glossary Part III
Preguntas del test (41)
1independence of testing
- ASeparation of responsibilities, which encourages the accomplishment of objective testing
- BA measure that can be used to estimate or predict another measure
- CA review not based on a formal (documented) procedure.
2indicator
- AA review not based on a formal (documented) procedure
- BA measure that can be used to estimate or predict another measure
- CSeparation of responsibilities, which encourages the accomplishment of objective testing
3informal review
- AA review not based on a formal (documented) procedure.
- BSeparation of responsibilities, which encourages the accomplishment of objective testing.
- CAn instance of an input
4input
- AA review not based on a formal (documented) procedure.
- BA variable (whether stored within a component or outside) that is read by a component
- CAn instance of an input
5inspection
- AThe process of combining components or systems into larger assemblies
- BA type of peer review that relies on visual examination of documents to detect defects, e.g., violations of development standards and non-conformance to higher level
documentation. The most formal review technique and therefore always based on a documented procedure. - CAn integration test type that is concerned with testing the interfaces between components or systems
6installation guide
- ASupplied instructions on any suitable media, which guides the installer through the installation process. This may be a manual guide, step-by-step procedure, installation
wizard, or any other similar process description. - BThe capability of the software product to interact with one or more specified components or systems.
- CAn integration test type that is concerned with testing the interfaces between components or systems
- ASupplied instructions on any suitable media, which guides the installer through the installation process. This may be a manual guide, step-by-step procedure, installation
7integration
- AThe process of combining components or systems into larger assemblies.
- BTesting performed to expose defects in the interfaces and in the interactions between integrated components or systems
- CAn integration test type that is concerned with testing the interfaces between components or systems.
8integration testing
- AAn integration test type that is concerned with testing the interfaces between components or systems.
- BTesting performed to expose defects in the interfaces and in the interactions between integrated components or systems
9Interface testing
- AThe process of combining components or systems into larger assemblies.
- BAn integration test type that is concerned with testing the interfaces between components or systems
- CThe capability of the software product to interact with one or more specified components or systems
10Interoperability
- ATesting using input values that should be rejected by the component or system
- BThe capability of the software product to interact with one or more specified components or systems
11Interoperability testing
Synonyms: compatibility testing- ATesting to determine the interoperability of a software product.
- BThe capability of the software product to interact with one or more specified components or systems.
12invalid testing
See Also: error tolerance, negative testing- ATesting using input values that should be rejected by the component or system
- BA test plan that typically addresses one test level.
13Iterative development model
- AA type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e.g., numbers of parallel users and/or numbers of
transactions, to determine what load can be handled by the component or system. - BA development lifecycle where a project is broken into a usually large number of iterations. An iteration is a complete development loop resulting in a release (internal or
external) of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product. - CA test plan that typically addresses one test level.
- AA type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e.g., numbers of parallel users and/or numbers of
14keyword-driven testing
Synonyms: action word-driven testing- AA type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e.g., numbers of parallel users and/or numbers of
transactions, to determine what load can be handled by the component or system. - BA scripting technique that uses data files to contain not only test data and expected results, but also keywords related to the application being tested. The keywords are
interpreted by special supporting scripts that are called by the control script for the test.
- AA type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e.g., numbers of parallel users and/or numbers of
15level test plan
- AA document describing the scope, approach, resources and schedule of intended test activities.
- BA test plan that typically addresses one test level
- CA test plan that typically addresses multiple test levels.
16load testing
- AA type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e.g., numbers of parallel users and/or numbers of
transactions, to determine what load can be handled by the component or system. - BTesting to determine the performance of a software product
- AA type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e.g., numbers of parallel users and/or numbers of
17Maintainability
- AModification of a software product after delivery to correct defects, to improve performance or other attributes, or to adapt the product to a modified environment.
- BThe 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 - CTesting the changes to an operational system or the impact of a changed environment to an operational system
18maintainability testing
Synonyms: serviceability testing- AThe 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. - BTesting to determine the maintainability of a software product
- CTesting the changes to an operational system or the impact of a changed environment to an operational system
- AThe 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
19Maintenance
- AModification of a software product after delivery to correct defects, to improve performance or other attributes, or to adapt the product to a modified environment
- BTesting the changes to an operational system or the impact of a changed environment to an operational system.
- CTesting to determine the maintainability of a software product
20Maintenance testing
- ATesting the changes to an operational system or the impact of a changed environment to an operational system.
- BModification of a software product after delivery to correct defects, to improve performance or other attributes, or to adapt the product to a modified environment.
- CTesting to determine the maintainability of a software product.
21Master test plan
- AA test plan that typically addresses multiple test levels.
- BA 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
22Maturity
- AThe capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. (2) The capability of the software product to avoid
failure as a result of defects in the software - BA structured collection of elements that describe certain aspects of maturity in an organization, and aid in the definition and understanding of an organization's processes. A
maturity model often provides a common language, shared vision and framework for prioritizing improvement actions. - CThe number or category assigned to an attribute of an entity by making a measurement
- AThe capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. (2) The capability of the software product to avoid
23Maturity model
- AThe number or category assigned to an attribute of an entity by making a measurement.
- BA structured collection of elements that describe certain aspects of maturity in an organization, and aid in the definition and understanding of an organization's processes. A
maturity model often provides a common language, shared vision and framework for prioritizing improvement actions. - CThe process of assigning a number or category to an entity to describe an attribute of that entity.
24Measure
- AThe process of assigning a number or category to an entity to describe an attribute of that entity
- BThe number or category assigned to an attribute of an entity by making a measurement
25measurement
- AThe number or category assigned to an attribute of an entity by making a measurement
- BThe process of assigning a number or category to an entity to describe an attribute of that entity.
- CA point in time in a project at which defined (intermediate) deliverables and results should be ready.
26memory leak
- AA memory access failure due to a defect in a program's dynamic store allocation logic that causes it to fail to release memory after it has finished using it, eventually causing
the program and/or other concurrent processes to fail due to lack of memory. - BThe number or category assigned to an attribute of an entity by making a measurement
- AA memory access failure due to a defect in a program's dynamic store allocation logic that causes it to fail to release memory after it has finished using it, eventually causing
27metric
- AA measurement scale and the method used for measurement.
- BThe number or category assigned to an attribute of an entity by making a measurement
- CThe process of assigning a number or category to an entity to describe an attribute of that entity.
28Milestone
- AA point in time in a project at which defined (intermediate) deliverables and results should be ready
- BA tool that supports the creation, amendment and verification of models of the software or system
- CA measurement scale and the method used for measurement.
29Modeling tool
- AA point in time in a project at which defined (intermediate) deliverables and results should be ready.
- BA tool that supports the creation, amendment and verification of models of the software or system.
- CA software tool or hardware device that runs concurrently with the component or system under test and supervises, records and/or analyzes the behavior of the component or system.
30Moderator
- AThe leader and main person responsible for an inspection or review process.(2) A neutral person who conducts a usability test session.
- BThe percentage of combinations of all single condition outcomes within one statement that have been exercised by a test suite. 100% multiple condition coverage implies
100% modified condition / decision coverage.
31Monitoring tool
- AA software tool or hardware device that runs concurrently with the component or system under test and supervises, records and/or analyzes the behavior of the component or system.
- BA requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability
32multiple condition coverage
Synonyms: branch condition combination coverage , condition combination coverage- AThe percentage of combinations of all single condition outcomes within one statement that have been exercised by a test suite. 100% multiple condition coverage implies
100% modified condition / decision coverage. - BTesting the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.
- CA software tool that is available to all potential users in source code form, usually via the internet. Its users are permitted, usually under license, to study, change, improve and, at times, to distribute the software.
- AThe percentage of combinations of all single condition outcomes within one statement that have been exercised by a test suite. 100% multiple condition coverage implies
33non-functional requirement
- ATesting the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.
- BA requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability.
- CA software tool that is available to all potential users in source code form, usually via the internet. Its users are permitted, usually under license, to study, change, improve and,
at times, to distribute the software.
34non-functional testing
- ATesting the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.
- BA requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability.
- COperational testing in the acceptance test phase, typically performed in a (simulated) operational environment by operations and/or systems administration staff focusing on operational aspects, e.g., recoverability, resource-behavior, installability and technical compliance.
35Open source tool
- AThe representation of a distinct set of tasks performed by the component or system, possibly based on user behavior when interacting with the component or system, and their
probabilities of occurrence. A task is logical rather that physical and can be executed over several machines or be executed in non-contiguous time segments. - BA software tool that is available to all potential users in source code form, usually via the internet. Its users are permitted, usually under license, to study, change, improve and, at times, to distribute the software.
- AThe representation of a distinct set of tasks performed by the component or system, possibly based on user behavior when interacting with the component or system, and their
36operational acceptance testing
Synonyms: production acceptance testing- AThe representation of a distinct set of tasks performed by the component or system, possibly based on user behavior when interacting with the component or system, and their
probabilities of occurrence. A task is logical rather that physical and can be executed over several machines or be executed in non-contiguous time segments. - BOperational testing in the acceptance test phase, typically performed in a (simulated) operational environment by operations and/or systems administration staff focusing on operational aspects, e.g., recoverability, resource-behavior, installability and technical compliance
- CTesting conducted to evaluate a component or system in its operational environment.
- AThe representation of a distinct set of tasks performed by the component or system, possibly based on user behavior when interacting with the component or system, and their
37operational profile
- AThe representation of a distinct set of tasks performed by the component or system, possibly based on user behavior when interacting with the component or system, and their
probabilities of occurrence. A task is logical rather that physical and can be executed over several machines or be executed in non-contiguous time segments. - BA variable (whether stored within a component or outside) that is written by a component.
- CTesting conducted to evaluate a component or system in its operational environment.
- AThe representation of a distinct set of tasks performed by the component or system, possibly based on user behavior when interacting with the component or system, and their
38output
- AA variable (whether stored within a component or outside) that is written by a component.
- BA variable (whether stored within a component or outside) that is read by a component.
39pair programming
- AA test is deemed to pass if its actual result matches its expected result.
- BA software development approach whereby lines of code (production and/or test) of a component are written by two programmers sitting at a single computer. This implicitly
means ongoing real-time code reviews are performed.
40pass
- AA test is deemed to fail if its actual result does not match its expected result.
- BA test is deemed to pass if its actual result matches its expected result.
41Path
Synonyms: control flow path- AThe task of analyzing, e.g., identifying performance bottlenecks based on generated metrics, and tuning the performance of a software component or system using tools
- BA sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.
Información
- Descripción
- ISTQB Fundamentals
- Autor
- yacki Dubon
- Idioma
- English
- Visitas
- 29
- Etiquetas
- Valoración
- Aún sin valoraciones Valora este test