Copy and Edit

ISTQB Fundamentals - Glossary Part III

Description

ISTQB Fundamentals
yacki Dubon
Quiz by yacki Dubon, updated more than 1 year ago
yacki Dubon
Created by yacki Dubon over 3 years ago
12
0
0

Resource summary

Question 1

Question
independence of testing
Answer
  • Separation of responsibilities, which encourages the accomplishment of objective testing
  • A measure that can be used to estimate or predict another measure
  • A review not based on a formal (documented) procedure.

Question 2

Question
indicator
Answer
  • A review not based on a formal (documented) procedure
  • A measure that can be used to estimate or predict another measure
  • Separation of responsibilities, which encourages the accomplishment of objective testing

Question 3

Question
informal review
Answer
  • A review not based on a formal (documented) procedure.
  • Separation of responsibilities, which encourages the accomplishment of objective testing.
  • An instance of an input

Question 4

Question
input
Answer
  • A review not based on a formal (documented) procedure.
  • A variable (whether stored within a component or outside) that is read by a component
  • An instance of an input

Question 5

Question
inspection
Answer
  • The process of combining components or systems into larger assemblies
  • A 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.
  • An integration test type that is concerned with testing the interfaces between components or systems

Question 6

Question
installation guide
Answer
  • Supplied 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.
  • The capability of the software product to interact with one or more specified components or systems.
  • An integration test type that is concerned with testing the interfaces between components or systems

Question 7

Question
integration
Answer
  • The process of combining components or systems into larger assemblies.
  • Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems
  • An integration test type that is concerned with testing the interfaces between components or systems.

Question 8

Question
integration testing
Answer
  • An integration test type that is concerned with testing the interfaces between components or systems.
  • Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems

Question 9

Question
Interface testing
Answer
  • The process of combining components or systems into larger assemblies.
  • An integration test type that is concerned with testing the interfaces between components or systems
  • The capability of the software product to interact with one or more specified components or systems

Question 10

Question
Interoperability
Answer
  • Testing using input values that should be rejected by the component or system
  • The capability of the software product to interact with one or more specified components or systems

Question 11

Question
Interoperability testing Synonyms: compatibility testing
Answer
  • Testing to determine the interoperability of a software product.
  • The capability of the software product to interact with one or more specified components or systems.

Question 12

Question
invalid testing See Also: error tolerance, negative testing
Answer
  • Testing using input values that should be rejected by the component or system
  • A test plan that typically addresses one test level.

Question 13

Question
Iterative development model
Answer
  • A 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.
  • A 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.
  • A test plan that typically addresses one test level.

Question 14

Question
keyword-driven testing Synonyms: action word-driven testing
Answer
  • A 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.
  • A 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.

Question 15

Question
level test plan
Answer
  • A document describing the scope, approach, resources and schedule of intended test activities.
  • A test plan that typically addresses one test level
  • A test plan that typically addresses multiple test levels.

Question 16

Question
load testing
Answer
  • A 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.
  • Testing to determine the performance of a software product

Question 17

Question
Maintainability
Answer
  • 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.
  • 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
  • Testing the changes to an operational system or the impact of a changed environment to an operational system

Question 18

Question
maintainability testing Synonyms: serviceability testing
Answer
  • 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.
  • Testing to determine the maintainability of a software product
  • Testing the changes to an operational system or the impact of a changed environment to an operational system

Question 19

Question
Maintenance
Answer
  • 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
  • Testing the changes to an operational system or the impact of a changed environment to an operational system.
  • Testing to determine the maintainability of a software product

Question 20

Question
Maintenance testing
Answer
  • Testing the changes to an operational system or the impact of a changed environment to an operational system.
  • 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.
  • Testing to determine the maintainability of a software product.

Question 21

Question
Master test plan
Answer
  • A test plan that typically addresses multiple test levels.
  • A 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

Question 22

Question
Maturity
Answer
  • The 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
  • A 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.
  • The number or category assigned to an attribute of an entity by making a measurement

Question 23

Question
Maturity model
Answer
  • The number or category assigned to an attribute of an entity by making a measurement.
  • A 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.
  • The process of assigning a number or category to an entity to describe an attribute of that entity.

Question 24

Question
Measure
Answer
  • The process of assigning a number or category to an entity to describe an attribute of that entity
  • The number or category assigned to an attribute of an entity by making a measurement

Question 25

Question
measurement
Answer
  • The number or category assigned to an attribute of an entity by making a measurement
  • The process of assigning a number or category to an entity to describe an attribute of that entity.
  • A point in time in a project at which defined (intermediate) deliverables and results should be ready.

Question 26

Question
memory leak
Answer
  • A 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.
  • The number or category assigned to an attribute of an entity by making a measurement

Question 27

Question
metric
Answer
  • A measurement scale and the method used for measurement.
  • The number or category assigned to an attribute of an entity by making a measurement
  • The process of assigning a number or category to an entity to describe an attribute of that entity.

Question 28

Question
Milestone
Answer
  • A point in time in a project at which defined (intermediate) deliverables and results should be ready
  • A tool that supports the creation, amendment and verification of models of the software or system
  • A measurement scale and the method used for measurement.

Question 29

Question
Modeling tool
Answer
  • A point in time in a project at which defined (intermediate) deliverables and results should be ready.
  • A tool that supports the creation, amendment and verification of models of the software or system.
  • A 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.

Question 30

Question
Moderator
Answer
  • The leader and main person responsible for an inspection or review process.(2) A neutral person who conducts a usability test session.
  • The 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.

Question 31

Question
Monitoring tool
Answer
  • A 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.
  • A requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability

Question 32

Question
multiple condition coverage Synonyms: branch condition combination coverage , condition combination coverage
Answer
  • The 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.
  • Testing the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.
  • A 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.

Question 33

Question
non-functional requirement
Answer
  • Testing the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.
  • A requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability.
  • A 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.

Question 34

Question
non-functional testing
Answer
  • Testing the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.
  • A requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability.
  • Operational 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.

Question 35

Question
Open source tool
Answer
  • The 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.
  • A 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.

Question 36

Question
operational acceptance testing Synonyms: production acceptance testing
Answer
  • The 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.
  • Operational 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
  • Testing conducted to evaluate a component or system in its operational environment.

Question 37

Question
operational profile
Answer
  • The 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.
  • A variable (whether stored within a component or outside) that is written by a component.
  • Testing conducted to evaluate a component or system in its operational environment.

Question 38

Question
output
Answer
  • A variable (whether stored within a component or outside) that is written by a component.
  • A variable (whether stored within a component or outside) that is read by a component.

Question 39

Question
pair programming
Answer
  • A test is deemed to pass if its actual result matches its expected result.
  • A 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.

Question 40

Question
pass
Answer
  • A test is deemed to fail if its actual result does not match its expected result.
  • A test is deemed to pass if its actual result matches its expected result.

Question 41

Question
Path Synonyms: control flow path
Answer
  • The task of analyzing, e.g., identifying performance bottlenecks based on generated metrics, and tuning the performance of a software component or system using tools
  • A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.
Show full summary Hide full summary

Want to create your own Quizzes for free with GoConqr? Learn more.

Similar

Diapositivas de Topología de Redes
lisi_98
Fase 5. Evaluar. Sustentar el diseño de modelo de propagación. MAPA DE RFID
Miller Suárez López
TEORIA DESCRIPCION DE LA FORMA
Stiven Ramirez
Construcción de software
CRHISTIAN SUAREZ
FUNCIONES MULTIVARIABLES
Jarumy cecilia Sánchez Hernández
Proceso de Simulación
Jesus Javier
Dibujo de ingeniería
Felipe Granada
Competencias Laborales de un Ingeniero en Diseño de Entretenimiento Digital
Daniel Giraldo
Modelos de Gestión de Inventarios en Cadenas de Abastecimiento
Rubén Darío Martínez Lira
Ingenieria Social
Diego Gutierrez
PROYECTOS DE INVERSIÓN
Pedro Martinez
Browse Library