ISTQB Fundamentals - Glossary Part III

Question

independence of testing

Answer 1

Separation of responsibilities, which encourages the accomplishment of objective testing

Answer 2

A measure that can be used to estimate or predict another measure

Answer 3

A review not based on a formal (documented) procedure.

Answer 4

A review not based on a formal (documented) procedure

Answer 5

A measure that can be used to estimate or predict another measure

Answer 6

Separation of responsibilities, which encourages the accomplishment of objective testing

Answer 7

A review not based on a formal (documented) procedure.

Answer 8

Separation of responsibilities, which encourages the accomplishment of objective testing.

Answer 9

An instance of an input

Answer 10

A review not based on a formal (documented) procedure.

Answer 11

A variable (whether stored within a component or outside) that is read by a component

Answer 12

An instance of an input

Answer 13

The process of combining components or systems into larger assemblies

Answer 14

A type of peer review that relies on visual examination of documents to detect defects, e.g., violations of development standards and non-conformance to higher level documentation. The most formal review technique and therefore always based on a documented procedure.

Answer 15

An integration test type that is concerned with testing the interfaces between components or systems

Answer 16

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.

Answer 17

The capability of the software product to interact with one or more specified components or systems.

Answer 18

An integration test type that is concerned with testing the interfaces between components or systems

Answer 19

The process of combining components or systems into larger assemblies.

Answer 20

Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems

Answer 21

An integration test type that is concerned with testing the interfaces between components or systems.

Answer 22

An integration test type that is concerned with testing the interfaces between components or systems.

Answer 23

Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems

Answer 24

The process of combining components or systems into larger assemblies.

Answer 25

An integration test type that is concerned with testing the interfaces between components or systems

Answer 26

The capability of the software product to interact with one or more specified components or systems

Answer 27

Testing using input values that should be rejected by the component or system

Answer 28

The capability of the software product to interact with one or more specified components or systems

Answer 29

Testing to determine the interoperability of a software product.

Answer 30

The capability of the software product to interact with one or more specified components or systems.

Answer 31

Testing using input values that should be rejected by the component or system

Answer 32

A test plan that typically addresses one test level.

Answer 33

A type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e.g., numbers of parallel users and/or numbers of transactions, to determine what load can be handled by the component or system.

Answer 34

A development lifecycle where a project is broken into a usually large number of iterations. An iteration is a complete development loop resulting in a release (internal or external) of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product.

Answer 35

A test plan that typically addresses one test level.

Answer 36

A type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e.g., numbers of parallel users and/or numbers of transactions, to determine what load can be handled by the component or system.

Answer 37

A scripting technique that uses data files to contain not only test data and expected results, but also keywords related to the application being tested. The keywords are interpreted by special supporting scripts that are called by the control script for the test.

Answer 38

A document describing the scope, approach, resources and schedule of intended test activities.

Answer 39

A test plan that typically addresses one test level

Answer 40

A test plan that typically addresses multiple test levels.

Answer 41

A type of performance testing conducted to evaluate the behavior of a component or system with increasing load, e.g., numbers of parallel users and/or numbers of transactions, to determine what load can be handled by the component or system.

Answer 42

Testing to determine the performance of a software product

Answer 43

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.

Answer 44

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

Answer 45

Testing the changes to an operational system or the impact of a changed environment to an operational system

Answer 46

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.

Answer 47

Testing to determine the maintainability of a software product

Answer 48

Testing the changes to an operational system or the impact of a changed environment to an operational system

Answer 49

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

Answer 50

Testing the changes to an operational system or the impact of a changed environment to an operational system.

Answer 51

Testing to determine the maintainability of a software product

Answer 52

Testing the changes to an operational system or the impact of a changed environment to an operational system.

Answer 53

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.

Answer 54

Testing to determine the maintainability of a software product.

Answer 55

A test plan that typically addresses multiple test levels.

Answer 56

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

Answer 57

The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. (2) The capability of the software product to avoid failure as a result of defects in the software

Answer 58

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.

Answer 59

The number or category assigned to an attribute of an entity by making a measurement

Answer 60

The number or category assigned to an attribute of an entity by making a measurement.

Answer 61

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.

Answer 62

The process of assigning a number or category to an entity to describe an attribute of that entity.

Answer 63

The process of assigning a number or category to an entity to describe an attribute of that entity

Answer 64

The number or category assigned to an attribute of an entity by making a measurement

Answer 65

The number or category assigned to an attribute of an entity by making a measurement

Answer 66

The process of assigning a number or category to an entity to describe an attribute of that entity.

Answer 67

A point in time in a project at which defined (intermediate) deliverables and results should be ready.

Answer 68

A memory access failure due to a defect in a program's dynamic store allocation logic that causes it to fail to release memory after it has finished using it, eventually causing the program and/or other concurrent processes to fail due to lack of memory.

Answer 69

The number or category assigned to an attribute of an entity by making a measurement

Answer 70

A measurement scale and the method used for measurement.

Answer 71

The number or category assigned to an attribute of an entity by making a measurement

Answer 72

The process of assigning a number or category to an entity to describe an attribute of that entity.

Answer 73

A point in time in a project at which defined (intermediate) deliverables and results should be ready

Answer 74

A tool that supports the creation, amendment and verification of models of the software or system

Answer 75

A measurement scale and the method used for measurement.

Answer 76

A point in time in a project at which defined (intermediate) deliverables and results should be ready.

Answer 77

A tool that supports the creation, amendment and verification of models of the software or system.

Answer 78

A software tool or hardware device that runs concurrently with the component or system under test and supervises, records and/or analyzes the behavior of the component or system.

Answer 79

The leader and main person responsible for an inspection or review process.(2) A neutral person who conducts a usability test session.

Answer 80

The percentage of combinations of all single condition outcomes within one statement that have been exercised by a test suite. 100% multiple condition coverage implies 100% modified condition / decision coverage.

Answer 81

A software tool or hardware device that runs concurrently with the component or system under test and supervises, records and/or analyzes the behavior of the component or system.

Answer 82

A requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability

Answer 83

The percentage of combinations of all single condition outcomes within one statement that have been exercised by a test suite. 100% multiple condition coverage implies 100% modified condition / decision coverage.

Answer 84

Testing the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.

Answer 85

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.

Answer 86

Testing the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.

Answer 87

A requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability.

Answer 88

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.

Answer 89

Testing the attributes of a component or system that do not relate to functionality, e.g., reliability, efficiency, usability, maintainability and portability.

Answer 90

A requirement that does not relate to functionality, but to attributes such as reliability, efficiency, usability, maintainability and portability.

Answer 91

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.

Answer 92

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.

Answer 93

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.

Answer 94

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.

Answer 95

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

Answer 96

Testing conducted to evaluate a component or system in its operational environment.

Answer 97

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.

Answer 98

A variable (whether stored within a component or outside) that is written by a component.

Answer 99

Testing conducted to evaluate a component or system in its operational environment.

Answer 100

A variable (whether stored within a component or outside) that is written by a component.

Answer 101

A variable (whether stored within a component or outside) that is read by a component.

Answer 102

A test is deemed to pass if its actual result matches its expected result.

Answer 103

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.

Answer 104

A test is deemed to fail if its actual result does not match its expected result.

Answer 105

A test is deemed to pass if its actual result matches its expected result.

Answer 106

The task of analyzing, e.g., identifying performance bottlenecks based on generated metrics, and tuning the performance of a software component or system using tools

Answer 107

A sequence of events, e.g., executable statements, of a component or system from an entry point to an exit point.

	Criado por yacki Dubon mais de 3 anos atrás

Próximo

ISTQB Fundamentals - Glossary Part III

Descrição

Resumo de Recurso

Questão 1

Questão 2

Questão 3

Questão 4

Questão 5

Questão 6

Questão 7

Questão 8

Questão 9

Questão 10

Questão 11

Questão 12

Questão 13

Questão 14

Questão 15

Questão 16

Questão 17

Questão 18

Questão 19

Questão 20

Questão 21

Questão 22

Questão 23

Questão 24

Questão 25

Questão 26

Questão 27

Questão 28

Questão 29

Questão 30

Questão 31

Questão 32

Questão 33

Questão 34

Questão 35

Questão 36

Questão 37

Questão 38

Questão 39

Questão 40

Questão 41

Semelhante