Story Transcript
ISTQB
GLOSARIO ESTÁNDAR DE TÉRMINOS UTILIZADOS EN PRUEBAS SOFTWARE VERSIÓN EN ESPAÑOL
VERSIÓN: 2.4.ES V001 E001
08/04/2016
Control del documento Histórico de la versión ELABORACIÓN VERSIÓN
2.4.ES V001 E001
FECHA
RESPONSABLE
08/04/2016
Xavier Escudero y Gustavo Márquez Sosa
Tabla 1 – Histórico de la versión
Cambios respecto a la versión anterior VERSIÓN
PUNTO ÍNDICE
MODIFICACIÓN RESPECTO VERSIÓN ANTERIOR
Tabla 2 – Cambios respecto de la versión anterior
Referencias [REF 001] : ISTQB ‐ Glossary, Standard Glossary of Terms used in Software Testing, Version 2.4
Tabla 3 ‐ Referencias
TABLA DE CONTENIDO 1
INTRODUCCIÓN __________________________________________________________________ 2 1.1
OBJETIVO __________________________________________________________________ 2
1.2
ANTECEDENTES _____________________________________________________________ 2
1.3
ALCANCE __________________________________________________________________ 2
1.4
ABREVIATURAS _____________________________________________________________ 2
2
TRADUCCIÓN INGLÉS / ESPAÑOL (ORDENADA POR TÉRMINOS EN ESPAÑOL) ________________ 3
3
TRADUCCIÓN INGLÉS / ESPAÑOL (ORDENADA POR TÉRMINOS EN INGLÉS) _________________ 84
TABLAS Tabla 1 – Histórico de la versión ......................................................................................................... II Tabla 2 – Cambios respecto de la versión anterior .............................................................................. II Tabla 3 ‐ Referencias .......................................................................................................................... II Tabla 4 ‐ Abreviaturas ........................................................................................................................ 2 Tabla 5 – Traducción ordenada por los términos en español (“TÉRMINO TRADUCIDO”) ..................... 83 Tabla 6 – Traducción ordenada por los términos en inglés español (“TÉRMINO EN INGLÉS”) ............ 164
1
INTRODUCCIÓN
1.1
OBJETIVO
El objetivo de este documento es presentar la versión 2.4.ES V001 E001 del Glosario, traducido por el Grupo de Trabajo del Glosario del Spanish Software Testing Qualifications Board ‐ SSTQB. 1.2
ANTECEDENTES
Esta versión ha sido desarrollada por un equipo de trabajo más amplio del que figura en el “Histórico de la Versión”. En una próxima versión se identificarán a todas las personas que han colaborado con esta versión. 1.3
ALCANCE
El presente documento:
1.4
constituye un borrador de la traducción de la referencia [REF 001].
es un glosario desarrollado de forma específica para dar soporte a las traducciones del SSTQB. ABREVIATURAS
Las siguientes abreviaturas corresponden a términos clave (relevantes) de los programas de estudio. ABREVIATURA F
PROGRAMA DE ESTUDIOS (INGLÉS)
PROGRAMA DE ESTUDIOS (ESPAÑOL)
ISTQB Foundation syllabus
ISTQB Programa de Estudios ‐ Nivel Básico
F‐AT
ISTQB Foundation Extension Agile Tester syllabus
ISTQB Programa de Estudios – Extensión Básica – Probador Ágil
ATM
ISTQB Advanced – Test Management syllabus
ISTQB Programa de Estudios – Nivel Avanzado – Jefe de Prueba
ATA
ISTQB Advanced – Test Analyst syllabus
ISTQB Programa de Estudios – Nivel Avanzado – Analista de Pruebas
ATT
ISTQB Advanced – Technical Test Analyst syllabus
ISTQB Programa de Estudios – Nivel Avanzado – Analista de Pruebas Técnicas
EITP
ISTQB Expert – Improving the Testing Process syllabus
ISTQB Programa de Estudios – Nivel Experto – Proceso de Prueba
ETAE
ISTQB Expert –Test Automation ‐ Engineering syllabus
ISTQB Programa de Estudios – Automatización de Pruebas
ETM
ISTQB Expert – Test Management syllabus
ISTQB Programa de Estudios – Gestión de Pruebas
Tabla 4 ‐ Abreviaturas
2
TRADUCCIÓN INGLÉS / ESPAÑOL (ORDENADA POR TÉRMINOS EN ESPAÑOL)
La siguiente tabla está ordenada por orden alfabético de los términos en español. En la columna “TÉRMINO TRADUCIDO” encuentra la traducción para cada “TÉRMINO EN INGLÉS” correspondiente al “ISTQB ‐ Glossary, Standard Glossary of Terms used in Software Testing, Version 2.4 [REF 001]”. La columna “TRADUCCIÓN PREVIA” corresponde a traducciones anteriores de los mismos términos (si aplica, es decir si en término no es nuevo). En la columna “PROGRAMA DE ESTUDIOS” se identifican los programas de estudios para los que un término es palabra clave. En esta versión del glosario no se traduce la descripción del término, por lo que sólo se encuentra la “DESCRIPCIÓN EN INGLÉS”.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
A
1.
EITP
acción (IDEAL)
NO APLICA
acting (IDEAL)
2.
aceptación
aceptación
acceptance
3.
actor
NO APLICA
actor
4.
ATT
adaptabilidad
adaptabilidad
adaptability
5.
adecuación
adecuación
suitability
6.
almacenamiento
almacenamiento
storage
7.
Análisis de Punto de Prueba (APP)
Análisis de Punto de Prueba (APP)
Test Point Analysis (TPA)
8.
análisis causa‐efecto
análisis causa‐efecto
cause‐effect analysis
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
The phase within the IDEAL model where the improvements are developed, put into practice, and deployed across the organization. The acting phase consists of the activities: create solution, pilot/test solution, refine solution and implement solution. See also IDEAL.
NO APLICA.
See acceptance testing.
NO APLICA.
User or any other person or system that interacts with the system under test in a specific way.
NO APLICA.
The capability of the software product to be adapted for different specified environments without applying actions NO APLICA. or means other than those provided for this purpose for the software considered. [ISO 9126] See also portability. The capability of the software product to provide an appropriate set of functions for specified tasks and user NO APLICA. objectives. [ISO 9126] See also functionality. See resource utilization.
NO APLICA.
A formula based test estimation method based on function NO APLICA. point analysis. [TMap] See cause‐effect graphing.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
EITP
análisis causal
NO APLICA
causal analysis
The analysis of defects to determine their root cause. [CMMI]
10.
EITP
Análisis de Árbol de Faltas (AAF)
análisis de árbol de faltas
Fault Tree Analysis (FTA)
11.
análisis de cobertura
análisis de cobertura
coverage analysis
12.
ATA
análisis de dominio
NO APLICA
domain analysis
13.
F
análisis de impacto
análisis de impacto
impact analysis
14.
ATA
análisis de la causa raíz
NO APLICA
root cause analysis
15.
Análisis de Modos de Fallo y Efectos en el Software (AMFES)
NO APLICA
Software Failure Mode and Effect Analysis (SFMEA)
16.
EITP
Análisis de Modos de Fallo y sus Efectos (AMFE)
Análisis del Modo de Fallo y Efecto (AMFE)
Failure Mode and Effect Analysis (FMEA)
17.
Análisis de Modos de Fallo, Efectos y Criticidad en el Software (AMFECS)
NO APLICA
Software Failure Mode, Effects, and Criticality Analysis (SFMECA)
9.
A technique used to analyze the causes of faults (defects). The technique visually models how logical relationships between failures, human errors, and external events can combine to cause specific faults to disclose. Measurement of achieved coverage to a specified coverage item during test execution referring to predetermined criteria to determine whether additional testing is required and if so, which test cases are needed. A black box test design technique that is used to identify efficient and effective test cases when multiple variables can or should be tested together. It builds on and generalizes equivalence partitioning and boundary values analysis. See also boundary value analysis, equivalence partitioning. The assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements. An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes, it is hoped that the likelihood of defect recurrence will be minimized.
OBSERVACIONES
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
See Failure Mode and Effect Analysis (FMEA).
NO APLICA.
A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to NO APLICA. prevent their occurrence. See also Failure Mode, Effect and Criticality Analysis (FMECA). See Failure Mode, Effects, and Criticality Analysis (FMECA).
NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
Análisis de Modos de Fallo, sus Efectos y Criticidad (AMFEC)
NO APLICA
19.
análisis de mutación
análisis de mutación
20.
EITP
análisis de Pareto
NO APLICA
21.
análisis de peligros
NO APLICA
22.
análisis de prueba
NO APLICA
23.
Análisis de Puntos de Función (APF)
Análisis de Punto de Función (APF)
análisis de valores frontera
análisis de valores límite
boundary value analysis
Análisis del Árbol de Faltas Software (AAFS)
NO APLICA
Software Fault Tree Analysis (SFTA)
ATT
análisis del flujo de control
25.
26.
F ATA
NO APLICA
DESCRIPCIÓN EN INGLÉS
An extension of FMEA, as in addition to the basic FMEA, it includes a criticality analysis, which is used to chart the probability of failure modes against the severity of their Failure Mode, Effects, and consequences. The result highlights failure modes with Criticality Analysis relatively high probability and severity of consequences, (FMECA) allowing remedial effort to be directed where it will produce the greatest value. See also Failure Mode and Effect Analysis (FMEA). A method to determine test suite thoroughness by measuring mutation analysis the extent to which a test suite can discriminate the program from slight variants (mutants) of the program. A statistical technique in decision making that is used for selection of a limited number of factors that produce Pareto analysis significant overall effect. In terms of quality improvement, a large majority of problems (80%) are produced by a few key causes (20%). A technique used to characterize the elements of risk. The hazard analysis result of a hazard analysis will drive the methods used for development and testing of a system. See also risk analysis. The process of analyzing the test basis and defining test test analysis objectives. Method aiming to measure the size of the functionality of an information system. The measurement is independent of the Function Point Analysis technology. This measurement may be used as a basis for the (FPA) measurement of productivity, the estimation of the needed resources, and project control.
18.
24.
TÉRMINO TRADUCIDO
control flow analysis
OBSERVACIONES
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA. NO APLICA.
NO APLICA.
A black box test design technique in which test cases are designed based on boundary values. See also boundary value.
NO APLICA.
See Fault Tree Analysis (FTA).
Análisis del Árbol de Defectos Software (AADS)
A form of static analysis based on a representation of unique paths (sequences of events) in the execution through a component or system. Control flow analysis evaluates the NO APLICA. integrity of control flow structures, looking for possible control flow anomalies such as closed loops or logically
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
unreachable process steps. 27.
ATT
análisis del flujo de datos
análisis del flujo de datos
data flow analysis
análisis del riesgo
análisis de riesgos
risk analysis
análisis dinámico
análisis dinámico
dynamic analysis
análisis estático
análisis estático
static analysis
análisis estático de código
análisis estático de código
static code analysis:
ATM 28.
ATA ATT
29.
30.
31.
F ATT
NO APLICA.
The process of assessing identified project or product risks to determine their level of risk, typically by estimating their NO APLICA. impact and probability of occurrence (likelihood). The process of evaluating behavior, e.g. memory performance, CPU usage, of a system or component during NO APLICA. execution. [After IEEE 610] Analysis of software development artifacts, e.g. requirements or code, carried out without execution of these software NO APLICA. development artifacts. Static analysis is usually carried out by means of a supporting tool. Analysis of source code carried out without execution of that software.
NO APLICA.
The analysis of transactions between people and within people’s minds; a transaction is defined as a stimulus plus a response. Transactions take place between people and NO APLICA. between the ego states (personality segments) within one person’s mind.
32.
EITP
análisis transaccional
NO APLICA
transactional analysis
33.
analizador de código
analizador de código
code analyzer
See static code analyzer.
NO APLICA.
34.
ATT
analizador estático
analizador estático
static analyzer
A tool that carries out static analysis.
NO APLICA.
35.
analizador estático de código
analizador estático de código
static code analyzer
36.
analizador:
analizador
analyzer
See static analyzer.
NO APLICA.
anomaly
Any condition that deviates from expectation based on requirements specifications, design documents, user documents, standards, etc. or from someone’s perception or experience. Anomalies may be found during, but not
NO APLICA.
37.
ATT
A form of static analysis based on the definition and usage of variables.
ATM
anomalía
anomalía
A tool that carries out static code analysis. The tool checks source code, for certain properties such as conformance to NO APLICA. coding standards, quality metrics or data flow anomalies.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
38.
ATT
anti‐patrón:
NO APLICA
anti‐pattern:
39.
ETAE
anzuelo de prueba
NO APLICA
test hook
40.
aparejo de prueba
NO APLICA
test rig
41.
API
NO APLICA
API
42.
EITP
aprendizaje (IDEAL)
NO APLICA
learning (IDEAL)
43.
árbol de clasificación
NO APLICA
classification tree
44.
F
arnés de prueba
arnés de pruebas
test harness
DESCRIPCIÓN EN INGLÉS limited to, reviewing, testing, analysis, compilation, or use of software products or applicable documentation. [IEEE 1044] See also bug, defect, deviation, error, fault, failure, incident, problem. Repeated action, process, structure or reusable solution that initially appears to be beneficial and is commonly used but is ineffective and/or counterproductive in practice.
OBSERVACIONES
NO APLICA.
A customized software interface that enables automated testing of a test object.
NO APLICA.
See test environment.
NO APLICA.
Acronym for Application Programming Interface.
NO APLICA.
The phase within the IDEAL model where one learns from experiences and improves one’s ability to adopt new processes and technologies in the future. The learning phase NO APLICA. consists of the activities: analyze and validate, and propose future actions. See also IDEAL. A tree showing equivalence partitions hierarchically ordered, which is used to design test cases in the NO APLICA. classification tree method. See also classification tree method. A test environment comprised of stubs and drivers needed to execute a test.
NO APLICA.
45.
ETM
arquitecto de la prueba
NO APLICA
test architect
(1) A person who provides guidance and strategic direction for a test organization and for its relationship with other disciplines. NO APLICA. (2) A person who defines the way testing is structured for a given system, including topics such as test tools and test data management.
46.
ETAE
arquitectura de autimatización de la prueba
NO APLICA
test automation architecture
An instantiation of the generic test automation architecture to define the architecture of a test automation solution, i.e., NO APLICA. its layers, components, services and interfaces.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
47.
ETAE
arquitectura de automatizacion de prueba genérica
NO APLICA
48.
ATA
arreglo ortogonal
NO APLICA
orthogonal array
A 2‐dimensional array constructed with special mathematical properties, such that choosing any two columns in the array NO APLICA. provides every pair combination of each number in the array.
49.
aseguramiento de la calidad
aseguramiento de la calidad
quality assurance
Part of quality management focused on providing confidence NO APLICA. that quality requirements will be fulfilled. [ISO 9000]
asistente de instalación
asistente de instalación
installation wizard
51.
F
ataque
NO APLICA
attack
52.
F
ataque de falta
NO APLICA
fault attack:
53.
ataque de hombre interpuesto
NO APLICA
man in the middle attack
54.
ataque software
NO APLICA
software attack
55.
ATA
atractivo
atractivo
56.
atributo de calidad
atributo de calidad
ATM
auditoría
auditoría
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
Representation of the layers, components, and interfaces of G generic test automation a test automation architecture, allowing for a structured and NO APLICA. architecture modular approach to implement test automation.
50.
57.
TÉRMINO EN INGLÉS
Supplied software on any suitable media, which leads the installer through the installation process. It normally runs the NO APLICA. installation process, provides feedback on installation results, and prompts for options. Directed and focused attempt to evaluate the quality, especially reliability, of a test object by attempting to force NO APLICA. specific failures to occur. See also negative testing. See attack.
NO APLICA.
The interception, mimicking and/or altering and subsequent relaying of communications (e.g., credit card transactions) by NO APLICA. a third party such that a user remains unaware of that third party’s presence. See attack.
NO APLICA.
attractiveness
The capability of the software product to be attractive to the user. [ISO 9126] See also usability.
NO APLICA.
quality attribute
A feature or characteristic that affects an item’s quality. [IEEE 610]
NO APLICA.
audit
An independent evaluation of software products or processes to ascertain compliance to standards, guidelines, specifications, and/or procedures based on objective criteria, including documents that specify: (1) the form or content of the products to be produced (2) the process by which the products shall be
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
produced (3) how compliance to standards or guidelines shall be measured. [IEEE 1028] 58.
59.
60.
61.
auditoría de la configuración
auditoría de la configuración
automatización de la ejecución de la pruéba
automatización de pruebas
F‐AT
automatización de la prueba
automatización de pruebas
B
F‐AT ETAE
F F‐AT
configuration auditing
The use of software, e.g. capture/playback tools, to control the execution of tests, the comparison of actual results to test execution automation NO APLICA. expected results, the setting up of test preconditions, and other test control and reporting functions. The use of software to perform or support test activities, e.g. test automation test management, test design, test execution and results NO APLICA. checking.
base de prueba
base de prueba
test basis
62.
base de prueba congelada
base de prueba congelada
frozen test basis
63.
bebugging
bebugging
bebugging
bitácora de la prueba
registro de pruebas
test log
bitácora de la ejecución de prueba
registro de ejecución de pruebas
test run log
64.
65.
F ATM
The function to check on the contents of libraries of NO APLICA. configuration items, e.g. for standards compliance. [IEEE 610]
All documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be amended only by NO APLICA. way of formal amendment procedure, then the test basis is called a frozen test basis. [After TMap] A test basis document that can only be amended by a formal NO APLICA. change control process. See also baseline. [Abbott] See fault seeding.
NO APLICA.
A chronological record of relevant details about the execution of tests. [IEEE 829]
NO APLICA.
See test log.
NO APLICA.
A sequence of one or more consecutive executable statements containing no branches. 66.
bloque básico
bloque básico
basic block
Note: A node in a control flow graph represents a basic block.
NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS A superior method or innovative practice that contributes to the improved performance of an organization under given context, usually recognized as ‘best’ by other peer organizations.
NO APLICA.
See defect.
NO APLICA.
67.
buena práctica
mejor práctica
best practice
68.
F
bug
bug
bug
C
69.
F
calendario de ejecución de prueba
calendario de ejecución de pruebas
test execution schedule
70.
calendario de prueba
NO APLICA
test schedule
71.
F
calidad
calidad
quality
72.
EITP
calidad basada en el producto
NO APLICA
product‐based quality
73.
EITP
calidad basada en el usuario
NO APLICA
user‐based quality
74.
EITP
calidad basada en el valor
NO APLICA
value‐based quality
TÉRMINO TRADUCIDO
A scheme for the execution of test procedures. Note: The test procedures are included in the test execution schedule in their context and in the order in which they are to be executed. A list of activities, tasks or events of the test process, identifying their intended start and finish dates and/or times, and interdependencies. The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations. [After IEEE 610] A view of quality, wherein quality is based on a well‐defined set of quality attributes. These attributes must be measured in an objective and quantitative way. Differences in the quality of products of the same type can be traced back to the way the specific quality attributes have been implemented. [After Garvin] See also manufacturing‐based quality, quality attribute, transcendent‐based quality, user‐ based quality, value‐based quality. A view of quality, wherein quality is the capacity to satisfy needs, wants and desires of the user(s). A product or service that does not fulfill user needs is unlikely to find any users. This is a context dependent, contingent approach to quality since different business characteristics require different qualities of a product. [after Garvin] See also manufacturing‐ based quality, product‐based quality, transcendent‐based quality, value‐based quality. A view of quality, wherein quality is defined by price. A quality product or service is one that provides desired performance at an acceptable cost. Quality is determined by means of a decision process with stakeholders on trade‐offs between time, effort and cost aspects. [After Garvin] See also
OBSERVACIONES
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
75.
EITP
TÉRMINO TRADUCIDO
calidad basada en la manufactura
TRADUCCIÓN PREVIA
NO APLICA
TÉRMINO EN INGLÉS
manufacturing‐based quality
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
manufacturing‐based quality, product‐based quality, transcendent‐based quality, user‐based quality. A view of quality, whereby quality is measured by the degree to which a product or service conforms to its intended design and requirements. Quality arises from the process(es) used. [After Garvin] See also product‐based quality, transcendent‐ NO APLICA. based quality, userbased quality, value‐based quality.
76.
EITP
calidad basada en la transcendencia
NO APLICA
A view of quality, wherein quality cannot be precisely defined, but we know it when we see it, or are aware of its absence when it is missing. Quality depends on the perception and affective feelings of an individual or group of transcendent‐based quality individuals towards a product. [After NO APLICA. Garvin] See also manufacturing‐based quality, product‐based quality, user‐based quality, valuebased quality.
77.
calidad de los datos:
NO APLICA
data quality
78.
calidad del software
calidad del software
software quality
79.
cama de la prueba
cama de pruebas
test bed
80.
camino
camino
path
81.
camino del flujo de control
camino del flujo de control
control flow path
82.
camino inviable
camino inviable
infeasible path
83.
camino viable
camino viable
feasible path
An attribute of data that indicates correctness with respect to some pre‐defined criteria, e.g., business expectations, NO APLICA. requirements on data integrity, data consistency. The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied NO APLICA. needs. [After ISO 9126] See also quality. See test environment.
NO APLICA.
A sequence of events, e.g. executable statements, of a NO APLICA. component or system from an entry point to an exit point. See path.
NO APLICA.
A path that cannot be exercised by any set of possible input values.
NO APLICA.
A path for which a set of input values and preconditions NO APLICA. exists which causes it to be executed.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
84.
camino‐dd
NO APLICA
dd‐path
85.
ETAE
capa de adaptación de la prueba
NO APLICA
test adaption layer
86.
ETAE
capa de definición de la prueba
NO APLICA
test definition layer
87.
ETAE
capa de ejecución de la prueba
NO APLICA
test execution layer
The layer in a generic test automation architecture which NO APLICA. supports the execution of test suites and/or test cases.
88.
ETAE
capa de generación de la prueba
NO APLICA
test generation layer
The layer in a generic test automation architecture which supports manual or automated design of test suites and/or NO APLICA. test cases.
Capability Maturity Model Integration (CMMI)
Capability Maturity Model Integration (CMMI)
Capability Maturity Model Integration (CMMI)
89.
ATM EITP
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A path between two decisions of an algorithm, or two decision nodes of a corresponding graph, that includes no NO APLICA. other decisions. See also path. The layer in a generic test automation architecture which provides the necessary code to adapt the automated tests for NO APLICA. the various components, configuration or interfaces of the SUT. The layer in a generic test automation architecture which supports test implementation by supporting the definition of NO APLICA. test suites and/or test cases, e.g., by offering templates or guidelines.
A framework that describes the key elements of an EITP effective product development and maintenance process. The Capability Maturity Model Integration covers best‐ practices for planning, engineering and managing product development and maintenance. [CMMI]
NO APLICA.
The capability of the software product to re‐establish a specified level of performance and recover the data directly NO APLICA. affected in case of failure. [ISO 9126] See also reliability. The capability of the software product to be diagnosed for deficiencies or causes of failures in the software, or for the NO APLICA. parts to be modified to be identified. [ISO 9126] See also maintainability.
90.
capacidad de recuperación
recuperabilidad
recoverability
91.
ATT
capacidad de ser analizado
analizabilidad
analyzability
92.
ATA
capacidad de ser aprendido
aprendibilidad
learnability
The capability of the software product to enable the user to NO APLICA. learn its application. [ISO 9126] See also usability.
93.
ATA
capacidad de ser entendido
comprensibilidad
understandability
The capability of the software product to enable the user to understand whether the software is suitable, and how it can NO APLICA. be used for particular tasks and conditions of use. [ISO 9126] See also usability.
PROGRAMA DE ESTUDIOS
94.
ETAE
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
capacidad de ser probado
testabilidad
testability
The capability of the software product to enable modified NO APLICA. software to be tested. [ISO 9126] See also maintainability. The capability of the software product to be used in place of another specified software product for the same purpose in NO APLICA. the same environment. [ISO 9126] See also portability.
95.
ATT
capacidad de ser reemplazado
reemplazabilidad
replaceability
96.
ATT
capacidad para ser modificado
modificabilidad
changeability
97.
ETAE
captura/reproducción
NO APLICA
capture/playback
98.
característica de calidad
característica de calidad
quality characteristic
See quality attribute.
NO APLICA.
99.
característica de calidad del software
característica de calidad del software
software quality characteristic
See quality attribute.
NO APLICA.
100.
característica de producto software
característica de producto software
software product characteristic
See quality attribute.
NO APLICA.
101.
carta
NO APLICA
charter
See test charter.
NO APLICA.
102.
CASE
CASE
CASE
Acronym for Computer Aided Software Engineering.
NO APLICA.
103.
ATT
TÉRMINO TRADUCIDO
F ATM
caso de prueba
caso de prueba
test case
The capability of the software product to enable specified modifications to be implemented. [ISO 9126] See also maintainability. A test automation approach, where inputs to the test object are recorded during manual testing in order to generate automated test scripts that could be executed later (i.e. replayed).
NO APLICA.
NO APLICA.
A set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a NO APLICA. particular program path or to verify compliance with a specific requirement. [After IEEE 610]
104.
caso de prueba abstracto
caso de prueba abstracto
abstract test case
See high level test case.
NO APLICA.
105.
caso de prueba bloqueado
caso de prueba bloqueado
blocked test case
A test case that cannot be executed because the preconditions for its execution are not fulfilled.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
106.
ATA
caso de prueba concreto
caso de prueba concreto
concrete test case
107.
ATA
caso de prueba de alto nivel
caso de prueba de alto nivel
high level test case
108.
ATA
caso de prueba de bajo nivel
caso de prueba de bajo nivel
low level test case:
109.
ATA
caso de prueba lógico
caso de prueba lógico
logical test case:
110.
caso de uso
caso de uso
use case
111.
CAST
CAST
CAST
112.
categoría del defecto
NO APLICA
defect category
See defect type.
NO APLICA.
113.
categoría del riesgo
NO APLICA
risk category:
See risk type.
NO APLICA.
114.
ATM
causa raíz
causa raíz
root cause
115.
CCDM
NO APLICA
MCDC
116.
certificación
certificación
certification
117.
EITP
Ciclo de Deming
NO APLICA
Deming cycle
118.
ciclo de prueba
ciclo de pruebas
test cycle
DESCRIPCIÓN EN INGLÉS See low level test case.
OBSERVACIONES NO APLICA.
A test case without concrete (implementation level) values for input data and expected results. Logical operators are NO APLICA. used; instances of the actual values are not yet defined and/or available. See also low level test case. A test case with concrete (implementation level) values for input data and expected results. Logical operators from high level test cases are replaced by actual values that correspond NO APLICA. to the objectives of the logical operators. See also high level test case. See high level test case.
NO APLICA.
A sequence of transactions in a dialogue between an actor and a component or system with a tangible result, where an NO APLICA. actor can be a user or anything that can exchange information with the system. Acronym for Computer Aided Software Testing. See also test automation.
NO APLICA.
A source of a defect such that if it is removed, the occurrence NO APLICA. of the defect type is decreased or removed. [CMMI] See modified condition decision coverage.
NO APLICA.
The process of confirming that a component, system or person complies with its specified requirements, e.g. by NO APLICA. passing an exam. An iterative four‐step problem‐solving process, (plan‐do‐ check‐act), typically used in process improvement. [After NO APLICA. Deming] Execution of the test process against a single identifiable
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
release of the test object.
119.
EITP
ciclo de vida del software
NO APLICA
software lifecycle
120.
ATM
cierre de la prueba
cierre de pruebas
test closure
121.
clase de equivalencia
clase de equivalencia
equivalence class
122.
CLI
NO APLICA
CLI
CMMI
NO APLICA
CMMI
123.
F‐AT
ATM EITP
The period of time that begins when a software product is conceived and ends when the software is no longer available for use. The software lifecycle typically includes a concept phase, requirements phase, design phase, implementation NO APLICA. phase, test phase, installation and checkout phase, operation and maintenance phase, and sometimes, retirement phase. Note these phases may overlap or be performed iteratively. During the test closure phase of a test process data is collected from completed activities to consolidate experience, testware, facts and numbers. The test closure NO APLICA. phase consists of finalizing and archiving the testware and evaluating the test process, including preparation of a test evaluation report. See also test process. See equivalence partition.
NO APLICA.
Acronym for Command‐Line Interface.
NO APLICA.
See Capability Maturity Model Integration.
NO APLICA.
124.
ETAE
cobertura
cobertura
coverage
The degree, expressed as a percentage, to which a specified NO APLICA. coverage item has been exercised by a test suite.
125.
cobertura de caminos
cobertura de camino
path coverage
The percentage of paths that have been exercised by a test NO APLICA. suite. 100% path coverage implies 100% LCSAJ coverage.
126.
F
cobertura de código
cobertura de código
code coverage
127.
cobertura de combinaciones de condiciones
cobertura de condición combinada
128.
cobertura de combinaciones de
cobertura de condición combinada de rama
An analysis method that determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed, e.g. statement coverage, decision coverage or condition coverage.
NO APLICA.
condition combination coverage
See multiple condition coverage.
NO APLICA.
branch condition combination coverage
See multiple condition coverage.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
cobertura de condición múltiple modificada
modified multiple condition coverage
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
condiciones de rama
129.
cobertura de condición múltiple modificada
130.
cobertura de condiciones
cobertura de condición
condition coverage
131.
cobertura de condiciones de rama:
cobertura de condición de rama
branch condition coverage
132.
cobertura de condiciones múltiples
cobertura de condición múltiple
multiple condition coverage
133.
cobertura de condiciones‐ decisiones
cobertura de condición de decisión
decision condition coverage
134.
cobertura de conmutador de orden N
cobertura de conmutador de multiplicidad N
N‐switch coverage
135.
F
cobertura de decisiones
cobertura de decisión
decision coverage
136.
cobertura de decisiones‐ condiciones modificadas
cobertura de decisión de condición modificada
modified condition decision coverage
137.
cobertura de determinación de condiciones
cobertura de determinación de condición
condition determination coverage
138.
F
cobertura de la prueba
cobertura de pruebas
test coverage
139.
cobertura de particiones
cobertura de partición de
equivalence partition
See modified condition decision coverage.
NO APLICA.
The percentage of condition outcomes that have been exercised by a test suite. 100% condition coverage requires NO APLICA. each single condition in every decision statement to be tested as True and False. See condition coverage.
NO APLICA.
The percentage of combinations of all single condition outcomes within one statement that have been exercised by NO APLICA. a test suite. 100% multiple condition coverage implies 100% modified condition decision coverage. The percentage of all condition outcomes and decision outcomes that have been exercised by a test suite. 100% NO APLICA. decision condition coverage implies both 100% condition coverage and 100% decision coverage. The percentage of sequences of N+1 transitions that have NO APLICA. been exercised by a test suite. [Chow] The percentage of decision outcomes that have been exercised by a test suite. 100% decision coverage implies NO APLICA. both 100% branch coverage and 100% statement coverage. The percentage of all single condition outcomes that independently affect a decision outcome that have been NO APLICA. exercised by a test case suite. 100% modified condition decision coverage implies 100% decision condition coverage. See modified condition decision coverage.
NO APLICA.
See coverage.
NO APLICA.
The percentage of equivalence partitions that have been NO APLICA. exercised by a test suite.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
de equivalencia
equivalencia
coverage
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
The percentage of branches that have been exercised by a test suite. 100% branch coverage implies both 100% NO APLICA. decision coverage and 100% statement coverage. The percentage of executable statements that have been NO APLICA. exercised by a test suite. The percentage of LCSAJs of a component that have been exercised by a test suite. 100% LCSAJ coverage implies 100% NO APLICA. decision coverage.
140.
cobertura de ramas
cobertura de rama
branch coverage
141.
F
cobertura de sentencias
cobertura de sentencia
statement coverage
142.
cobertura de SLCYS
cobertura SLYSC
LCSAJ coverage
143.
cobertura de valores frontera
cobertura de valores límite
boundary value coverage
The percentage of boundary values that have been exercised by a test suite.
NO APLICA.
144.
cobertura del flujo de datos
cobertura del flujo de datos
data flow coverage
The percentage of definition‐use pairs that have been exercised by a test suite.
NO APLICA.
145.
cobertura estructural
cobertura estructural
structural coverage
Coverage measures based on the internal structure of a component or system.
NO APLICA.
146.
código
código
code
Computer instructions and data definitions expressed in a programming language or in a form output by an assembler, compiler or other translator. [IEEE 610]
NO APLICA.
147.
código inaccesible
código inaccesible
unreachable code
Code that cannot be reached and therefore is impossible to execute.
NO APLICA.
148.
código muerto:
código muerto
dead code
See unreachable code.
NO APLICA.
149.
ATT
coexistencia
coexistencia
co‐existence
150.
comité de control de la configuración (CCC)
comité de control de la configuración (CCC)
configuration control board (CCB)
151.
comité de control del cambio
comité de control de cambio
change control board
The capability of the software product to co‐exist with other independent software in a common environment NO APLICA. sharing common resources. [ISO 9126] See also portability. A group of people responsible for evaluating and approving or disapproving proposed changes to configuration items, NO APLICA. and for ensuring implementation of approved changes. [IEEE 610] See configuration control board.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
152.
ATM
comité de gestión de defectos
NO APLICA
defect management committee
153.
ATM
comité de priorización de defectos
NO APLICA
defect triage committee
154.
comparación de pruebas
comparación de pruebas
test comparison
155.
comparación dinámica
comparación dinámica
dynamic comparison
156.
comparación post‐ ejecución
comparación post‐ ejecución
post‐execution comparison
157.
comparador
comparador
comparator
158.
F
comparador de prueba
comparador de pruebas
test comparator
159.
compilación diaria
construcción diaria
daily build
160.
F
compilador
compilador
compiler
161.
F
complejidad
complejidad
complexity
162.
ATT
complejidad ciclomática
complejidad ciclomática
cyclomatic complexity
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A cross‐functional team of stakeholders who manage reported defects from initial detection to ultimate resolution (defect removal, defect deferral, or report cancellation). In NO APLICA. some cases, the same team as the configuration control board. See also configuration control board. See defect management committee.
NO APLICA.
The process of identifying differences between the actual results produced by the component or system under test and the xpected results for NO APLICA. a test. Test comparison can be performed during test execution (dynamic comparison) or after test execution. Comparison of actual and expected results, performed while the software is being executed, for example by a test NO APLICA. execution tool. Comparison of actual and expected results, performed after NO APLICA. the software has finished running. See test comparator.
NO APLICA.
A test tool to perform automated test comparison of actual NO APLICA. results with expected results. Actividad diaria de desarrollo en la que un sistema completo se compila y enlaza (normalmente durante la noche), de modo que un sistema consistente esté disponible en cualquier momento incluyendo la totalidad de los últimos cambios.
NO APLICA.
A software tool that translates programs expressed in a high order language into their machine language NO APLICA. equivalents. [IEEE 610] The degree to which a component or system has a design and/or internal structure that is difficult to understand, NO APLICA. maintain and verify. See also cyclomatic complexity. The maximum number of linear, independent paths through a program. Cyclomatic complexity may be computed as: L – N NO APLICA. + 2P, where
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
‐ L = the number of edges/links in a graph ‐ N = the number of nodes in a graph ‐ P = the number of disconnected parts of the graph (e.g. a called graph or subroutine) [After McCabe]
163.
componente
componente
component
A minimal software item that can be tested in isolation.
NO APLICA.
164.
comportamiento
comportamiento
behavior
The response of a component or system to a set of input values and preconditions.
NO APLICA.
Excessive emotional or psychological dependence on another person, specifically in trying to change that person’s current (undesirable) behavior while supporting them in continuing that behavior. For example, in software testing, complaining about late delivery to test and yet enjoying the necessary “heroism” working additional hours to make up time when delivery is running late, therefore reinforcing the lateness.
NO APLICA.
See performance.
NO APLICA.
165.
EITP
comportamiento codependiente
NO APLICA
codependent behavior
166.
comportamiento temporal
comportamiento temporal
time behavior
167.
comprobación de escritorio
comprobación de escritorio
desk checking
168.
comprobador
evaluador
checker
169.
condición
condición
condition
170.
ATT
condición atómica
NO APLICA
atomic condition
171.
condición compuesta
condición compuesta
compound condition
172.
F
condición de prueba
condición de prueba
test condition
Testing of software or a specification by manual simulation of NO APLICA. its execution. See also static testing. See reviewer.
NO APLICA.
A logical expression that can be evaluated as True or False, NO APLICA. e.g. A>B. See also condition testing. A condition that cannot be decomposed, i.e., a condition that does not contain two or more single conditions joined NO APLICA. by a logical operator (AND, OR, XOR). Two or more single conditions joined by means of a logical NO APLICA. operator (AND, OR or XOR), e.g. ‘A>B AND C>1000’. An item or event of a component or system that could be NO APLICA. verified by one or more test cases, e.g. a function,
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
ATM
OBSERVACIONES
transaction, feature, quality attribute, or structural element.
173.
condición de rama
condición de rama
branch condition
See condition.
NO APLICA.
174.
condición múltiple
condición múltiple
multiple condition
See compound condition.
NO APLICA.
175.
configuración
configuración
configuration
176.
conjunto de prueba
conjunto de prueba
test set
177.
conjunto de pruebas base
conjunto de pruebas base
basis test set
178.
consistencia
consistencia
consistency
contención de fase
NO APLICA
phase containment
The percentage of defects that are removed in the same phase of the software lifecycle in which they were NO APLICA. introduced.
contrato de la prueba
contrato de pruebas
test charter
A statement of test objectives, and possibly test ideas about how to test. Test charters are used in exploratory testing. See NO APLICA. also exploratory testing.
179.
180.
ATA ATM F‐AT ATA
181.
control de calidad
NO APLICA
quality control
182.
control de la configuración
control de la configuración
configuration control
F 183.
ATM ATA
DESCRIPCIÓN EN INGLÉS
control de la prueba
control de pruebas
test control
The composition of a component or system as defined by the number, nature, and interconnections of its constituent NO APLICA. parts. See test suite.
NO APLICA.
A set of test cases derived from the internal structure of a component or specification to ensure that 100% of a NO APLICA. specified coverage criterion will be achieved. The degree of uniformity, standardization, and freedom from contradiction among the documents or parts of a component NO APLICA. or system. [IEEE 610]
The operational techniques and activities, part of quality management, that are focused on fulfilling quality NO APLICA. requirements. [after ISO 8402] An element of configuration management, consisting of the evaluation, coordination, approval or disapproval, and implementation of changes to configuration items after NO APLICA. formal establishment of their configuration identification. [IEEE 610] A test management task that deals with developing and applying a set of corrective actions to get a test project on NO APLICA. track when monitoring shows a deviation from what was planned. See also test management.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
184.
F
control de versión
control de versión
version control
See configuration control.
NO APLICA.
185.
control del cambio
control de cambios
change control
See configuration control.
NO APLICA.
control del riesgo
control de riesgos
risk control
The process through which decisions are reached and protective measures are implemented for reducing risks to, NO APLICA. or maintaining risks within, specified levels.
controlador
controlador
driver
A software component or test tool that replaces a component that takes care of the ETAE control and/or the NO APLICA. calling of a component or system. [After TMap]
controlador de prueba
controlador de prueba
test driver
ATM 186.
ATA ATT
187.
188.
F ETAE
DESCRIPCIÓN EN INGLÉS
See driver.
OBSERVACIONES
NO APLICA.
A programming language/interpreter technique for evaluating compound conditions in which a condition on one side of a logical operator may not be evaluated if the NO APLICA. condition on the other side is sufficient to determine the final outcome. The total costs incurred on quality activities and issues and often split into prevention costs, appraisal costs, internal NO APLICA. failure costs and external failure costs.
189.
ATT
cortocircuitado
NO APLICA
short‐circuiting
190.
coste de la calidad
NO APLICA
cost of quality:
191.
F
COTS
COTS
COTS
Acronym for Commercial Off‐The‐Shelf software. See off‐ the‐shelf software.
NO APLICA.
192.
F‐AT
criterios de aceptación
criterios de aceptación
acceptance criteria
The exit criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity. [IEEE 610]
NO APLICA.
193.
criterios de compleción
criterios de compleción
completion criteria
See exit criteria.
NO APLICA.
194.
criterios de compleción de la prueba
criterios de compleción de pruebas
test completion criteria
See exit criteria.
NO APLICA.
195.
F
criterios de entrada
criterios de entrada
entry criteria
The set of generic and specific conditions for permitting a NO APLICA. process to go forward with a defined task, e.g. test phase.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
196.
criterios de paso/fallo
criterios de paso/fallo
pass/fail criteria
197.
criterios de reanudación
criterios de reanudación
resumption criteria
198.
ATM
criterios de salida
criterios de salida
exit criteria
criterios de suspensión
criterios de suspensión
suspension criteria
Critical Testing Processes
NO APLICA
Critical Testing Processes
CTP
NO APLICA
CTP
F
ATA
199.
200.
201.
ATM EITP
ATM EITP
202.
cuadro de mando
NO APLICA
scorecard
203.
EITP
cuadro de mando integral
NO APLICA
balanced scorecard
204.
cualificación
NO APLICA
qualification
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
The purpose of entry criteria is to prevent a task from starting which would entail more (wasted) effort compared to the effort needed to remove the failed entry criteria. [Gilb and Graham] Decision rules used to determine whether a test item NO APLICA. (function) or feature has passed or failed a test. [IEEE 829] The criteria used to restart all or a portion of the testing activities that were suspended previously. The set of generic and specific conditions, agreed upon with the stakeholders for permitting a process to be officially completed. The purpose of exit criteria is to prevent a task from being considered completed when there are still outstanding parts of the task which have not been finished. Exit criteria are used to report against and to plan when to stop testing. [After Gilb and Graham] The criteria used to (temporarily) stop all or a portion of the testing activities on the test items. [After IEEE 829] A content‐based model for test process improvement built around twelve critical processes. These include highly visible processes, by which peers and management judge competence and mission‐critical processes in which performance affects the company's profits and reputation. See also content‐based model. See Critical Testing Processes.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
A representation of summarized performance measurements representing progress towards the implementation of long‐ term goals. A scorecard provides static measurements of NO APLICA. performance over or at the end of a defined interval. See also balanced scorecard, dashboard. A strategic tool for measuring whether the operational activities of a company are aligned with its objectives in NO APLICA. terms of business vision and strategy. See also corporate dashboard, scorecard. The process of demonstrating the ability to fulfill specified NO APLICA. requirements. Note the term ‘qualified’ is used to designate
PROGRAMA DE ESTUDIOS
205.
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
cumplimiento
cumplimiento
compliance
D
206.
F
datos de prueba
datos de prueba
test data
207.
dd
NO APLICA
dd
208.
decisión
decisión
decision
defecto
defecto
defect
209.
TÉRMINO TRADUCIDO
F ATM
210.
defecto escapado
NO APLICA
escaped defect
211.
definición de datos
definición de datos
data definition
212.
ATM
Delphi de Banda Ancha
Delphi de Banda Ancha
Wide Band Delphi
213.
F
densidad de defectos
densidad de defectos
defect density
214.
densidad de faltas
densidad de faltas
fault density
DESCRIPCIÓN EN INGLÉS the corresponding status. [ISO 9000] The capability of the software product to adhere to standards, conventions or regulations in laws and similar prescriptions. [ISO 9126]
OBSERVACIONES
NO APLICA.
Data that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or NO APLICA. system under test. Abreviation of "decision‐to‐decision".
Este término no pertenece al glosario original.
A program point at which the control flow has two or more alternative routes. A node with two or more links to separate NO APLICA. branches. A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g. an incorrect statement or data definition. A defect, if NO APLICA. encountered during execution, may cause a failure of the component or system. A defect that was not detected in a previous test level which is supposed to find such type of defects. See also Defect NO APLICA. Detection Percentage. An executable statement where a variable is assigned a value.
NO APLICA.
An expert based test estimation technique that aims at making an accurate estimation using the collective wisdom of NO APLICA. the team members. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms, e.g. lines‐of‐code, number of classes or function points).
NO APLICA.
See defect density.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
215.
F
depuración:
depuración
debugging
The process of finding, analyzing and removing the causes of failures in software.
NO APLICA.
216.
depurador:
depurador
debugger
See debugging tool.
NO APLICA.
F‐AT
desarrollo ágil de software
NO APLICA
agile software development
desarrollo guiado por prestaciones
NO APLICA
feature‐driven development
desarrollo guiado por pruebas
desarrollo guiado por pruebas
test‐driven development
217.
218.
EITP
ETM
F 219.
F‐AT ETM
220.
desbordamiento de memoria intermedia
221.
despliegue de la función de calidad
NO APLICA
quality function deployment
222.
desviación
desviación
deviation
223.
DFC
NO APLICA
QFD
224.
EITP
diagnóstico (IDEAL)
NO APLICA
buffer overflow
NO APLICA
diagnosing (IDEAL)
OBSERVACIONES
A group of software development methodologies based on iterative incremental development, where requirements NO APLICA. and solutions evolve through collaboration between self‐ organizing cross‐functional teams. An iterative and incremental software development process driven from a client‐valued functionality (feature) perspective. Feature‐driven development is mostly used in NO APLICA. agile software development. See also agile software development. A way of developing software where the test cases are developed, and often automated, before the software is NO APLICA. developed to run those test cases. A memory access failure due to the attempt by a process to store data beyond the boundaries of a fixed length buffer, NO APLICA. resulting in overwriting of adjacent memory areas or the raising of an overflow exception. See also buffer. A method to transform user demands into design quality, to deploy the functions forming quality, and to deploy methods for achieving the design quality into subsystems and NO APLICA. component parts, and ultimately to specific elements of the manufacturing process. [Akao] See incident.
NO APLICA.
See quality function deployment.
NO APLICA.
The phase within the IDEAL model where it is determined where one is, relative to where one wants to be. The diagnosing phase consists of the activities: characterize NO APLICA. current and desired states and develop recommendations. See also IDEAL.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS A graphical representation used to organize and display the interrelationships of various possible root causes of a problem. Possible causes of a real or potential defect or failure are organized in categories and subcategories in a horizontal tree‐structure, with the (potential) defect or failure as the root node. [After Juran]
NO APLICA.
See cause‐effect diagram.
NO APLICA.
225.
EITP
diagrama causa‐efecto
NO APLICA
cause‐effect diagram
226.
diagrama de espina de pescado
NO APLICA
fishbone diagram
227.
diagrama de estados
diagrama de estado
state diagram
228.
ETM
diagrama de Ishikawa
NO APLICA
Ishikawa diagram
See cause‐effect diagram.
NO APLICA.
NO APLICA.
NO APLICA.
A diagram that depicts the states that a component or system can assume, and shows the events or circumstances NO APLICA. that cause and/or result from a change from one state to another. [IEEE 610]
229.
diagrama de trabajo pendiente
NO APLICA
burndown chart
A publicly displayed chart that depicts the outstanding effort versus time in an iteration. It shows the status and trend of completing the tasks of the iteration. The X‐axis typically represents days in the sprint, while the Y‐axis is the remaining effort (usually either in ideal engineering hours or story points).
230.
ATM
director de prueba
NO APLICA
test director
A senior manager who manages test managers. See also test manager.
diseño de la prueba
diseño de pruebas
test design
F 231.
ATM ATA
OBSERVACIONES
(1) See test design specification. (2) The process of transforming general test objectives into NO APLICA. tangible test conditions and test cases.
232.
disponibilidad
disponibilidad
availability
The degree to which a component or system is operational and accessible when required for use. Often expressed as a percentage. [IEEE 610]
NO APLICA.
233.
dominio
dominio
domain
The set from which valid input and/or output values can be selected.
NO APLICA.
234.
dominio de entrada
dominio de entrada
input domain
The set from which valid input values can be selected. See
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
also domain. 235.
dominio de salida
dominio de salida
output domain
E
236.
EDT
NO APLICA
WBS
237.
ATM
efectividad
NO APLICA
effectiveness
238.
239.
F
ATM ATT
efecto sonda
efecto sonda
probe effect
eficiencia
eficiencia
efficiency
ejecución de una prueba
ejecución de prueba
test execution
The set from which valid output values can be selected. See also domain.
NO APLICA.
See Work Breakdown Structure.
Estructura de descomposición del trabajo (EDT).
The capability of producing an intended result. See also efficiency.
NO APLICA.
The effect on the component or system by the measurement instrument when the component or system is being measured, e.g. by a performance testing tool or monitor. For NO APLICA. example performance may be slightly worse when performance testing tools are being used. (1) The capability of the software product to provide appropriate performance, relative to the amount of resources used under stated conditions. [ISO 9126] NO APLICA. (2) The capability of a process to produce the intended outcome, relative to the amount of resources used
F‐AT 240.
ATM
The process of running a test on the component or system NO APLICA. under test, producing actual result(s).
ATA
241.
elemento de cobertura
elemento de cobertura
coverage item
242.
F‐AT
elemento de la configuración
elemento de la configuración
configuration item
243.
elemento de prueba
elemento de prueba
test item
An entity or property used as a basis for test coverage, e.g. NO APLICA. equivalence partitions or code statements. An aggregation of hardware, software or both, that is designated for configuration management and treated as a NO APLICA. single entity in the configuration management process. [IEEE 610] The individual element to be tested. There usually is one test NO APLICA. object and many test items. See also test object.
244.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
emulador:
emulador
emulator
enfoque de prueba
enfoque de pruebas
test approach
F 245.
F‐AT ATM
246.
enmascaramiento de falta
enmascaramiento de faltas
fault masking
247.
enmascaramiento de un defecto
enmascaramiento de defectos
defect masking
248.
entorno de operaciones
entorno de operaciones
operational environment
249.
F
entorno de prueba
entorno de pruebas
test environment
250.
entrada
entrada
input
251.
entrada de prueba
entrada de prueba
test input
252.
entrada especificada
entrada especificada
specified input
253.
entrega
entregable
deliverable
254.
entrega de la prueba
NO APLICA
test deliverable
255.
EPME
NO APLICA
EMTE
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A device, computer program, or system that accepts the same inputs and produces the same outputs as a given NO APLICA. system. [IEEE 610] See also simulator. The implementation of the test strategy for a specific project. It typically includes the decisions made that follow based on the (test) project’s goal and the risk assessment carried out, NO APLICA. starting points regarding the test process, the test design techniques to be applied, exit criteria and test types to be performed See defect masking.
NO APLICA.
An occurrence in which one defect prevents the detection of NO APLICA. another. [After IEEE 610] Hardware and software products installed at users’ or customers’ sites where the component or system under test NO APLICA. will be used. The software may include operating systems, database management systems, and other applications. An environment containing hardware, instrumentation, simulators, software tools, and other support elements NO APLICA. needed to conduct a test. [After IEEE 610] A variable (whether stored within a component or outside) that is read by a component.
NO APLICA.
The data received from an external source by the test object during test execution. The external source can be hardware, NO APLICA. software or human. An input for which the specification predicts a result.
NO APLICA.
Any (work) product that must be delivered to someone other NO APLICA. than the (work) product’s author. Any test (work) product that must be delivered to someone other than the test (work) product’s author. See also NO APLICA. deliverable. Esfuerzo de Prueba Manual Acronym for Equivalent Manual Test Effort. Equivalente Equivalent Manual Test Effort.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
256.
F
equivocación
equivocación
mistake
257.
F
error
error
error
258.
escala de medición
escala de medida
measurement scale
A scale that constrains the type of data analysis that can be NO APLICA. performed on it. [ISO 14598]
259.
escalabilidad
escalabilidad
scalability
The capability of the software product to be upgraded to NO APLICA. accommodate increased loads. [After Gerrard]
260.
escenario de prueba
escenario de prueba
test scenario
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
See error.
NO APLICA.
A human action that produces an incorrect result. [After IEEE 610]
NO APLICA.
See test procedure specification.
NO APLICA.
261.
F
escriba
escriba
scribe
The person who records each defect mentioned and any suggestions for process improvement during a review NO APLICA. meeting, on a logging form. The scribe should ensure that the logging form is readable and understandable.
262.
ETAE
escritura de guiones lineales
NO APLICA
linear scripting
A simple scripting technique without any control structure in NO APLICA. the test scripts.
263.
ETAE
esfuerzo de prueba manual equivalente
NO APLICA
equivalent manual test effort
264.
especificación
especificación
specification
265.
F
especificación de caso de prueba
especificación de casos de prueba
test case specification
266.
especificación de componente
especificación de componente
component specification
267.
especificación de diseño de prueba
especificación de diseño de prueba
test design specification
Effort required for running tests manually. A document that specifies, ideally in a complete, precise and verifiable manner, the requirements, design, behavior, or other characteristics of a component or system, and, often, the procedures for determining whether these provisions have been satisfied. [After IEEE 610] A document specifying a set of test cases (objective, inputs, test actions, expected results, and execution preconditions) for a test item. [After IEEE 829] See also test specification. A description of a component’s function in terms of its output values for specified input values under specified conditions, and required non‐functional behavior (e.g. resource‐utilization). A document specifying the test conditions (coverage items) for a test item, the detailed test approach and identifying the associated high level test cases. [After IEEE 829] See also test specification.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
ATM
especificación de procedimiento de prueba
especificación de procedimiento de prueba
test procedure specification
269.
especificación de prueba
especificación de prueba
test specification
270.
ATT
estabilidad
estabilidad
stability
271.
EITP
establecimiento (IDEAL)
NO APLICA
establishing (IDEAL)
272.
EITP
estándar
NO APLICA
standard
estimación de la prueba
NO APLICA
test estimation
268.
273.
F
F‐AT ATM
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test NO APLICA. script. [After IEEE 829] See also test specification. A document that consists of a test design specification, test case specification and/or test procedure specification. The capability of the software product to avoid unexpected effects from modifications in the software. [ISO 9126] See also maintainability. The phase within the IDEAL model where the specifics of how an organization will reach its destination are planned. The establishing phase consists of the activities: set priorities, develop approach and plan actions. See also IDEAL. Formal, possibly mandatory, set of requirements developed and used to prescribe consistent approaches to the way of working or to provide guidelines (e.g., ISO/IEC standards, IEEE standards, and organizational standards). [After CMMI] The calculated approximation of a result related to various aspects of testing (e.g. effort spent, completion date, costs involved, number of test cases, etc.) which is usable even if input data may be incomplete, uncertain, or noisy. A test estimation method using estimated values for the “best case”, “worst case”, and “most likely case” of the matter being estimated, to define the degree of certainty associated with the resultant estimate.
NO APLICA. NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
274.
estimación de tres puntos
NO APLICA
three point estimation:
275.
ETAE
estrategia de automatización de la prueba
NO APLICA
test automation strategy
A high‐level plan to achieve long‐term objectives of test NO APLICA. automation under given boundary conditions.
estrategia de prueba
estrategia de prueba
test strategy
A high‐level description of the test levels to be performed and the testing within those levels for an organization or NO APLICA. programme (one or more projects).
NO APLICA.
F F‐AT 276.
ATM ATA ETM
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
277.
Estructura de Descomposición del Trabajo
NO APLICA
Work Breakdown Structure
278.
etapa de prueba
etapa de prueba
test stage
See test level.
NO APLICA.
279.
evaluación
evaluación
evaluation
See testing.
NO APLICA.
280.
EITP
evaluación del proceso
NO APLICA
process assessment
A disciplined evaluation of an organization’s software NO APLICA. processes against a reference model. [after ISO 15504]
risk assessment
The process of identifying and subsequently analyzing the identified project or product risk to determine its level of risk, typically by assigning likelihood and impact ratings. See also NO APLICA. product risk, project risk, risk, risk impact, risk level, risk likelihood.
ATM 281.
ATT
evaluación del riesgo
NO APLICA
ETAE
282.
ATA
evaluación heurística
evaluación heurística
heuristic evaluation
283.
EITP
evaluador
NO APLICA
assessor
284.
EITP
evaluador jefe
NO APLICA
lead assessor
285.
exactitud
exactitud
accuracy
F
EITP
factor crítico de éxito
NO APLICA
critical success factor
286.
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
An arrangement of work elements and their relationship to NO APLICA. each other and to the end product. [CMMI]
A usability review technique that targets usability problems in the user interface or user interface design. With this technique, the reviewers examine the interface and judge its compliance with recognized usability principles (the "heuristics"). A person who conducts an assessment; any member of an assessment team. The person who leads an assessment. In some cases, for instance CMMi and TMMi when formal assessments are conducted, the lead assessor must be accredited and formally trained. The capability of the software product to provide the right or agreed results or effects with the needed degree of precision. [ISO 9126] See also functionality.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
An element necessary for an organization or project to achieve its mission. Critical success factors are the critical NO APLICA. factors or activities required for ensuring the success.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
287.
fallar
fallar
fail
A test is deemed to fail if its actual result does not match its expected result.
NO APLICA.
288.
fallar prueba
fallo de prueba
test fail
See fail.
NO APLICA.
fallo
fallo
failure
289.
ATM
290.
F
falta
falta
fault
291.
fase de ejecución de prueba
fase de ejecución de pruebas
test execution phase
292.
fase de prueba
fase de prueba
test phase
293.
fase de requisitos
fase de requisitos
requirements phase
294.
fiabilidad
fiabilidad
reliability
295.
F
flujo de control
flujo de control
control flow
296.
F
flujo de datos
flujo de datos
data flow
297.
forzado del camino
forzar camino
path sensitizing
298.
F
ATT
fuga de memoria
fuga de memoria
memory leak
OBSERVACIONES
Deviation of the component or system from its expected NO APLICA. delivery, service or result. [After Fenton] See defect. The period of time in a software development lifecycle during which the components of a software product are executed, and the software product is evaluated to determine whether or not requirements have been satisfied. [IEEE 610] A distinct set of test activities collected into a manageable phase of a project, e.g. the execution activities of a test level. [After Gerrard] The period of time in the software lifecycle during which the requirements for a software product are defined and documented. [IEEE 610] The ability of the software product to perform its required functions under stated conditions for a specified period of time, or for a specified number of operations. [ISO 9126] A sequence of events (paths) in the execution through a component or system.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
An abstract representation of the sequence and possible changes of the state of data objects, where the state of an NO APLICA. object is any of: creation, usage, or destruction. [Beizer] Choosing a set of input values to force the execution of a given path.
NO APLICA.
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 NO APLICA. program and/or other concurrent processes to fail due to lack of memory.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
funcionalidad
NO APLICA
functionality
G
300.
EITP
GCT
NO APLICA
TQM
301.
generación de perfiles de rendimiento
NO APLICA
performance profiling
302.
generador de la prueba
generador de pruebas
test generator
303.
gestión de datos de prueba
NO APLICA
test data management
304.
gestión de defectos:
gestión de defectos
defect management
305.
F
gestión de incidencias
gestión de incidencias
incident management
306.
ETAE
gestión de información de la prueba
NO APLICA
test reporting
307.
gestión de la calidad
gestión de la calidad
quality management
308.
EITP
Gestión de la Calidad Total
NO APLICA
Total Quality Management
299.
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
The capability of the software product to provide functions which meet stated and implied needs when the software is NO APLICA. used under specified conditions. [ISO 9126]
See Total Quality Management.
NO APLICA.
The task of analyzing, e.g., identifying performance bottlenecks based on generated metrics, and tuning the NO APLICA. performance of a software component or system using tools. See test data preparation tool.
NO APLICA.
The process of analyzing test data requirements, designing NO APLICA. test data structures, creating and maintaining test data. The process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying them and identifying the impact. [After IEEE 1044] The process of recognizing, investigating, taking action and disposing of incidents. It involves logging incidents, classifying them and identifying the impact. [After IEEE 1044] Collecting and analyzing data from testing activities and subsequently consolidating the data in a report to inform stakeholders. See also test process. Coordinated activities to direct and control an organization with regard to quality. Direction and control with regard to quality generally includes the establishment of the quality policy and quality objectives, quality planning, quality control, quality assurance and quality improvement. [ISO 9000] An organization‐wide management approach centered on quality, based on the participation of all members of the organization and aiming at long‐term success through customer satisfaction, and benefits to all members of the organization and to society. Total Quality Management consists of planning, organizing, directing, control, and assurance. [After ISO 8402]
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item, control NO APLICA. changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements. [IEEE 610]
F‐AT
gestión de la configuración
gestión de la configuración
configuration management
310.
gestión de problemas
gestión de problemas
problem management
311.
ATM
gestión de prueba
gestión de pruebas
test management
The planning, estimating, monitoring and control of test NO APLICA. activities, typically carried out by a test manager.
312.
gestión de prueba basada en sesiones
NO APLICA
session‐based test management
A method for measuring and managing session‐based testing, NO APLICA. e.g. exploratory testing.
309.
313.
314.
F
TÉRMINO TRADUCIDO
EITP
ATM ATA
gestión del cambio
NO APLICA
change management
gestión del riesgo
gestión de riesgos
risk management
315.
EITP
GPG
NO APLICA
TPG
316.
EITP
gráfico causa‐efecto
gráfico causa‐efecto
cause‐effect graph
317.
ETM
gráfico de control
NO APLICA
control chart
318.
ETM
gráfico de Shewhart
NO APLICA
Shewhart chart
319.
grafo de llamadas
NO APLICA
call graph
See defect management.
(1) A structured approach to transitioning individuals, and organizations from a current state to a desired future state. (2) Controlled way to effect a change, or a proposed change, to a product or service. See also configuration management.
NO APLICA.
NO APLICA.
Systematic application of procedures and practices to the tasks of identifying, analyzing, prioritizing, and controlling NO APLICA. risk. See Test Process Group.
NO APLICA.
A graphical representation of inputs and/or stimuli (causes) with their associated outputs (effects), which can be used NO APLICA. to design test cases. A statistical process control tool used to monitor a process and determine whether it is statistically controlled. It graphically depicts the average value and the upper and NO APLICA. lower control limits (the highest and lowest values) of a process. See control chart.
NO APLICA.
An abstract representation of calling relationships between subroutines in a program.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
320.
grafo del flujo de control
gráfico de flujo de control
control flow graph
321.
EITP
Grupo del Proceso de Prueba
NO APLICA
Test Process Group
322.
guía de instalación
guía de instalación
installation guide
guion de prueba
guion de prueba
test script
Commonly used to refer to a test procedure specification, NO APLICA. especially an automated one.
ETAE
guion estructurado
NO APLICA
structured scripting
A scripting technique that builds and utilizes a library of NO APLICA. reusable (parts of) scripts.
H
325.
ATM
herramienta a medida
NO APLICA
custom tool
326.
F
herramienta de análisis dinámico
herramienta de análisis dinámico
dynamic analysis tool
327.
F
herramienta de análisis estático
herramienta de análisis estático
static analysis tool
See static analyzer.
NO APLICA.
328.
herramienta de captura/repetición
herramienta de captura/repetición
capture/replay tool
See capture/playback tool.
NO APLICA.
A type of test execution tool where inputs are recorded during manual testing in order to generate automated test scripts that can be executed later (i.e. replayed). These tools are often used to support automated regression testing.
NO APLICA.
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
An abstract representation of all possible sequences of events (paths) in the execution through a component or NO APLICA. system. A collection of (test) specialists who facilitate the definition, maintenance, and improvement of the test processes used NO APLICA. by an organization. [After CMMI] Supplied instructions on any suitable media, which guides the installer through the installation process. This may be a NO APLICA. manual guide, step‐by‐step procedure, installation wizard, or any other similar process description.
F 323.
ATM ETAE
324.
329.
ATT
herramienta de captura/reproducción
herramienta de captura/reproducción
capture/playback tool
A software tool developed specifically for a set of users or NO APLICA. customers. A tool that provides run‐time information on the state of the software code. These tools are most commonly used to identify unassigned pointers, check pointer arithmetic and to NO APLICA. monitor the allocation, use and de‐allocation of memory and to flag memory leaks.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
330.
F
herramienta de cobertura
herramienta de cobertura
coverage tool
331.
ATM
herramienta de código abierto
NO APLICA
open source tool
herramienta de depuración
NO APLICA
debugging tool:
herramienta de diseño de pruebas
herramienta de diseño de pruebas
test design tool
herramienta de ejecución de pruebas
herramienta de ejecución de pruebas
test execution tool
herramienta de gestión de defectos:
herramienta de gestión de defectos
336.
F
herramienta de gestión de incidencias
herramienta de gestión de incidencias
337.
F
herramienta de gestión de la configuración
herramienta de gestión de la configuración
332.
333.
F ATT
F ATA
DESCRIPCIÓN EN INGLÉS A tool that provides objective measures of what structural elements, e.g. statements, branches have been exercised by a test suite. 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. A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute programs step by step, to halt a program at any program statement and to set and examine program variables. A tool that supports the test design activity by generating test inputs from a specification that may be held in a CASE tool repository, e.g. requirements management tool, from specified test conditions held in the tool itself, or from code.
OBSERVACIONES
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
F 334.
ATA ATT
A type of test tool that is able to execute other software using an automated test script, e.g. capture/playback. NO APLICA. [Fewster and Graham]
ETAE
335.
defect management tool
A tool that facilitates the recording and status tracking of defects and changes. They often have workflow‐oriented facilities to track and control the allocation, correction and re‐testing of defects and provide reporting facilities. See also incident management tool.
NO APLICA.
A tool that facilitates the recording and status tracking of incidents. They often have workflow‐oriented facilities to incident management tool track and control the allocation, correction and re‐testing of NO APLICA. incidents and provide reporting facilities. See also defect management tool. A tool that provides support for the identification and control configuration of configuration items, their status over changes and NO APLICA. management tool versions, and the release of baselines consisting of configuration items.
PROGRAMA DE ESTUDIOS
338.
ATT
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
herramienta de gestión de pruebas
herramienta de gestión de pruebas
test management tool
339.
F
herramienta de gestión de requisitos
herramienta de gestión de requisitos
requirements management tool
340.
ATT
herramienta de grabación/reproducción
herramienta de grabación/reproducción
record/playback tool
341.
herramienta de instrumentación
instrumentador
instrumenter
342.
herramienta de instrumentación de programa
instrumentador de programa
343.
herramienta de medición de la cobertura
344.
F
345.
F
346.
347.
F
TÉRMINO TRADUCIDO
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A tool that provides support to the test management and control part of a test process. It often has several capabilities, such as testware management, scheduling of tests, the NO APLICA. logging of results, progress tracking, incident management and test reporting. A tool that supports the recording of requirements, requirements attributes (e.g. priority, knowledge responsible) and annotation, and facilitates traceability through layers of requirements and requirements change NO APLICA. management. Some requirements management tools also provide facilities for static analysis, such as consistency checking and violations to predefined requirements rules. See capture/playback tool.
NO APLICA.
A software tool used to carry out instrumentation.
NO APLICA.
program instrumenter
See instrumenter.
NO APLICA.
herramienta de medición de cobertura
coverage measurement tool
See coverage tool.
NO APLICA.
herramienta de modelado
herramienta de modelado
modeling tool
herramienta de monitorización
herramienta de monitorización
monitoring tool
ATA
herramienta de preparación de datos de prueba
herramienta de preparación de datos de prueba
EITP
herramienta de prueba
herramienta de pruebas
F
A tool that supports the creation, amendment and NO APLICA. verification of models of the software or system [Graham]. See monitor.
NO APLICA.
A type of test tool that enables data to be selected from test data preparation tool existing databases or created, generated, manipulated and NO APLICA. edited for use in testing. test tool
A software product that supports one or more test activities, such as planning and control, specification, building initial NO APLICA. files and data, test execution and test analysis. [TMap] See
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
also CAST. 348.
ATT
herramienta de prueba de hipervínculos
NO APLICA
hyperlink test tool
A tool used to check that no broken hyperlinks are present on a web site.
NO APLICA.
349.
F
herramienta de pruebas de estrés
herramienta de pruebas de estrés
stress testing tool
A tool that supports stress testing.
NO APLICA.
350.
351.
F ATT
herramienta de pruebas de rendimiento
herramienta de pruebas de rendimiento
performance testing tool
A tool to support performance testing that usually has two main facilities: load generation and test transaction measurement. Load generation can simulate either multiple users or high volumes of input data. During execution, NO APLICA. response time measurements are taken from selected transactions and these are logged. Performance testing tools normally provide reports based on test logs and graphs of load against response times.
herramienta de pruebas de seguridad
herramienta de pruebas de seguridad
security testing tool
A tool that provides support for testing security NO APLICA. characteristics and vulnerabilities. A tool that provides support to the review process. Typical features include review planning and tracking support, NO APLICA. communication support, collaborative reviews and a repository for collecting and reporting of metrics.
352.
F
herramienta de revisión
herramienta de revisión
review tool
353.
herramienta de seguimiento de bugs:
herramienta de seguimiento de bugs
bug tracking tool
See defect management tool.
NO APLICA.
354.
herramienta de seguimiento de defectos
herramienta de seguimiento de defectos
defect tracking tool
See defect management tool.
NO APLICA.
355.
F
herramienta de seguridad
herramienta de seguridad
security tool
A tool that supports operational security.
NO APLICA.
356.
herramienta de siembra de errores
NO APLICA
error seeding tool
See fault seeding tool.
NO APLICA.
357.
ATT
herramienta de siembra de faltas
NO APLICA
fault seeding tool
A tool for seeding (i.e. intentionally inserting) faults in a component or system.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
358.
F
herramienta para pruebas de carga
NO APLICA
load testing tool
359.
hipervínculo
NO APLICA
hyperlink
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
360.
F‐AT
historia de usuario
NO APLICA
user story
361.
hito
hito
milestone
I
ATA
IAMSW
NO APLICA
WAMMI
362.
363.
EITP
IDEAL
NO APLICA
IDEAL
364.
identificación de la configuración
identificación de la configuración
configuration identification
identificación del riesgo
identificación de riesgos
risk identification
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A tool to support load testing whereby it can simulate increasing load, e.g., numbers of concurrent users and/or NO APLICA. transactions within a specified time‐period. See also performance testing tool. A pointer within a web page that leads to other web pages.
NO APLICA.
A high‐level user or business requirement commonly used in agile software development, typically consisting of one or more sentences in the everyday or business language NO APLICA. capturing what functionality a user needs, any non‐functional criteria, and also includes acceptance criteria. See also agile software development, requirement. A point in time in a project at which defined (intermediate) NO APLICA. deliverables and results should be ready.
See Website Analysis and MeasureMent Inventory.
NO APLICA.
An organizational improvement model that serves as a roadmap for initiating, planning, and implementing improvement actions. The IDEAL model is named for the five NO APLICA. phases it describes: initiating, diagnosing, establishing, acting, and learning. An element of configuration management, consisting of selecting the configuration items for a system and recording NO APLICA. their functional and physical characteristics in technical documentation. [IEEE 610]
ATM 365.
ATA
The process of identifying risks using techniques such as NO APLICA. brainstorming, checklists and failure history.
ATT
366.
ILC
NO APLICA
CLI
367.
impacto del riesgo
NO APLICA
risk impact
Acrónimo para Interface de Línea de Comando.
Traducción de “CLI”.
The damage that will be caused if the risk become an actual outcome or event.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
NO APLICA
test implementation
ATA
implementación de prueba
369.
ATA
IMUS
NO APLICA
SUMI
370.
F
incidencia
incidencia
incident
371.
incidencia de prueba
incidencia de prueba
372.
incidencia de prueba software
ATM
374.
368.
OBSERVACIONES
The process of developing and prioritizing test procedures, creating test data and, optionally, preparing test harnesses NO APLICA. and writing automated test scripts. See Software Usability Measurement Inventory.
NO APLICA.
Any event occurring that requires investigation. [After IEEE 1008]
NO APLICA.
test incident
See incident.
NO APLICA.
incidencia de prueba software
software test incident
See incident.
NO APLICA.
independencia de las pruebas
independencia de pruebas
independence of testing
EITP
indicador
NO APLICA
indicator
375.
indicador clave de rendimiento
indicador clave de rendimiento
key performance indicator
376.
indicador de rendimiento
indicador de rendimiento
performance indicator
377.
indicador de rendimiento de prueba
indicador de rendimiento de prueba
test performance indicator
378.
Indicador Tipo Myers‐ Briggs (ITMB)
NO APLICA
Myers‐Briggs Type Indicator (MBTI)
An indicator of psychological preference representing the NO APLICA. different personalities and communication styles of people.
status accounting
An element of configuration management, consisting of the recording and reporting of information needed to manage a NO APLICA. configuration effectively. This information includes a listing of the approved configuration identification, the status of
373.
379.
ATM
DESCRIPCIÓN EN INGLÉS
F
información de estado
información de estado
Separation of responsibilities, which encourages the NO APLICA. accomplishment of objective testing. [After DO‐178b] A measure that can be used to estimate or predict another measure. [ISO 14598]
NO APLICA.
See performance indicator.
NO APLICA.
A high level metric of effectiveness and/or efficiency used to guide and control progressive development, e.g. lead‐time NO APLICA. slip for software development. [CMMI] A high level metric of effectiveness and/or efficiency used to guide and control progressive test development, e.g. Defect NO APLICA. Detection Percentage (DDP).
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
proposed changes to the configuration, and the implementation status of the approved changes. [IEEE 610]
380.
informe de bug
informe de bugs
bug report
See defect report.
NO APLICA.
381.
informe de defecto
informe de defectos
defect report
A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function. [After IEEE 829]
Se trata del informe de un solo defecto.
382.
informe de desviación
informe de desviaciones
deviation report
See incident report.
Se trata del informe de una única desviación.
383.
EITP
informe de evaluación
NO APLICA
assessment report
384.
informe de evaluación de prueba
informe de la evaluación de las pruebas
test evaluation report
385.
F
informe de incidencia
informe de incidencias
incident report
386.
informe de incidencia de la prueba
informe de incidencias de pruebas
test incident report
See incident report.
NO APLICA.
387.
informe de incidencia de la prueba software
informe de incidencias de pruebas software
software test incident report:
See incident report.
NO APLICA.
388.
informe de problema
informe de problemas
problem report
See defect report.
NO APLICA.
389.
informe de prueba
informe de pruebas
test report
See test summary report and test progress report.
NO APLICA.
390.
informe de transmisión de elemento
informe de transmisión de elemento
item transmittal report
See release note.
NO APLICA.
391.
informe de transmisión de elemento de prueba
informe de transmisión de elemento de prueba
test item transmittal report
See release note.
NO APLICA.
392.
informe del avance de la
NO APLICA
test progress report
A document summarizing the assessment results, e.g. conclusions, recommendations and findings. See also NO APLICA. process assessment. A document produced at the end of the test process summarizing all testing activities and results. It also contains NO APLICA. an evaluation of the test process and lessons learned. A document reporting on any event that occurred, e.g. during NO APLICA. the testing, which requires investigation. [After IEEE 829]
A document summarizing testing activities and results, NO APLICA. produced at regular intervals, to report progress of testing
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
prueba
OBSERVACIONES
activities against a baseline (such as the original test plan) and to communicate risks and alternatives requiring a decision to management.
informe resumen de prueba
informe resumen de pruebas
test summary report
A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items NO APLICA. against exit criteria. [After IEEE 829]
infraestructura de la prueba
infraestructura de pruebas
test infrastructure
The organizational artifacts needed to perform testing, consisting of test environments, test tools, office NO APLICA. environment and procedures.
395.
ETAE
ingeniero de autimatización de la prueba
NO APLICA
396.
EITP
iniciación (IDEAL)
NO APLICA
inspección
inspección
393.
394.
F ATM
F 397.
ATM AITP
DESCRIPCIÓN EN INGLÉS
A person who is responsible for the design, implementation and maintenance of a test automation architecture as well as test automation engineer NO APLICA. the technical evolution of the resulting test automation solution. The phase within the IDEAL model where the groundwork is laid for a successful improvement effort. The initiating phase initiating (IDEAL) NO APLICA. consists of the activities: set context, build sponsorship and charter infrastructure. See also IDEAL. 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 inspection NO APLICA. documentation. The most formal review technique and therefore always based on a documented procedure. [After IEEE 610, IEEE 1028] See also peer review.
398.
inspector
inspector
inspector
399.
ATT
instalabilidad
instalabilidad
installability
400.
instrumentación
instrumentación
instrumentation
401.
F
integración
integración
integration
402.
integración funcional
integración funcional
functional integration
See reviewer.
NO APLICA.
The capability of the software product to be installed in a NO APLICA. specified environment [ISO 9126]. See also portability. The insertion of additional code into the program in order to collect information about program behavior during NO APLICA. execution, e.g. for measuring code coverage. The process of combining components or systems into larger assemblies.
NO APLICA.
An integration approach that combines the components or systems for the purpose of getting a basic functionality NO APLICA. working early. See also integration testing.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
403.
EITP
inteligencia emocional
NO APLICA
emotional intelligence
404.
Interface Gráfica de Usuario
NO APLICA
GUI
405.
interoperabilidad
interoperabilidad
interoperability
406.
ETM
intervalo de confianza
NO APLICA
confidence interval
407.
ATA
Inventario de Análisis y Medición de Sitios Web (IAMSW)
NO APLICA
Website Analysis and MeasureMent Inventory (WAMMI)
A questionnaire‐based usability test technique for measuring NO APLICA. web site software quality from the end user's point of view.
408.
ATA
Inventario de Medición de Usabilidad Software (IMUS)
Inventario de Medición de Usabilidad Software (IMUS)
Software Usability Measurement Inventory (SUMI)
A questionnaire‐based usability test technique for measuring software quality from the end user's point of view. NO APLICA. [Veenendaal04] The process of intentionally adding defects to a system for the purpose of finding out whether the system can detect, and possibly recover from, a defect. Fault injection intended NO APLICA. to mimic failures that might occur in the field. See also fault tolerance.
409.
inyección de faltas
NO APLICA
fault injection
J
410.
ETAE
jefe de automatización de la prueba
NO APLICA
411.
F
jefe de prueba
jefe de pruebas
412.
juego de casos de prueba
juego de casos de prueba
test case suite
413.
F
juego de prueba
juego de prueba
test suite
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
The ability, capacity, and skill to identify, assess, and manage NO APLICA. the emotions of one's self, of others, and of groups. Acronym for Graphical User Interface.
NO APLICA.
The capability of the software product to interact with one or more specified components or systems. [After ISO 9126] See NO APLICA. also functionality. In managing project risks, the period of time within which a contingency action must be implemented in order to be NO APLICA. effective in reducing the impact of the risk.
A person who is responsible for the planning and supervision test automation manager of the development and evolution of a test automation NO APLICA. solution. The person responsible for project management of testing activities and resources, and evaluation of a test object. The test manager NO APLICA. individual who directs, controls, administers, plans and regulates the evaluation of a test object. See test suite.
NO APLICA.
A set of several test cases for a component or system under NO APLICA. test, where the post condition of one test is often used as the
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
precondition for the next one.
K
L
414.
F
lenguaje de guion
lenguaje de creación de scripts
scripting language
415.
líder de inspección
líder de inspección
inspection leader
416.
F
líder de la prueba
líder de pruebas
test leader
417.
línea base
línea base
baseline
M
418.
ATT
madurez
madurez
419.
F‐AT
manifiesto ágil
NO APLICA
420.
EITP
manifiesto por la mejora del proceso de prueba
NO APLICA
A programming language in which executable test scripts are written, used by a test execution tool (e.g. a NO APLICA. capture/playback tool). See moderator.
NO APLICA.
See test manager.
NO APLICA.
A specification or software product that has been formally reviewed or agreed upon, that thereafter serves as the basis for further development, and that can be changed only through a formal change control process. [After IEEE 610]
NO APLICA.
(1) The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. See also Capability Maturity Model Integration, NO APLICA. maturity Test Maturity Model integration. (2) The capability of the software product to avoid failure as a result of defects in the software. [ISO 9126] See also reliability. A statement on the values that underpin agile software development. The values are: ‐ individuals and interactions over processes and tools agile manifesto NO APLICA. ‐ working software over comprehensive documentation ‐ customer collaboration over contract negotiation ‐ responding to change over following a plan. A statement that echoes the agile manifesto, and defines values for improving the testing process. The values are: test process improvement ‐ flexibility over detailed processes NO APLICA. manifesto ‐ best practices over templates ‐ deployment orientation over process orientation
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
421.
mantenibilidad
mantenibilidad
maintainability
422.
ETAE
mantenimiento
mantenimiento
maintenance
423.
EITP
mapa mental
NO APLICA
mind map
424.
máquina de estados finitos
máquina de estado finito
finite state machine
425.
ETAE
marco de trabajo de automatización de la prueba
NO APLICA
test automation framework
marco de trabajo para prueba unitaria
marco de trabajo de pruebas unitarias
unit test framework
426.
TÉRMINO TRADUCIDO
F F‐AT
427.
ETM
matriz de asignación de responsabilidades (RACI)
NO APLICA
RACI matrix
428.
matriz de trazabilidad
NO APLICA
traceability matrix
429.
medición
medición
measurement
DESCRIPCIÓN EN INGLÉS ‐ peer reviews over quality assurance (departments) ‐ business driven over model driven. [Veenendaal08] 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. [ISO 9126] 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. [IEEE 1219] A diagram used to represent words, ideas, tasks, or other items linked to and arranged around a central keyword or idea. Mind maps are used to generate, visualize, structure, and classify ideas, and as an aid in study, organization, problem solving, decision making, and writing. A computational model consisting of a finite number of states and transitions between those states, possibly with accompanying actions. [IEEE 610]
OBSERVACIONES
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
A tool that provides an environment for test automation. It NO APLICA. usually includes a test harness and test libraries. A tool that provides an environment for unit or component testing in which a component can be tested in isolation or with suitable stubs and drivers. It also provides other support for the developer, such as debugging capabilities. [Graham] A matrix describing the participation by various roles in completing tasks or deliverables for a project or process. It is especially useful in clarifying roles and responsibilities. RACI is an acronym derived from the four key responsibilities most typically used: Responsible, Accountable, Consulted, and Informed. A two‐dimensional table, which correlates two entities (e.g., requirements and test cases). The table allows tracing back and forth the links of one entity to the other, thus enabling the determination of coverage achieved and the assessment of impact of proposed changes. The process of assigning a number or category to an entity to describe an attribute of that entity. [ISO 14598]
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
430.
EITP
medida
medida
431.
mejora del proceso
NO APLICA
432.
ETAE
mejora del proceso de prueba
NO APLICA
433.
EITP
Mejora del Proceso Software
NO APLICA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
The number or category assigned to an attribute of an entity NO APLICA. by making a measurement. [ISO 14598] A program of activities designed to improve the performance process improvement and maturity of the organization’s processes, and the result NO APLICA. of such a program. [CMMI] A program of activities designed to improve the performance test process improvement and maturity of the organization’s test processes and the NO APLICA. results of such a program. [After CMMI] measure
Software Process Improvement
434.
memoria intermedia
NO APLICA
buffer
435.
meta de la prueba
meta de prueba
test target
A program of activities designed to improve the performance and maturity of the organization’s software processes and NO APLICA. the results of such a program. [After CMMI] A device or storage area used to store data temporarily for differences in rates of data flow, time or occurrence of events, or amounts of data that can be handled by the devices or processes involved in the transfer or use of the data. [IEEE 610]
NO APLICA.
A set of exit criteria.
NO APLICA.
A black box test design technique in which test cases, described by means of a classification tree, are designed to classification tree method execute combinations of representatives of input and/or NO APLICA. output domains. [Grochtmann] See also combinatorial testing. A methodology whereby objectives are defined very S.M.A.R.T. goal specifically rather than generically. SMART is an acronym NO APLICA. methodology derived from the attributes of the objective to be defined: Specific, Measurable, Attainable, Relevant and Timely.
436.
ATA
método del árbol de clasificación:
método de árbol de clasificación
437.
ETM
metodología de objetivos S.M.A.R.T.
NO APLICA
métrica
métrica
metric
F 438.
EITP
A measurement scale and the method used for measurement. [ISO 14598]
NO APLICA.
ETAE
439.
ETM
métrica de convergencia
NO APLICA
convergence metric
440.
EITP
Métrica de Pregunta
NO APLICA
Goal Question Metric
A metric that shows progress toward a defined criterion, e.g., convergence of the total number of test executed to the total NO APLICA. number of tests planned for execution. An approach to software measurement using a three‐level NO APLICA. model: conceptual level (goal), operational level (question)
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
Objetivo 441.
442.
ETM
métricas de cobertura de Chow
misión de la prueba
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
and quantitative level (metric). métricas de cobertura de Chow
NO APLICA
Chow's coverage metrics
test mission
See N‐switch coverage. [Chow] The purpose of testing for an organization, often documented as part of the test policy.
NO APLICA.
NO APLICA.
See also test policy. ATM 443.
ATA ATT
mitigación del riesgo
mitigación de riesgos
risk mitigation
See risk control.
NO APLICA.
ETAE 444.
EITP
modelo basado en el contenido
NO APLICA
content‐based model
445.
EITP
modelo basado en el contenido:
NO APLICA
content reference model
446.
EITP
modelo de ciclo de vida
NO APLICA
F
modelo de desarrollo incremental
modelo de desarrollo incremental
modelo de desarrollo iterativo
modelo de desarrollo iterativo
447.
448.
F‐AT
F F‐AT
A process model providing a detailed description of good NO APLICA. engineering practices, e.g. test practices. See content‐based model.
NO APLICA.
A partitioning of the life of a product or project into phases. NO APLICA. [CMMI] See also software lifecycle. A development lifecycle where a project is broken into a series of increments, each of which delivers a portion of the functionality in the overall project requirements. The incremental development requirements are prioritized and delivered in priority order in NO APLICA. model the appropriate increment. In some (but not all) versions of this lifecycle model, each subproject follows a ‘mini Vmodel’ with its own design, coding and testing phases. A development lifecycle where a project is broken into a usually large number of iterations. An iteration is a complete iterative development development loop resulting in a release (internal or external) NO APLICA. model of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product. lifecycle model
PROGRAMA DE ESTUDIOS
modelo de desarrollo iterativo embebido
450.
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS A development lifecycle sub‐model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations. A non‐prescriptive framework for an organisation's quality management system, defined and owned by the European Foundation for Quality Management, based on five 'Enabling' criteria (covering what an organisation does), and four 'Results' criteria (covering what an organisation achieves). 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. A framework wherein processes of the same nature are classified into a overall model, e.g. a test improvement model.
OBSERVACIONES
NO APLICA
embedded iterative development model
EITP
modelo de excelencia EFQM (European Foundation for Quality Management)
NO APLICA
EFQM (European Foundation for Quality Management) excellence model
451.
modelo de madurez
NO APLICA
maturity model
452.
EITP
modelo de proceso
NO APLICA
process model
453.
modelo de referencia de contenido
NO APLICA
content reference model
See content‐based model.
454.
modelo de referencia de proceso
NO APLICA
process reference model
A process model providing a generic body of best practices and how to improve a process in a prescribed step‐by‐step NO APLICA. manner.
455.
ATT
modelo del crecimiento de la fiabilidad
NO APLICA
reliability growth model
A model that shows the growth in reliability over time during continuous testing of a component or system as a result of NO APLICA. the removal of defects that result in reliability failures.
449.
456.
457.
TÉRMINO TRADUCIDO
F
F ATM
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
modelo‐V
modelo‐V
V‐model
A framework to describe the software development lifecycle activities from requirements specification to maintenance. The V‐model illustrates how testing activities can be NO APLICA. integrated into each phase of the software development lifecycle.
moderador
moderador
moderator
The leader and main person responsible for an inspection or NO APLICA. other review process.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
458.
modo de fallo
modo de fallo
failure mode
459.
módulo
módulo
module
460.
ATM
test monitoring
MPO
NO APLICA
GQM
463.
EITP
MPS
NO APLICA
SPI
N
464.
nivel de integridad software
NO APLICA
software integrity level
465.
ETAE
nivel de intrusión
NO APLICA
level of intrusion
466.
EITP
nivel de madurez
NO APLICA
maturity level
nivel de prueba
nivel de prueba
test level
ATM
NO APLICA.
A test management task that deals with the activities related to periodically checking the status of a test project. Reports NO APLICA. are prepared that compare the actuals to that which was planned. See also test management.
monitorización de la prueba
EITP
F
See component.
monitorización de pruebas
monitor
462.
467.
The physical or functional manifestation of a failure. For example, a system in failure mode may be characterized by NO APLICA. slow operation, incorrect outputs, or complete termination of execution. [IEEE 610]
monitor
monitor
ATA
OBSERVACIONES
A software tool or hardware device that runs concurrently with the component or system under test and supervises, NO APLICA. records and/or analyses the behavior of the component or system. [After IEEE 610]
F 461.
DESCRIPCIÓN EN INGLÉS
See Goal Question Metric.
NO APLICA.
See Software Process Improvement.
NO APLICA.
The degree to which software complies or must comply with a set of stakeholder‐selected software and/or software‐ based system characteristics (e.g., software complexity, risk assessment, safety level, security level, desired performance, reliability, or cost) which are defined to reflect the importance of the software to its stakeholders. The level to which a test object is modified by adjusting it for testability. Degree of process improvement across a predefined set of process areas in which all goals in the set are attained. [TMMi] A group of test activities that are organized and managed together. A test level is linked to the responsibilities in a project. Examples of test levels are component test, integration test, system test and acceptance test. [After TMap]
NO APLICA.
NO APLICA. NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
ATM 468.
ATA
nivel de riesgo
NO APLICA
risk level
no conformidad
no conformidad
non‐conformity
ATT 469.
470.
nota de la entrega
nota de la entrega
release note
471.
notario
secretario
recorder
472.
número ciclomático
número ciclomático
cyclomatic number
Ñ
O
473.
F
474.
OBSERVACIONES
The importance of a risk as defined by its characteristics impact and likelihood. The level of risk can be used to determine the intensity of testing to be performed. A risk NO APLICA. level can be expressed either qualitatively (e.g. high, medium, low) or quantitatively. Non fulfillment of a specified requirement. [ISO 9000]
NO APLICA.
A document identifying test items, their configuration, current status and other delivery information delivered by NO APLICA. development to testing, and possibly other stakeholders, at the start of a test execution phase. [After IEEE 829] See scribe.
NO APLICA.
See cyclomatic complexity.
NO APLICA.
objetivo de prueba
objetivo de prueba
test objective
A reason or purpose for designing and executing a test.
NO APLICA.
objeto de prueba
objeto de prueba
test object
The component or system to be tested. See also test item.
NO APLICA.
475.
ATA
operabilidad
operabilidad
operability
The capability of the software product to enable the user to NO APLICA. operate and control it. [ISO 9126] See also usability.
476.
EITP
optimizador del proceso de prueba
NO APLICA
test process improver
A person implementing improvements in the test process NO APLICA. based on a test improvement plan.
477.
oráculo
oráculo
oracle
478.
DESCRIPCIÓN EN INGLÉS
F‐AT
oráculo de prueba
oráculo de prueba
test oracle
See test oracle.
NO APLICA.
A source to determine expected results to compare with the actual result of the software under test. An oracle may be the existing system (for a benchmark), other software, a user NO APLICA. manual, or an individual’s specialized knowledge, but should not be the code. [After Adrion]
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
P
479.
ETM
panel de control
NO APLICA
dashboard
480.
EITP
panel de control corporativo
NO APLICA
corporate dashboard
481.
ATT
par definición‐uso
par definición‐uso
definition‐use pair
482.
partición de equivalencia
partición de equivalencia
equivalence partition
483.
pasar
pasar
pass
484.
pasar prueba
pasado de prueba
test pass
485.
pequisito susceptible de ser probado
requisitos testeables
testable requirement
486.
perfil de carga
NO APLICA
load profile
487.
ETM
perfil operativo
NO APLICA
operational profile
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A representation of dynamic measurements of operational performance for some organization or activity, using metrics represented via metaphors such as visual ‘dials’, ‘counters’, and other devices resembling those on the dashboard of an automobile, so that the effects of events or activities can be easily understood and related to operational goals. See also corporate dashboard, scorecard.
NO APLICA.
A dashboard‐style representation of the status of corporate NO APLICA. performance data. See also balanced scorecard, dashboard. The association of a definition of a variable with the subsequent use of that variable. Variable uses include NO APLICA. computational (e.g. multiplication) or to direct the execution of a path (“predicate” use). A portion of an input or output domain for which the behavior of a component or system is assumed to be the NO APLICA. same, based on the specification. A test is deemed to pass if its actual result matches its expected result.
NO APLICA.
See pass.
NO APLICA.
A requirements that is stated in terms that permit establishment of test designs (and subsequently test cases) NO APLICA. and execution of tests to determine whether the requirement has been met. [After IEEE 610] A specification of the activity which a component or system being tested may experience in production. A load profile consists of a designated number of virtual users who process NO APLICA. a defined set of transactions in a specified time period and according to a predefined operational profile. See also operational profile. The representation of a distinct set of tasks performed by the component or system, possibly based on user behavior when NO APLICA. interacting with the component or system, and their
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
ATT
488.
perfilado operativo
NO APLICA
operational profiling
The process of developing and implementing an operational NO APLICA. profile. See also operational profile. A plan for achieving organizational test process improvement objectives based on a thorough understanding of the current NO APLICA. strengths and weaknesses of the organization’s test processes and test process assets. [After CMMI]
EITP
plan de mejora de prueba
NO APLICA
test improvement plan
490.
ATM
plan de nivel de prueba
plan de pruebas de nivel
level test plan
F ATM
OBSERVACIONES
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.
489.
491.
ETM
DESCRIPCIÓN EN INGLÉS
plan de prueba
plan de prueba
test plan
A test plan that typically addresses one test level. See also test plan.
NO APLICA.
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, the NO APLICA. test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process. [After IEEE 829]
492.
plan de prueba de la fase
plan de pruebas de fase
phase test plan
A test plan that typically addresses one test phase. See also test plan.
NO APLICA.
493.
plan de prueba de proyecto
plan de pruebas de proyecto
project test plan
See master test plan.
NO APLICA.
494.
ATM
plan de prueba maestro
plan maestro de pruebas
master test plan
A test plan that typically addresses multiple test levels. See also test plan.
NO APLICA.
495.
ATM
plan de revisión
NO APLICA
review plan
496.
ATM
planificación de prueba
planificación de prueba
test planning
A document describing the approach, resources and schedule of intended review activities. It identifies, amongst others: documents and code to be reviewed, review types to be NO APLICA. used, participants, as well as entry and exit criteria to be applied in case of formal reviews, and the rationale for their choice. It is a record of the review planning process. The activity of establishing or updating a test plan.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
ATA
497.
ETM
planificación póker
NO APLICA
planning poker
A consensus‐based estimation technique, mostly used to estimate effort or relative size of user stories in agile software development. It is a variation of the Wide Band NO APLICA. Delphi method using a deck of cards with values representing the units in which the team estimates. See also agile software development, Wide Band Delphi.
política de prueba
política de pruebas
test policy
A high level document describing the principles, approach NO APLICA. and major objectives of the organization regarding testing.
The number of defects found by a test level, divided by the number found by that test level and any other means NO APLICA. afterwards. See also escaped defects.
F 498.
ATM EITP ETM
499.
EITP
Porcentaje de Detección de Defectos (PDD)
Porcentaje de Detección de Defectos (PDD)
Defect Detection Percentage (DDP)
500.
Porcentaje de Detección de Faltas (PDF)
Porcentaje de Detección de Faltas (PDF)
Fault Detection Percentage (FDP)
501.
portabilidad
portabilidad
portability
502.
postcondición
postcondición
postcondition
503.
practicado
practicado
exercised
504.
precondición
precondición
precondition
505.
predicado
NO APLICA
predicate
predicción de errores
predicción de error
error guessing
506.
F ATA
See Defect Detection Percentage (DDP). The ease with which the software product can be transferred from one hardware or software environment to another. [ISO 9126] Environmental and state conditions that must be fulfilled after the execution of a test or test procedure. A program element is said to be exercised by a test case when the input value causes the execution of that element, such as a statement, decision, or other structural element. Environmental and state conditions that must be fulfilled before the component or system can be executed with a particular test or test procedure. A statement that can evaluate to true or false and may be used to determine the control flow of subsequent decision logic. See also decision.
NO APLICA.
NO APLICA. NO APLICA. NO APLICA.
NO APLICA.
NO APLICA.
A test design technique where the experience of the tester is used to anticipate what defects might be present in the NO APLICA. component or system under test as a result of errors made,
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
and to design tests specifically to expose them. An attribute of a component or system specified or implied by requirements documentation (for example reliability, NO APLICA. usability or design constraints). [After IEEE 1008]
507.
prestación
prestación
feature
508.
prestación software
prestación del software
software feature
509.
ATM
prioridad
prioridad
priority
510.
PRISMA (Product RISk MAnagement)
NO APLICA
PRISMA (Product RISk MAnagement)
511.
probabilidad del riesgo
NO APLICA
risk likelihood
The estimated probability that a risk will become an actual outcome or event.
NO APLICA.
512.
F
probador
probador
tester
A skilled professional who is involved in the testing of a component or system.
NO APLICA.
513.
problema
problema
problem
See defect.
NO APLICA.
procedimiento de prueba
procedimiento de prueba
test procedure
See test procedure specification.
NO APLICA.
proceso
proceso
process
A set of interrelated activities, which transform inputs into outputs. [ISO 12207]
NO APLICA.
514.
515.
F ATM
516.
proceso de prueba
proceso de prueba
517.
Product RISk MAnagement
NO APLICA
productos de prueba
producto de soporte de prueba
518.
TÉRMINO TRADUCIDO
F ETAE
test process
See feature.
NO APLICA.
The level of (business) importance assigned to an item, e.g. defect.
NO APLICA.
A systematic approach to risk‐based testing that employs product risk identification and analysis to create a product NO APLICA. risk matrix based on likelihood and impact.
The fundamental test process comprises test planning and control, test analysis and design, test implementation and NO APLICA. execution, evaluating exit criteria and reporting, and test closure activities.
Product RISk MAnagement See PRISMA.
testware
NO APLICA.
Artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, NO APLICA. inputs, expected results, set‐up and clear‐up procedures, files, databases, environment, and any additional software or
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
utilities used in testing. [After Fewster and Graham]
519.
productos de prueba automatizados
producto de soporte de pruebas automatizadas
automated testware
520.
programación en pareja
programación por pares
pair programming
521.
EITP
programación extrema
NO APLICA
extreme programming:
522.
proyecto
proyecto
project
523.
F
prueba
probar
testing
524.
prueba
prueba
test
525.
prueba comparativa
prueba comparativa
benchmark test
526.
prueba de admisión
prueba de admisión
intake test
527.
prueba de algoritmo
pruebas algorítmicas [TMap]
algorithm test
Testware used in automated testing, such as tool scripts. 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. A software engineering methodology used within agile software development whereby core practices are programming in pairs, doing extensive code review, unit testing of all code, and simplicity and clarity in code. See also agile software development. A project is a unique set of coordinated and controlled activities with start and finish dates undertaken to achieve an objective conforming to specific requirements, including the constraints of time, cost and resources. [ISO 9000] The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects. A set of one or more test cases. [IEEE 829]
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
(1) A standard against which measurements or comparisons can be made. (2) A test that is be used to compare components or NO APLICA. systems to each other or to a standard as in (1). [After IEEE 610] A special instance of a smoke test to decide if the component or system is ready for detailed and further testing. An intake NO APLICA. test is typically carried out at the start of the test execution phase. See also smoke test. [TMap] See branch testing.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
528.
prueba de ciclo de proceso
prueba de ciclo de proceso
process cycle test
529.
prueba de confianza
prueba de confianza
confidence test
530.
prueba de escenarios de usuario
pruebas de escenarios de usuario
user scenario testing
531.
ATA
prueba de historia de usuario
NO APLICA
user story testing
532.
prueba de humo
pruebas de humo
smoke test
533.
prueba de salud
pruebas de circunspección
sanity test
534.
prueba de usuario
pruebas de usuario
user test
535.
F‐AT
prueba de verificación de la compilación
NO APLICA
build verification test
536.
prueba del mono
pruebas de mono
monkey testing
537.
prueba mediante guion
pruebas programadas
scripted testing
538.
prueba previa
prueba previa
pretest
539.
pruebas ad hoc
pruebas ad hoc
ad hoc testing
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A black box test design technique in which test cases are designed to execute business procedures and processes. NO APLICA. [TMap] See also procedure testing. See smoke test.
NO APLICA.
See use case testing
NO APLICA.
A black box test design technique in which test cases are designed based on user stories to verify their correct NO APLICA. implementation. See also user story. A subset of all defined/planned test cases that cover the main functionality of a component or system, to ascertaining that the most crucial functions of a program work, but not NO APLICA. bothering with finer details. See also build, verification test, intake test. See smoke test.
NO APLICA.
A test whereby real‐life users are involved to evaluate the NO APLICA. usability of a component or system. A set of automated tests which validates the integrity of each new build and verifies its key/core functionality, stability and testability. It is an industry practice when a NO APLICA. high frequency of build releases occurs (e.g., agile projects) and it is run on every new build before the build is released for further testing. See also regression testing, smoke test. Testing by means of a random selection from a large range of inputs and by randomly pushing buttons, ignorant of how the NO APLICA. product is being used. Test execution carried out by following a previously documented sequence of tests.
NO APLICA.
See intake test.
NO APLICA.
Testing carried out informally; no formal test preparation takes place, no recognized test design technique is used,
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS there are no expectations for results and arbitrariness guides the test execution activity. Testing using various techniques to manage the risk of regression, e.g., by designing re‐usable testware and by extensive automation of testing at one or more test levels. Testing practice for a project using agile software development methodologies, incorporating techniques and methods, such as extreme programming (XP), treating development as the customer of testing and emphasizing the test‐first design paradigm. See also test‐driven development. A black box test design technique where test cases are selected, possibly using a pseudo‐random generation algorithm, to match an operational profile. This technique can be used for testing non‐functional attributes such as reliability and performance. Simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site, but outside the development organization. Alpha testing is often employed for off‐the‐shelf software as a form of internal acceptance testing. Testing based on a systematic analysis of e.g., product risks or requirements. An incremental approach to integration testing where the lowest level components are tested first, and then used to facilitate the testing of higher level components. This process is repeated until the component at the top of the hierarchy is tested. See also integration testing.
OBSERVACIONES
540.
ETM
pruebas adversas a la regresión
NO APLICA
regression‐averse testing
541.
EITP
pruebas ágiles
pruebas ágiles
agile testing
542.
pruebas aleatorias
pruebas aleatorias
random testing
543.
F
pruebas alfa
pruebas alfa
alpha testing
544.
ETM
pruebas analíticas
NO APLICA
analytical testing
545.
pruebas ascendentes
pruebas ascendentes
bottom‐up testing
546.
pruebas basadas en ataques
NO APLICA
attack‐based testing
An experience‐based testing technique that uses software attacks to induce failures, particularly security related failures. See also attack.
NO APLICA.
547.
pruebas basadas en el código
pruebas basadas en código
code‐based testing
See white box testing.
NO APLICA.
548.
pruebas basadas en el diseño
pruebas basadas en el diseño
design‐based testing
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
An approach to testing in which test cases are designed based on the architecture and/or detailed design of a NO APLICA. component or system (e.g. tests of interfaces between components or systems).
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
pruebas basadas en el riesgo
NO APLICA
risk‐based testing
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
F 549.
ATM ATA
An approach to testing to reduce the level of product risks and inform stakeholders of their status, starting in the initial NO APLICA. stages of a project. It involves the identification of product risks and the use of risk levels to guide the test process.
ATT 550.
pruebas basadas en la especificación
pruebas basadas en la especificación
specification‐based testing
See black box testing.
NO APLICA.
551.
F
pruebas basadas en la estructura
NO APLICA
structure‐based testing
See white‐box testing.
NO APLICA.
552.
pruebas basadas en la experiencia
NO APLICA
experience‐based testing
553.
ATA
pruebas basadas en listas de comprobación
NO APLICA
checklist‐based testing
pruebas basadas en modelos
NO APLICA
model‐based testing
554.
ETM ETAE
Testing based on the tester’s experience, knowledge and NO APLICA. intuition. An experience‐based test design technique whereby the experienced tester uses a high‐level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified. Testing based on a model of the component or system under test, e.g., reliability growth models, usage models such as operational profiles or behavioral models such as decision table or state transition diagram. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes. An approach to testing in which test cases are designed based on test objectives and test conditions derived from requirements, e.g. tests that exercise specific functions or probe non‐functional attributes such as reliability or usability.
NO APLICA.
NO APLICA.
555.
pruebas basadas en procesos de negocio:
pruebas basadas en el proceso de negocio
business process‐based testing
556.
ATA
pruebas basadas en requisitos
pruebas basadas en requisitos
requirements‐based testing
557.
pruebas basadas en sesiones
NO APLICA
session‐based testing
An approach to testing in which test activities are planned as uninterrupted sessions of test design and execution, often used in conjunction with exploratory testing.
NO APLICA.
558.
F
pruebas beta
pruebas beta
beta 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
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
559.
ATA
pruebas combinatorias
NO APLICA
combinatorial testing
560.
pruebas completas
pruebas completas
complete testing
561.
ETM
pruebas conforme a estándar
NO APLICA
562.
ETM
pruebas conforme a proceso
NO APLICA
563.
ETM
pruebas consultivas
NO APLICA
564.
pruebas contiguas
pruebas secuenciadas
565.
pruebas de a n elementos
NO APLICA
566.
ATA
pruebas de a pares de elementos
NO APLICA
567.
ATA
pruebas de accesibilidad
pruebas de accesibilidad
DESCRIPCIÓN EN INGLÉS component or system satisfies the user/customer needs and fits within the business processes. Beta testing is often employed as a form of external acceptance testing for off‐ the‐shelf software in order to acquire feedback from the market. A means to identify a suitable subset of test combinations to achieve a predetermined level of coverage when testing an object with multiple parameters and where those parameters themselves each have several values, which gives rise to more combinations than are feasible to test in the time allowed. See also classification tree method, n‐ wise testing, pairwise testing, orthogonal array testing. See exhaustive testing.
Testing that complies to a set of requirements defined by a standard, e.g., an industry testing standard or a standard for testing safety‐critical systems. See also process‐compliant testing. Testing that follows a set of defined processes, e.g., defined process‐compliant testing by an external party such as a standards committee. See also standard‐compliant testing. Testing driven by the advice and guidance of appropriate consultative testing experts from outside the test team (e.g., technology experts and/or business domain experts). Testing in which two or more variants of a component or system are executed with the same inputs, the outputs back‐to‐back testing compared, and analyzed in cases of discrepancies. [IEEE 610] A black box test design technique in which test cases are designed to execute all possible discrete combinations of any n‐wise testing set of n input parameters. See also combinatorial testing, orthogonal array testing, pairwise testing. A black box test design technique in which test cases are designed to execute all possible discrete combinations of pairwise testing each pair of input parameters. See also combinatorial testing, nwise testing, orthogonal array testing. standard‐compliant testing
accessibility testing
Testing to determine the ease by which users with
OBSERVACIONES
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
disabilities can use a component or system. [Gerrard]
568.
pruebas de aceptación
pruebas de aceptación
acceptance testing
Formal testing with respect to 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 determine whether or not to accept the system. [After IEEE 610]
NO APLICA.
Acceptance testing conducted at the site at which the product is developed and performed by employees of the supplier organization, to determine whether or not a NO APLICA. factory acceptance testing component or system satisfies the requirements, normally including hardware as well as software. See also alpha testing.
569.
pruebas de aceptación de factoría
NO APLICA
570.
pruebas de aceptación de producción
NO APLICA
production acceptance testing
See operational acceptance testing.
NO APLICA.
571.
F
pruebas de aceptación de usuario
pruebas de aceptación de usuario
user acceptance testing
See acceptance testing.
NO APLICA.
572.
pruebas de aceptación in situ
pruebas de aceptación in situ
site acceptance testing
573.
ATT
pruebas de aceptación operativa
NO APLICA
operational acceptance testing:
574.
ATA
pruebas de adecuación
NO APLICA
suitability testing
575.
pruebas de aislamiento
pruebas de aislamiento
isolation testing
Acceptance testing by users/customers at their site, to determine whether or not a component or system satisfies NO APLICA. the user/customer needs and fits within the business processes, normally including hardware as well as software. Operational testing in the acceptance test phase, typically performed in a (simulated) operational environment by operations and/or systems administration staff focusing on NO APLICA. operational aspects, e.g. recoverability, resource‐behavior, installability and technical compliance. See also operational testing. The process of testing to determine the suitability of a software product.
NO APLICA.
Testing of individual components in isolation from surrounding components, with surrounding components NO APLICA. being simulated by stubs and drivers, if needed.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
576.
pruebas de almacenamiento
pruebas de almacenamiento
storage testing
577.
ETAE
pruebas de API
NO APLICA
578.
pruebas de arco
pruebas de arco
OBSERVACIONES
See resource utilization testing.
NO APLICA.
API testing
Testing performed by submitting commands to the software under test using programming interfaces of the application directly.
NO APLICA.
arc testing
See branch testing.
NO APLICA.
A systematic way of testing all‐pair combinations of variables using orthogonal arrays. It significantly reduces the number of all combinations of variables to test all pair combinations. NO APLICA. See also combinatorial testing, n‐wise testing, pairwise testing.
579.
ATA
pruebas de arreglos ortogonales
NO APLICA
orthogonal array testing
580.
F
pruebas de caja blanca
pruebas de caja blanca
white‐box testing
Testing based on an analysis of the internal structure of the component or system.
NO APLICA.
581.
pruebas de caja de cristal
pruebas de caja de cristal
glass box testing
See white box testing.
NO APLICA.
582.
F
pruebas de caja negra
pruebas de caja negra
black box testing:
Testing, either functional or non‐functional, without reference to the internal structure of the component or system.
NO APLICA.
583.
pruebas de caja transparente
NO APLICA
clear‐box testing
See white‐box testing.
NO APLICA.
584.
ATT
pruebas de camino
pruebas de camino
path testing
A white box test design technique in which test cases are designed to execute paths.
NO APLICA.
585.
pruebas de campo
pruebas de campo
field testing
See beta testing.
NO APLICA.
586.
ATT
pruebas de capacidad de recuperación
pruebas de recuperabilidad
recoverability testing
The process of testing to determine the recoverability of a NO APLICA. software product. See also reliability testing.
load testing
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 NO APLICA. determine what load can be handled by the component or system. See also performance testing,stress testing.
587.
DESCRIPCIÓN EN INGLÉS
F
pruebas de carga
pruebas de carga
PROGRAMA DE ESTUDIOS
588.
F ATA
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
pruebas de caso de uso
pruebas de caso de uso
use case testing
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A black box test design technique in which test cases are NO APLICA. designed to execute scenarios of use cases.
589.
pruebas de cobertura de la lógica
pruebas de cobertura lógica
logic‐coverage testing
See white box testing. [Myers]
NO APLICA.
590.
pruebas de combinaciones de condiciones
pruebas de condición combinada
condition combination testing
See multiple condition testing.
NO APLICA.
591.
pruebas de combinaciones de condiciones de rama
pruebas de condición combinada de rama
branch condition combination testing
See multiple condition testing.
NO APLICA.
592.
pruebas de comparación elemental
pruebas de comparación elemental
elementary comparison testing
593.
pruebas de compatibilidad
pruebas de compatibilidad
compatibility testing
594.
F
pruebas de componente
pruebas de componente
component testing
595.
pruebas de concurrencia
pruebas de concurrencia
concurrency testing
596.
ATT
pruebas de condición
pruebas de condición
condition testing
597.
ATT
pruebas de condición múltiple
pruebas de condición múltiple
598.
pruebas de condición múltiple modificada
pruebas de condición múltiple modificada
A black box test design technique in which test cases are designed to execute combinations of inputs using the NO APLICA. concept of modified condition decision coverage. [TMap] See interoperability testing.
NO APLICA.
The testing of individual software components. [After IEEE 610]
NO APLICA.
Testing to determine how the occurrence of two or more activities within the same interval of time, achieved either by NO APLICA. interleaving the activities or by simultaneous execution, is handled by the component or system. [After IEEE 610] A white box test design technique in which test cases are NO APLICA. designed to execute condition outcomes.
A white box test design technique in which test cases are multiple condition testing designed to execute combinations of single condition NO APLICA. outcomes (within one statement). modified multiple condition testing
See modified condition decision testing.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
599.
ATT
pruebas de condiciónes‐ decisiónes
pruebas de condición‐ decisión
600.
pruebas de configuración
pruebas de configuración
configuration testing
601.
F
pruebas de confirmación
pruebas de confirmación
confirmation testing
602.
pruebas de conformidad
pruebas de conformidad
conformance testing
603.
pruebas de conmutador de orden N
pruebas de conmutador de multiplicidad N
N‐switch testing
A form of state transition testing in which test cases are designed to execute all valid sequences of N+1 transitions. NO APLICA. [Chow] See also state transition testing.
604.
pruebas de conversión
pruebas de conversión
conversion testing
Testing of software used to convert data from existing NO APLICA. systems for use in replacement systems.
605.
pruebas de cumplimiento
pruebas de cumplimiento
compliance testing
606.
pruebas de decisión
pruebas de decisión
decision testing
607.
pruebas de decisiones‐ condiciones modificadas
pruebas de decisión de condición modificada
modified condition decision testing
608.
pruebas de desarrollo
pruebas de desarrollo
development testing
609.
pruebas de determinación de condiciones
pruebas de determinación de condición
condition determination testing
610.
pruebas de eficiencia:
pruebas de eficiencia
efficiency testing
611.
pruebas de enlaces
pruebas de enlace
link testing
612.
pruebas de escalabilidad
pruebas de escalabilidad
scalability testing
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A white box test design technique in which test cases are decision condition testing designed to execute condition outcomes and decision NO APLICA. outcomes. See portability testing.
NO APLICA.
Testing that runs test cases that failed the last time they NO APLICA. were run, in order to verify the success of corrective actions. See compliance testing.
The process of testing to determine the compliance of the component or system.
NO APLICA.
NO APLICA.
A white box test design technique in which test cases are NO APLICA. designed to execute decision outcomes. A white box test design technique in which test cases are designed to execute single condition outcomes that NO APLICA. independently affect a decision outcome. Formal or informal testing conducted during the implementation of a component or system, usually in the NO APLICA. development environment by developers. [After IEEE 610] See modified condition decision testing.
NO APLICA.
The process of testing to determine the efficiency of a software product.
NO APLICA.
See component integration testing.
NO APLICA.
Testing to determine the scalability of the software product.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
613.
pruebas de escenario
scenario testing
614.
pruebas de estados finitos
pruebas de estado finito
615.
pruebas de estándares
pruebas de estándares
NO APLICA.
finite state testing
See state transition testing.
NO APLICA.
standards testing:
See compliance testing.
NO APLICA.
F
pruebas de estrés
pruebas de estrés
stress testing
617.
ATA
pruebas de exactitud
NO APLICA
accuracy testing:
pruebas de fiabilidad
pruebas de fiabilidad
reliability testing
F ATT
OBSERVACIONES
See use case testing.
616.
618.
DESCRIPCIÓN EN INGLÉS
619.
ATT
pruebas de flujo de control:
NO APLICA
control flow testing
620.
pruebas de hilo
pruebas de hilo
thread testing
621.
pruebas de instalabilidad
pruebas de instalabilidad
installability testing
622.
F
pruebas de integración
pruebas de integración
integration testing
623.
pruebas de integración a gran escala
pruebas de integración a gran escala
integration testing in the large
A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified workloads, or with reduced NO APLICA. availability of resources such as access to memory or servers. [After IEEE 610] See also performance testing, load testing. The process of testing to determine the accuracy of a NO APLICA. software product. See also accuracy. The process of testing to determine the reliability of a software product. An approach to structure‐based testing in which test cases are designed to execute specific sequences of events. Various techniques exist for control flow testing, e.g., decision testing, condition testing, and path testing, that each have their specific approach and level of control flow coverage. See also decision testing, condition testing, path testing. An approach to component integration testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by levels of a hierarchy. The process of testing the installability of a software product. See also portability testing. Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. See also component integration testing, system integration testing. See system integration testing.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
624.
pruebas de integración a pequeña escala
pruebas de integración a pequeña escala
integration testing in the small
625.
ATT
pruebas de integración de a pares de elementos
NO APLICA
pairwise integration testing
626.
pruebas de integración de componente
pruebas de integración de componente
component integration testing
627.
ATT
pruebas de integración de proximidad
NO APLICA
A form of integration testing where all of the nodes that neighborhood integration connect to a given node are the basis for the integration NO APLICA. testing testing.
628.
pruebas de integración de sistemas
pruebas de integración de sistema
Testing the integration of systems and packages; testing system integration testing interfaces to external organizations (e.g. Electronic Data NO APLICA. Interchange, Internet).
629.
pruebas de integración hardware‐software
NO APLICA
630.
pruebas de integridad de base de datos
pruebas de integridad de base de datos
631.
pruebas de integridad de datos
pruebas de integridad de datos
data integrity testing
632.
pruebas de interface
pruebas de interfaz
interface testing
An integration test type that is concerned with testing the NO APLICA. interfaces between components or systems.
633.
ETAE
Pruebas de Interface Gráfica de Usuario
NO APLICA
GUI testing
Testing performed by interacting with the software under NO APLICA. test via the graphical user interface.
ATA
pruebas de interoperabilidad
pruebas de interoperabilidad
interoperability testing
The process of testing to determine the interoperability of a NO APLICA. software product. See also functionality testing.
pruebas de invalidez
pruebas inválidas
invalid testing
Testing using input values that should be rejected by the NO APLICA. component or system. See also error tolerance, negative
634.
635.
F
DESCRIPCIÓN EN INGLÉS
See component integration testing.
OBSERVACIONES
NO APLICA.
A form of integration testing that targets pairs of NO APLICA. components that work together, as shown in a call graph. Testing performed to expose defects in the interfaces and interaction between integrated components.
NO APLICA.
Testing performed to expose defects in the interfaces and interaction between hardware and software components. NO APLICA. See also integration testing. Testing the methods and processes used to access and manage the data (base), to ensure access methods, processes database integrity testing and data rules function as expected and that during access to NO APLICA. the database, data is not corrupted or unexpectedly deleted, updated or created. hardware‐software integration testing
See database integrity testing.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
testing. 636.
pruebas de la capacidad de servicio
pruebas de capacidad de servicio
serviceability testing
637.
pruebas de la documentación
pruebas de documentación
documentation testing
638.
pruebas de la funcionalidad
pruebas de funcionalidad
functionality testing
pruebas de mantenibilidad
pruebas de mantenibilidad
maintainability testing
The process of testing to determine the maintainability of a NO APLICA. software product.
Testing the changes to an operational system or the impact NO APLICA. of a changed environment to an operational system.
See maintainability testing.
NO APLICA.
Testing the quality of the documentation, e.g. user guide or NO APLICA. installation guide. The process of testing to determine the functionality of a software product.
NO APLICA.
F 639.
F‐AT ATT
640.
F
pruebas de mantenimiento
pruebas de mantenimiento
maintenance testing
641.
pruebas de migración
pruebas de migración
migration testing
See conversion testing.
NO APLICA.
642.
pruebas de módulo
pruebas de módulo
module testing
See component testing.
NO APLICA.
643.
pruebas de mutación
pruebas de mutación
mutation testing
See back‐to‐back testing.
NO APLICA.
644.
pruebas de particiones
pruebas de partición
partition testing
See equivalence partitioning. [Beizer]
NO APLICA.
pruebas de portabilidad
pruebas de portabilidad
portability testing
The process of testing to determine the portability of a software product.
NO APLICA.
645.
F ATT
646.
pruebas de procedimientos
NO APLICA
procedure testing:
647.
pruebas de programa
pruebas de programa
program testing
Testing aimed at ensuring that the component or system can operate in conjunction with new or existing users’ business NO APLICA. procedures or operational procedures. See component testing.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
648.
pruebas de rama
pruebas de rama
branch testing
A white box test design technique in which test cases are designed to execute branches.
NO APLICA.
649.
pruebas de recuperación
pruebas de recuperación
recovery testing
See recoverability testing.
NO APLICA.
F 650.
F‐AT
pruebas de regresión
pruebas de regresión
regression testing
pruebas de regulación
pruebas de regulación
regulation testing
pruebas de rendimiento
pruebas de rendimiento
performance testing
pruebas de robustez
pruebas de robustez
robustness testing
pruebas de seguridad
pruebas de seguridad
security testing
ETAE 651.
OBSERVACIONES
Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a result of NO APLICA. the changes made. It is performed when the software or its environment is changed. See compliance testing.
NO APLICA.
F 652.
F‐AT
The process of testing to determine the performance of a NO APLICA. software product. See also efficiency testing.
ATT 653.
F
Testing to determine the robustness of the software product.
NO APLICA.
F 654.
F‐AT
Testing to determine the security of the software product. NO APLICA. See also functionality testing.
ATT
655.
pruebas de seguridad física
pruebas de seguridad (efectos adversos)
safety testing
656.
ATT
pruebas de sentencia
pruebas de sentencia
statement testing
657.
pruebas de sintáxis
pruebas sintácticas
syntax testing
658.
pruebas de sistema
NO APLICA
system testing
Testing to determine the safety of a software product.
NO APLICA.
A white box test design technique in which test cases are NO APLICA. designed to execute statements. A black box test design technique in which test cases are designed based upon the definition of the input domain NO APLICA. and/or output domain. The process of testing an integrated system to verify that it NO APLICA. meets specified requirements. [Hetzel]
659.
660.
661.
662.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
pruebas de SLCYS
pruebas SLYSC
LCSAJ testing
F
pruebas de tabla de decisión
pruebas de tabla de decisión
decision table testing
pruebas de tolerancia a fallos:
NO APLICA
failover testing:
pruebas de transición de estado
pruebas de transición de estado
state transition testing
A black box test design technique in which test cases are designed to execute valid and invalid state transitions. See NO APLICA. also N‐switch testing.
pruebas de usabilidad
pruebas de usabilidad
usability testing
Testing to determine the extent to which the software product is understood, easy to learn, easy to operate and NO APLICA. attractive to the users under specified conditions. [After ISO 9126] The process of testing to determine the resource‐utilization NO APLICA. of a software product. See also efficiency testing.
ATA
F ATA F
663.
F‐AT ATA
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A white box test design technique in which test cases are NO APLICA. designed to execute LCSAJs. A black box test design technique in which test cases are designed to execute the combinations of inputs and/or NO APLICA. stimuli (causes) shown in a decision table. [Veenendaal04] See also decision table. Testing by simulating failure modes or actually causing failures in a controlled environment. Following a failure, the failover mechanism is tested to ensure that data is not lost or NO APLICA. corrupted and that any agreed service levels are maintained (e.g., function availability or response times). See also recoverability testing.
664.
ATT
pruebas de utilización de recursos
pruebas de utilización de recursos
resource utilization testing
665.
pruebas de valores frontera
pruebas de valores límite
boundary value testing
666.
pruebas de volumen
pruebas de volumen
volume testing
Testing where the system is subjected to large volumes of NO APLICA. data. See also resource utilization testing.
667.
pruebas del flujo de datos
pruebas de flujo de datos
data flow testing
A white box test design technique in which test cases are NO APLICA. designed to execute definition‐use pairs of variables.
668.
pruebas del perfil operativo
pruebas de perfil operativo
operational profile testing
Statistical testing using a model of system operations (short NO APLICA. duration tasks) and their probability of typical use. [Musa]
669.
pruebas descendentes
pruebas descendentes
top‐down testing
An incremental approach to integration testing where the component at the top of the component hierarchy is tested NO APLICA. first, with lower level components being simulated by stubs.
See boundary value analysis.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested. See also integration testing. 670.
F
pruebas dinámicas
pruebas dinámicas
dynamic testing
An integration testing approach in which software elements, hardware elements, or both are combined all at once into a component or an overall system, rather than in stages. [After IEEE 610] See also integration testing. Two persons, e.g. two testers, a developer and a tester, or an end‐user and a tester, working together to find defects. Typically, they share one computer and trade control of it while testing. A test design technique in which a model of the statistical distribution of the input is used to construct representative test cases. See also operational profile testing. Testing of a software development artifact, e.g., requirements, design or code, without execution of these artifacts, e.g., reviews or static analysis.
NO APLICA.
671.
pruebas en big‐bang
pruebas tipo big‐bang
big‐bang testing
672.
pruebas en pareja
pruebas por pares
pair testing
673.
pruebas estadísticas
pruebas estadísticas
statistical testing
674.
F
pruebas estáticas
pruebas estáticas
static testing
675.
F
pruebas estructurales
pruebas estructurales
structural testing
676.
F
pruebas exhaustivas
pruebas exhaustivas
exhaustive testing
A test approach in which the test suite comprises all NO APLICA. combinations of input values and preconditions. An informal test design technique where the tester actively controls the design of the tests as those tests are performed NO APLICA. and uses information gained while testing to design new and better tests. [After Bach]
F 677.
F‐AT
pruebas exploratorias
pruebas exploratorias
exploratory testing
ATA 678.
pruebas externalizadas
NO APLICA
outsourced testing
679.
F
pruebas funcionales
pruebas funcionales
functional testing
pruebas guiadas por datos
pruebas guiadas por datos
data driven testing
680.
Testing that involves the execution of the software of a component or system.
F ATT
See white‐box testing.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA. NO APLICA.
Testing performed by people who are not co‐located with the NO APLICA. project team and are not fellow employees. Testing based on an analysis of the specification of the functionality of a component or system. See also black box NO APLICA. testing. A scripting technique that stores test input and expected results in a table or spreadsheet, so that a single control NO APLICA. script can execute all of the tests in the table. Data‐driven
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
ETAE
681.
682.
ATT
pruebas guiadas por la lógica
pruebas guiadas por lógica
logic‐driven testing
pruebas guiadas por palabra clave
pruebas guiadas por palabras clave
keyword driven testing
ETAE
OBSERVACIONES
testing is often used to support the application of test execution tools such as capture/playback tools. [Fewster and Graham] See also keyword‐driven testing.
F ATA
DESCRIPCIÓN EN INGLÉS
683.
pruebas guiadas por palabra de acción
pruebas guiadas por palabra de acción
action word driven testing
684.
ETAE
pruebas guiadas por proceso
NO APLICA
process‐driven testing
685.
ETAE
Pruebas ILC
NO APLICA
CLI testing
686.
pruebas incrementales
pruebas incrementales
incremental testing
687.
pruebas internalizadas
NO APLICA
insourced testing
688.
ETM
pruebas metódicas
NO APLICA
methodical testing
689.
pruebas negativas
pruebas negativas
negative testing
690.
pruebas no funcionales
pruebas no funcionales
non‐functional testing
See white box testing.
NO APLICA.
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 NO APLICA. by special supporting scripts that are called by the control script for the test. See also data‐driven testing.
See keyword‐driven testing. A scripting technique where scripts are structured into scenarios which represent use cases of the software under test. The scripts can be parameterized with test data. Testing performed by submitting commands to the software under test using a dedicated command‐line interface. Testing where components or systems are integrated and tested one or some at a time, until all the components or systems are integrated and tested. Testing performed by people who are co‐located with the project team but are not fellow employees.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA. NO APLICA.
Testing based on a standard set of tests, e.g., a checklist, a NO APLICA. quality standard, or a set of generalized test cases. Tests aimed at showing that a component or system does not work. Negative testing is related to the testers’ attitude rather than a specific test approach or test design technique, NO APLICA. e.g. testing with invalid input values or exceptions. [After Beizer]. Testing the attributes of a component or system that do not relate to functionality, e.g. reliability, efficiency, usability, NO APLICA. maintainability and portability.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
691.
pruebas operativas
pruebas operativas
operational testing
692.
ETM
pruebas reactivas
NO APLICA
reactive testing
693.
pruebas sucias
pruebas sucias
dirty testing
See negative testing.
NO APLICA.
694.
pruebas unitarias
pruebas unitarias
unit testing
See component testing.
NO APLICA.
695.
pseudo‐aleatoria
pseudo‐aleatoria
pseudo‐random
696.
puerta de calidad
NO APLICA
quality gate
697.
puntero
NO APLICA
pointer
698.
ATT
puntero sin referencia
NO APLICA
wild pointer
A pointer that references a location that is out of scope for NO APLICA. that pointer or that does not exist. See also pointer.
699.
punto de entrada
punto de entrada
entry point
An executable statement or process step which defines a NO APLICA. point at which a given process is intended to begin.
700.
punto de salida
punto de salida
exit point
An executable statement or process step which defines a NO APLICA. point at which a given process is intended to cease.
701.
PVC
NO APLICA
BVT
Q
R
702.
rama
rama
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
Testing conducted to evaluate a component or system in its NO APLICA. operational environment. [IEEE 610] Testing that dynamically responds to the actual system under test and test results being obtained. Typically reactive testing has a reduced planning cycle and the design and NO APLICA. implementation test phases are not carried out until the test object is received.
A series which appears to be random but is in fact generated NO APLICA. according to some prearranged sequence. A special milestone in a project. Quality gates are located between those phases of a project strongly depending on the NO APLICA. outcome of a previous phase. A quality gate includes a formal check of the documents of the previous phase. A data item that specifies the location of another data item; for example, a data item that specifies the address of the NO APLICA. next employee record to be processed. [IEEE 610]
See build verification test.
NO APLICA.
A basic block that can be selected for execution based on a program construct in which one of two or more alternative program paths is available, e.g. case, jump, go to, if‐then‐ else.
NO APLICA.
branch
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
703.
rastro de auditoría
rastro de auditoría
audit trail
704.
EITP
Rational Unified Process
NO APLICA
Rational Unified Process
705.
realización de una prueba
ejecución de una prueba
test run
706.
ETAE
registrar en bitácora de la prueba
registrar pruebas
707.
F
registrar incidencia
708.
709.
710.
711.
TÉRMINO TRADUCIDO
F ETAE
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A path by which the original input to a process (e.g. data) can be traced back through the process, taking the process NO APLICA. output as a starting point. This facilitates defect analysis and allows a process audit to be carried out. [After TMap] A proprietary adaptable iterative software development process framework consisting of four project lifecycle phases: NO APLICA. inception, elaboration, construction and transition. Execution of a test on a specific version of the test object.
NO APLICA.
test logging
The process of recording information about tests executed into a test log.
NO APLICA.
registrar incidencias
incident logging
Recording the details of any incident that occurred, e.g. during testing.
NO APLICA.
registrar prueba
registrar pruebas
test recording
See test logging.
NO APLICA.
registro de la prueba
registro de pruebas
test record
See test log.
NO APLICA.
rendimiento
rendimiento
performance
repetición de las pruebas
repetición de pruebas
re‐testing
The degree to which a system or component accomplishes its designated functions within given constraints regarding NO APLICA. processing time and throughput rate. [After IEEE 610] See also efficiency. See confirmation testing.
NO APLICA.
A black box test design technique in which test cases are designed from cause‐effect graphs. [BS 7925/2]
NO APLICA.
712.
ATA
representación causa‐ efecto
representación causa‐ efecto
cause‐effect graphing
713.
EITP
representación continua
NO APLICA
continuous representation
A capability maturity model structure wherein capability levels provide a recommended order for approaching process NO APLICA. improvement within specified process areas. [CMMI]
714.
EITP
representación por niveles
NO APLICA
staged representation
A model structure wherein attaining the goals of a set of process areas establishes a maturity level; each level builds a NO APLICA. foundation for subsequent levels. [CMMI]
715.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
reproducibilidad de la prueba
reproducibilidad de una prueba
test reproducibility
An attribute of a test indicating whether the same results are NO APLICA. produced each time the test is executed. 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, NO APLICA. specification, or other formally imposed document. [After IEEE 610]
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
716.
F
requisito
requisito
requirement
717.
requisito de prueba
requisito de prueba
test requirement
718.
F
requisito funcional
requisito funcional
functional requirement
A requirement that specifies a function that a component or NO APLICA. system must perform. [IEEE 610]
719.
F
requisito no funcional
requisito no funcional
non‐functional requirement:
A requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, NO APLICA. maintainability and portability.
720.
requisitos de reanudación
NO APLICA
resumption requirements
The defined set of testing activities that must be repeated NO APLICA. when testing is re‐started after a suspension. [After IEEE 829]
721.
resultado
resultado
outcome
See test condition.
See result.
NO APLICA.
NO APLICA.
The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and NO APLICA. communication messages sent out. See also actual result, expected result. A test result in which a defect is reported although no such NO APLICA. defect actually exists in the test object.
722.
resultado
resultado
result
723.
ATM
resultado de falso‐fallo
NO APLICA
false‐fail result
724.
ATM
resultado de falso‐ negativo
NO APLICA
false‐negative result
725.
ATM
resultado de falso‐paso
NO APLICA
false‐pass result
726.
ATM
resultado de falso‐ positivo
NO APLICA
false‐positive result
See false‐fail result.
NO APLICA.
727.
resultado de la condición
resultado de condición
condition outcome
The evaluation of a condition to True or False.
NO APLICA.
See false‐pass result.
NO APLICA.
A test result which fails to identify the presence of a defect NO APLICA. that is actually present in the test object.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
728.
resultado de la decisión
resultado de decisión
decision outcome
The result of a decision (which therefore determines the branches to be taken).
NO APLICA.
729.
resultado de la prueba
resultado de prueba
test outcome
See result.
NO APLICA.
730.
resultado de prueba
resultado de prueba
test result
See result.
NO APLICA.
731.
ETAE
resultado del caso de prueba
NO APLICA
test case result
732.
resultado esperado
resultado esperado
expected outcome
733.
resultado esperado
resultado esperado
expected result
734.
resultado previsto
resultado previsto
predicted outcome
735.
resultado real
resultado real
actual outcome
736.
resultado real
resultado real
actual result
737.
EITP
retrospectiva del proyecto
NO APLICA
project retrospective
738.
reunión post proyecto
NO APLICA
post‐project meeting
739.
EITP
reunión retrospectiva
NO APLICA
retrospective meeting
revisión
revisión
review
740.
F ATM
OBSERVACIONES
The final verdict on the execution of a test and its outcomes, like pass, fail, or error. The result of error is used for NO APLICA. situations where it is not clear whether the problem is in the test object. See expected result.
NO APLICA.
The behavior predicted by the specification, or another source, of the component or system under specified NO APLICA. conditions. See expected result.
NO APLICA.
See actual result.
NO APLICA.
The behavior produced/observed when a component or system is tested.
NO APLICA.
A structured way to capture lessons learned and to create specific action plans for improving on the next project or next NO APLICA. project phase. See retrospective meeting.
NO APLICA.
A meeting at the end of a project during which the project team members evaluate the project and learn lessons that NO APLICA. can be applied to the next project. An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples include management review, NO APLICA. informal review, technical review, inspection, and walkthrough. [After IEEE 1028]
741.
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
revisión ad hoc
revisión ad hoc
ad hoc review
742.
ATM
revisión de gestión
revisión de gestión
management review
743.
revisión de la capacidad de ser comprobado
revisión de testabilidad
testability review
744.
F
revisión entre pares
revisión entre pares
peer review
745.
F
revisión formal
revisión formal
formal review
746.
747.
748.
749.
750.
PROGRAMA DE ESTUDIOS
F ATM
F ATM F ATM F ATM
DESCRIPCIÓN EN INGLÉS See informal review.
OBSERVACIONES NO APLICA.
A systematic evaluation of software acquisition, supply, development, operation, or maintenance process, performed by or on behalf of management that monitors progress, determines the status of plans and schedules, confirms NO APLICA. requirements and their system allocation, or evaluates the effectiveness of management approaches to achieve fitness for purpose. [After IEEE 610, IEEE 1028] A detailed check of the test basis to determine whether the test basis is at an adequate quality level to act as an input NO APLICA. document for the test process. [After TMap] A review of a software work product by colleagues of the producer of the product for the purpose of identifying NO APLICA. defects and Improvements. Examples are inspection, technical review and walkthrough. A review characterized by documented procedures and requirements, e.g. inspection.
NO APLICA.
A step‐by‐step presentation by the author of a document in order to gather information and to establish a common NO APLICA. understanding of its content. [Freedman and Weinberg, IEEE 1028] See also peer review.
revisión guiada
revisión guiada
walkthrough
revisión guiada estructurada
revisión guiada estructurada
structured walkthrough
revisión informal
revisión informal
informal review
revisión técnica
revisión técnica
technical review
A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. [Gilb and NO APLICA. Graham], [IEEE 1028] See also peer review.
reviewer
The person involved in the review that identifies and describes anomalies in the product or project under review. NO APLICA. Reviewers can be chosen to represent different viewpoints and roles in the review process.
revisor
revisor
See walkthrough.
NO APLICA.
A review not based on a formal (documented) procedure.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
riesgo
riesgo
risk
A factor that could result in future negative consequences; NO APLICA. usually expressed as impact and likelihood.
riesgo de calidad
NO APLICA
quality risk
A product risk related to a quality attribute. See also quality NO APLICA. attribute, product ATM risk.
riesgo de producto
riesgo de producto
product risk
riesgo de proyecto
riesgo de proyecto
project risk
A risk related to management and control of the (test) project, e.g. lack of ATM staffing, strict deadlines, changing NO APLICA. requirements, etc. See also risk. The degree to which a component or system can function correctly in the presence of invalid inputs or stressful NO APLICA. environmental conditions. [IEEE 610] See also error‐ tolerance, faulttolerance.
F 751.
ATM ETAE
752.
F‐AT ATM F F‐AT
753.
ATM
A risk directly related to the test object. See also risk.
NO APLICA.
ATA ATT
754.
F ATM
755.
ATT
robustez
robustez
robustness
756.
RUP
NO APLICA
RUP
S
757.
salida
salida
output
758.
EITP
SCRUM
NO APLICA
SCRUM
759.
F
segmentación de
segmentación de
equivalence partitioning
See Rational Unified Process.
NO APLICA.
A variable (whether stored within a component or outside) that is written by a component.
NO APLICA.
An iterative incremental framework for managing projects commonly used with agile software development. See also NO APLICA. agile software development. A black box test design technique in which test cases are NO APLICA. designed to execute representatives from equivalence
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
ATA
equivalencia
equivalencia
760.
seguridad
seguridad
security
761.
seguridad física
seguridad (efectos adversos)
safety
762.
sentencia
sentencia
statement
763.
sentencia ejecutable
sentencia ejecutable
executable statement
764.
sentencia fuente
sentencia fuente
source statement
TÉRMINO EN INGLÉS
765.
sesión de prueba
NO APLICA
test session
766.
ATM
severidad
severidad
severity
767.
siembra de errores
siembra de errores
error seeding
768.
siembra de faltas
NO APLICA
fault seeding
769.
simulación
simulación
simulation
770.
simulador
simulador
simulator
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
partitions. In principle test cases are designed to cover each partition at least once. Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or NO APLICA. deliberate, to programs and data. [ISO 9126] See also functionality. The capability of the software product to achieve acceptable levels of risk of harm to people, business, software, property NO APLICA. or the environment in a specified context of use. [ISO 9126] An entity in a programming language, which is typically the NO APLICA. smallest indivisible unit of execution. A statement which, when compiled, is translated into object code, and which will be executed procedurally when the NO APLICA. program is running and may perform an action on data. See statement.
NO APLICA.
An uninterrupted period of time spent in executing tests. In exploratory testing, each test session is focused on a charter, but testers can also explore new opportunities or issues NO APLICA. during a session. The tester creates and executes on the fly and records their progress. See also exploratory testing. The degree of impact that a defect has on the development NO APLICA. or operation of a component or system. [After IEEE 610] See fault seeding.
NO APLICA.
The process of intentionally adding defects to those already in the component or system for the purpose of monitoring the rate of detection and removal, and estimating the number of remaining defects. Fault seeding is typically part of NO APLICA. development (pre‐release) testing and can be performed at any test level (component, integration, or system). [After IEEE 610] The representation of selected behavioral characteristics of one physical or abstract system by another system. [ISO NO APLICA. 2382/1] A device, computer program or system used during testing, which behaves or operates like a given system when NO APLICA. provided with a set of controlled inputs. [After IEEE 610,
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
DO178b] See also emulator. A collection of components organized to accomplish a NO APLICA. specific function or set of functions. [IEEE 610]
771.
sistema
sistema
system
772.
sistema de seguridad crítica
NO APLICA
safety critical system
A system whose failure or malfunction may result in death or serious injury to people, or loss or severe damage to NO APLICA. equipment, or environmental harm.
773.
sistema de sistemas
NO APLICA
system of systems
Multiple heterogeneous, distributed systems that are embedded in networks at multiple levels and in multiple interconnected domains, addressing large‐scale inter‐ NO APLICA. disciplinary common problems and purposes, usually without a common management structure.
774.
sistema sujeto a prueba
NO APLICA
system under test
See test object.
775.
situación de prueba
situación de prueba
test situation
776.
SLCYS
SLYSC
LCSAJ
777.
software
software
software
778.
software a medida
software a medida
bespoke software
779.
software a medida
software a medida
custom software
780.
F
software comercial de distribución masiva
software comercial de distribución masiva
Commercial Off‐The‐Shelf software
781.
software de distribución masiva
software de distribución masiva
off‐the‐shelf software
782.
software estándar
software estándar
standard software
See test condition.
NO APLICA. NO APLICA.
A Linear Code Sequence And Jump, consists of the following three items (conventionally identified by line numbers in a source code listing): the start of the linear sequence of NO APLICA. executable statements, the end of the linear sequence, and the target line to which control flow is transferred at the end of the linear sequence. Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a NO APLICA. computer system. [IEEE 610] Software developed specifically for a set of users or NO APLICA. customers. The opposite is off‐the‐shelf software. See bespoke software.
NO APLICA.
See off‐the‐shelf software.
NO APLICA.
A software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to NO APLICA. many customers in identical format. See off‐the‐shelf software.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
783.
ETAE
solución de automatización de la prueba
NO APLICA
test automation solution
784.
ETAE
SSP
NO APLICA
SUT
STEP
NO APLICA
STEP
stub
stub
stub
subcamino
subcamino
subpath
ATM
NO APLICA
EITP
Systematic Test and Evaluation Process
Systematic Test and Evaluation Process
T
789.
tabla de decisión
tabla de decisión
decision table
790.
tabla de decisión causa‐ efecto
tabla de decisión causa‐ efecto
cause‐effect decision table
791.
tabla de estados
tabla de estado
state table
792.
F
tasa de fallos
frecuencia de fallos
failure rate
785.
786.
787.
788.
ATM EITP F ETAE
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A realization/implementation of a test automation architecture, i.e., a combination of components implementing a specific test automation assignment. The NO APLICA. components may include off‐the‐shelf test tools, test automation frameworks, as well as test hardware. Acronym for system under test.
See Systematic Test and Evaluation Process.
NO APLICA.
NO APLICA.
A skeletal or special‐purpose implementation of a software component, used to develop or test a component that calls NO APLICA. or is otherwise dependent on it. It replaces a called component. [After IEEE 610] A sequence of executable statements within a component.
NO APLICA.
A structured testing methodology, also used as a EITP content‐based model for improving the testing process. Proceso Sistemático de Systematic Test and Evaluation Process (STEP) does not Evaluación y Pruebas require that improvements occur in a specific order. See also content‐based model.
A table showing combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions NO APLICA. (effects), which can be used to design test cases. See decision table.
NO APLICA.
A grid showing the resulting transitions for each state combined with each possible event, showing both valid and NO APLICA. invalid transitions. The ratio of the number of failures of a given category to a given unit of measure, e.g. failures per unit of time, failures NO APLICA. per number of transactions, failures per number of computer runs. [IEEE 610]
793.
794.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
taxonomía de bugs
NO APLICA
bug taxonomy
taxonomía de defectos
NO APLICA
defect taxonomy
F‐AT ATA
DESCRIPCIÓN EN INGLÉS See defect taxonomy.
OBSERVACIONES NO APLICA.
A system of (hierarchical) categories designed to be a useful NO APLICA. aid for reproducibly classifying defects.
795.
ATA
técnica basada en defectos
NO APLICA
defect‐based technique
796.
ATA
técnica basada en la especificación
técnica basada en especificación
specification‐based technique
See black box test design technique.
NO APLICA.
797.
ATT
técnica basada en la estructura
técnicas basadas en la estructura
structure‐based technique:
See white‐box test design technique.
NO APLICA.
798.
ATA
técnica basada en la experiencia
técnica basada en la experiencia
experience‐based technique
See experience‐based test design technique.
NO APLICA.
799.
técnica de caja blanca
técnicas de caja blanca
white‐box technique:
See white‐box test design technique.
NO APLICA.
800.
técnica de caja negra
técnica de caja negra
black box technique
See black box test design technique.
NO APLICA.
801.
técnica de diseño de caso de prueba
técnica de diseño de casos de prueba
test case design technique
See test design technique.
NO APLICA.
802.
F
técnica de diseño de prueba
técnica de diseño de prueba
test design technique
Procedure used to derive and/or select test cases.
NO APLICA.
803.
ATA
técnica de diseño de prueba basada en defectos
NO APLICA
defect‐based test design technique
804.
técnica de diseño de prueba basada en la especificación
técnica de diseño de pruebas basada en la especificación
specification‐based test design technique
See defect‐based test design technique.
NO APLICA.
A procedure to derive and/or select test cases targeted at one or more defect types, with tests being developed from NO APLICA. what is known about the specific defect type. See also defect taxonomy. See black box test design technique.
NO APLICA.
805.
806.
807.
808.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
técnica de diseño de prueba basada en la estructura
NO APLICA
structure‐based test design technique
técnica de diseño de prueba basada en la experiencia
técnica de diseño de pruebas basada en la experiencia
experience‐based test design technique
técnica de diseño de prueba de caja blanca
NO APLICA
white‐box test design technique
técnica de diseño de prueba de caja negra:
técnica de diseño de prueba de caja negra
black box test design technique
Procedure to derive and/or select test cases based on an analysis of the specification, either functional or non‐ functional, of a component or system without reference to its internal structure.
NO APLICA.
structural test design technique
See white‐box test design technique.
NO APLICA.
F ATA F ATT F ATA
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
See white‐box test design technique.
NO APLICA.
Procedure to derive and/or select test cases based on the tester’s experience, knowledge and intuition.
NO APLICA.
Procedure to derive and/or select test cases based on an NO APLICA. analysis of the internal structure of a component or system.
809.
técnica de diseño de prueba estructural
técnica de diseño de prueba estructural
810.
técnica de diseño de prueba funcional
técnica de diseño de prueba funcional
811.
técnica de diseño de prueba no funcional
técnicas de diseño de pruebas no funcionales
812.
técnica de ejecución de prueba
técnica de ejecución de pruebas
test execution technique
813.
técnica de especificación de prueba
técnica de especificación de prueba
test specification technique
See test design technique.
NO APLICA.
814.
técnica de prueba
técnica de prueba
test technique
See test design technique.
NO APLICA.
815.
ATM
Test Maturity Model
NO APLICA
Test Maturity Model
Procedure to derive and/or select test cases based on an analysis of the specification of the functionality of a NO APLICA. component or system without reference to its internal structure. See also black box test design technique. Procedure to derive and/or select test cases for non‐ non‐functional test design functional testing based on an analysis of the specification of NO APLICA. technique a component or system without reference to its internal structure. See also black box test design technique. functional test design technique
The method used to perform the actual test execution, either NO APLICA. manual or automated.
A five level staged framework for test process improvement, related to the Capability Maturity Model Integration (CMMI), NO APLICA. that describes the key elements of an effective test process.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
EITP
integration
816.
TGP
NO APLICA
TDD
817.
Tiempo Medio de Reparación
NO APLICA
Mean Time To Repair
818.
Tiempo Medio Entre Fallos
NO APLICA
Mean Time Between Failures
819.
tipo de defecto
NO APLICA
defect type
820.
tipo de prueba
tipo de prueba
test type
821.
tipo de riesgo
NO APLICA
risk type
822.
TMDR
NO APLICA
MTTR
See Mean Time To Repair.
NO APLICA.
823.
TMEF
NO APLICA
MTBF
See Mean Time Between Failures.
NO APLICA.
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
integration See test‐driven development.
NO APLICA.
The arithmetic mean (average) time a system will take to recover from any failure. This typically includes testing to NO APLICA. insure that the defect has been resolved. The arithmetic mean (average) time between failures of a system. The MTBF is typically part of a reliability growth model that assumes the failed system is immediately repaired, as a part of a defect fixing process. See also reliability growth model. An element in a taxonomy of defects. Defect taxonomies can be identified with respect to a variety of considerations, including, but not limited to: ‐ Phase or development activity in which the defect is created, e.g., a specification error or a coding error ‐ Characterization of defects, e.g., an “off‐by‐one” defect ‐ Incorrectness, e.g., an incorrect relational operator, a programming language syntax error, or an invalid assumption ‐ Performance issues, e.g., excessive execution time, insufficient availability. 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. A test type may take place on one or more test levels or test phases. [After TMap] A set of risks grouped by one or more common factors such as a quality attribute, cause, location, or potential effect of risk;. A specific set of product risk types is related to the type of testing that can mitigate (control) that risk type. For example the risk of user‐interactions being misunderstood can be mitigated by usability testing.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
824.
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
TMMi
NO APLICA
TMMi
EITP
825.
tolerancia a errores
tolerancia al error
error tolerance
826.
tolerancia a faltas
tolerancia a faltas
fault tolerance
TPI Next
NO APLICA
TPI Next
827.
ATM
TÉRMINO TRADUCIDO
ATM EITP
828.
transición de estado
transición de estado
state transition
829.
tratamiento de excepciones
tratamiento de excepciones
exception handling
830.
F
trazabilidad
trazabilidad
traceability
831.
trazabilidad horizontal
trazabilidad horizontal
horizontal traceability
832.
trazabilidad vertical
trazabilidad vertical
vertical traceability
U
833.
unidad
unidad
unit
834.
usabilidad
usabilidad
usability
835.
utilización de recursos
utilización de recursos
resource utilization
DESCRIPCIÓN EN INGLÉS
See Test Maturity Model integration.
OBSERVACIONES
NO APLICA.
The ability of a system or component to continue normal operation despite the presence of erroneous inputs. [After NO APLICA. IEEE 610]. The capability of the software product to maintain a specified level of performance in cases of software faults (defects) or NO APLICA. of infringement of its specified interface. [ISO 9126] See also reliability, robustness. A continuous business‐driven framework for test process improvement that describes the key elements of an effective NO APLICA. and efficient test process. A transition between two states of a component or system. Behavior of a component or system in response to erroneous input, from either a human user or from another component or system, or to an internal failure. The ability to identify related items in documentation and software, such as requirements with associated tests. See also horizontal traceability, vertical traceability. The tracing of requirements for a test level through the layers of test documentation (e.g. test plan, test design specification, test case specification and test procedure specification or test script). The tracing of requirements through the layers of development documentation to components.
NO APLICA. NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
See component.
NO APLICA.
The capability of the software to be understood, learned, used and attractive to the user when used under specified NO APLICA. conditions. [ISO 9126] The capability of the software product to use appropriate NO APLICA. amounts and types of resources, for example the amounts of
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions. [After ISO 9126] See also efficiency.
V
836.
F
validación
validación
validation
837.
valor de entrada
valor de entrada
input value
838.
valor de salida
valor de salida
output value
Confirmation by examination and through provision of objective evidence that the requirements for a specific NO APLICA. intended use or application have been fulfilled. [ISO 9000] An instance of an input. See also input.
NO APLICA.
An instance of an output. See also output.
NO APLICA.
An input value or output value which is on the edge of an equivalence partition or at the smallest incremental NO APLICA. distance on either side of an edge, for example the minimum or maximum value of a range. An element of storage in a computer that is accessible by a NO APLICA. software program by referring to it by a name.
839.
valor frontera
valor límite
boundary value
840.
variable
variable
variable
verificación
verificación
verification
W
X
Y
Z
841.
F ETAE
Confirmation by examination and through provision of objective evidence that ETAE specified requirements have NO APLICA. been fulfilled. [ISO 9000]
Tabla 5 – Traducción ordenada por los términos en español (“TÉRMINO TRADUCIDO”)
3
TRADUCCIÓN INGLÉS / ESPAÑOL (ORDENADA POR TÉRMINOS EN INGLÉS)
La siguiente tabla está ordenada por orden alfabético de los términos en inglés. En la columna “TÉRMINO TRADUCIDO” encuentra la traducción para cada “TÉRMINO EN INGLÉS” correspondiente al “ISTQB ‐ Glossary, Standard Glossary of Terms used in Software Testing, Version 2.4 [REF 001]”. La columna “TRADUCCIÓN PREVIA” corresponde a traducciones anteriores de los mismos términos (si aplica, es decir si en término no es nuevo). En la columna “PROGRAMA DE ESTUDIOS” se identifican los programas de estudios para los que un término es palabra clave. En esta versión del glosario no se traduce la descripción del término, por lo que sólo se encuentra la “DESCRIPCIÓN EN INGLÉS”.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
A
1.
caso de prueba abstracto
caso de prueba abstracto
2.
aceptación
3.
F‐AT
criterios de aceptación
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
abstract test case
See high level test case.
NO APLICA.
aceptación
acceptance
See acceptance testing.
NO APLICA.
criterios de aceptación
acceptance criteria
The exit criteria that a component or system must satisfy in order to be accepted by a user, customer, or other authorized entity. [IEEE 610]
NO APLICA.
NO APLICA.
NO APLICA.
4.
pruebas de aceptación
pruebas de aceptación
acceptance testing
Formal testing with respect to 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 determine whether or not to accept the system. [After IEEE 610]
5.
ATA
pruebas de accesibilidad
pruebas de accesibilidad
accessibility testing
Testing to determine the ease by which users with disabilities can use a component or system. [Gerrard]
6.
exactitud
exactitud
accuracy
7.
ATA
pruebas de exactitud
NO APLICA
accuracy testing:
The capability of the software product to provide the right or agreed results or effects with the needed degree of precision. [ISO 9126] See also functionality. The process of testing to determine the accuracy of a software product. See also accuracy.
NO APLICA. NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS The phase within the IDEAL model where the improvements are developed, put into practice, and deployed across the organization. The acting phase consists of the activities: create solution, pilot/test solution, refine solution and implement solution. See also IDEAL.
NO APLICA.
See keyword‐driven testing.
NO APLICA.
User or any other person or system that interacts with the system under test in a specific way.
NO APLICA.
See actual result.
NO APLICA.
The behavior produced/observed when a component or system is tested.
NO APLICA.
See informal review.
NO APLICA.
8.
EITP
acción (IDEAL)
NO APLICA
acting (IDEAL)
9.
pruebas guiadas por palabra de acción
pruebas guiadas por palabra de acción
action word driven testing
10.
actor
NO APLICA
actor
11.
resultado real
resultado real
actual outcome
12.
resultado real
resultado real
actual result
13.
revisión ad hoc
revisión ad hoc
ad hoc review
14.
pruebas ad hoc
pruebas ad hoc
ad hoc testing
15.
ATT
adaptabilidad
adaptabilidad
adaptability
16.
F‐AT
manifiesto ágil
NO APLICA
agile manifesto
F‐AT
desarrollo ágil de software
NO APLICA
agile software development
17.
TÉRMINO TRADUCIDO
EITP
Testing carried out informally; no formal test preparation takes place, no recognized test design technique is used, there are no expectations for results and arbitrariness guides the test execution activity. The capability of the software product to be adapted for different specified environments without applying actions or means other than those provided for this purpose for the software considered. [ISO 9126] See also portability. A statement on the values that underpin agile software development. The values are: ‐ individuals and interactions over processes and tools ‐ working software over comprehensive documentation ‐ customer collaboration over contract negotiation ‐ responding to change over following a plan. A group of software development methodologies based on iterative incremental development, where requirements and solutions evolve through collaboration between self‐ organizing cross‐functional teams.
OBSERVACIONES
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS Testing practice for a project using agile software development methodologies, incorporating techniques and methods, such as extreme programming (XP), treating development as the customer of testing and emphasizing the test‐first design paradigm. See also test‐driven development.
NO APLICA.
[TMap] See branch testing.
NO APLICA.
18.
EITP
pruebas ágiles
pruebas ágiles
agile testing
19.
prueba de algoritmo
pruebas algorítmicas [TMap]
algorithm test
20.
F
pruebas alfa
pruebas alfa
alpha testing
21.
ETM
pruebas analíticas
NO APLICA
analytical testing
22.
ATT
capacidad de ser analizado
analizabilidad
analyzability
23.
analizador:
analizador
analyzer
24.
ATM
anomalía
anomalía
anomaly
25.
ATT
anti‐patrón:
NO APLICA
anti‐pattern:
26.
API
NO APLICA
API
27.
ETAE
pruebas de API
NO APLICA
API testing
Simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site, but outside the development organization. Alpha testing is often employed for off‐the‐shelf software as a form of internal acceptance testing. Testing based on a systematic analysis of e.g., product risks or requirements. The capability of the software product to be diagnosed for deficiencies or causes of failures in the software, or for the parts to be modified to be identified. [ISO 9126] See also maintainability. See static analyzer. Any condition that deviates from expectation based on requirements specifications, design documents, user documents, standards, etc. or from someone’s perception or experience. Anomalies may be found during, but not limited to, reviewing, testing, analysis, compilation, or use of software products or applicable documentation. [IEEE 1044] See also bug, defect, deviation, error, fault, failure, incident, problem. Repeated action, process, structure or reusable solution that initially appears to be beneficial and is commonly used but is ineffective and/or counterproductive in practice.
OBSERVACIONES
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
Acronym for Application Programming Interface.
NO APLICA.
Testing performed by submitting commands to the software under test using programming interfaces of the application directly.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
28.
pruebas de arco
pruebas de arco
arc testing
29.
EITP
informe de evaluación
NO APLICA
assessment report
30.
EITP
evaluador
NO APLICA
assessor
31.
ATT
condición atómica
NO APLICA
atomic condition
32.
F
ataque
NO APLICA
attack
33.
pruebas basadas en ataques
NO APLICA
attack‐based testing
34.
ATA
atractivo
atractivo
attractiveness
35.
ATM
auditoría
auditoría
audit
36.
rastro de auditoría
rastro de auditoría
audit trail
37.
productos de prueba automatizados
producto de soporte de pruebas automatizadas
automated testware
38.
disponibilidad
disponibilidad
availability
DESCRIPCIÓN EN INGLÉS See branch testing. A document summarizing the assessment results, e.g. conclusions, recommendations and findings. See also process assessment. A person who conducts an assessment; any member of an assessment team. A condition that cannot be decomposed, i.e., a condition that does not contain two or more single conditions joined by a logical operator (AND, OR, XOR). Directed and focused attempt to evaluate the quality, especially reliability, of a test object by attempting to force specific failures to occur. See also negative testing. An experience‐based testing technique that uses software attacks to induce failures, particularly security related failures. See also attack. The capability of the software product to be attractive to the user. [ISO 9126] See also usability. An independent evaluation of software products or processes to ascertain compliance to standards, guidelines, specifications, and/or procedures based on objective criteria, including documents that specify: (4) the form or content of the products to be produced (5) the process by which the products shall be produced (6) how compliance to standards or guidelines shall be measured. [IEEE 1028] A path by which the original input to a process (e.g. data) can be traced back through the process, taking the process output as a starting point. This facilitates defect analysis and allows a process audit to be carried out. [After TMap]
OBSERVACIONES NO APLICA. NO APLICA. NO APLICA. NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
Testware used in automated testing, such as tool scripts.
NO APLICA.
The degree to which a component or system is operational and accessible when required for use. Often expressed as a
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
percentage. [IEEE 610]
B
39.
pruebas contiguas
pruebas secuenciadas
back‐to‐back testing
40.
EITP
cuadro de mando integral
NO APLICA
balanced scorecard
41.
línea base
línea base
baseline
42.
bloque básico
bloque básico
basic block
43.
conjunto de pruebas base
conjunto de pruebas base
basis test set
44.
bebugging
bebugging
bebugging
45.
comportamiento
comportamiento
behavior
46.
prueba comparativa
prueba comparativa
benchmark test
47.
software a medida
software a medida
bespoke software
Testing in which two or more variants of a component or system are executed with the same inputs, the outputs compared, and analyzed in cases of discrepancies. [IEEE 610] A strategic tool for measuring whether the operational activities of a company are aligned with its objectives in terms of business vision and strategy. See also corporate dashboard, scorecard. A specification or software product that has been formally reviewed or agreed upon, that thereafter serves as the basis for further development, and that can be changed only through a formal change control process. [After IEEE 610] A sequence of one or more consecutive executable statements containing no branches. Note: A node in a control flow graph represents a basic block.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
A set of test cases derived from the internal structure of a component or specification to ensure that 100% of a specified coverage criterion will be achieved.
NO APLICA.
[Abbott] See fault seeding.
NO APLICA.
The response of a component or system to a set of input values and preconditions.
NO APLICA.
(1) A standard against which measurements or comparisons can be made. (2) A test that is be used to compare components or systems to each other or to a standard as in (1). [After IEEE 610] Software developed specifically for a set of users or customers. The opposite is off‐the‐shelf software.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
48.
buena práctica
mejor práctica
best practice
49.
F
pruebas beta
pruebas beta
beta testing
50.
pruebas en big‐bang
pruebas tipo big‐bang
big‐bang testing
51.
técnica de caja negra
técnica de caja negra
black box technique
F ATA
técnica de diseño de prueba de caja negra:
técnica de diseño de prueba de caja negra
black box test design technique
53.
F
pruebas de caja negra
pruebas de caja negra
black box testing:
54.
caso de prueba bloqueado
caso de prueba bloqueado
blocked test case
52.
TÉRMINO TRADUCIDO
55.
pruebas ascendentes
pruebas ascendentes
bottom‐up testing
56.
valor frontera
valor límite
boundary value
DESCRIPCIÓN EN INGLÉS A superior method or innovative practice that contributes to the improved performance of an organization under given context, usually recognized as ‘best’ by other peer organizations. 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 is often employed as a form of external acceptance testing for off‐ the‐shelf software in order to acquire feedback from the market. An integration testing approach in which software elements, hardware elements, or both are combined all at once into a component or an overall system, rather than in stages. [After IEEE 610] See also integration testing. See black box test design technique. Procedure to derive and/or select test cases based on an analysis of the specification, either functional or non‐ functional, of a component or system without reference to its internal structure. Testing, either functional or non‐functional, without reference to the internal structure of the component or system. A test case that cannot be executed because the preconditions for its execution are not fulfilled. An incremental approach to integration testing where the lowest level components are tested first, and then used to facilitate the testing of higher level components. This process is repeated until the component at the top of the hierarchy is tested. See also integration testing. An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either side of an edge, for example the minimum or maximum value of a range.
OBSERVACIONES
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
57.
F ATA
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
análisis de valores frontera
análisis de valores límite
boundary value analysis
A black box test design technique in which test cases are designed based on boundary values. See also boundary value.
NO APLICA.
The percentage of boundary values that have been exercised by a test suite.
NO APLICA.
See boundary value analysis.
NO APLICA.
A basic block that can be selected for execution based on a program construct in which one of two or more alternative program paths is available, e.g. case, jump, go to, if‐then‐ else.
NO APLICA.
See condition.
NO APLICA.
See multiple condition coverage.
NO APLICA.
See multiple condition testing.
NO APLICA.
See condition coverage.
NO APLICA.
58.
cobertura de valores frontera
cobertura de valores límite
boundary value coverage
59.
pruebas de valores frontera
pruebas de valores límite
boundary value testing
60.
rama
rama
branch
61.
condición de rama
condición de rama
branch condition
62.
cobertura de combinaciones de condiciones de rama
cobertura de condición combinada de rama
branch condition combination coverage
63.
pruebas de combinaciones de condiciones de rama
pruebas de condición combinada de rama
branch condition combination testing
64.
cobertura de condiciones de rama:
cobertura de condición de rama
branch condition coverage
65.
cobertura de ramas
cobertura de rama
branch coverage
66.
pruebas de rama
pruebas de rama
branch testing
67.
memoria intermedia
NO APLICA
buffer
The percentage of branches that have been exercised by a test suite. 100% branch coverage implies both 100% decision coverage and 100% statement coverage. A white box test design technique in which test cases are designed to execute branches. A device or storage area used to store data temporarily for differences in rates of data flow, time or occurrence of events, or amounts of data that can be handled by the devices or processes involved in the transfer or use of the data. [IEEE 610]
OBSERVACIONES
NO APLICA. NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
68.
desbordamiento de memoria intermedia
69.
F
70.
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
NO APLICA
buffer overflow
A memory access failure due to the attempt by a process to store data beyond the boundaries of a fixed length buffer, resulting in overwriting of adjacent memory areas or the raising of an overflow exception. See also buffer.
NO APLICA.
bug
bug
bug
See defect.
NO APLICA.
informe de bug
informe de bugs
bug report
See defect report.
NO APLICA.
71.
taxonomía de bugs
NO APLICA
bug taxonomy
See defect taxonomy.
NO APLICA.
72.
herramienta de seguimiento de bugs:
herramienta de seguimiento de bugs
bug tracking tool
See defect management tool.
NO APLICA.
73.
F‐AT
prueba de verificación de la compilación
NO APLICA
build verification test
74.
diagrama de trabajo pendiente
NO APLICA
burndown chart
75.
pruebas basadas en procesos de negocio:
pruebas basadas en el proceso de negocio
business process‐based testing
76.
PVC
NO APLICA
BVT
C
77.
grafo de llamadas
NO APLICA
78.
ATM
Capability Maturity Model
Capability Maturity Model
TRADUCCIÓN PREVIA
A set of automated tests which validates the integrity of each new build and verifies its key/core functionality, stability and testability. It is an industry practice when a high frequency of build releases occurs (e.g., agile projects) and it is run on every new build before the build is released for further testing. See also regression testing, smoke test. A publicly displayed chart that depicts the outstanding effort versus time in an iteration. It shows the status and trend of completing the tasks of the iteration. The X‐axis typically represents days in the sprint, while the Y‐axis is the remaining effort (usually either in ideal engineering hours or story points). An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes.
OBSERVACIONES
NO APLICA.
NO APLICA.
NO APLICA.
See build verification test.
NO APLICA.
call graph
An abstract representation of calling relationships between subroutines in a program.
NO APLICA.
Capability Maturity Model
A framework that describes the key elements of an EITP
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
EITP
Integration (CMMI)
Integration (CMMI)
Integration (CMMI)
effective product development and maintenance process. The Capability Maturity Model Integration covers best‐ practices for planning, engineering and managing product development and maintenance. [CMMI]
79.
ETAE
captura/reproducción
NO APLICA
capture/playback
80.
ATT
herramienta de captura/reproducción
herramienta de captura/reproducción
capture/playback tool
81.
herramienta de captura/repetición
herramienta de captura/repetición
capture/replay tool
82.
CASE
CASE
83.
CAST
84.
EITP
85. 86.
A test automation approach, where inputs to the test object are recorded during manual testing in order to generate automated test scripts that could be executed later (i.e. replayed). A type of test execution tool where inputs are recorded during manual testing in order to generate automated test scripts that can be executed later (i.e. replayed). These tools are often used to support automated regression testing.
OBSERVACIONES
NO APLICA.
NO APLICA.
See capture/playback tool.
NO APLICA.
CASE
Acronym for Computer Aided Software Engineering.
NO APLICA.
CAST
CAST
Acronym for Computer Aided Software Testing. See also test automation.
NO APLICA.
análisis causal
NO APLICA
causal analysis
The analysis of defects to determine their root cause. [CMMI]
NO APLICA.
análisis causa‐efecto
análisis causa‐efecto
cause‐effect analysis
See cause‐effect graphing.
NO APLICA.
tabla de decisión causa‐ efecto
tabla de decisión causa‐ efecto
cause‐effect decision table
See decision table.
NO APLICA.
87.
EITP
diagrama causa‐efecto
NO APLICA
cause‐effect diagram
88.
EITP
gráfico causa‐efecto
gráfico causa‐efecto
cause‐effect graph
A graphical representation used to organize and display the interrelationships of various possible root causes of a problem. Possible causes of a real or potential defect or failure are organized in categories and subcategories in a horizontal tree‐structure, with the (potential) defect or failure as the root node. [After Juran] A graphical representation of inputs and/or stimuli (causes) with their associated outputs (effects), which can be used
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
to design test cases.
89.
ATA
representación causa‐ efecto
representación causa‐ efecto
cause‐effect graphing
A black box test design technique in which test cases are designed from cause‐effect graphs. [BS 7925/2]
NO APLICA.
90.
certificación
certificación
certification
The process of confirming that a component, system or person complies with its specified requirements, e.g. by passing an exam.
NO APLICA.
91.
control del cambio
control de cambios
change control
See configuration control.
NO APLICA.
92.
comité de control del cambio
comité de control de cambio
change control board
See configuration control board.
NO APLICA.
(1) A structured approach to transitioning individuals, and organizations from a current state to a desired future state. (2) Controlled way to effect a change, or a proposed change, to a product or service. See also configuration management. The capability of the software product to enable specified modifications to be implemented. [ISO 9126] See also maintainability.
93.
EITP
gestión del cambio
NO APLICA
change management
94.
ATT
capacidad para ser modificado
modificabilidad
changeability
95.
carta
NO APLICA
charter
See test charter.
NO APLICA.
96.
comprobador
evaluador
checker
See reviewer.
NO APLICA.
97.
ATA
pruebas basadas en listas de comprobación
NO APLICA
checklist‐based testing
An experience‐based test design technique whereby the experienced tester uses a high‐level list of items to be noted, checked, or remembered, or a set of rules or criteria against which a product has to be verified.
NO APLICA.
98.
métricas de cobertura de Chow
métricas de cobertura de Chow
Chow's coverage metrics
See N‐switch coverage. [Chow]
NO APLICA.
99.
árbol de clasificación
NO APLICA
classification tree
100.
ATA
método del árbol de
método de árbol de
classification tree method
A tree showing equivalence partitions hierarchically ordered, which is used to design test cases in the classification tree method. See also classification tree method. A black box test design technique in which test cases, described by means of a classification tree, are designed to
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
clasificación:
clasificación
TÉRMINO EN INGLÉS
pruebas de caja transparente
NO APLICA
clear‐box testing
102.
CLI
NO APLICA
103.
ILC
104.
ETAE ATM EITP
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
execute combinations of representatives of input and/or output domains. [Grochtmann] See also combinatorial testing.
101.
105.
See white‐box testing.
NO APLICA.
CLI
Acronym for Command‐Line Interface.
NO APLICA.
NO APLICA
CLI
Acrónimo para Interface de Línea de Comando.
Traducción de “CLI”.
Pruebas ILC
NO APLICA
CLI testing
Testing performed by submitting commands to the software under test using a dedicated command‐line interface.
NO APLICA.
CMMI
NO APLICA
CMMI
See Capability Maturity Model Integration.
NO APLICA.
Computer instructions and data definitions expressed in a programming language or in a form output by an assembler, compiler or other translator. [IEEE 610]
NO APLICA.
106.
código
código
code
107.
analizador de código
analizador de código
code analyzer
See static code analyzer.
NO APLICA.
An analysis method that determines which parts of the software have been executed (covered) by the test suite and which parts have not been executed, e.g. statement coverage, decision coverage or condition coverage.
NO APLICA.
See white box testing.
NO APLICA.
Excessive emotional or psychological dependence on another person, specifically in trying to change that person’s current (undesirable) behavior while supporting them in continuing that behavior. For example, in software testing, complaining about late delivery to test and yet enjoying the necessary “heroism” working additional hours to make up time when delivery is running late, therefore reinforcing the lateness.
NO APLICA.
108.
F
cobertura de código
cobertura de código
code coverage
109.
pruebas basadas en el código
pruebas basadas en código
code‐based testing
110.
TÉRMINO TRADUCIDO
EITP
comportamiento codependiente
NO APLICA
codependent behavior
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
111.
ATT
coexistencia
coexistencia
co‐existence
112.
ATA
pruebas combinatorias
NO APLICA
combinatorial testing
113.
F
software comercial de distribución masiva
software comercial de distribución masiva
Commercial Off‐The‐Shelf software
114.
comparador
comparador
comparator
115.
pruebas de compatibilidad
pruebas de compatibilidad
compatibility testing
116.
F
compilador
compilador
compiler
117.
pruebas completas
pruebas completas
complete testing
118.
criterios de compleción
criterios de compleción
completion criteria
119.
F
complejidad
complejidad
complexity
120.
cumplimiento
cumplimiento
compliance
121.
pruebas de cumplimiento
pruebas de cumplimiento
compliance testing
122.
componente
componente
component
DESCRIPCIÓN EN INGLÉS The capability of the software product to co‐exist with other independent software in a common environment sharing common resources. [ISO 9126] See also portability. A means to identify a suitable subset of test combinations to achieve a predetermined level of coverage when testing an object with multiple parameters and where those parameters themselves each have several values, which gives rise to more combinations than are feasible to test in the time allowed. See also classification tree method, n‐ wise testing, pairwise testing, orthogonal array testing.
OBSERVACIONES
NO APLICA.
NO APLICA.
See off‐the‐shelf software.
NO APLICA.
See test comparator.
NO APLICA.
See interoperability testing.
NO APLICA.
A software tool that translates programs expressed in a high order language into their machine language equivalents. [IEEE 610]
NO APLICA.
See exhaustive testing.
NO APLICA.
See exit criteria.
NO APLICA.
The degree to which a component or system has a design and/or internal structure that is difficult to understand, maintain and verify. See also cyclomatic complexity. The capability of the software product to adhere to standards, conventions or regulations in laws and similar prescriptions. [ISO 9126]
NO APLICA.
NO APLICA.
The process of testing to determine the compliance of the component or system.
NO APLICA.
A minimal software item that can be tested in isolation.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
pruebas de integración de componente
pruebas de integración de componente
component integration testing
Testing performed to expose defects in the interfaces and interaction between integrated components.
NO APLICA.
124.
especificación de componente
especificación de componente
component specification
A description of a component’s function in terms of its output values for specified input values under specified conditions, and required non‐functional behavior (e.g. resource‐utilization).
NO APLICA.
125.
F
pruebas de componente
pruebas de componente
component testing
The testing of individual software components. [After IEEE 610]
NO APLICA.
126.
condición compuesta
condición compuesta
compound condition
Two or more single conditions joined by means of a logical operator (AND, OR or XOR), e.g. ‘A>B AND C>1000’.
NO APLICA.
127.
ATA
caso de prueba concreto
caso de prueba concreto
concrete test case
See low level test case.
NO APLICA.
123.
OBSERVACIONES
Testing to determine how the occurrence of two or more activities within the same interval of time, achieved either by NO APLICA. interleaving the activities or by simultaneous execution, is handled by the component or system. [After IEEE 610] A logical expression that can be evaluated as True or False, NO APLICA. e.g. A>B. See also condition testing.
128.
pruebas de concurrencia
pruebas de concurrencia
concurrency testing
129.
condición
condición
condition
130.
cobertura de combinaciones de condiciones
cobertura de condición combinada
condition combination coverage
See multiple condition coverage.
NO APLICA.
131.
pruebas de combinaciones de condiciones
pruebas de condición combinada
condition combination testing
See multiple condition testing.
NO APLICA.
132.
cobertura de condiciones
cobertura de condición
condition coverage
133.
cobertura de determinación de condiciones
cobertura de determinación de condición
condition determination coverage
The percentage of condition outcomes that have been exercised by a test suite. 100% condition coverage requires NO APLICA. each single condition in every decision statement to be tested as True and False. See modified condition decision coverage.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
134.
pruebas de determinación de condiciones
pruebas de determinación de condición
condition determination testing
135.
resultado de la condición
resultado de condición
condition outcome
136.
ATT
pruebas de condición
pruebas de condición
condition testing
137.
ETM
intervalo de confianza
NO APLICA
confidence interval
138.
prueba de confianza
prueba de confianza
confidence test
139.
configuración
configuración
configuration
The composition of a component or system as defined by the number, nature, and interconnections of its constituent NO APLICA. parts.
140.
auditoría de la configuración
auditoría de la configuración
configuration auditing
The function to check on the contents of libraries of NO APLICA. configuration items, e.g. for standards compliance. [IEEE 610]
141.
control de la configuración
control de la configuración
configuration control
142.
comité de control de la configuración (CCC)
comité de control de la configuración (CCC)
configuration control board (CCB)
143.
identificación de la configuración
identificación de la configuración
configuration identification
144.
F‐AT
elemento de la configuración
elemento de la configuración
configuration item
145.
F
gestión de la
gestión de la
configuration
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
See modified condition decision testing.
NO APLICA.
The evaluation of a condition to True or False.
NO APLICA.
A white box test design technique in which test cases are NO APLICA. designed to execute condition outcomes. In managing project risks, the period of time within which a contingency action must be implemented in order to be NO APLICA. effective in reducing the impact of the risk. See smoke test.
An element of configuration management, consisting of the evaluation, coordination, approval or disapproval, and implementation of changes to configuration items after formal establishment of their configuration identification. [IEEE 610] A group of people responsible for evaluating and approving or disapproving proposed changes to configuration items, and for ensuring implementation of approved changes. [IEEE 610] An element of configuration management, consisting of selecting the configuration items for a system and recording their functional and physical characteristics in technical documentation. [IEEE 610] An aggregation of hardware, software or both, that is designated for configuration management and treated as a single entity in the configuration management process. [IEEE 610] A discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item, control
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
F‐AT
configuración
configuración
management
146.
F
herramienta de gestión de la configuración
herramienta de gestión de la configuración
configuration management tool
147.
pruebas de configuración
pruebas de configuración
configuration testing
148.
F
pruebas de confirmación
pruebas de confirmación
confirmation testing
149.
pruebas de conformidad
pruebas de conformidad
conformance testing
150.
consistencia
consistencia
consistency
151.
ETM
pruebas consultivas
NO APLICA
consultative testing
152.
EITP
modelo basado en el contenido:
NO APLICA
content reference model
See content‐based model.
NO APLICA.
153.
modelo de referencia de contenido
NO APLICA
content reference model
See content‐based model.
NO APLICA.
154.
EITP
modelo basado en el contenido
NO APLICA
content‐based model
155.
EITP
representación continua
NO APLICA
continuous representation
156.
ETM
gráfico de control
NO APLICA
control chart
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
changes to those characteristics, record and report change processing and implementation status, and verify compliance with specified requirements. [IEEE 610] A tool that provides support for the identification and control of configuration items, their status over changes and NO APLICA. versions, and the release of baselines consisting of configuration items. See portability testing.
NO APLICA.
Testing that runs test cases that failed the last time they NO APLICA. were run, in order to verify the success of corrective actions. See compliance testing.
NO APLICA.
The degree of uniformity, standardization, and freedom from contradiction among the documents or parts of a component NO APLICA. or system. [IEEE 610] Testing driven by the advice and guidance of appropriate experts from outside the test team (e.g., technology experts NO APLICA. and/or business domain experts).
A process model providing a detailed description of good NO APLICA. engineering practices, e.g. test practices. A capability maturity model structure wherein capability levels provide a recommended order for approaching process NO APLICA. improvement within specified process areas. [CMMI] A statistical process control tool used to monitor a process and determine whether it is statistically controlled. It graphically depicts the average value and the upper and NO APLICA. lower control limits (the highest and lowest values) of a process.
157.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
F
flujo de control
flujo de control
control flow
A sequence of events (paths) in the execution through a component or system.
158.
ATT
análisis del flujo de control
NO APLICA
control flow analysis
159.
grafo del flujo de control
gráfico de flujo de control
control flow graph
160.
camino del flujo de control
camino del flujo de control
control flow path
OBSERVACIONES
NO APLICA.
A form of static analysis based on a representation of unique paths (sequences of events) in the execution through a component or system. Control flow analysis evaluates the NO APLICA. integrity of control flow structures, looking for possible control flow anomalies such as closed loops or logically unreachable process steps. An abstract representation of all possible sequences of events (paths) in the execution through a component or NO APLICA. system. See path.
NO APLICA.
An approach to structure‐based testing in which test cases are designed to execute specific sequences of events. Various techniques exist for control flow testing, e.g., decision NO APLICA. testing, condition testing, and path testing, that each have their specific approach and level of control flow coverage. See also decision testing, condition testing, path testing. A metric that shows progress toward a defined criterion, e.g., convergence of the total number of test executed to the total NO APLICA. number of tests planned for execution. Testing of software used to convert data from existing NO APLICA. systems for use in replacement systems.
161.
ATT
pruebas de flujo de control:
NO APLICA
control flow testing
162.
ETM
métrica de convergencia
NO APLICA
convergence metric
163.
pruebas de conversión
pruebas de conversión
conversion testing
164.
EITP
panel de control corporativo
NO APLICA
corporate dashboard
A dashboard‐style representation of the status of corporate NO APLICA. performance data. See also balanced scorecard, dashboard.
165.
coste de la calidad
NO APLICA
cost of quality:
The total costs incurred on quality activities and issues and often split into prevention costs, appraisal costs, internal NO APLICA. failure costs and external failure costs.
166.
F
COTS
COTS
COTS
167.
ETAE
cobertura
cobertura
coverage
Acronym for Commercial Off‐The‐Shelf software. See off‐ the‐shelf software.
NO APLICA.
The degree, expressed as a percentage, to which a specified NO APLICA. coverage item has been exercised by a test suite.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
168.
análisis de cobertura
análisis de cobertura
coverage analysis
169.
elemento de cobertura
elemento de cobertura
coverage item
170.
herramienta de medición de la cobertura
herramienta de medición de cobertura
coverage measurement tool
171.
F
herramienta de cobertura
herramienta de cobertura
coverage tool
172.
EITP
factor crítico de éxito
NO APLICA
critical success factor
Critical Testing Processes
NO APLICA
Critical Testing Processes
CTP
NO APLICA
CTP
173.
174.
TÉRMINO TRADUCIDO
ATM EITP
ATM EITP
175.
software a medida
software a medida
custom software
176.
ATM
herramienta a medida
NO APLICA
custom tool
177.
ATT
complejidad ciclomática
complejidad ciclomática
cyclomatic complexity
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
Measurement of achieved coverage to a specified coverage item during test execution referring to predetermined NO APLICA. criteria to determine whether additional testing is required and if so, which test cases are needed. An entity or property used as a basis for test coverage, e.g. NO APLICA. equivalence partitions or code statements. See coverage tool.
NO APLICA.
A tool that provides objective measures of what structural elements, e.g. statements, branches have been exercised by NO APLICA. a test suite. An element necessary for an organization or project to achieve its mission. Critical success factors are the critical NO APLICA. factors or activities required for ensuring the success. A content‐based model for test process improvement built around twelve critical processes. These include highly visible processes, by which peers and management judge NO APLICA. competence and mission‐critical processes in which performance affects the company's profits and reputation. See also content‐based model. See Critical Testing Processes.
See bespoke software.
NO APLICA.
NO APLICA.
A software tool developed specifically for a set of users or NO APLICA. customers. The maximum number of linear, independent paths through a program. Cyclomatic complexity may be computed as: L – N + 2P, where NO APLICA. ‐ L = the number of edges/links in a graph ‐ N = the number of nodes in a graph ‐ P = the number of disconnected parts of the graph (e.g. a called graph or subroutine)
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
[After McCabe] 178.
179.
número ciclomático
número ciclomático
cyclomatic number
D
compilación diaria
construcción diaria
See cyclomatic complexity.
NO APLICA.
daily build
Actividad diaria de desarrollo en la que un sistema completo se compila y enlaza (normalmente durante la noche), de modo que un sistema consistente esté disponible en cualquier momento incluyendo la totalidad de los últimos cambios.
NO APLICA.
NO APLICA.
NO APLICA.
180.
ETM
panel de control
NO APLICA
dashboard
A representation of dynamic measurements of operational performance for some organization or activity, using metrics represented via metaphors such as visual ‘dials’, ‘counters’, and other devices resembling those on the dashboard of an automobile, so that the effects of events or activities can be easily understood and related to operational goals. See also corporate dashboard, scorecard.
181.
definición de datos
definición de datos
data definition
An executable statement where a variable is assigned a value.
F 182.
ATT
pruebas guiadas por datos
pruebas guiadas por datos
data driven testing
ETAE
A scripting technique that stores test input and expected results in a table or spreadsheet, so that a single control script can execute all of the tests in the table. Data‐driven NO APLICA. testing is often used to support the application of test execution tools such as capture/playback tools. [Fewster and Graham] See also keyword‐driven testing. An abstract representation of the sequence and possible changes of the state of data objects, where the state of an NO APLICA. object is any of: creation, usage, or destruction. [Beizer]
183.
F
flujo de datos
flujo de datos
data flow
184.
ATT
análisis del flujo de datos
análisis del flujo de datos
data flow analysis
A form of static analysis based on the definition and usage of variables.
NO APLICA.
185.
cobertura del flujo de
cobertura del flujo de
data flow coverage
The percentage of definition‐use pairs that have been
NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
datos
datos
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
exercised by a test suite. A white box test design technique in which test cases are NO APLICA. designed to execute definition‐use pairs of variables.
186.
pruebas del flujo de datos
pruebas de flujo de datos
data flow testing
187.
pruebas de integridad de datos
pruebas de integridad de datos
data integrity testing
188.
calidad de los datos:
NO APLICA
189.
pruebas de integridad de base de datos
pruebas de integridad de base de datos
190.
dd
NO APLICA
dd
191.
camino‐dd
NO APLICA
dd‐path
192.
código muerto:
código muerto
dead code
See unreachable code.
NO APLICA.
193.
depurador:
depurador
debugger
See debugging tool.
NO APLICA.
194.
F
depuración:
depuración
debugging
The process of finding, analyzing and removing the causes of failures in software.
NO APLICA.
F ATT
herramienta de depuración
NO APLICA
debugging tool:
decisión
decisión
decision
195.
196.
TÉRMINO TRADUCIDO
See database integrity testing.
NO APLICA.
An attribute of data that indicates correctness with respect to some pre‐defined criteria, e.g., business expectations, NO APLICA. requirements on data integrity, data consistency. Testing the methods and processes used to access and manage the data (base), to ensure access methods, processes database integrity testing and data rules function as expected and that during access to NO APLICA. the database, data is not corrupted or unexpectedly deleted, updated or created. data quality
Abreviation of "decision‐to‐decision".
Este término no pertenece al glosario original.
A path between two decisions of an algorithm, or two decision nodes of a corresponding graph, that includes no NO APLICA. other decisions. See also path.
A tool used by programmers to reproduce failures, investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute programs NO APLICA. step by step, to halt a program at any program statement and to set and examine program variables. A program point at which the control flow has two or more alternative routes. A node with two or more links to separate NO APLICA. branches.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
197.
cobertura de condiciones‐ decisiones
cobertura de condición de decisión
198.
ATT
pruebas de condiciónes‐ decisiónes
pruebas de condición‐ decisión
199.
F
cobertura de decisiones
cobertura de decisión
200.
resultado de la decisión
resultado de decisión
decision outcome
201.
tabla de decisión
tabla de decisión
decision table
F ATA
pruebas de tabla de decisión
pruebas de tabla de decisión
decision table testing
pruebas de decisión
pruebas de decisión
decision testing
defecto
defecto
defect
categoría del defecto
NO APLICA
defect category
202.
203.
204.
205.
F ATM
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
The percentage of all condition outcomes and decision outcomes that have been exercised by a test suite. 100% NO APLICA. decision condition coverage implies both 100% condition coverage and 100% decision coverage. A white box test design technique in which test cases are decision condition testing designed to execute condition outcomes and decision NO APLICA. outcomes. The percentage of decision outcomes that have been decision coverage exercised by a test suite. 100% decision coverage implies NO APLICA. both 100% branch coverage and 100% statement coverage. decision condition coverage
206.
F
densidad de defectos
densidad de defectos
defect density
207.
EITP
Porcentaje de Detección de Defectos (PDD)
Porcentaje de Detección de Defectos (PDD)
Defect Detection Percentage (DDP)
The result of a decision (which therefore determines the branches to be taken). A table showing combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects), which can be used to design test cases. A black box test design technique in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table. [Veenendaal04] See also decision table. A white box test design technique in which test cases are designed to execute decision outcomes. A flaw in a component or system that can cause the component or system to fail to perform its required function, e.g. an incorrect statement or data definition. A defect, if encountered during execution, may cause a failure of the component or system. See defect type. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms, e.g. lines‐of‐code, number of classes or function points).
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
The number of defects found by a test level, divided by the number found by that test level and any other means NO APLICA. afterwards. See also escaped defects.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
208.
gestión de defectos:
gestión de defectos
defect management
209.
ATM
comité de gestión de defectos
NO APLICA
defect management committee
210.
herramienta de gestión de defectos:
herramienta de gestión de defectos
defect management tool
211.
enmascaramiento de un defecto
enmascaramiento de defectos
defect masking
212.
informe de defecto
informe de defectos
defect report
taxonomía de defectos
NO APLICA
defect taxonomy
213.
ATA
214.
herramienta de seguimiento de defectos
herramienta de seguimiento de defectos
defect tracking tool
215.
ATM
comité de priorización de defectos
NO APLICA
defect triage committee
216.
F‐AT
tipo de defecto
NO APLICA
defect type
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
The process of recognizing, investigating, taking action and disposing of defects. It involves recording defects, classifying NO APLICA. them and identifying the impact. [After IEEE 1044] A cross‐functional team of stakeholders who manage reported defects from initial detection to ultimate resolution (defect removal, defect deferral, or report cancellation). In NO APLICA. some cases, the same team as the configuration control board. See also configuration control board. A tool that facilitates the recording and status tracking of defects and changes. They often have workflow‐oriented facilities to track and control the allocation, correction and re‐testing of defects and provide reporting facilities. See also incident management tool.
NO APLICA.
An occurrence in which one defect prevents the detection of NO APLICA. another. [After IEEE 610] A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function. [After IEEE 829]
Se trata del informe de un solo defecto.
A system of (hierarchical) categories designed to be a useful NO APLICA. aid for reproducibly classifying defects.
See defect management tool.
See defect management committee.
NO APLICA.
NO APLICA.
An element in a taxonomy of defects. Defect taxonomies can be identified with respect to a variety of considerations, including, but not limited to: ‐ Phase or development activity in which the defect is NO APLICA. created, e.g., a specification error or a coding error ‐ Characterization of defects, e.g., an “off‐by‐one” defect ‐ Incorrectness, e.g., an incorrect relational operator, a
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
programming language syntax error, or an invalid assumption ‐ Performance issues, e.g., excessive execution time, insufficient availability. 217.
ATA
técnica basada en defectos
NO APLICA
defect‐based technique
218.
ATA
técnica de diseño de prueba basada en defectos
NO APLICA
defect‐based test design technique
219.
ATT
par definición‐uso
par definición‐uso
definition‐use pair
220.
entrega
entregable
deliverable
221.
EITP
Ciclo de Deming
NO APLICA
Deming cycle
222.
pruebas basadas en el diseño
pruebas basadas en el diseño
design‐based testing
223.
comprobación de escritorio
comprobación de escritorio
desk checking
Testing of software or a specification by manual simulation of NO APLICA. its execution. See also static testing.
224.
pruebas de desarrollo
pruebas de desarrollo
development testing
Formal or informal testing conducted during the implementation of a component or system, usually in the NO APLICA. development environment by developers. [After IEEE 610]
225.
desviación
desviación
deviation
226.
informe de desviación
informe de desviaciones
deviation report
227.
EITP
diagnóstico (IDEAL)
NO APLICA
diagnosing (IDEAL)
See defect‐based test design technique. A procedure to derive and/or select test cases targeted at one or more defect types, with tests being developed from what is known about the specific defect type. See also defect taxonomy. The association of a definition of a variable with the subsequent use of that variable. Variable uses include computational (e.g. multiplication) or to direct the execution of a path (“predicate” use). Any (work) product that must be delivered to someone other than the (work) product’s author. An iterative four‐step problem‐solving process, (plan‐do‐ check‐act), typically used in process improvement. [After Deming] An approach to testing in which test cases are designed based on the architecture and/or detailed design of a component or system (e.g. tests of interfaces between components or systems).
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA. NO APLICA.
NO APLICA.
See incident.
NO APLICA.
See incident report.
Se trata del informe de una única desviación.
The phase within the IDEAL model where it is determined where one is, relative to where one wants to be. The NO APLICA. diagnosing phase consists of the activities: characterize current and desired states and develop recommendations.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
See also IDEAL. 228.
pruebas sucias
pruebas sucias
dirty testing
229.
pruebas de la documentación
pruebas de documentación
documentation testing
230.
dominio
dominio
domain
231.
232.
F ETAE
Testing the quality of the documentation, e.g. user guide or NO APLICA. installation guide. The set from which valid input and/or output values can be selected.
NO APLICA.
análisis de dominio
NO APLICA
domain analysis
controlador
controlador
driver
A software component or test tool that replaces a component that takes care of the ETAE control and/or the NO APLICA. calling of a component or system. [After TMap]
ATT
análisis dinámico
análisis dinámico
dynamic analysis
234.
F
herramienta de análisis dinámico
herramienta de análisis dinámico
dynamic analysis tool
235.
comparación dinámica
comparación dinámica
dynamic comparison
236.
F
pruebas dinámicas
pruebas dinámicas
dynamic testing
E
ATM
efectividad
NO APLICA
effectiveness
237.
NO APLICA.
A black box test design technique that is used to identify efficient and effective test cases when multiple variables can or should be tested together. It builds on and generalizes NO APLICA. equivalence partitioning and boundary values analysis. See also boundary value analysis, equivalence partitioning.
233.
ATA
See negative testing.
The process of evaluating behavior, e.g. memory performance, CPU usage, of a system or component during NO APLICA. execution. [After IEEE 610] A tool that provides run‐time information on the state of the software code. These tools are most commonly used to identify unassigned pointers, check pointer arithmetic and to NO APLICA. monitor the allocation, use and de‐allocation of memory and to flag memory leaks. Comparison of actual and expected results, performed while the software is being executed, for example by a test NO APLICA. execution tool. Testing that involves the execution of the software of a component or system.
NO APLICA.
The capability of producing an intended result. See also efficiency.
NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
eficiencia
eficiencia
efficiency
pruebas de eficiencia:
pruebas de eficiencia
efficiency testing
240.
EITP
modelo de excelencia EFQM (European Foundation for Quality Management)
NO APLICA
EFQM (European Foundation for Quality Management) excellence model
241.
pruebas de comparación elemental
pruebas de comparación elemental
elementary comparison testing
242.
modelo de desarrollo iterativo embebido
NO APLICA
embedded iterative development model
243.
EITP
inteligencia emocional
NO APLICA
emotional intelligence
244.
EPME
NO APLICA
EMTE
245.
emulador:
emulador
emulator
246.
F
criterios de entrada
criterios de entrada
entry criteria
247.
punto de entrada
punto de entrada
entry point
238.
239.
ATM
TÉRMINO TRADUCIDO
ATT
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
(1) The capability of the software product to provide appropriate performance, relative to the amount of resources used under stated conditions. [ISO 9126] NO APLICA. (2) The capability of a process to produce the intended outcome, relative to the amount of resources used The process of testing to determine the efficiency of a software product.
NO APLICA.
A non‐prescriptive framework for an organisation's quality management system, defined and owned by the European Foundation for Quality Management, based on five 'Enabling' NO APLICA. criteria (covering what an organisation does), and four 'Results' criteria (covering what an organisation achieves). A black box test design technique in which test cases are designed to execute combinations of inputs using the NO APLICA. concept of modified condition decision coverage. [TMap] A development lifecycle sub‐model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design NO APLICA. documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations. The ability, capacity, and skill to identify, assess, and manage NO APLICA. the emotions of one's self, of others, and of groups. Esfuerzo de Prueba Manual Acronym for Equivalent Manual Test Effort. Equivalente Equivalent Manual Test Effort. A device, computer program, or system that accepts the same inputs and produces the same outputs as a given NO APLICA. system. [IEEE 610] See also simulator. The set of generic and specific conditions for permitting a process to go forward with a defined task, e.g. test phase. The purpose of entry criteria is to prevent a task from NO APLICA. starting which would entail more (wasted) effort compared to the effort needed to remove the failed entry criteria. [Gilb and Graham] An executable statement or process step which defines a NO APLICA. point at which a given process is intended to begin.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
248.
clase de equivalencia
clase de equivalencia
equivalence class
249.
partición de equivalencia
partición de equivalencia
equivalence partition
A portion of an input or output domain for which the behavior of a component or system is assumed to be the NO APLICA. same, based on the specification.
250.
cobertura de particiones de equivalencia
cobertura de partición de equivalencia
equivalence partition coverage
The percentage of equivalence partitions that have been NO APLICA. exercised by a test suite.
segmentación de equivalencia
segmentación de equivalencia
equivalence partitioning
A black box test design technique in which test cases are designed to execute representatives from equivalence NO APLICA. partitions. In principle test cases are designed to cover each partition at least once. Effort required for running tests manually.
251.
ATA
252.
ETAE
esfuerzo de prueba manual equivalente
NO APLICA
equivalent manual test effort
253.
F
error
error
error
254.
F
F ATA
predicción de errores
predicción de error
error guessing
255.
siembra de errores
siembra de errores
error seeding
256.
herramienta de siembra de errores
NO APLICA
error seeding tool
257.
tolerancia a errores
tolerancia al error
error tolerance
258.
defecto escapado
NO APLICA
escaped defect
259.
EITP
establecimiento (IDEAL)
NO APLICA
establishing (IDEAL)
DESCRIPCIÓN EN INGLÉS See equivalence partition.
A human action that produces an incorrect result. [After IEEE 610]
OBSERVACIONES NO APLICA.
NO APLICA.
NO APLICA.
A test design technique where the experience of the tester is used to anticipate what defects might be present in the NO APLICA. component or system under test as a result of errors made, and to design tests specifically to expose them. See fault seeding.
NO APLICA.
See fault seeding tool.
NO APLICA.
The ability of a system or component to continue normal operation despite the presence of erroneous inputs. [After NO APLICA. IEEE 610]. A defect that was not detected in a previous test level which is supposed to find such type of defects. See also Defect NO APLICA. Detection Percentage. The phase within the IDEAL model where the specifics of how an organization will reach its destination are planned. The NO APLICA. establishing phase consists of the activities: set priorities, develop approach and plan actions. See also IDEAL.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
260.
evaluación
evaluación
evaluation
261.
tratamiento de excepciones
tratamiento de excepciones
exception handling
262.
sentencia ejecutable
sentencia ejecutable
executable statement
263.
practicado
practicado
exercised
264.
F
pruebas exhaustivas
pruebas exhaustivas
exhaustive testing
criterios de salida
criterios de salida
exit criteria
F 265.
ATM ATA
266.
punto de salida
punto de salida
exit point
267.
resultado esperado
resultado esperado
expected outcome
268.
resultado esperado
resultado esperado
expected result
269.
ATA
técnica basada en la experiencia
técnica basada en la experiencia
experience‐based technique
técnica de diseño de prueba basada en la experiencia
técnica de diseño de pruebas basada en la experiencia
experience‐based test design technique
pruebas basadas en la experiencia
NO APLICA
experience‐based testing
270.
271.
F ATA
DESCRIPCIÓN EN INGLÉS See testing. Behavior of a component or system in response to erroneous input, from either a human user or from another component or system, or to an internal failure. A statement which, when compiled, is translated into object code, and which will be executed procedurally when the program is running and may perform an action on data. A program element is said to be exercised by a test case when the input value causes the execution of that element, such as a statement, decision, or other structural element. A test approach in which the test suite comprises all combinations of input values and preconditions. The set of generic and specific conditions, agreed upon with the stakeholders for permitting a process to be officially completed. The purpose of exit criteria is to prevent a task from being considered completed when there are still outstanding parts of the task which have not been finished. Exit criteria are used to report against and to plan when to stop testing. [After Gilb and Graham] An executable statement or process step which defines a point at which a given process is intended to cease. See expected result.
OBSERVACIONES NO APLICA. NO APLICA.
NO APLICA.
NO APLICA. NO APLICA.
NO APLICA.
NO APLICA. NO APLICA.
The behavior predicted by the specification, or another source, of the component or system under specified NO APLICA. conditions. See experience‐based test design technique.
NO APLICA.
Procedure to derive and/or select test cases based on the tester’s experience, knowledge and intuition.
NO APLICA.
Testing based on the tester’s experience, knowledge and NO APLICA. intuition.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
pruebas exploratorias
pruebas exploratorias
exploratory testing
An informal test design technique where the tester actively controls the design of the tests as those tests are performed NO APLICA. and uses information gained while testing to design new and better tests. [After Bach] A software engineering methodology used within agile software development whereby core practices are programming in pairs, doing extensive code review, unit NO APLICA. testing of all code, and simplicity and clarity in code. See also agile software development.
F 272.
F‐AT ATA
273.
programación extrema
NO APLICA
extreme programming:
F
274.
pruebas de aceptación de factoría
NO APLICA
275.
fallar
fallar
276.
277.
EITP
F ATM
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
Acceptance testing conducted at the site at which the product is developed and performed by employees of the supplier organization, to determine whether or not a NO APLICA. factory acceptance testing component or system satisfies the requirements, normally including hardware as well as software. See also alpha testing. fail
A test is deemed to fail if its actual result does not match its expected result.
NO APLICA.
pruebas de tolerancia a fallos:
NO APLICA
failover testing:
Testing by simulating failure modes or actually causing failures in a controlled environment. Following a failure, the failover mechanism is tested to ensure that data is not lost or NO APLICA. corrupted and that any agreed service levels are maintained (e.g., function availability or response times). See also recoverability testing.
fallo
fallo
failure
Deviation of the component or system from its expected NO APLICA. delivery, service or result. [After Fenton]
278.
modo de fallo
modo de fallo
failure mode
279.
EITP
Análisis de Modos de Fallo y sus Efectos (AMFE)
Análisis del Modo de Fallo y Efecto (AMFE)
Failure Mode and Effect Analysis (FMEA)
The physical or functional manifestation of a failure. For example, a system in failure mode may be characterized by NO APLICA. slow operation, incorrect outputs, or complete termination of execution. [IEEE 610] A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to NO APLICA. prevent their occurrence. See also Failure Mode, Effect and
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
Análisis de Modos de Fallo, sus Efectos y Criticidad (AMFEC)
NO APLICA
281.
F
tasa de fallos
frecuencia de fallos
282.
ATM
resultado de falso‐fallo
NO APLICA
283.
ATM
resultado de falso‐ negativo
NO APLICA
false‐negative result
284.
ATM
resultado de falso‐paso
NO APLICA
false‐pass result
285.
ATM
resultado de falso‐ positivo
NO APLICA
false‐positive result
286.
F
falta
falta
287.
F
ataque de falta
288.
289.
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
Criticality Analysis (FMECA). An extension of FMEA, as in addition to the basic FMEA, it includes a criticality analysis, which is used to chart the probability of failure modes against the severity of their Failure Mode, Effects, and consequences. The result highlights failure modes with Criticality Analysis NO APLICA. relatively high probability and severity of consequences, (FMECA) allowing remedial effort to be directed where it will produce the greatest value. See also Failure Mode and Effect Analysis (FMEA). The ratio of the number of failures of a given category to a given unit of measure, e.g. failures per unit of time, failures failure rate NO APLICA. per number of transactions, failures per number of computer runs. [IEEE 610] A test result in which a defect is reported although no such false‐fail result NO APLICA. defect actually exists in the test object.
280.
290.
TÉRMINO TRADUCIDO
See false‐pass result.
NO APLICA.
A test result which fails to identify the presence of a defect NO APLICA. that is actually present in the test object. See false‐fail result.
NO APLICA.
fault
See defect.
NO APLICA.
NO APLICA
fault attack:
See attack.
NO APLICA.
densidad de faltas
densidad de faltas
fault density
See defect density.
NO APLICA.
Porcentaje de Detección de Faltas (PDF)
Porcentaje de Detección de Faltas (PDF)
Fault Detection Percentage (FDP)
See Defect Detection Percentage (DDP).
NO APLICA.
inyección de faltas
NO APLICA
fault injection
The process of intentionally adding defects to a system for the purpose of finding out whether the system can detect, and possibly recover from, a defect. Fault injection intended NO APLICA. to mimic failures that might occur in the field. See also fault tolerance.
291.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
enmascaramiento de falta
enmascaramiento de faltas
fault masking
292.
siembra de faltas
NO APLICA
fault seeding
293.
ATT
herramienta de siembra de faltas
NO APLICA
fault seeding tool
294.
tolerancia a faltas
tolerancia a faltas
fault tolerance
295.
EITP
Análisis de Árbol de Faltas (AAF)
análisis de árbol de faltas
Fault Tree Analysis (FTA)
296.
camino viable
camino viable
feasible path
297.
prestación
prestación
feature
298.
ETM
desarrollo guiado por prestaciones
NO APLICA
feature‐driven development
299.
pruebas de campo
pruebas de campo
field testing
300.
máquina de estados finitos
máquina de estado finito
finite state machine
DESCRIPCIÓN EN INGLÉS
See defect masking.
OBSERVACIONES
NO APLICA.
The process of intentionally adding defects to those already in the component or system for the purpose of monitoring the rate of detection and removal, and estimating the number of remaining defects. Fault seeding is typically part of NO APLICA. development (pre‐release) testing and can be performed at any test level (component, integration, or system). [After IEEE 610] A tool for seeding (i.e. intentionally inserting) faults in a component or system. The capability of the software product to maintain a specified level of performance in cases of software faults (defects) or of infringement of its specified interface. [ISO 9126] See also reliability, robustness. A technique used to analyze the causes of faults (defects). The technique visually models how logical relationships between failures, human errors, and external events can combine to cause specific faults to disclose. A path for which a set of input values and preconditions exists which causes it to be executed. An attribute of a component or system specified or implied by requirements documentation (for example reliability, usability or design constraints). [After IEEE 1008] An iterative and incremental software development process driven from a client‐valued functionality (feature) perspective. Feature‐driven development is mostly used in agile software development. See also agile software development. See beta testing.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA. NO APLICA.
NO APLICA.
NO APLICA.
A computational model consisting of a finite number of states and transitions between those states, possibly with NO APLICA. accompanying actions. [IEEE 610]
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
301.
pruebas de estados finitos
pruebas de estado finito
finite state testing
See state transition testing.
NO APLICA.
302.
diagrama de espina de pescado
NO APLICA
fishbone diagram
See cause‐effect diagram.
NO APLICA.
303.
F
revisión formal
revisión formal
formal review
A review characterized by documented procedures and requirements, e.g. inspection.
NO APLICA.
304.
base de prueba congelada
base de prueba congelada
frozen test basis
305.
Análisis de Puntos de Función (APF)
Análisis de Punto de Función (APF)
Function Point Analysis (FPA)
306.
integración funcional
integración funcional
functional integration
307.
F
requisito funcional
requisito funcional
functional requirement
308.
técnica de diseño de prueba funcional
técnica de diseño de prueba funcional
functional test design technique
309.
F
pruebas funcionales
pruebas funcionales
functional testing
310.
funcionalidad
NO APLICA
functionality
311.
pruebas de la funcionalidad
pruebas de funcionalidad
functionality testing
G
ETAE
arquitectura de
NO APLICA
312.
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A test basis document that can only be amended by a formal change control process. See also baseline. Method aiming to measure the size of the functionality of an information system. The measurement is independent of the technology. This measurement may be used as a basis for the measurement of productivity, the estimation of the needed resources, and project control. An integration approach that combines the components or systems for the purpose of getting a basic functionality working early. See also integration testing. A requirement that specifies a function that a component or system must perform. [IEEE 610] Procedure to derive and/or select test cases based on an analysis of the specification of the functionality of a component or system without reference to its internal structure. See also black box test design technique. Testing based on an analysis of the specification of the functionality of a component or system. See also black box testing. The capability of the software product to provide functions which meet stated and implied needs when the software is used under specified conditions. [ISO 9126]
NO APLICA.
The process of testing to determine the functionality of a software product.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
Representation of the layers, components, and interfaces of G generic test automation a test automation architecture, allowing for a structured and NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
automatizacion de prueba genérica
architecture
313.
pruebas de caja de cristal
pruebas de caja de cristal
glass box testing
314.
EITP
Métrica de Pregunta Objetivo
NO APLICA
Goal Question Metric
315.
EITP
MPO
NO APLICA
GQM
316.
Interface Gráfica de Usuario
NO APLICA
GUI
317.
ETAE
Pruebas de Interface Gráfica de Usuario
NO APLICA
GUI testing
H
318.
pruebas de integración hardware‐software
NO APLICA
hardware‐software integration testing
319.
análisis de peligros
NO APLICA
hazard analysis
320.
ATA
evaluación heurística
evaluación heurística
heuristic evaluation
321.
ATA
caso de prueba de alto nivel
caso de prueba de alto nivel
high level test case
322.
trazabilidad horizontal
trazabilidad horizontal
horizontal traceability
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
modular approach to implement test automation.
See white box testing.
NO APLICA.
An approach to software measurement using a three‐level model: conceptual level (goal), operational level (question) NO APLICA. and quantitative level (metric). See Goal Question Metric.
NO APLICA.
Acronym for Graphical User Interface.
NO APLICA.
Testing performed by interacting with the software under NO APLICA. test via the graphical user interface. Testing performed to expose defects in the interfaces and interaction between hardware and software components. See also integration testing. A technique used to characterize the elements of risk. The result of a hazard analysis will drive the methods used for development and testing of a system. See also risk analysis. A usability review technique that targets usability problems in the user interface or user interface design. With this technique, the reviewers examine the interface and judge its compliance with recognized usability principles (the "heuristics"). A test case without concrete (implementation level) values for input data and expected results. Logical operators are used; instances of the actual values are not yet defined and/or available. See also low level test case. The tracing of requirements for a test level through the layers of test documentation (e.g. test plan, test design specification, test case specification and test procedure specification or test script).
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
323.
hipervínculo
NO APLICA
hyperlink
A pointer within a web page that leads to other web pages.
NO APLICA.
324.
ATT
herramienta de prueba de hipervínculos
NO APLICA
hyperlink test tool
A tool used to check that no broken hyperlinks are present on a web site.
NO APLICA.
I
An organizational improvement model that serves as a roadmap for initiating, planning, and implementing improvement actions. The IDEAL model is named for the five NO APLICA. phases it describes: initiating, diagnosing, establishing, acting, and learning. The assessment of change to the layers of development documentation, test documentation and components, in NO APLICA. order to implement a given change to specified requirements.
325.
EITP
IDEAL
NO APLICA
IDEAL
326.
F
análisis de impacto
análisis de impacto
impact analysis
327.
F
incidencia
incidencia
incident
Any event occurring that requires investigation. [After IEEE 1008]
NO APLICA.
328.
F
registrar incidencia
registrar incidencias
incident logging
Recording the details of any incident that occurred, e.g. during testing.
NO APLICA.
329.
F
gestión de incidencias
gestión de incidencias
330.
F
herramienta de gestión de incidencias
herramienta de gestión de incidencias
331.
F
informe de incidencia
informe de incidencias
F
modelo de desarrollo incremental
modelo de desarrollo incremental
332.
OBSERVACIONES
F‐AT
The process of recognizing, investigating, taking action and disposing of incidents. It involves logging incidents, classifying them and identifying the impact. [After IEEE 1044] A tool that facilitates the recording and status tracking of incidents. They often have workflow‐oriented facilities to incident management tool track and control the allocation, correction and re‐testing of incidents and provide reporting facilities. See also defect management tool. A document reporting on any event that occurred, e.g. during incident report the testing, which requires investigation. [After IEEE 829] A development lifecycle where a project is broken into a series of increments, each of which delivers a portion of the incremental development functionality in the overall project requirements. The model requirements are prioritized and delivered in priority order in the appropriate increment. In some (but not all) versions of incident management
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
333.
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
this lifecycle model, each subproject follows a ‘mini Vmodel’ with its own design, coding and testing phases. Testing where components or systems are integrated and tested one or some at a time, until all the components or NO APLICA. systems are integrated and tested.
pruebas incrementales
pruebas incrementales
incremental testing
F ATM
independencia de las pruebas
independencia de pruebas
independence of testing
335.
EITP
indicador
NO APLICA
indicator
A measure that can be used to estimate or predict another measure. [ISO 14598]
NO APLICA.
336.
camino inviable
camino inviable
infeasible path
A path that cannot be exercised by any set of possible input values.
NO APLICA.
revisión informal
revisión informal
informal review
A review not based on a formal (documented) procedure.
NO APLICA.
334.
337.
F ATM
Separation of responsibilities, which encourages the NO APLICA. accomplishment of objective testing. [After DO‐178b]
The phase within the IDEAL model where the groundwork is laid for a successful improvement effort. The initiating phase NO APLICA. consists of the activities: set context, build sponsorship and charter infrastructure. See also IDEAL.
338.
EITP
iniciación (IDEAL)
NO APLICA
initiating (IDEAL)
339.
entrada
entrada
input
A variable (whether stored within a component or outside) that is read by a component.
NO APLICA.
340.
dominio de entrada
dominio de entrada
input domain
The set from which valid input values can be selected. See also domain.
NO APLICA.
341.
valor de entrada
valor de entrada
input value
An instance of an input. See also input.
NO APLICA.
342.
pruebas internalizadas
NO APLICA
insourced testing
inspección
inspección
inspection
343.
TÉRMINO TRADUCIDO
F ATM
Testing performed by people who are co‐located with the NO APLICA. project team but are not fellow employees. 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 NO APLICA. documentation. The most formal review technique and therefore always based on a documented procedure. [After
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
AITP
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
IEEE 610, IEEE 1028] See also peer review.
344.
líder de inspección
líder de inspección
inspection leader
345.
inspector
inspector
inspector
346.
ATT
instalabilidad
instalabilidad
installability
347.
pruebas de instalabilidad
pruebas de instalabilidad
installability testing
348.
guía de instalación
guía de instalación
installation guide
349.
asistente de instalación
asistente de instalación
installation wizard
350.
instrumentación
instrumentación
instrumentation
351.
herramienta de instrumentación
instrumentador
instrumenter
352.
prueba de admisión
prueba de admisión
intake test
353.
F
integración
integración
integration
354.
F
pruebas de integración
pruebas de integración
integration testing
355.
pruebas de integración a
pruebas de integración a
integration testing in the
See moderator.
NO APLICA.
See reviewer.
NO APLICA.
The capability of the software product to be installed in a NO APLICA. specified environment [ISO 9126]. See also portability. The process of testing the installability of a software product. See also portability testing. 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. Supplied software on any suitable media, which leads the installer through the installation process. It normally runs the installation process, provides feedback on installation results, and prompts for options. The insertion of additional code into the program in order to collect information about program behavior during execution, e.g. for measuring code coverage. A software tool used to carry out instrumentation.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
A special instance of a smoke test to decide if the component or system is ready for detailed and further testing. An intake NO APLICA. test is typically carried out at the start of the test execution phase. See also smoke test. The process of combining components or systems into larger assemblies.
NO APLICA.
Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. NO APLICA. See also component integration testing, system integration testing. See system integration testing.
NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
gran escala
gran escala
large
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
356.
pruebas de integración a pequeña escala
pruebas de integración a pequeña escala
integration testing in the small
357.
pruebas de interface
pruebas de interfaz
interface testing
358.
interoperabilidad
interoperabilidad
interoperability
F ATA
pruebas de interoperabilidad
pruebas de interoperabilidad
interoperability testing
The process of testing to determine the interoperability of a NO APLICA. software product. See also functionality testing.
360.
pruebas de invalidez
pruebas inválidas
invalid testing
Testing using input values that should be rejected by the component or system. See also error tolerance, negative NO APLICA. testing.
361.
ETM
diagrama de Ishikawa
NO APLICA
Ishikawa diagram
362.
pruebas de aislamiento
pruebas de aislamiento
isolation testing
363.
informe de transmisión de elemento
informe de transmisión de elemento
item transmittal report
359.
F
See component integration testing.
NO APLICA.
An integration test type that is concerned with testing the NO APLICA. interfaces between components or systems. The capability of the software product to interact with one or more specified components or systems. [After ISO 9126] See NO APLICA. also functionality.
See cause‐effect diagram.
NO APLICA.
Testing of individual components in isolation from surrounding components, with surrounding components NO APLICA. being simulated by stubs and drivers, if needed. See release note.
NO APLICA.
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) NO APLICA. of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product.
F‐AT
modelo de desarrollo iterativo
modelo de desarrollo iterativo
iterative development model
J
K
indicador clave de rendimiento
indicador clave de rendimiento
key performance indicator
See performance indicator.
NO APLICA.
364.
365.
TÉRMINO TRADUCIDO
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
F 366.
ATA ATT
pruebas guiadas por palabra clave
pruebas guiadas por palabras clave
keyword driven testing
L
ETAE
367.
SLCYS
SLYSC
LCSAJ
368.
cobertura de SLCYS
cobertura SLYSC
LCSAJ coverage
369.
pruebas de SLCYS
pruebas SLYSC
LCSAJ testing
370.
EITP
evaluador jefe
NO APLICA
lead assessor
371.
ATA
capacidad de ser aprendido
aprendibilidad
learnability
372.
EITP
aprendizaje (IDEAL)
NO APLICA
learning (IDEAL)
373.
ETAE
nivel de intrusión
NO APLICA
level of intrusion
374.
ATM
plan de nivel de prueba
plan de pruebas de nivel
level test plan
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
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 NO APLICA. by special supporting scripts that are called by the control script for the test. See also data‐driven testing. A Linear Code Sequence And Jump, consists of the following three items (conventionally identified by line numbers in a source code listing): the start of the linear sequence of executable statements, the end of the linear sequence, and the target line to which control flow is transferred at the end of the linear sequence. The percentage of LCSAJs of a component that have been exercised by a test suite. 100% LCSAJ coverage implies 100% decision coverage. A white box test design technique in which test cases are designed to execute LCSAJs. The person who leads an assessment. In some cases, for instance CMMi and TMMi when formal assessments are conducted, the lead assessor must be accredited and formally trained.
NO APLICA.
NO APLICA. NO APLICA.
NO APLICA.
The capability of the software product to enable the user to NO APLICA. learn its application. [ISO 9126] See also usability. The phase within the IDEAL model where one learns from experiences and improves one’s ability to adopt new processes and technologies in the future. The learning phase NO APLICA. consists of the activities: analyze and validate, and propose future actions. See also IDEAL. The level to which a test object is modified by adjusting it for NO APLICA. testability. A test plan that typically addresses one test level. See also test plan.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
375.
EITP
modelo de ciclo de vida
NO APLICA
lifecycle model
A partitioning of the life of a product or project into phases. NO APLICA. [CMMI] See also software lifecycle.
376.
ETAE
escritura de guiones lineales
NO APLICA
linear scripting
A simple scripting technique without any control structure in NO APLICA. the test scripts.
377.
pruebas de enlaces
pruebas de enlace
link testing
378.
perfil de carga
NO APLICA
load profile
379.
F
pruebas de carga
pruebas de carga
load testing
380.
F
herramienta para pruebas de carga
NO APLICA
load testing tool
381.
ATA
caso de prueba lógico
caso de prueba lógico
logical test case:
382.
pruebas de cobertura de la lógica
pruebas de cobertura lógica
logic‐coverage testing
383.
pruebas guiadas por la lógica
pruebas guiadas por lógica
logic‐driven testing
384.
ATA
caso de prueba de bajo nivel
caso de prueba de bajo nivel
low level test case:
M
DESCRIPCIÓN EN INGLÉS
See component integration testing.
OBSERVACIONES
NO APLICA.
A specification of the activity which a component or system being tested may experience in production. A load profile consists of a designated number of virtual users who process NO APLICA. a defined set of transactions in a specified time period and according to a predefined operational profile. See also operational profile. 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 NO APLICA. determine what load can be handled by the component or system. See also performance testing,stress testing. A tool to support load testing whereby it can simulate increasing load, e.g., numbers of concurrent users and/or NO APLICA. transactions within a specified time‐period. See also performance testing tool. See high level test case.
NO APLICA.
See white box testing. [Myers]
NO APLICA.
See white box testing.
NO APLICA.
A test case with concrete (implementation level) values for input data and expected results. Logical operators from high level test cases are replaced by actual values that correspond NO APLICA. to the objectives of the logical operators. See also high level test case.
PROGRAMA DE ESTUDIOS
385.
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
mantenibilidad
mantenibilidad
maintainability
The ease with which a software product can be modified to correct defects, modified to meet new requirements, NO APLICA. modified to make future maintenance easier, or adapted to a changed environment. [ISO 9126]
pruebas de mantenibilidad
pruebas de mantenibilidad
maintainability testing
The process of testing to determine the maintainability of a NO APLICA. software product.
F 386.
F‐AT ATT
387.
ETAE
mantenimiento
mantenimiento
maintenance
Modification of a software product after delivery to correct defects, to improve performance or other attributes, or to NO APLICA. adapt the product to a modified environment. [IEEE 1219]
388.
F
pruebas de mantenimiento
pruebas de mantenimiento
maintenance testing
Testing the changes to an operational system or the impact NO APLICA. of a changed environment to an operational system.
389.
ataque de hombre interpuesto
NO APLICA
man in the middle attack
390.
ATM
revisión de gestión
revisión de gestión
management review
391.
EITP
calidad basada en la manufactura
NO APLICA
manufacturing‐based quality
The interception, mimicking and/or altering and subsequent relaying of communications (e.g., credit card transactions) by NO APLICA. a third party such that a user remains unaware of that third party’s presence. A systematic evaluation of software acquisition, supply, development, operation, or maintenance process, performed by or on behalf of management that monitors progress, determines the status of plans and schedules, confirms NO APLICA. requirements and their system allocation, or evaluates the effectiveness of management approaches to achieve fitness for purpose. [After IEEE 610, IEEE 1028] A view of quality, whereby quality is measured by the degree to which a product or service conforms to its intended design and requirements. Quality arises from the process(es) used. [After Garvin] See also product‐based quality, transcendent‐ NO APLICA. based quality, userbased quality, value‐based quality.
392.
ATM
plan de prueba maestro
plan maestro de pruebas
master test plan
393.
ATT
madurez
madurez
maturity
A test plan that typically addresses multiple test levels. See also test plan.
NO APLICA.
(1) The capability of an organization with respect to the NO APLICA. effectiveness and efficiency of its processes and work
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
394.
EITP
nivel de madurez
NO APLICA
maturity level
395.
modelo de madurez
NO APLICA
maturity model
396.
CCDM
NO APLICA
MCDC
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
practices. See also Capability Maturity Model Integration, Test Maturity Model integration. (2) The capability of the software product to avoid failure as a result of defects in the software. [ISO 9126] See also reliability. Degree of process improvement across a predefined set of process areas in which all goals in the set are attained. NO APLICA. [TMMi] 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. NO APLICA. A maturity model often provides a common language, shared vision and framework for prioritizing improvement actions. See modified condition decision coverage.
NO APLICA.
397.
Tiempo Medio Entre Fallos
NO APLICA
Mean Time Between Failures
The arithmetic mean (average) time between failures of a system. The MTBF is typically part of a reliability growth model that assumes the failed system is immediately NO APLICA. repaired, as a part of a defect fixing process. See also reliability growth model.
398.
Tiempo Medio de Reparación
NO APLICA
Mean Time To Repair
The arithmetic mean (average) time a system will take to recover from any failure. This typically includes testing to NO APLICA. insure that the defect has been resolved.
399.
EITP
medida
medida
measure
The number or category assigned to an attribute of an entity NO APLICA. by making a measurement. [ISO 14598]
400.
medición
medición
measurement
The process of assigning a number or category to an entity to NO APLICA. describe an attribute of that entity. [ISO 14598]
401.
escala de medición
escala de medida
measurement scale
402.
ATT
fuga de memoria
fuga de memoria
memory leak
403.
ETM
pruebas metódicas
NO APLICA
methodical testing
A scale that constrains the type of data analysis that can be NO APLICA. performed on it. [ISO 14598] 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 NO APLICA. program and/or other concurrent processes to fail due to lack of memory. Testing based on a standard set of tests, e.g., a checklist, a NO APLICA. quality standard, or a set of generalized test cases.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
métrica
métrica
metric
A measurement scale and the method used for measurement. [ISO 14598]
NO APLICA.
See conversion testing.
NO APLICA.
F 404.
EITP ETAE
405.
pruebas de migración
pruebas de migración
migration testing
406.
hito
hito
milestone
407.
EITP
mapa mental
NO APLICA
mind map
408.
F
equivocación
equivocación
mistake
ETM ETAE
pruebas basadas en modelos
NO APLICA
model‐based testing
F
herramienta de modelado
herramienta de modelado
modeling tool
moderador
moderador
moderator
cobertura de decisión de condición modificada
modified condition decision coverage
409.
410.
411.
F ATM
412.
cobertura de decisiones‐ condiciones modificadas
413.
pruebas de decisiones‐ condiciones modificadas
pruebas de decisión de condición modificada
modified condition decision testing
414.
cobertura de condición múltiple modificada
cobertura de condición múltiple modificada
modified multiple condition coverage
A point in time in a project at which defined (intermediate) NO APLICA. deliverables and results should be ready. A diagram used to represent words, ideas, tasks, or other items linked to and arranged around a central keyword or idea. Mind maps are used to generate, visualize, structure, NO APLICA. and classify ideas, and as an aid in study, organization, problem solving, decision making, and writing. See error.
NO APLICA.
Testing based on a model of the component or system under test, e.g., reliability growth models, usage models such as NO APLICA. operational profiles or behavioral models such as decision table or state transition diagram. A tool that supports the creation, amendment and NO APLICA. verification of models of the software or system [Graham]. The leader and main person responsible for an inspection or NO APLICA. other review process. The percentage of all single condition outcomes that independently affect a decision outcome that have been NO APLICA. exercised by a test case suite. 100% modified condition decision coverage implies 100% decision condition coverage. A white box test design technique in which test cases are designed to execute single condition outcomes that NO APLICA. independently affect a decision outcome. See modified condition decision coverage.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
415.
pruebas de condición múltiple modificada
pruebas de condición múltiple modificada
modified multiple condition testing
416.
módulo
módulo
module
417.
pruebas de módulo
pruebas de módulo
module testing
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
See modified condition decision testing.
NO APLICA.
See component.
NO APLICA.
See component testing.
NO APLICA.
A software tool or hardware device that runs concurrently with the component or system under test and supervises, NO APLICA. records and/or analyses the behavior of the component or system. [After IEEE 610]
418.
monitor
monitor
monitor
419.
F
herramienta de monitorización
herramienta de monitorización
monitoring tool
420.
prueba del mono
pruebas de mono
monkey testing
421.
TMEF
NO APLICA
MTBF
See Mean Time Between Failures.
NO APLICA.
422.
TMDR
NO APLICA
MTTR
See Mean Time To Repair.
NO APLICA.
423.
condición múltiple
condición múltiple
multiple condition
See compound condition.
NO APLICA.
424.
cobertura de condiciones múltiples
cobertura de condición múltiple
425.
ATT
pruebas de condición múltiple
pruebas de condición múltiple
426.
análisis de mutación
análisis de mutación
427.
pruebas de mutación
pruebas de mutación
See monitor.
NO APLICA.
Testing by means of a random selection from a large range of inputs and by randomly pushing buttons, ignorant of how the NO APLICA. product is being used.
The percentage of combinations of all single condition outcomes within one statement that have been exercised by NO APLICA. a test suite. 100% multiple condition coverage implies 100% modified condition decision coverage. A white box test design technique in which test cases are multiple condition testing designed to execute combinations of single condition NO APLICA. outcomes (within one statement). A method to determine test suite thoroughness by measuring mutation analysis the extent to which a test suite can discriminate the program NO APLICA. from slight variants (mutants) of the program. multiple condition coverage
mutation testing
See back‐to‐back testing.
NO APLICA.
428.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
Indicador Tipo Myers‐ Briggs (ITMB)
NO APLICA
Myers‐Briggs Type Indicator (MBTI)
N
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
An indicator of psychological preference representing the NO APLICA. different personalities and communication styles of people.
Tests aimed at showing that a component or system does not work. Negative testing is related to the testers’ attitude negative testing rather than a specific test approach or test design technique, NO APLICA. e.g. testing with invalid input values or exceptions. [After Beizer]. A form of integration testing where all of the nodes that neighborhood integration connect to a given node are the basis for the integration NO APLICA. testing testing.
429.
pruebas negativas
pruebas negativas
430.
ATT
pruebas de integración de proximidad
NO APLICA
431.
no conformidad
no conformidad
432.
F
requisito no funcional
requisito no funcional
433.
técnica de diseño de prueba no funcional
técnicas de diseño de pruebas no funcionales
434.
pruebas no funcionales
pruebas no funcionales
435.
cobertura de conmutador de orden N
cobertura de conmutador de multiplicidad N
N‐switch coverage
436.
pruebas de conmutador de orden N
pruebas de conmutador de multiplicidad N
N‐switch testing
437.
pruebas de a n elementos
NO APLICA
n‐wise testing
O
non‐conformity
Non fulfillment of a specified requirement. [ISO 9000]
NO APLICA.
A requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, NO APLICA. maintainability and portability. Procedure to derive and/or select test cases for non‐ non‐functional test design functional testing based on an analysis of the specification of NO APLICA. technique a component or system without reference to its internal structure. See also black box test design technique. Testing the attributes of a component or system that do not non‐functional testing relate to functionality, e.g. reliability, efficiency, usability, NO APLICA. maintainability and portability. non‐functional requirement:
The percentage of sequences of N+1 transitions that have NO APLICA. been exercised by a test suite. [Chow] A form of state transition testing in which test cases are designed to execute all valid sequences of N+1 transitions. NO APLICA. [Chow] See also state transition testing. A black box test design technique in which test cases are designed to execute all possible discrete combinations of any NO APLICA. set of n input parameters. See also combinatorial testing, orthogonal array testing, pairwise testing.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
438.
software de distribución masiva
software de distribución masiva
off‐the‐shelf software
439.
ATM
herramienta de código abierto
NO APLICA
open source tool
440.
ATA
operabilidad
operabilidad
operability
441.
ATT
pruebas de aceptación operativa
NO APLICA
operational acceptance testing:
442.
entorno de operaciones
entorno de operaciones
operational environment
perfil operativo
NO APLICA
operational profile
443.
ETM ATT
DESCRIPCIÓN EN INGLÉS 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. 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. The capability of the software product to enable the user to operate and control it. [ISO 9126] See also usability. 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. See also operational testing. Hardware and software products installed at users’ or customers’ sites where the component or system under test will be used. The software may include operating systems, database management systems, and other applications. 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.
OBSERVACIONES
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
444.
pruebas del perfil operativo
pruebas de perfil operativo
operational profile testing
Statistical testing using a model of system operations (short NO APLICA. duration tasks) and their probability of typical use. [Musa]
445.
ETM
perfilado operativo
NO APLICA
operational profiling
The process of developing and implementing an operational NO APLICA. profile. See also operational profile.
446.
pruebas operativas
pruebas operativas
operational testing
Testing conducted to evaluate a component or system in its NO APLICA. operational environment. [IEEE 610]
447.
oráculo
oráculo
oracle
448.
ATA
arreglo ortogonal
NO APLICA
orthogonal array
See test oracle.
NO APLICA.
A 2‐dimensional array constructed with special mathematical properties, such that choosing any two columns in the array NO APLICA. provides every pair combination of each number in the array.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
449.
ATA
pruebas de arreglos ortogonales
NO APLICA
orthogonal array testing
450.
resultado
resultado
outcome
451.
salida
salida
452.
dominio de salida
453.
454.
TÉRMINO TRADUCIDO
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A systematic way of testing all‐pair combinations of variables using orthogonal arrays. It significantly reduces the number of all combinations of variables to test all pair combinations. NO APLICA. See also combinatorial testing, n‐wise testing, pairwise testing. See result.
NO APLICA.
output
A variable (whether stored within a component or outside) that is written by a component.
NO APLICA.
dominio de salida
output domain
The set from which valid output values can be selected. See also domain.
NO APLICA.
valor de salida
valor de salida
output value
An instance of an output. See also output.
NO APLICA.
pruebas externalizadas
NO APLICA
outsourced testing
P
455.
programación en pareja
programación por pares
pair programming
456.
pruebas en pareja
pruebas por pares
pair testing
457.
ATT
pruebas de integración de a pares de elementos
NO APLICA
pairwise integration testing
458.
ATA
pruebas de a pares de elementos
NO APLICA
pairwise testing
459.
EITP
análisis de Pareto
NO APLICA
Pareto analysis
Testing performed by people who are not co‐located with the NO APLICA. project team and are not fellow employees.
A software development approach whereby lines of code (production and/or test) of a component are written by two NO APLICA. programmers sitting at a single computer. This implicitly means ongoing real‐time code reviews are performed. Two persons, e.g. two testers, a developer and a tester, or an end‐user and a tester, working together to find defects. NO APLICA. Typically, they share one computer and trade control of it while testing. A form of integration testing that targets pairs of NO APLICA. components that work together, as shown in a call graph. A black box test design technique in which test cases are designed to execute all possible discrete combinations of NO APLICA. each pair of input parameters. See also combinatorial testing, nwise testing, orthogonal array testing. A statistical technique in decision making that is used for selection of a limited number of factors that produce NO APLICA. significant overall effect. In terms of quality improvement, a
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
large majority of problems (80%) are produced by a few key causes (20%).
460.
pruebas de particiones
pruebas de partición
partition testing
See equivalence partitioning. [Beizer]
NO APLICA.
461.
pasar
pasar
pass
A test is deemed to pass if its actual result matches its expected result.
NO APLICA.
462.
criterios de paso/fallo
criterios de paso/fallo
pass/fail criteria
Decision rules used to determine whether a test item NO APLICA. (function) or feature has passed or failed a test. [IEEE 829]
463.
camino
camino
path
A sequence of events, e.g. executable statements, of a NO APLICA. component or system from an entry point to an exit point.
464.
cobertura de caminos
cobertura de camino
path coverage
The percentage of paths that have been exercised by a test NO APLICA. suite. 100% path coverage implies 100% LCSAJ coverage.
465.
forzado del camino
forzar camino
path sensitizing
Choosing a set of input values to force the execution of a given path.
NO APLICA.
466.
ATT
pruebas de camino
pruebas de camino
path testing
A white box test design technique in which test cases are designed to execute paths.
NO APLICA.
A review of a software work product by colleagues of the producer of the product for the purpose of identifying NO APLICA. defects and Improvements. Examples are inspection, technical review and walkthrough. The degree to which a system or component accomplishes its designated functions within given constraints regarding NO APLICA. processing time and throughput rate. [After IEEE 610] See also efficiency. A high level metric of effectiveness and/or efficiency used to guide and control progressive development, e.g. lead‐time NO APLICA. slip for software development. [CMMI]
467.
F
revisión entre pares
revisión entre pares
peer review
468.
rendimiento
rendimiento
performance
469.
indicador de rendimiento
indicador de rendimiento
performance indicator
470.
generación de perfiles de rendimiento
NO APLICA
performance profiling
The task of analyzing, e.g., identifying performance bottlenecks based on generated metrics, and tuning the NO APLICA. performance of a software component or system using tools.
471.
F
pruebas de rendimiento
pruebas de rendimiento
performance testing
The process of testing to determine the performance of a NO APLICA. software product. See also efficiency testing.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
F‐AT ATT
472.
473.
474.
ATA
herramienta de pruebas de rendimiento
herramienta de pruebas de rendimiento
performance testing tool
contención de fase
NO APLICA
phase containment
The percentage of defects that are removed in the same phase of the software lifecycle in which they were NO APLICA. introduced.
plan de prueba de la fase
plan de pruebas de fase
phase test plan
ATM
475.
ETM
planificación póker
NO APLICA
planning poker
476.
puntero
NO APLICA
pointer
477.
portabilidad
portabilidad
portability
pruebas de portabilidad
pruebas de portabilidad
portability testing
478.
F ATT
A tool to support performance testing that usually has two main facilities: load generation and test transaction measurement. Load generation can simulate either multiple users or high volumes of input data. During execution, NO APLICA. response time measurements are taken from selected transactions and these are logged. Performance testing tools normally provide reports based on test logs and graphs of load against response times.
F ATT
A test plan that typically addresses one test phase. See also test plan.
NO APLICA.
A consensus‐based estimation technique, mostly used to estimate effort or relative size of user stories in agile software development. It is a variation of the Wide Band NO APLICA. Delphi method using a deck of cards with values representing the units in which the team estimates. See also agile software development, Wide Band Delphi. A data item that specifies the location of another data item; for example, a data item that specifies the address of the NO APLICA. next employee record to be processed. [IEEE 610] The ease with which the software product can be transferred from one hardware or software environment to another. [ISO NO APLICA. 9126] The process of testing to determine the portability of a software product.
NO APLICA.
479.
postcondición
postcondición
postcondition
Environmental and state conditions that must be fulfilled NO APLICA. after the execution of a test or test procedure.
480.
comparación post‐
comparación post‐
post‐execution
Comparison of actual and expected results, performed after NO APLICA. the software has finished running.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
ejecución
ejecución
comparison
481.
reunión post proyecto
NO APLICA
post‐project meeting
482.
precondición
precondición
precondition
483.
predicado
NO APLICA
predicate
484.
resultado previsto
resultado previsto
predicted outcome
485.
prueba previa
prueba previa
486.
ATM
prioridad
487.
488.
DESCRIPCIÓN EN INGLÉS
See retrospective meeting.
OBSERVACIONES
NO APLICA.
Environmental and state conditions that must be fulfilled before the component or system can be executed with a NO APLICA. particular test or test procedure. A statement that can evaluate to true or false and may be used to determine the control flow of subsequent decision NO APLICA. logic. See also decision. See expected result.
NO APLICA.
pretest
See intake test.
NO APLICA.
prioridad
priority
The level of (business) importance assigned to an item, e.g. defect.
NO APLICA.
PRISMA (Product RISk MAnagement)
NO APLICA
PRISMA (Product RISk MAnagement)
F
efecto sonda
efecto sonda
probe effect
489.
problema
problema
problem
490.
gestión de problemas
gestión de problemas
problem management
491.
informe de problema
informe de problemas
problem report
492.
pruebas de procedimientos
NO APLICA
procedure testing:
493.
proceso
proceso
process
A systematic approach to risk‐based testing that employs product risk identification and analysis to create a product NO APLICA. risk matrix based on likelihood and impact. The effect on the component or system by the measurement instrument when the component or system is being measured, e.g. by a performance testing tool or monitor. For NO APLICA. example performance may be slightly worse when performance testing tools are being used. See defect.
NO APLICA.
See defect management.
NO APLICA.
See defect report.
NO APLICA.
Testing aimed at ensuring that the component or system can operate in conjunction with new or existing users’ business NO APLICA. procedures or operational procedures. A set of interrelated activities, which transform inputs into
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
outputs. [ISO 12207] A disciplined evaluation of an organization’s software NO APLICA. processes against a reference model. [after ISO 15504]
494.
EITP
evaluación del proceso
NO APLICA
process assessment
495.
prueba de ciclo de proceso
prueba de ciclo de proceso
process cycle test
496.
mejora del proceso
NO APLICA
process improvement
497.
EITP
modelo de proceso
NO APLICA
process model
498.
modelo de referencia de proceso
NO APLICA
process reference model
499.
ETM
pruebas conforme a proceso
NO APLICA
Testing that follows a set of defined processes, e.g., defined process‐compliant testing by an external party such as a standards committee. See also NO APLICA. standard‐compliant testing.
500.
ETAE
pruebas guiadas por proceso
NO APLICA
process‐driven testing
riesgo de producto
riesgo de producto
product risk
Product RISk MAnagement
NO APLICA
EITP
calidad basada en el producto
A black box test design technique in which test cases are designed to execute business procedures and processes. [TMap] See also procedure testing. A program of activities designed to improve the performance and maturity of the organization’s processes, and the result of such a program. [CMMI] A framework wherein processes of the same nature are classified into a overall model, e.g. a test improvement model. A process model providing a generic body of best practices and how to improve a process in a prescribed step‐by‐step manner.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
A scripting technique where scripts are structured into scenarios which represent use cases of the software under NO APLICA. test. The scripts can be parameterized with test data.
F F‐AT 501.
ATM
A risk directly related to the test object. See also risk.
NO APLICA.
ATA ATT 502.
503.
NO APLICA
Product RISk MAnagement See PRISMA.
product‐based quality
NO APLICA.
A view of quality, wherein quality is based on a well‐defined set of quality attributes. These attributes must be measured in an objective and quantitative way. Differences in the NO APLICA. quality of products of the same type can be traced back to the way the specific quality attributes have been
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
implemented. [After Garvin] See also manufacturing‐based quality, quality attribute, transcendent‐based quality, user‐ based quality, value‐based quality. 504.
pruebas de aceptación de producción
NO APLICA
production acceptance testing
505.
herramienta de instrumentación de programa
instrumentador de programa
program instrumenter
506.
pruebas de programa
pruebas de programa
program testing
507.
proyecto
proyecto
project
508.
EITP
retrospectiva del proyecto
NO APLICA
project retrospective
riesgo de proyecto
riesgo de proyecto
project risk
509.
ATM
510.
plan de prueba de proyecto
plan de pruebas de proyecto
project test plan
511.
pseudo‐aleatoria
pseudo‐aleatoria
pseudo‐random
Q
512.
DFC
NO APLICA
QFD
513.
cualificación
NO APLICA
qualification
514.
F
calidad
calidad
quality
F
See operational acceptance testing.
NO APLICA.
See instrumenter.
NO APLICA.
See component testing.
NO APLICA.
A project is a unique set of coordinated and controlled activities with start and finish dates undertaken to achieve an NO APLICA. objective conforming to specific requirements, including the constraints of time, cost and resources. [ISO 9000] A structured way to capture lessons learned and to create specific action plans for improving on the next project or next NO APLICA. project phase. A risk related to management and control of the (test) project, e.g. lack of ATM staffing, strict deadlines, changing NO APLICA. requirements, etc. See also risk. See master test plan.
NO APLICA.
A series which appears to be random but is in fact generated NO APLICA. according to some prearranged sequence.
See quality function deployment.
NO APLICA.
The process of demonstrating the ability to fulfill specified requirements. Note the term ‘qualified’ is used to designate NO APLICA. the corresponding status. [ISO 9000] The degree to which a component, system or process meets NO APLICA. specified requirements and/or user/customer needs and
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
expectations. [After IEEE 610] 515.
aseguramiento de la calidad
aseguramiento de la calidad
quality assurance
516.
atributo de calidad
atributo de calidad
quality attribute
517.
característica de calidad
característica de calidad
quality characteristic
518.
control de calidad
NO APLICA
quality control
519.
despliegue de la función de calidad
NO APLICA
quality function deployment
520.
puerta de calidad
NO APLICA
quality gate
521.
gestión de la calidad
gestión de la calidad
quality management
riesgo de calidad
NO APLICA
quality risk
R
522.
ATM
523.
F‐AT
ETM
matriz de asignación de responsabilidades (RACI)
NO APLICA
RACI matrix
Part of quality management focused on providing confidence NO APLICA. that quality requirements will be fulfilled. [ISO 9000] A feature or characteristic that affects an item’s quality. [IEEE 610]
NO APLICA.
See quality attribute.
NO APLICA.
The operational techniques and activities, part of quality management, that are focused on fulfilling quality requirements. [after ISO 8402] A method to transform user demands into design quality, to deploy the functions forming quality, and to deploy methods for achieving the design quality into subsystems and component parts, and ultimately to specific elements of the manufacturing process. [Akao] A special milestone in a project. Quality gates are located between those phases of a project strongly depending on the outcome of a previous phase. A quality gate includes a formal check of the documents of the previous phase. Coordinated activities to direct and control an organization with regard to quality. Direction and control with regard to quality generally includes the establishment of the quality policy and quality objectives, quality planning, quality control, quality assurance and quality improvement. [ISO 9000]
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
A product risk related to a quality attribute. See also quality NO APLICA. attribute, product ATM risk.
A matrix describing the participation by various roles in completing tasks or deliverables for a project or process. It is especially useful in clarifying roles and responsibilities. RACI NO APLICA. is an acronym derived from the four key responsibilities most typically used: Responsible, Accountable, Consulted, and
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
OBSERVACIONES
Informed. A black box test design technique where test cases are selected, possibly using a pseudo‐random generation algorithm, to match an operational profile. This technique NO APLICA. can be used for testing non‐functional attributes such as reliability and performance. A proprietary adaptable iterative software development process framework consisting of four project lifecycle phases: NO APLICA. inception, elaboration, construction and transition. Testing that dynamically responds to the actual system under test and test results being obtained. Typically reactive testing has a reduced planning cycle and the design and NO APLICA. implementation test phases are not carried out until the test object is received.
524.
pruebas aleatorias
pruebas aleatorias
random testing
525.
EITP
Rational Unified Process
NO APLICA
Rational Unified Process
526.
ETM
pruebas reactivas
NO APLICA
reactive testing
527.
ATT
herramienta de grabación/reproducción
herramienta de grabación/reproducción
record/playback tool
528.
notario
secretario
recorder
529.
capacidad de recuperación
recuperabilidad
recoverability
The capability of the software product to re‐establish a specified level of performance and recover the data directly NO APLICA. affected in case of failure. [ISO 9126] See also reliability.
530.
ATT
pruebas de capacidad de recuperación
pruebas de recuperabilidad
recoverability testing
The process of testing to determine the recoverability of a NO APLICA. software product. See also reliability testing.
531.
pruebas de recuperación
pruebas de recuperación
recovery testing
532.
F‐AT
See capture/playback tool.
NO APLICA.
See scribe.
NO APLICA.
See recoverability testing.
NO APLICA.
pruebas de regresión
pruebas de regresión
regression testing
Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software, as a result of NO APLICA. the changes made. It is performed when the software or its environment is changed. Testing using various techniques to manage the risk of regression, e.g., by designing re‐usable testware and by NO APLICA. extensive automation of testing at one or more test levels.
F
ETAE
DESCRIPCIÓN EN INGLÉS
533.
ETM
pruebas adversas a la regresión
NO APLICA
regression‐averse testing
534.
pruebas de regulación
pruebas de regulación
regulation testing
See compliance testing.
NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
535.
nota de la entrega
nota de la entrega
release note
536.
fiabilidad
fiabilidad
reliability
537.
ATT
modelo del crecimiento de la fiabilidad
NO APLICA
reliability growth model
pruebas de fiabilidad
pruebas de fiabilidad
reliability testing
538.
TÉRMINO TRADUCIDO
F ATT
539.
ATT
capacidad de ser reemplazado
reemplazabilidad
replaceability
540.
F
requisito
requisito
requirement
541.
F
herramienta de gestión de requisitos
herramienta de gestión de requisitos
requirements management tool
542.
fase de requisitos
fase de requisitos
requirements phase
543.
ATA
pruebas basadas en requisitos
pruebas basadas en requisitos
requirements‐based testing
544.
utilización de recursos
utilización de recursos
resource utilization
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A document identifying test items, their configuration, current status and other delivery information delivered by NO APLICA. development to testing, and possibly other stakeholders, at the start of a test execution phase. [After IEEE 829] The ability of the software product to perform its required functions under stated conditions for a specified period of NO APLICA. time, or for a specified number of operations. [ISO 9126] A model that shows the growth in reliability over time during continuous testing of a component or system as a result of NO APLICA. the removal of defects that result in reliability failures. The process of testing to determine the reliability of a software product. The capability of the software product to be used in place of another specified software product for the same purpose in the same environment. [ISO 9126] See also portability. 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. [After IEEE 610] A tool that supports the recording of requirements, requirements attributes (e.g. priority, knowledge responsible) and annotation, and facilitates traceability through layers of requirements and requirements change management. Some requirements management tools also provide facilities for static analysis, such as consistency checking and violations to predefined requirements rules. The period of time in the software lifecycle during which the requirements for a software product are defined and documented. [IEEE 610] An approach to testing in which test cases are designed based on test objectives and test conditions derived from requirements, e.g. tests that exercise specific functions or probe non‐functional attributes such as reliability or usability. The capability of the software product to use appropriate amounts and types of resources, for example the amounts of
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions. [After ISO 9126] See also efficiency. 545.
pruebas de utilización de recursos
pruebas de utilización de recursos
resource utilization testing
546.
resultado
resultado
result
547.
criterios de reanudación
criterios de reanudación
resumption criteria
548.
requisitos de reanudación
NO APLICA
resumption requirements
repetición de las pruebas
repetición de pruebas
re‐testing
reunión retrospectiva
NO APLICA
retrospective meeting
revisión
revisión
review
549.
550.
551.
ATT
F ETAE EITP
F ATM
552.
ATM
plan de revisión
NO APLICA
review plan
553.
F
herramienta de revisión
herramienta de revisión
review tool
The process of testing to determine the resource‐utilization NO APLICA. of a software product. See also efficiency testing. The consequence/outcome of the execution of a test. It includes outputs to screens, changes to data, reports, and NO APLICA. communication messages sent out. See also actual result, expected result. The criteria used to restart all or a portion of the testing NO APLICA. activities that were suspended previously. The defined set of testing activities that must be repeated NO APLICA. when testing is re‐started after a suspension. [After IEEE 829] See confirmation testing. A meeting at the end of a project during which the project team members evaluate the project and learn lessons that can be applied to the next project. An evaluation of a product or project status to ascertain discrepancies from planned results and to recommend improvements. Examples include management review, informal review, technical review, inspection, and walkthrough. [After IEEE 1028] A document describing the approach, resources and schedule of intended review activities. It identifies, amongst others: documents and code to be reviewed, review types to be used, participants, as well as entry and exit criteria to be applied in case of formal reviews, and the rationale for their choice. It is a record of the review planning process. A tool that provides support to the review process. Typical features include review planning and tracking support, communication support, collaborative reviews and a repository for collecting and reporting of metrics.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
PROGRAMA DE ESTUDIOS
554.
F ATM
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
revisor
revisor
reviewer
The person involved in the review that identifies and describes anomalies in the product or project under review. NO APLICA. Reviewers can be chosen to represent different viewpoints and roles in the review process.
riesgo
riesgo
risk
A factor that could result in future negative consequences; NO APLICA. usually expressed as impact and likelihood.
análisis del riesgo
análisis de riesgos
risk analysis
The process of assessing identified project or product risks to determine their level of risk, typically by estimating their NO APLICA. impact and probability of occurrence (likelihood). The process of identifying and subsequently analyzing the identified project or product risk to determine its level of risk, typically by assigning likelihood and impact ratings. See also NO APLICA. product risk, project risk, risk, risk impact, risk level, risk likelihood.
F 555.
ATM ETAE ATM
556.
ATA ATT ATM
557.
ATT
evaluación del riesgo
NO APLICA
risk assessment
categoría del riesgo
NO APLICA
risk category:
control del riesgo
control de riesgos
risk control
The process through which decisions are reached and protective measures are implemented for reducing risks to, NO APLICA. or maintaining risks within, specified levels.
identificación del riesgo
identificación de riesgos
risk identification
The process of identifying risks using techniques such as NO APLICA. brainstorming, checklists and failure history.
ETAE 558.
ATM
559.
ATA ATT
See risk type.
NO APLICA.
ATM 560.
ATA ATT
561.
impacto del riesgo
NO APLICA
risk impact
562.
ATM
nivel de riesgo
NO APLICA
risk level
The damage that will be caused if the risk become an actual outcome or event.
NO APLICA.
The importance of a risk as defined by its characteristics NO APLICA. impact and likelihood. The level of risk can be used to
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
ATA
564.
ATM ATA
OBSERVACIONES
determine the intensity of testing to be performed. A risk level can be expressed either qualitatively (e.g. high, medium, low) or quantitatively.
ATT 563.
DESCRIPCIÓN EN INGLÉS
probabilidad del riesgo
NO APLICA
risk likelihood
gestión del riesgo
gestión de riesgos
risk management
mitigación del riesgo
mitigación de riesgos
risk mitigation
The estimated probability that a risk will become an actual outcome or event.
NO APLICA.
Systematic application of procedures and practices to the tasks of identifying, analyzing, prioritizing, and controlling NO APLICA. risk.
ATM 565.
ATA ATT
See risk control.
NO APLICA.
ETAE
566.
tipo de riesgo
NO APLICA
risk type
A set of risks grouped by one or more common factors such as a quality attribute, cause, location, or potential effect of risk;. A specific set of product risk types is related to the type NO APLICA. of testing that can mitigate (control) that risk type. For example the risk of user‐interactions being misunderstood can be mitigated by usability testing.
pruebas basadas en el riesgo
NO APLICA
risk‐based testing
An approach to testing to reduce the level of product risks and inform stakeholders of their status, starting in the initial NO APLICA. stages of a project. It involves the identification of product risks and the use of risk levels to guide the test process. The degree to which a component or system can function correctly in the presence of invalid inputs or stressful NO APLICA. environmental conditions. [IEEE 610] See also error‐ tolerance, faulttolerance.
F 567.
ATM ATA ATT
568.
ATT
robustez
robustez
robustness
569.
F
pruebas de robustez
pruebas de robustez
robustness testing
Testing to determine the robustness of the software product.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
570.
ATM
causa raíz
causa raíz
root cause
571.
ATA
análisis de la causa raíz
NO APLICA
root cause analysis
572.
RUP
NO APLICA
RUP
S
573.
ETM
metodología de objetivos S.M.A.R.T.
NO APLICA
S.M.A.R.T. goal methodology
574.
seguridad física
seguridad (efectos adversos)
safety
575.
sistema de seguridad crítica
NO APLICA
safety critical system
576.
pruebas de seguridad física
pruebas de seguridad (efectos adversos)
safety testing
577.
prueba de salud
pruebas de circunspección
sanity test
578.
escalabilidad
escalabilidad
scalability
579.
pruebas de escalabilidad
pruebas de escalabilidad
scalability testing
Testing to determine the scalability of the software product.
NO APLICA.
580.
pruebas de escenario
NO APLICA
scenario testing
See use case testing.
NO APLICA.
581.
cuadro de mando
NO APLICA
scorecard
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A source of a defect such that if it is removed, the occurrence NO APLICA. of the defect type is decreased or removed. [CMMI] An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes, it is NO APLICA. hoped that the likelihood of defect recurrence will be minimized. See Rational Unified Process.
NO APLICA.
A methodology whereby objectives are defined very specifically rather than generically. SMART is an acronym NO APLICA. derived from the attributes of the objective to be defined: Specific, Measurable, Attainable, Relevant and Timely. The capability of the software product to achieve acceptable levels of risk of harm to people, business, software, property NO APLICA. or the environment in a specified context of use. [ISO 9126] A system whose failure or malfunction may result in death or serious injury to people, or loss or severe damage to NO APLICA. equipment, or environmental harm. Testing to determine the safety of a software product.
NO APLICA.
See smoke test.
NO APLICA.
The capability of the software product to be upgraded to NO APLICA. accommodate increased loads. [After Gerrard]
A representation of summarized performance measurements representing progress towards the implementation of long‐ NO APLICA. term goals. A scorecard provides static measurements of
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
performance over or at the end of a defined interval. See also balanced scorecard, dashboard. The person who records each defect mentioned and any suggestions for process improvement during a review NO APLICA. meeting, on a logging form. The scribe should ensure that the logging form is readable and understandable.
582.
F
escriba
escriba
scribe
583.
prueba mediante guion
pruebas programadas
scripted testing
584.
F
lenguaje de guion
lenguaje de creación de scripts
scripting language
585.
EITP
SCRUM
NO APLICA
SCRUM
586.
seguridad
seguridad
security
pruebas de seguridad
pruebas de seguridad
security testing
Testing to determine the security of the software product. NO APLICA. See also functionality testing.
A tool that provides support for testing security NO APLICA. characteristics and vulnerabilities.
Test execution carried out by following a previously documented sequence of tests.
NO APLICA.
A programming language in which executable test scripts are written, used by a test execution tool (e.g. a NO APLICA. capture/playback tool). An iterative incremental framework for managing projects commonly used with agile software development. See also NO APLICA. agile software development. Attributes of software products that bear on its ability to prevent unauthorized access, whether accidental or NO APLICA. deliberate, to programs and data. [ISO 9126] See also functionality.
F 587.
F‐AT ATT
588.
herramienta de pruebas de seguridad
herramienta de pruebas de seguridad
security testing tool
589.
F
herramienta de seguridad
herramienta de seguridad
security tool
590.
pruebas de la capacidad de servicio
pruebas de capacidad de servicio
serviceability testing
591.
gestión de prueba basada en sesiones
NO APLICA
session‐based test management
592.
pruebas basadas en
NO APLICA
session‐based testing
A tool that supports operational security.
NO APLICA.
See maintainability testing.
NO APLICA.
A method for measuring and managing session‐based testing, NO APLICA. e.g. exploratory testing. An approach to testing in which test activities are planned
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
sesiones
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
as uninterrupted sessions of test design and execution, often used in conjunction with exploratory testing.
593.
ATM
severidad
severidad
severity
594.
ETM
gráfico de Shewhart
NO APLICA
Shewhart chart
595.
ATT
cortocircuitado
NO APLICA
short‐circuiting
596.
simulación
simulación
simulation
597.
simulador
simulador
simulator
598.
pruebas de aceptación in situ
pruebas de aceptación in situ
site acceptance testing
599.
prueba de humo
pruebas de humo
smoke test
600.
software
software
software
601.
ataque software
NO APLICA
software attack
602.
Análisis de Modos de Fallo y Efectos en el Software (AMFES)
NO APLICA
Software Failure Mode and Effect Analysis (SFMEA)
The degree of impact that a defect has on the development NO APLICA. or operation of a component or system. [After IEEE 610] See control chart. A programming language/interpreter technique for evaluating compound conditions in which a condition on one side of a logical operator may not be evaluated if the condition on the other side is sufficient to determine the final outcome. The representation of selected behavioral characteristics of one physical or abstract system by another system. [ISO 2382/1] A device, computer program or system used during testing, which behaves or operates like a given system when provided with a set of controlled inputs. [After IEEE 610, DO178b] See also emulator. Acceptance testing by users/customers at their site, to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes, normally including hardware as well as software. A subset of all defined/planned test cases that cover the main functionality of a component or system, to ascertaining that the most crucial functions of a program work, but not bothering with finer details. See also build, verification test, intake test. Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system. [IEEE 610] See attack.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA. NO APLICA.
See Failure Mode and Effect Analysis (FMEA).
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
603.
Análisis de Modos de Fallo, Efectos y Criticidad en el Software (AMFECS)
NO APLICA
Software Failure Mode, Effects, and Criticality Analysis (SFMECA)
604.
Análisis del Árbol de Faltas Software (AAFS)
NO APLICA
Software Fault Tree Analysis (SFTA)
605.
prestación software
prestación del software
software feature
606.
607.
F‐AT EITP
nivel de integridad software
NO APLICA
software integrity level
ciclo de vida del software
NO APLICA
software lifecycle
608.
EITP
Mejora del Proceso Software
NO APLICA
Software Process Improvement
609.
característica de producto software
característica de producto software
software product characteristic
610.
calidad del software
calidad del software
software quality
611.
característica de calidad del software
característica de calidad del software
software quality characteristic
612.
incidencia de prueba
incidencia de prueba
software test incident
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
See Failure Mode, Effects, and Criticality Analysis (FMECA).
NO APLICA.
See Fault Tree Analysis (FTA).
Análisis del Árbol de Defectos Software (AADS)
See feature.
NO APLICA.
The degree to which software complies or must comply with a set of stakeholder‐selected software and/or software‐ based system characteristics (e.g., software complexity, risk NO APLICA. assessment, safety level, security level, desired performance, reliability, or cost) which are defined to reflect the importance of the software to its stakeholders. The period of time that begins when a software product is conceived and ends when the software is no longer available for use. The software lifecycle typically includes a concept phase, requirements phase, design phase, implementation NO APLICA. phase, test phase, installation and checkout phase, operation and maintenance phase, and sometimes, retirement phase. Note these phases may overlap or be performed iteratively. A program of activities designed to improve the performance and maturity of the organization’s software processes and NO APLICA. the results of such a program. [After CMMI] See quality attribute.
NO APLICA.
The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied NO APLICA. needs. [After ISO 9126] See also quality. See quality attribute.
NO APLICA.
See incident.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
software
software
TÉRMINO EN INGLÉS
613.
informe de incidencia de la prueba software
informe de incidencias de pruebas software
software test incident report:
614.
ATA
Inventario de Medición de Usabilidad Software (IMUS)
Inventario de Medición de Usabilidad Software (IMUS)
Software Usability Measurement Inventory (SUMI)
615.
sentencia fuente
sentencia fuente
source statement
DESCRIPCIÓN EN INGLÉS
See incident report.
OBSERVACIONES
NO APLICA.
A questionnaire‐based usability test technique for measuring software quality from the end user's point of view. NO APLICA. [Veenendaal04] See statement.
NO APLICA.
A document that specifies, ideally in a complete, precise and verifiable manner, the requirements, design, behavior, or other characteristics of a component or system, and, often, NO APLICA. the procedures for determining whether these provisions have been satisfied. [After IEEE 610]
616.
especificación
especificación
specification
617.
ATA
técnica basada en la especificación
técnica basada en especificación
specification‐based technique
See black box test design technique.
NO APLICA.
618.
técnica de diseño de prueba basada en la especificación
técnica de diseño de pruebas basada en la especificación
specification‐based test design technique
See black box test design technique.
NO APLICA.
619.
pruebas basadas en la especificación
pruebas basadas en la especificación
specification‐based testing
See black box testing.
NO APLICA.
620.
entrada especificada
entrada especificada
specified input
An input for which the specification predicts a result.
NO APLICA.
621.
EITP
MPS
NO APLICA
SPI
See Software Process Improvement.
NO APLICA.
622.
ATT
estabilidad
estabilidad
stability
623.
EITP
representación por niveles
NO APLICA
staged representation
The capability of the software product to avoid unexpected effects from modifications in the software. [ISO 9126] See NO APLICA. also maintainability. A model structure wherein attaining the goals of a set of process areas establishes a maturity level; each level builds a NO APLICA. foundation for subsequent levels. [CMMI]
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
624.
EITP
estándar
NO APLICA
standard
625.
software estándar
software estándar
standard software
626.
ETM
pruebas conforme a estándar
NO APLICA
standard‐compliant testing
627.
pruebas de estándares
pruebas de estándares
standards testing:
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
Formal, possibly mandatory, set of requirements developed and used to prescribe consistent approaches to the way of NO APLICA. working or to provide guidelines (e.g., ISO/IEC standards, IEEE standards, and organizational standards). [After CMMI] See off‐the‐shelf software.
NO APLICA.
Testing that complies to a set of requirements defined by a standard, e.g., an industry testing standard or a standard for NO APLICA. testing safety‐critical systems. See also process‐compliant testing. See compliance testing.
NO APLICA.
A diagram that depicts the states that a component or system can assume, and shows the events or circumstances NO APLICA. that cause and/or result from a change from one state to another. [IEEE 610] A grid showing the resulting transitions for each state combined with each possible event, showing both valid and NO APLICA. invalid transitions.
628.
diagrama de estados
diagrama de estado
state diagram
629.
tabla de estados
tabla de estado
state table
630.
transición de estado
transición de estado
state transition
F ATA
pruebas de transición de estado
pruebas de transición de estado
state transition testing
A black box test design technique in which test cases are designed to execute valid and invalid state transitions. See NO APLICA. also N‐switch testing.
632.
sentencia
sentencia
statement
An entity in a programming language, which is typically the NO APLICA. smallest indivisible unit of execution.
633.
F
cobertura de sentencias
cobertura de sentencia
statement coverage
The percentage of executable statements that have been NO APLICA. exercised by a test suite.
634.
ATT
pruebas de sentencia
pruebas de sentencia
statement testing
análisis estático
análisis estático
static analysis
herramienta de análisis
herramienta de análisis
static analysis tool
631.
635.
636.
TÉRMINO TRADUCIDO
F ATT F
A transition between two states of a component or system.
NO APLICA.
A white box test design technique in which test cases are NO APLICA. designed to execute statements. Analysis of software development artifacts, e.g. requirements or code, carried out without execution of these software NO APLICA. development artifacts. Static analysis is usually carried out by means of a supporting tool. See static analyzer.
NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
estático
estático
TÉRMINO EN INGLÉS
637.
ATT
analizador estático
analizador estático
static analyzer
638.
análisis estático de código
análisis estático de código
static code analysis:
639.
analizador estático de código
analizador estático de código
static code analyzer
640.
F
pruebas estáticas
pruebas estáticas
static testing
641.
pruebas estadísticas
pruebas estadísticas
statistical testing
642.
información de estado
información de estado
status accounting
STEP
NO APLICA
STEP
643.
TÉRMINO TRADUCIDO
ATM EITP
644.
almacenamiento
almacenamiento
storage
645.
pruebas de almacenamiento
pruebas de almacenamiento
storage testing
646.
F
pruebas de estrés
pruebas de estrés
stress testing
647.
F
herramienta de pruebas
herramienta de pruebas
stress testing tool
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A tool that carries out static analysis.
NO APLICA.
Analysis of source code carried out without execution of that software.
NO APLICA.
A tool that carries out static code analysis. The tool checks source code, for certain properties such as conformance to coding standards, quality metrics or data flow anomalies. Testing of a software development artifact, e.g., requirements, design or code, without execution of these artifacts, e.g., reviews or static analysis. A test design technique in which a model of the statistical distribution of the input is used to construct representative test cases. See also operational profile testing. An element of configuration management, consisting of the recording and reporting of information needed to manage a configuration effectively. This information includes a listing of the approved configuration identification, the status of proposed changes to the configuration, and the implementation status of the approved changes. [IEEE 610]
NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
See Systematic Test and Evaluation Process.
NO APLICA.
See resource utilization.
NO APLICA.
See resource utilization testing.
NO APLICA.
A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified workloads, or with reduced NO APLICA. availability of resources such as access to memory or servers. [After IEEE 610] See also performance testing, load testing. A tool that supports stress testing.
NO APLICA.
PROGRAMA DE ESTUDIOS
TRADUCCIÓN PREVIA
de estrés
de estrés
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
Coverage measures based on the internal structure of a component or system.
NO APLICA.
See white‐box test design technique.
NO APLICA.
648.
cobertura estructural
cobertura estructural
structural coverage
649.
técnica de diseño de prueba estructural
técnica de diseño de prueba estructural
structural test design technique
650.
F
pruebas estructurales
pruebas estructurales
structural testing
See white‐box testing.
NO APLICA.
651.
ATT
técnica basada en la estructura
técnicas basadas en la estructura
structure‐based technique:
See white‐box test design technique.
NO APLICA.
652.
técnica de diseño de prueba basada en la estructura
NO APLICA
structure‐based test design technique
See white‐box test design technique.
NO APLICA.
653.
F
pruebas basadas en la estructura
NO APLICA
structure‐based testing
See white‐box testing.
NO APLICA.
654.
ETAE
guion estructurado
NO APLICA
structured scripting
655.
revisión guiada estructurada
revisión guiada estructurada
structured walkthrough
656.
TÉRMINO TRADUCIDO
F ETAE
stub
stub
stub
657.
subcamino
subcamino
subpath
658.
adecuación
adecuación
suitability
659.
ATA
pruebas de adecuación
NO APLICA
suitability testing
A scripting technique that builds and utilizes a library of NO APLICA. reusable (parts of) scripts. See walkthrough.
NO APLICA.
A skeletal or special‐purpose implementation of a software component, used to develop or test a component that calls NO APLICA. or is otherwise dependent on it. It replaces a called component. [After IEEE 610] A sequence of executable statements within a component.
NO APLICA.
The capability of the software product to provide an appropriate set of functions for specified tasks and user NO APLICA. objectives. [ISO 9126] See also functionality. The process of testing to determine the suitability of a software product.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
660.
ATA
IMUS
NO APLICA
SUMI
661.
criterios de suspensión
criterios de suspensión
suspension criteria
662.
ETAE
SSP
NO APLICA
SUT
663.
pruebas de sintáxis
pruebas sintácticas
syntax testing
664.
sistema
sistema
system
665.
pruebas de integración de sistemas
pruebas de integración de sistema
666.
sistema de sistemas
NO APLICA
667.
pruebas de sistema
NO APLICA
system testing
668.
sistema sujeto a prueba
NO APLICA
system under test
ATM
NO APLICA
EITP
Systematic Test and Evaluation Process
Systematic Test and Evaluation Process
T
670.
TGP
NO APLICA
TDD
revisión técnica
revisión técnica
technical review
669.
671.
F ATM
DESCRIPCIÓN EN INGLÉS
See Software Usability Measurement Inventory.
OBSERVACIONES
NO APLICA.
The criteria used to (temporarily) stop all or a portion of the NO APLICA. testing activities on the test items. [After IEEE 829] Acronym for system under test.
NO APLICA.
A black box test design technique in which test cases are designed based upon the definition of the input domain NO APLICA. and/or output domain. A collection of components organized to accomplish a NO APLICA. specific function or set of functions. [IEEE 610]
Testing the integration of systems and packages; testing system integration testing interfaces to external organizations (e.g. Electronic Data NO APLICA. Interchange, Internet). Multiple heterogeneous, distributed systems that are embedded in networks at multiple levels and in multiple system of systems interconnected domains, addressing large‐scale inter‐ NO APLICA. disciplinary common problems and purposes, usually without a common management structure. The process of testing an integrated system to verify that it NO APLICA. meets specified requirements. [Hetzel] See test object.
NO APLICA.
A structured testing methodology, also used as a EITP content‐based model for improving the testing process. Proceso Sistemático de Systematic Test and Evaluation Process (STEP) does not Evaluación y Pruebas require that improvements occur in a specific order. See also content‐based model.
See test‐driven development.
NO APLICA.
A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. [Gilb and NO APLICA. Graham], [IEEE 1028] See also peer review.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
672.
prueba
prueba
test
673.
ETAE
capa de adaptación de la prueba
NO APLICA
test adaption layer
674.
análisis de prueba
NO APLICA
test analysis
enfoque de prueba
enfoque de pruebas
test approach
F 675.
F‐AT ATM
DESCRIPCIÓN EN INGLÉS A set of one or more test cases. [IEEE 829] The layer in a generic test automation architecture which provides the necessary code to adapt the automated tests for the various components, configuration or interfaces of the SUT. The process of analyzing the test basis and defining test objectives. The implementation of the test strategy for a specific project. It typically includes the decisions made that follow based on the (test) project’s goal and the risk assessment carried out, starting points regarding the test process, the test design techniques to be applied, exit criteria and test types to be performed (1) A person who provides guidance and strategic direction for a test organization and for its relationship with other disciplines. (2) A person who defines the way testing is structured for a given system, including topics such as test tools and test data management. The use of software to perform or support test activities, e.g. test management, test design, test execution and results checking.
OBSERVACIONES NO APLICA.
NO APLICA.
NO APLICA.
NO APLICA.
676.
ETM
arquitecto de la prueba
NO APLICA
test architect
677.
F‐AT
automatización de la prueba
automatización de pruebas
test automation
678.
ETAE
arquitectura de autimatización de la prueba
NO APLICA
test automation architecture
An instantiation of the generic test automation architecture to define the architecture of a test automation solution, i.e., NO APLICA. its layers, components, services and interfaces.
679.
ETAE
ingeniero de autimatización de la prueba
NO APLICA
test automation engineer
A person who is responsible for the design, implementation and maintenance of a test automation architecture as well as NO APLICA. the technical evolution of the resulting test automation solution.
680.
ETAE
marco de trabajo de automatización de la prueba
NO APLICA
test automation framework
A tool that provides an environment for test automation. It NO APLICA. usually includes a test harness and test libraries.
681.
ETAE
jefe de automatización de
NO APLICA
NO APLICA.
NO APLICA.
A person who is responsible for the planning and supervision test automation manager of the development and evolution of a test automation NO APLICA. solution.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
la prueba
682.
ETAE
solución de automatización de la prueba
683.
ETAE
estrategia de automatización de la prueba
684.
685.
F‐AT
F
test automation solution
NO APLICA
test automation strategy
A high‐level plan to achieve long‐term objectives of test NO APLICA. automation under given boundary conditions. All documents from which the requirements of a component or system can be inferred. The documentation on which the test cases are based. If a document can be amended only by NO APLICA. way of formal amendment procedure, then the test basis is called a frozen test basis. [After TMap]
base de prueba
base de prueba
test basis
cama de la prueba
cama de pruebas
test bed
caso de prueba
caso de prueba
test case
técnica de diseño de caso de prueba
técnica de diseño de casos de prueba
test case design technique
688.
ETAE
resultado del caso de prueba
NO APLICA
test case result
689.
F
especificación de caso de prueba
especificación de casos de prueba
test case specification
690.
juego de casos de prueba
juego de casos de prueba
test case suite
691.
F‐AT
contrato de la prueba
contrato de pruebas
test charter
686.
687.
F
NO APLICA
A realization/implementation of a test automation architecture, i.e., a combination of components implementing a specific test automation assignment. The NO APLICA. components may include off‐the‐shelf test tools, test automation frameworks, as well as test hardware.
ATM
See test environment.
NO APLICA.
A set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a NO APLICA. particular program path or to verify compliance with a specific requirement. [After IEEE 610] See test design technique.
NO APLICA.
The final verdict on the execution of a test and its outcomes, like pass, fail, or error. The result of error is used for NO APLICA. situations where it is not clear whether the problem is in the test object. A document specifying a set of test cases (objective, inputs, test actions, expected results, and execution preconditions) NO APLICA. for a test item. [After IEEE 829] See also test specification. See test suite.
NO APLICA.
A statement of test objectives, and possibly test ideas about how to test. Test charters are used in exploratory testing. See NO APLICA. also exploratory testing.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
ATA
692.
ATM
cierre de la prueba
cierre de pruebas
test closure
693.
F
comparador de prueba
comparador de pruebas
test comparator
694.
comparación de pruebas
comparación de pruebas
test comparison
695.
criterios de compleción de la prueba
criterios de compleción de pruebas
test completion criteria
condición de prueba
condición de prueba
test condition
An item or event of a component or system that could be verified by one or more test cases, e.g. a function, NO APLICA. transaction, feature, quality attribute, or structural element. A test management task that deals with developing and applying a set of corrective actions to get a test project on NO APLICA. track when monitoring shows a deviation from what was planned. See also test management.
696.
F ATM F
697.
ATM
control de la prueba
control de pruebas
test control
ATA
During the test closure phase of a test process data is collected from completed activities to consolidate experience, testware, facts and numbers. The test closure NO APLICA. phase consists of finalizing and archiving the testware and evaluating the test process, including preparation of a test evaluation report. See also test process. A test tool to perform automated test comparison of actual NO APLICA. results with expected results. The process of identifying differences between the actual results produced by the component or system under test and the xpected results for NO APLICA. a test. Test comparison can be performed during test execution (dynamic comparison) or after test execution. See exit criteria.
NO APLICA.
698.
F
cobertura de la prueba
cobertura de pruebas
test coverage
See coverage.
NO APLICA.
699.
ciclo de prueba
ciclo de pruebas
test cycle
Execution of the test process against a single identifiable release of the test object.
NO APLICA.
700.
F
datos de prueba
datos de prueba
test data
Data that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or NO APLICA. system under test.
701.
gestión de datos de prueba
NO APLICA
test data management
The process of analyzing test data requirements, designing NO APLICA. test data structures, creating and maintaining test data.
PROGRAMA DE ESTUDIOS
702.
F ATA
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
herramienta de preparación de datos de prueba
herramienta de preparación de datos de prueba
TÉRMINO EN INGLÉS
OBSERVACIONES
A type of test tool that enables data to be selected from test data preparation tool existing databases or created, generated, manipulated and NO APLICA. edited for use in testing. The layer in a generic test automation architecture which supports test implementation by supporting the definition of NO APLICA. test suites and/or test cases, e.g., by offering templates or guidelines. Any test (work) product that must be delivered to someone other than the test (work) product’s author. See also NO APLICA. deliverable.
703.
ETAE
capa de definición de la prueba
704.
entrega de la prueba
NO APLICA
test deliverable
diseño de la prueba
diseño de pruebas
test design
(1) See test design specification. (2) The process of transforming general test objectives into NO APLICA. tangible test conditions and test cases.
especificación de diseño de prueba
test design specification
A document specifying the test conditions (coverage items) for a test item, the detailed test approach and identifying the NO APLICA. associated high level test cases. [After IEEE 829] See also test specification.
test design technique
NO APLICA
test definition layer
F 705.
ATM ATA
706.
especificación de diseño de prueba
707.
F
técnica de diseño de prueba
técnica de diseño de prueba
ATA
herramienta de diseño de pruebas
herramienta de diseño de pruebas
test design tool
709.
ATM
director de prueba
NO APLICA
test director
710.
controlador de prueba
controlador de prueba
test driver
711.
F
entorno de prueba
entorno de pruebas
test environment
712.
F‐AT
estimación de la prueba
NO APLICA
test estimation
708.
DESCRIPCIÓN EN INGLÉS
F
Procedure used to derive and/or select test cases.
NO APLICA.
A tool that supports the test design activity by generating test inputs from a specification that may be held in a CASE NO APLICA. tool repository, e.g. requirements management tool, from specified test conditions held in the tool itself, or from code. A senior manager who manages test managers. See also test manager.
NO APLICA.
See driver.
NO APLICA.
An environment containing hardware, instrumentation, simulators, software tools, and other support elements NO APLICA. needed to conduct a test. [After IEEE 610] The calculated approximation of a result related to various NO APLICA. aspects of testing (e.g. effort spent, completion date, costs
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
ATM
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
involved, number of test cases, etc.) which is usable even if input data may be incomplete, uncertain, or noisy. A document produced at the end of the test process summarizing all testing activities and results. It also contains NO APLICA. an evaluation of the test process and lessons learned.
informe de evaluación de prueba
informe de la evaluación de las pruebas
test evaluation report
ejecución de una prueba
ejecución de prueba
test execution
The process of running a test on the component or system NO APLICA. under test, producing actual result(s).
automatización de la ejecución de la pruéba
automatización de pruebas
test execution automation
The use of software, e.g. capture/playback tools, to control the execution of tests, the comparison of actual results to NO APLICA. expected results, the setting up of test preconditions, and other test control and reporting functions.
ETAE
capa de ejecución de la prueba
NO APLICA
test execution layer
The layer in a generic test automation architecture which NO APLICA. supports the execution of test suites and/or test cases.
717.
fase de ejecución de prueba
fase de ejecución de pruebas
test execution phase
718.
F
calendario de ejecución de prueba
calendario de ejecución de pruebas
test execution schedule
719.
técnica de ejecución de prueba
técnica de ejecución de pruebas
test execution technique
The method used to perform the actual test execution, either NO APLICA. manual or automated.
herramienta de ejecución de pruebas
herramienta de ejecución de pruebas
test execution tool
A type of test tool that is able to execute other software using an automated test script, e.g. capture/playback. NO APLICA. [Fewster and Graham]
fallar prueba
fallo de prueba
test fail
713.
714.
ATM
F‐AT
ATA
715.
716.
F‐AT ETAE
The period of time in a software development lifecycle during which the components of a software product are executed, NO APLICA. and the software product is evaluated to determine whether or not requirements have been satisfied. [IEEE 610] A scheme for the execution of test procedures. Note: The test procedures are included in the test execution schedule in NO APLICA. their context and in the order in which they are to be executed.
F 720.
ATA ATT ETAE
721.
See fail.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
722.
ETAE
capa de generación de la prueba
NO APLICA
test generation layer
723.
generador de la prueba
generador de pruebas
test generator
724.
F
arnés de prueba
arnés de pruebas
725.
ETAE
anzuelo de prueba
ATM
implementación de prueba
726.
ATA
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
The layer in a generic test automation architecture which supports manual or automated design of test suites and/or NO APLICA. test cases. See test data preparation tool.
NO APLICA.
test harness
A test environment comprised of stubs and drivers needed to execute a test.
NO APLICA.
NO APLICA
test hook
A customized software interface that enables automated testing of a test object.
NO APLICA.
NO APLICA
test implementation
The process of developing and prioritizing test procedures, creating test data and, optionally, preparing test harnesses NO APLICA. and writing automated test scripts. A plan for achieving organizational test process improvement objectives based on a thorough understanding of the current NO APLICA. strengths and weaknesses of the organization’s test processes and test process assets. [After CMMI]
727.
EITP
plan de mejora de prueba
NO APLICA
test improvement plan
728.
incidencia de prueba
incidencia de prueba
test incident
729.
informe de incidencia de la prueba
informe de incidencias de pruebas
test incident report
730.
infraestructura de la prueba
infraestructura de pruebas
test infrastructure
731.
entrada de prueba
entrada de prueba
test input
732.
elemento de prueba
elemento de prueba
test item
733.
informe de transmisión de elemento de prueba
informe de transmisión de elemento de prueba
test item transmittal report
See release note.
NO APLICA.
734.
F
líder de la prueba
líder de pruebas
test leader
See test manager.
NO APLICA.
See incident.
NO APLICA.
See incident report.
NO APLICA.
The organizational artifacts needed to perform testing, consisting of test environments, test tools, office NO APLICA. environment and procedures. The data received from an external source by the test object during test execution. The external source can be hardware, NO APLICA. software or human. The individual element to be tested. There usually is one test NO APLICA. object and many test items. See also test object.
PROGRAMA DE ESTUDIOS
735.
736.
F ATM
F ATM
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
test level
bitácora de la prueba
registro de pruebas
test log
A chronological record of relevant details about the execution of tests. [IEEE 829]
NO APLICA.
The process of recording information about tests executed into a test log.
NO APLICA.
registrar en bitácora de la prueba
registrar pruebas
test logging
738.
ATM
gestión de prueba
gestión de pruebas
test management
F ATT
herramienta de gestión de pruebas
herramienta de gestión de pruebas
test management tool
F
jefe de prueba
jefe de pruebas
test manager
ATM
Test Maturity Model integration
NO APLICA
Test Maturity Model integration
741.
742.
EITP
ETM
A group of test activities that are organized and managed together. A test level is linked to the responsibilities in a project. Examples of test levels are component test, NO APLICA. integration test, system test and acceptance test. [After TMap]
nivel de prueba
ETAE
740.
OBSERVACIONES
nivel de prueba
737.
739.
DESCRIPCIÓN EN INGLÉS
misión de la prueba
NO APLICA
test mission
The planning, estimating, monitoring and control of test NO APLICA. activities, typically carried out by a test manager. A tool that provides support to the test management and control part of a test process. It often has several capabilities, such as testware management, scheduling of tests, the NO APLICA. logging of results, progress tracking, incident management and test reporting. The person responsible for project management of testing activities and resources, and evaluation of a test object. The NO APLICA. individual who directs, controls, administers, plans and regulates the evaluation of a test object. A five level staged framework for test process improvement, related to the Capability Maturity Model Integration (CMMI), NO APLICA. that describes the key elements of an effective test process. The purpose of testing for an organization, often documented as part of the test policy.
NO APLICA.
See also test policy. F 743.
ATM
monitorización de la prueba
monitorización de pruebas
test monitoring
objeto de prueba
objeto de prueba
test object
ATA 744.
A test management task that deals with the activities related to periodically checking the status of a test project. Reports NO APLICA. are prepared that compare the actuals to that which was planned. See also test management. The component or system to be tested. See also test item.
NO APLICA.
745.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
F
objetivo de prueba
objetivo de prueba
test objective
DESCRIPCIÓN EN INGLÉS A reason or purpose for designing and executing a test.
OBSERVACIONES NO APLICA.
A source to determine expected results to compare with the actual result of the software under test. An oracle may be the existing system (for a benchmark), other software, a user NO APLICA. manual, or an individual’s specialized knowledge, but should not be the code. [After Adrion]
746.
F‐AT
oráculo de prueba
oráculo de prueba
test oracle
747.
resultado de la prueba
resultado de prueba
test outcome
See result.
NO APLICA.
748.
pasar prueba
pasado de prueba
test pass
See pass.
NO APLICA.
749.
indicador de rendimiento de prueba
indicador de rendimiento de prueba
test performance indicator
750.
fase de prueba
fase de prueba
test phase
plan de prueba
plan de prueba
test plan
planificación de prueba
planificación de prueba
test planning
Análisis de Punto de Prueba (APP)
Análisis de Punto de Prueba (APP)
Test Point Analysis (TPA)
A formula based test estimation method based on function NO APLICA. point analysis. [TMap]
política de prueba
política de pruebas
test policy
A high level document describing the principles, approach NO APLICA. and major objectives of the organization regarding testing.
751.
752.
753.
F ATM
ATM ATA
A high level metric of effectiveness and/or efficiency used to guide and control progressive test development, e.g. Defect NO APLICA. Detection Percentage (DDP). A distinct set of test activities collected into a manageable phase of a project, e.g. the execution activities of a test level. NO APLICA. [After Gerrard] 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, the NO APLICA. test environment, the test design techniques and entry and exit criteria to be used, and the rationale for their choice, and any risks requiring contingency planning. It is a record of the test planning process. [After IEEE 829] The activity of establishing or updating a test plan.
NO APLICA.
F 754.
ATM EITP
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
procedimiento de prueba
procedimiento de prueba
test procedure
especificación de procedimiento de prueba
especificación de procedimiento de prueba
test procedure specification
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
ETM
755.
756.
F ATM F ATM
757.
proceso de prueba
proceso de prueba
test process
758.
EITP
Grupo del Proceso de Prueba
NO APLICA
Test Process Group
759.
ETAE
mejora del proceso de prueba
NO APLICA
760.
EITP
manifiesto por la mejora del proceso de prueba
NO APLICA
761.
EITP
optimizador del proceso de prueba
NO APLICA
See test procedure specification.
NO APLICA.
A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test NO APLICA. script. [After IEEE 829] See also test specification. The fundamental test process comprises test planning and control, test analysis and design, test implementation and NO APLICA. execution, evaluating exit criteria and reporting, and test closure activities. A collection of (test) specialists who facilitate the definition, maintenance, and improvement of the test processes used NO APLICA. by an organization. [After CMMI]
A program of activities designed to improve the performance test process improvement and maturity of the organization’s test processes and the NO APLICA. results of such a program. [After CMMI] A statement that echoes the agile manifesto, and defines values for improving the testing process. The values are: ‐ flexibility over detailed processes test process improvement NO APLICA. ‐ best practices over templates manifesto ‐ deployment orientation over process orientation ‐ peer reviews over quality assurance (departments) ‐ business driven over model driven. [Veenendaal08] test process improver
A person implementing improvements in the test process NO APLICA. based on a test improvement plan. A document summarizing testing activities and results, produced at regular intervals, to report progress of testing activities against a baseline (such as the original test plan) NO APLICA. and to communicate risks and alternatives requiring a decision to management.
762.
informe del avance de la prueba
NO APLICA
test progress report
763.
registro de la prueba
registro de pruebas
test record
See test log.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
764.
registrar prueba
registrar pruebas
test recording
765.
informe de prueba
informe de pruebas
test report
766.
ETAE
gestión de información de la prueba
NO APLICA
test reporting
Collecting and analyzing data from testing activities and subsequently consolidating the data in a report to inform NO APLICA. stakeholders. See also test process.
767.
reproducibilidad de la prueba
reproducibilidad de una prueba
test reproducibility
An attribute of a test indicating whether the same results are NO APLICA. produced each time the test is executed.
768.
requisito de prueba
requisito de prueba
test requirement
769.
resultado de prueba
resultado de prueba
test result
770.
aparejo de prueba
NO APLICA
771.
realización de una prueba
772.
773.
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
See test logging.
NO APLICA.
See test summary report and test progress report.
NO APLICA.
See test condition.
NO APLICA.
See result.
NO APLICA.
test rig
See test environment.
NO APLICA.
ejecución de una prueba
test run
Execution of a test on a specific version of the test object.
NO APLICA.
bitácora de la ejecución de prueba
registro de ejecución de pruebas
test run log
See test log.
NO APLICA.
escenario de prueba
escenario de prueba
test scenario
See test procedure specification.
NO APLICA.
774.
calendario de prueba
NO APLICA
test schedule
A list of activities, tasks or events of the test process, identifying their intended start and finish dates and/or times, NO APLICA. and interdependencies.
775.
ATM
guion de prueba
guion de prueba
test script
Commonly used to refer to a test procedure specification, NO APLICA. especially an automated one.
test session
An uninterrupted period of time spent in executing tests. In exploratory testing, each test session is focused on a charter, but testers can also explore new opportunities or issues NO APLICA. during a session. The tester creates and executes on the fly and records their progress. See also exploratory testing.
F
ETAE
776.
sesión de prueba
NO APLICA
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
777.
conjunto de prueba
conjunto de prueba
test set
778.
situación de prueba
situación de prueba
test situation
779.
especificación de prueba
especificación de prueba
test specification
780.
técnica de especificación de prueba
técnica de especificación de prueba
test specification technique
781.
etapa de prueba
etapa de prueba
test stage
estrategia de prueba
estrategia de prueba
test strategy
A high‐level description of the test levels to be performed and the testing within those levels for an organization or NO APLICA. programme (one or more projects).
F
juego de prueba
juego de prueba
test suite
A set of several test cases for a component or system under test, where the post condition of one test is often used as the NO APLICA. precondition for the next one.
F ATM
informe resumen de prueba
informe resumen de pruebas
test summary report
A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items NO APLICA. against exit criteria. [After IEEE 829]
785.
meta de la prueba
meta de prueba
test target
786.
técnica de prueba
técnica de prueba
test technique
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
See test suite.
NO APLICA.
See test condition.
NO APLICA.
A document that consists of a test design specification, test NO APLICA. case specification and/or test procedure specification. See test design technique.
NO APLICA.
See test level.
NO APLICA.
F F‐AT 782.
ATM ATA ETM
783.
784.
787.
EITP
herramienta de prueba
herramienta de pruebas
test tool
A set of exit criteria.
NO APLICA.
See test design technique.
NO APLICA.
A software product that supports one or more test activities, such as planning and control, specification, building initial NO APLICA. files and data, test execution and test analysis. [TMap] See also CAST.
PROGRAMA DE ESTUDIOS
788.
789.
ATT ETAE
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
tipo de prueba
tipo de prueba
test type
capacidad de ser probado
testabilidad
testability
The capability of the software product to enable modified NO APLICA. software to be tested. [ISO 9126] See also maintainability.
revisión de la capacidad de ser comprobado
revisión de testabilidad
testability review
791.
pequisito susceptible de ser probado
requisitos testeables
testable requirement
desarrollo guiado por pruebas
desarrollo guiado por pruebas
test‐driven development
probador
probador
tester
F F‐AT ETM 793.
794.
795.
796.
F
F
F ETAE
OBSERVACIONES
A group of test activities aimed at testing a component or system focused on a specific test objective, i.e. functional NO APLICA. test, usability test, regression test etc. A test type may take place on one or more test levels or test phases. [After TMap]
790.
792.
DESCRIPCIÓN EN INGLÉS
prueba
probar
testing
productos de prueba
producto de soporte de prueba
testware
pruebas de hilo
pruebas de hilo
thread testing
A detailed check of the test basis to determine whether the test basis is at an adequate quality level to act as an input NO APLICA. document for the test process. [After TMap] A requirements that is stated in terms that permit establishment of test designs (and subsequently test cases) NO APLICA. and execution of tests to determine whether the requirement has been met. [After IEEE 610] A way of developing software where the test cases are developed, and often automated, before the software is NO APLICA. developed to run those test cases.
A skilled professional who is involved in the testing of a component or system.
NO APLICA.
The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to NO APLICA. determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects. Artifacts produced during the test process required to plan, design, and execute tests, such as documentation, scripts, inputs, expected results, set‐up and clear‐up procedures, NO APLICA. files, databases, environment, and any additional software or utilities used in testing. [After Fewster and Graham] An approach to component integration testing where the progressive integration of components follows the NO APLICA. implementation of subsets of the requirements, as opposed to the integration of components by levels of a hierarchy.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
797.
estimación de tres puntos
NO APLICA
three point estimation:
798.
comportamiento temporal
comportamiento temporal
time behavior
TMMi
NO APLICA
TMMi
799.
EITP
800.
pruebas descendentes
pruebas descendentes
top‐down testing
801.
EITP
Gestión de la Calidad Total
NO APLICA
Total Quality Management
802.
EITP
GPG
NO APLICA
TPG
TPI Next
NO APLICA
TPI Next
803.
ATM
ATM EITP
804.
EITP
GCT
NO APLICA
TQM
805.
F
trazabilidad
trazabilidad
traceability
806.
matriz de trazabilidad
NO APLICA
traceability matrix
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
A test estimation method using estimated values for the “best case”, “worst case”, and “most likely case” of the NO APLICA. matter being estimated, to define the degree of certainty associated with the resultant estimate. See performance.
NO APLICA.
See Test Maturity Model integration.
NO APLICA.
An incremental approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. NO APLICA. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested. See also integration testing. An organization‐wide management approach centered on quality, based on the participation of all members of the organization and aiming at long‐term success through customer satisfaction, and benefits to all members of the NO APLICA. organization and to society. Total Quality Management consists of planning, organizing, directing, control, and assurance. [After ISO 8402] See Test Process Group.
NO APLICA.
A continuous business‐driven framework for test process improvement that describes the key elements of an effective NO APLICA. and efficient test process. See Total Quality Management.
NO APLICA.
The ability to identify related items in documentation and software, such as requirements with associated tests. See NO APLICA. also horizontal traceability, vertical traceability. A two‐dimensional table, which correlates two entities (e.g., requirements and test cases). The table allows tracing back NO APLICA. and forth the links of one entity to the other, thus enabling
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
807.
EITP
análisis transaccional
NO APLICA
808.
EITP
calidad basada en la transcendencia
NO APLICA
TÉRMINO EN INGLÉS
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
the determination of coverage achieved and the assessment of impact of proposed changes. The analysis of transactions between people and within people’s minds; a transaction is defined as a stimulus plus a transactional analysis response. Transactions take place between people and NO APLICA. between the ego states (personality segments) within one person’s mind. A view of quality, wherein quality cannot be precisely defined, but we know it when we see it, or are aware of its absence when it is missing. Quality depends on the perception and affective feelings of an individual or group of transcendent‐based quality individuals towards a product. [After NO APLICA. Garvin] See also manufacturing‐based quality, product‐based quality, user‐based quality, valuebased quality.
U
809.
ATA
capacidad de ser entendido
comprensibilidad
understandability
810.
unidad
unidad
unit
F F‐AT
marco de trabajo para prueba unitaria
marco de trabajo de pruebas unitarias
unit test framework
812.
pruebas unitarias
pruebas unitarias
unit testing
813.
código inaccesible
código inaccesible
unreachable code
814.
usabilidad
usabilidad
usability
811.
The capability of the software product to enable the user to understand whether the software is suitable, and how it can NO APLICA. be used for particular tasks and conditions of use. [ISO 9126] See also usability. See component.
NO APLICA.
A tool that provides an environment for unit or component testing in which a component can be tested in isolation or NO APLICA. with suitable stubs and drivers. It also provides other support for the developer, such as debugging capabilities. [Graham] See component testing.
NO APLICA.
Code that cannot be reached and therefore is impossible to execute.
NO APLICA.
The capability of the software to be understood, learned, used and attractive to the user when used under specified NO APLICA. conditions. [ISO 9126]
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
pruebas de usabilidad
pruebas de usabilidad
usability testing
Testing to determine the extent to which the software product is understood, easy to learn, easy to operate and NO APLICA. attractive to the users under specified conditions. [After ISO 9126]
F 815.
F‐AT ATA
816.
817.
F ATA
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
caso de uso
caso de uso
use case
A sequence of transactions in a dialogue between an actor and a component or system with a tangible result, where an NO APLICA. actor can be a user or anything that can exchange information with the system.
pruebas de caso de uso
pruebas de caso de uso
use case testing
A black box test design technique in which test cases are NO APLICA. designed to execute scenarios of use cases.
818.
F
pruebas de aceptación de usuario
pruebas de aceptación de usuario
user acceptance testing
819.
prueba de escenarios de usuario
pruebas de escenarios de usuario
user scenario testing
820.
F‐AT
historia de usuario
NO APLICA
user story
821.
ATA
prueba de historia de usuario
NO APLICA
user story testing
822.
prueba de usuario
pruebas de usuario
user test
823.
EITP
calidad basada en el usuario
NO APLICA
user‐based quality
See acceptance testing.
NO APLICA.
See use case testing
NO APLICA.
A high‐level user or business requirement commonly used in agile software development, typically consisting of one or more sentences in the everyday or business language NO APLICA. capturing what functionality a user needs, any non‐functional criteria, and also includes acceptance criteria. See also agile software development, requirement. A black box test design technique in which test cases are designed based on user stories to verify their correct NO APLICA. implementation. See also user story. A test whereby real‐life users are involved to evaluate the NO APLICA. usability of a component or system. A view of quality, wherein quality is the capacity to satisfy needs, wants and desires of the user(s). A product or service that does not fulfill user needs is unlikely to find any users. This is a context dependent, contingent approach to quality NO APLICA. since different business characteristics require different qualities of a product. [after Garvin] See also manufacturing‐ based quality, product‐based quality, transcendent‐based quality, value‐based quality.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
V
824.
F
validación
validación
validation
825.
EITP
calidad basada en el valor
NO APLICA
value‐based quality
826.
variable
variable
variable
verificación
verificación
verification
827.
ETAE
828.
F
control de versión
control de versión
version control
829.
trazabilidad vertical
trazabilidad vertical
vertical traceability
830.
F
modelo‐V
modelo‐V
V‐model
831.
pruebas de volumen
pruebas de volumen
volume testing
W
832.
833.
F
F ATM ATA
revisión guiada
revisión guiada
walkthrough
IAMSW
NO APLICA
WAMMI
DESCRIPCIÓN EN INGLÉS
OBSERVACIONES
Confirmation by examination and through provision of objective evidence that the requirements for a specific NO APLICA. intended use or application have been fulfilled. [ISO 9000] A view of quality, wherein quality is defined by price. A quality product or service is one that provides desired performance at an acceptable cost. Quality is determined by means of a decision process with stakeholders on trade‐offs NO APLICA. between time, effort and cost aspects. [After Garvin] See also manufacturing‐based quality, product‐based quality, transcendent‐based quality, user‐based quality. An element of storage in a computer that is accessible by a NO APLICA. software program by referring to it by a name. Confirmation by examination and through provision of objective evidence that ETAE specified requirements have NO APLICA. been fulfilled. [ISO 9000] See configuration control.
NO APLICA.
The tracing of requirements through the layers of NO APLICA. development documentation to components. A framework to describe the software development lifecycle activities from requirements specification to maintenance. The V‐model illustrates how testing activities can be NO APLICA. integrated into each phase of the software development lifecycle. Testing where the system is subjected to large volumes of NO APLICA. data. See also resource utilization testing.
A step‐by‐step presentation by the author of a document in order to gather information and to establish a common NO APLICA. understanding of its content. [Freedman and Weinberg, IEEE 1028] See also peer review. See Website Analysis and MeasureMent Inventory.
NO APLICA.
PROGRAMA DE ESTUDIOS
TÉRMINO TRADUCIDO
TRADUCCIÓN PREVIA
TÉRMINO EN INGLÉS
834.
EDT
NO APLICA
WBS
835.
ATA
Inventario de Análisis y Medición de Sitios Web (IAMSW)
NO APLICA
Website Analysis and MeasureMent Inventory (WAMMI)
836.
técnica de caja blanca
técnicas de caja blanca
white‐box technique:
F ATT
técnica de diseño de prueba de caja blanca
NO APLICA
white‐box test design technique
838.
F
pruebas de caja blanca
pruebas de caja blanca
white‐box testing
839.
ATM
Delphi de Banda Ancha
Delphi de Banda Ancha
Wide Band Delphi
An expert based test estimation technique that aims at making an accurate estimation using the collective wisdom of NO APLICA. the team members.
840.
ATT
puntero sin referencia
NO APLICA
wild pointer
A pointer that references a location that is out of scope for NO APLICA. that pointer or that does not exist. See also pointer.
841.
Estructura de Descomposición del Trabajo
NO APLICA
Work Breakdown Structure
An arrangement of work elements and their relationship to NO APLICA. each other and to the end product. [CMMI]
X
Y
Z
837.
DESCRIPCIÓN EN INGLÉS
See Work Breakdown Structure.
Estructura de descomposición del trabajo (EDT).
A questionnaire‐based usability test technique for measuring NO APLICA. web site software quality from the end user's point of view. See white‐box test design technique.
NO APLICA.
Procedure to derive and/or select test cases based on an NO APLICA. analysis of the internal structure of a component or system. Testing based on an analysis of the internal structure of the component or system.
Tabla 6 – Traducción ordenada por los términos en inglés español (“TÉRMINO EN INGLÉS”)
OBSERVACIONES
NO APLICA.