Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

must get > itt > Flashcards

itt Flashcards

1
Q

acceptance criteria

A

criteria that a component or system must satisfy in order to be accepted by a user, customer or authorized entity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

acceptance testing

A

formal testing with respect to user needs, requirements and business processes conducted to determine whether or not a system satisfies the acceptance criteria in order to accept the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

accessibility

A

the degree to which a component or system can be used by people with the widest range of characteristics and capabilities to achieve a specified goal in a specified context of use

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

accessibility testing

A

testing the ease by which users with disabilities can use a component or system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

actual result

A

behavior produced/observed by object under test

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

ad hoc reviewing

A

informal review technique by independent reviewers without a structured process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

alpha testing

A

simulated or actual operational testing in developer’s test environment by roles outside the development organization

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

anomaly

A

any condition that deviates from expected results by requirements specs, design docs, user docs, standards from one’s perception or experience.
Anomalies can be found at reviews, testing, analysis, compilation, usage or products or docs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

audit

A

independent examination of work product, process(es) performed by a third party to assess compliance with specs, standards, contractual agreements or other criteria

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

availability

A

the degree to which a component or system is operational and accessible when in use

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

behavior

A

response of component/system to set of input values and preconditions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

beta testing

A

simulated or actual operational testing conducted at an external site by roles outside the development organization (see: field testing)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

black-box test technique

A

to derive/select test cases based on specs, functional or non-functional, of a component/system without reference to internal structure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

boundary value

A

minimum or maximum value of an ordere

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

boundary value

A

minimum or maximum value of an ordered equivalence partition

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

boundary value analysis

A

black-box test case based on boundary values

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

burndown chart

A

chat that depicts outstanding effort versus time in an iteration that shows status and trend of completing tasks.
x-axis is usually days in sprint
y-axis is remaining effort (e.g., story points)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

checklist-based reviewing

A

review technique guided by list of questions or required attributes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

checklist-based testing

A

experience based test technique where 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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

code coverage

A

an analysis method that determines which parts of the software have been executed (covered) by the test suite.
Types: statement, decision, condition coverage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

commercial off-the-shelf (COTS)

A

software product developed for the general market, i.e., for a large number of customers in identical format
e.g. Duolingo

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

compatibility

A

the degree a component/system can exchange information with other components/systems

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

complexity

A

the degree a component/system has a design/internal structure that is difficult to understand, maintain and verify

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

compliance

A

capability of software product to adhere to standards, conventions, regulations in laws and such

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

component

A

minimal part of a system that can be tested in isolation
e.g. Unit, Module

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

component integration testing

A

testing of interfaces and interactions between integrated components/systems
Also: link testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

component specification

A

description of component’s function in terms of input/output under conditions and required non-functional behavior such as resource utilization

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

component testing

A

testing of individual hardware or software components
e.g. module/unit testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

condition

A

logical expression evaluated as True or False
Also: branch condition

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

configuration

A

number, nature and interconnections of parts in composition of component/system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

configuration item

A

single entity in the configuration management process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

configuration management

A

administrative direction and surveillance to identify and document the functional and physical characteristics of a configuration item, control changes, record, report change processing and implementation status, verify compliance with requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

configuration management tool

A

provides support for identification and control of configuration items, their status over changes and versions and release of baselines

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

confirmation testing

A

dynamic testing after fixing a defect to confirm failures caused by the defect no longer occurs
Also: re-testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

contractual acceptance testing

A

acceptance testing to verify if a system satisfies its contractual requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

control flow

A

sequence of operations performed by execution of a test item

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
37
Q

cost of quality

A

total costs incurred on quality activities and issues often split into prevention, appraisal, internal failure and external failure costs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
38
Q

coverage

A

percentage of coverage items that have been covered/executed by a test suite
Also: test coverage

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
39
Q

coverage item

A

attribute or combination of attributes derived by test condition(s) that enables measurement of thoroughness of the test execution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
40
Q

coverage tool

A

tool that provides objective measures of elements (statements, branches, etc) that have been exercised/covered by a test suite
Also: coverage measurement tool

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
41
Q

data flow

A

abstract representation of sequences and possible changes of the state of data objects (creation, usage, destruction)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
42
Q

data-driven testing

A

testing with a table/spreadsheets of inputs and expected results that is provided to a single control script that executes all tests according to inputs and records output/actual results to table/spreadsheet.
Often used in capture/playback tools.
Also: keyword-driven testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
43
Q

debugging

A

process of finding, analyzing and removing the causes of failures in software

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
44
Q

decision

A

type of statement where a choice between two or more outcomes control set of resulting actions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
45
Q

decision coverage

A

coverage of decision outcomes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
46
Q

decision outcome

A

result of decision that determines the next statement to be execiuted

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
47
Q

decision outcome

A

result of decision that determines the next statement to be executed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
48
Q

decision table

A

a table of conditions and resulting actions
Also: cause-effect decision table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
49
Q

decision table testing

A

a black-box test technique where test cases are designed to execute combinations of inputs/causes shown in a decision table

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
50
Q

decision testing

A

a white-box test technique where test cases are designed to execute decision outcomes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
51
Q

defect

A

an imperfection or deficiency in a work product where it does not meet requirements or specifications
Also: bug, fault

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
52
Q

defect density

A

number of defects per unit size of a work product
Also: fault density

53
Q

defect management

A

process of recognizing, recording, classifying, investigating, taking action to resolve/dispose of defects

54
Q

defect management tool

A

tool that facilitates the recording and status tracking of defects

55
Q

defect report

A

documentation of occurrence, nature and status of a defect
Also: incident report

56
Q

driver

A

software component or test tool that replaces a component that takes care of the control/calling of a component/system
Also: test driver

57
Q

dynamic analysis

A

process of evaluating behavior (memory performance, CPU usage) of a system/component during execution

58
Q

dynamic analysis tool

A

tool that gives runtime information on the state of the software code. Commonly used to identify unassigned pointers, check pointer arithmetic and monitor allocation, use/de-allocate memory, flag memory leaks

59
Q

dynamic testing

A

testing during the execution of the software/component/system

60
Q

effectiveness

A

extent to which correct and complete goals are achieved
Also: efficiency

61
Q

efficiency

A

resources expended in relation to the extent with which users achieve specified goals
Also: effectiveness

62
Q

entry criteria

A

set of conditions for officially starting a defined task

63
Q

equivalence partition

A

a portion of the value domain of a data element related to the test object for which all values are expected to be treated the same based on the specification
Also: equivalence class

64
Q

equivalence partitioning

A

black-box test technique where test cases are designed to exercise equivalence partitions by using one representative member of each partition

65
Q

error

A

a human action that produces an incorrect result
Also: mistake

66
Q

error guessing

A

tests are derived on the basis of tester’s knowledge of past failures or failure modes

67
Q

executable statement

A

statement that is compiled and translated into object code to be executed to perform an action on data

68
Q

exercised

A

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 stat

69
Q

exercised

A

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

70
Q

exhuastive testing

A

test approach where the test suite comprises all combinations of input values and preconditions
Also: complete testing

71
Q

exit criteria

A

set of conditions for officially completing a defined task
Also: definition of done, completion criteria

72
Q

expected result

A

predicted observable behaior of component/system executing under specific conditions
Also: expected outcome

73
Q

experience-based testing

A

testing based on tester’s experience, knowledge and intuition

74
Q

exploratory testing

A

an approach to testing where testers dynamically design and execute tests based on their knowledge, exploration of the test item and the results of previous tests

75
Q

extreme programming (XP)

A

software engineering methodology used in Agile development where there is pair programming, extensive code review, unit testing all code, simplicity and clarity in code

76
Q

facilitator

A

leader and main person responsible for an inspection or review process
See: Moderator

77
Q

fail

A

actual result does not match its expected result

78
Q

failure

A

an event in which a component or system does not perform a required function within specified limits

79
Q

failure rate

A

ratio of number of failures of a given category to a given unit of measure

80
Q

feature

A

attribute of component or system specified or implied by requirements documentation
e.g. reliability, usability, design constraints

81
Q

finding

A

a result of an evalution that identifies some important issue, problem or opportunity

82
Q

formal review

A

form of review that follows a defined process with a formally documented output

83
Q

functional integration

A

combines the components or systems for the purpose of getting a basic functionality working early
See: integration testing

84
Q

functional requirement

A

a function that a component or system must be able to perform

85
Q

functional suitability

A

degree to which a component or system provides functions that meet stated and implied needs when used under specified conditions

86
Q

functional testing

A

testing conducted to evaluate the compliance of a component or system with functional requirements

87
Q

GUI

A

Graphical User Interface

88
Q

high-level test case

A

test case without concrete values for input data and expected results
Also: abstract test case, logical test case

89
Q

IDEAL

A

organizational improvement model that serves as a roadmap for initiating, planning and implementing improvement actions.
Initiating, Diagnosing, Establishing, Acting, Learning

90
Q

impact analysis

A

identification of all work products affected by a change including an estimate of the resources needed to accomplish the change

91
Q

incident report

A

documentation of the occurrence, nature and status of an incident
Also: deviation report, test incident report
See: defect report

92
Q

incremental development model

A

development life cycle model in which the project scope is determined early in the project life cycle but time and cost estimates are routinely modified as the project team understanding of the product increases. The product is developed through a series of repeated cycles, each delivering an increment which successively add s to the functionality of the product
See: iterative development model

93
Q

independence of testing

A

separation of responsibilities which encourages the accomplishment of objective testing

94
Q

informal group review

A

informal review performed by three or more persons

95
Q

informal review

A

type of review without a formal documented procedure

96
Q

input

A

data received by a component or system from an external source

97
Q

inspection

A

a type of formal review to identify issues in a work product which provides measurements to improve the review process and the software development process

98
Q

installation guide

A

supplied instructions on any suitable media which guies installer through the installation process.

99
Q

integration

A

process of combining components or systems into larger assemblies

100
Q

integration testing

A

testing performed to expose defects in the interfaces and in the interactions between integrated components or systems
See: component/system integration testing

101
Q

interoperability

A

degree to which two or more components or systems can exchange information and use the information that has been exchanged

102
Q

interoperability testing

A

testing to determine the interoperability of a software product
Also: compatibility testing

103
Q

iterative development model

A

development life cycle where a project is broken into a 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

104
Q

keyword-driven testing

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.
keywords are interpreted by special supporting scripts that are called by the control script for the test
Also: action word-driven testing

105
Q

life cycle model

A

description of the processes, workflows and activities used in the development, delivery, maintenance and retirement of a system

106
Q

load testing

A

type of performance test conducted to evaluate the behaviour of a component/system under varying loads (low, typical, peak usage)

107
Q

low-level test case

A

test case with concrete values for input data and expected results
Also: concrete test case

108
Q

maintainability

A

degree to which a component/system can be modified by the intended maintainers

109
Q

maintenance

A

process of modifying a component/system after delivery to correct defects, improve quality attributes or adapt to a changed environment

110
Q

maintenance testing

A

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

111
Q

master test plan

A

test plan used to coordinate multiple test levels or test types

112
Q

maturity

A

capability of an organization with respect to the effectiveness and efficiency of its processes and work practices.
degress to which a component or system meets needs for reliability under normal operation

113
Q

measure

A

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

114
Q

measurement

A

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

115
Q

memory leak

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

116
Q

metric

A

measurement scale and the method used for measurement

117
Q

milestone

A

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

118
Q

model-based testing (MBT)

A

testing based on or involving models

119
Q

moderator

A

neutral person who conducts a usability test session.
see: facilitator

120
Q

monitoring tool

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
Also: dynamic analysis tool

121
Q

non-functional requirement

A

requirement that describes how well the component or system will do what it is intended to do

122
Q

non-functional testing

A

testing conducted to evaluate the compliance of a component or system with non-functional requirements

123
Q

operational acceptance testing

A

focus on operational aspects like recoverability, resource-behavior, installability and technical compliance

124
Q

operational environment

A

hardware and software products installed at users’ or customers’ sites where the component/system under test will be used.
the software may include OS, DB management systems, other applications

125
Q

output

A

data transmitted by a component/system to an external destination

126
Q

pass

A

actual result matches its expected result

127
Q

path

A

sequence of events, i.e. executable statements, of a component/system from an entry point to an exit point
Also: control flow path

128
Q

peer review

A

for of review of work products performed by others qualified to do the same work

129
Q

performance efficiency

A

degree to which a component/system uses time, resources and capacity when accomplishing its designated functions
Also: time behavior, performance

must get (14 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions