itt Flashcards
(129 cards)
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
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
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
4
Q
accessibility testing
A
testing the ease by which users with disabilities can use a component or system
5
Q
actual result
A
behavior produced/observed by object under test
6
Q
ad hoc reviewing
A
informal review technique by independent reviewers without a structured process
7
Q
alpha testing
A
simulated or actual operational testing in developer’s test environment by roles outside the development organization
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.
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
10
Q
availability
A
the degree to which a component or system is operational and accessible when in use
11
Q
behavior
A
response of component/system to set of input values and preconditions
12
Q
beta testing
A
simulated or actual operational testing conducted at an external site by roles outside the development organization (see: field testing)
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
14
Q
boundary value
A
minimum or maximum value of an ordere
15
Q
boundary value
A
minimum or maximum value of an ordered equivalence partition
16
Q
boundary value analysis
A
black-box test case based on boundary values
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)
18
Q
checklist-based reviewing
A
review technique guided by list of questions or required attributes
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
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
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
22
Q
compatibility
A
the degree a component/system can exchange information with other components/systems
23
Q
complexity
A
the degree a component/system has a design/internal structure that is difficult to understand, maintain and verify
24
Q
compliance
A
capability of software product to adhere to standards, conventions, regulations in laws and such
25
component
minimal part of a system that can be tested in isolation
e.g. Unit, Module
26
component integration testing
testing of interfaces and interactions between integrated components/systems
Also: link testing
27
component specification
description of component's function in terms of input/output under conditions and required non-functional behavior such as resource utilization
28
component testing
testing of individual hardware or software components
e.g. module/unit testing
29
condition
logical expression evaluated as True or False
Also: branch condition
30
configuration
number, nature and interconnections of parts in composition of component/system
31
configuration item
single entity in the configuration management process
32
configuration management
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
33
configuration management tool
provides support for identification and control of configuration items, their status over changes and versions and release of baselines
34
confirmation testing
dynamic testing after fixing a defect to confirm failures caused by the defect no longer occurs
Also: re-testing
35
contractual acceptance testing
acceptance testing to verify if a system satisfies its contractual requirements
36
control flow
sequence of operations performed by execution of a test item
37
cost of quality
total costs incurred on quality activities and issues often split into prevention, appraisal, internal failure and external failure costs
38
coverage
percentage of coverage items that have been covered/executed by a test suite
Also: test coverage
39
coverage item
attribute or combination of attributes derived by test condition(s) that enables measurement of thoroughness of the test execution
40
coverage tool
tool that provides objective measures of elements (statements, branches, etc) that have been exercised/covered by a test suite
Also: coverage measurement tool
41
data flow
abstract representation of sequences and possible changes of the state of data objects (creation, usage, destruction)
42
data-driven testing
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
43
debugging
process of finding, analyzing and removing the causes of failures in software
44
decision
type of statement where a choice between two or more outcomes control set of resulting actions
45
decision coverage
coverage of decision outcomes
46
decision outcome
result of decision that determines the next statement to be execiuted
47
decision outcome
result of decision that determines the next statement to be executed
48
decision table
a table of conditions and resulting actions
Also: cause-effect decision table
49
decision table testing
a black-box test technique where test cases are designed to execute combinations of inputs/causes shown in a decision table
50
decision testing
a white-box test technique where test cases are designed to execute decision outcomes
51
defect
an imperfection or deficiency in a work product where it does not meet requirements or specifications
Also: bug, fault
52
defect density
number of defects per unit size of a work product
Also: fault density
53
defect management
process of recognizing, recording, classifying, investigating, taking action to resolve/dispose of defects
54
defect management tool
tool that facilitates the recording and status tracking of defects
55
defect report
documentation of occurrence, nature and status of a defect
Also: incident report
56
driver
software component or test tool that replaces a component that takes care of the control/calling of a component/system
Also: test driver
57
dynamic analysis
process of evaluating behavior (memory performance, CPU usage) of a system/component during execution
58
dynamic analysis tool
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
dynamic testing
testing during the execution of the software/component/system
60
effectiveness
extent to which correct and complete goals are achieved
Also: efficiency
61
efficiency
resources expended in relation to the extent with which users achieve specified goals
Also: effectiveness
62
entry criteria
set of conditions for officially starting a defined task
63
equivalence partition
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
equivalence partitioning
black-box test technique where test cases are designed to exercise equivalence partitions by using one representative member of each partition
65
error
a human action that produces an incorrect result
Also: mistake
66
error guessing
tests are derived on the basis of tester's knowledge of past failures or failure modes
67
executable statement
statement that is compiled and translated into object code to be executed to perform an action on data
68
exercised
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
exercised
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
exhuastive testing
test approach where the test suite comprises all combinations of input values and preconditions
Also: complete testing
71
exit criteria
set of conditions for officially completing a defined task
Also: definition of done, completion criteria
72
expected result
predicted observable behaior of component/system executing under specific conditions
Also: expected outcome
73
experience-based testing
testing based on tester's experience, knowledge and intuition
74
exploratory testing
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
extreme programming (XP)
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
facilitator
leader and main person responsible for an inspection or review process
See: Moderator
77
fail
actual result does not match its expected result
78
failure
an event in which a component or system does not perform a required function within specified limits
79
failure rate
ratio of number of failures of a given category to a given unit of measure
80
feature
attribute of component or system specified or implied by requirements documentation
e.g. reliability, usability, design constraints
81
finding
a result of an evalution that identifies some important issue, problem or opportunity
82
formal review
form of review that follows a defined process with a formally documented output
83
functional integration
combines the components or systems for the purpose of getting a basic functionality working early
See: integration testing
84
functional requirement
a function that a component or system must be able to perform
85
functional suitability
degree to which a component or system provides functions that meet stated and implied needs when used under specified conditions
86
functional testing
testing conducted to evaluate the compliance of a component or system with functional requirements
87
GUI
Graphical User Interface
88
high-level test case
test case without concrete values for input data and expected results
Also: abstract test case, logical test case
89
IDEAL
organizational improvement model that serves as a roadmap for initiating, planning and implementing improvement actions.
Initiating, Diagnosing, Establishing, Acting, Learning
90
impact analysis
identification of all work products affected by a change including an estimate of the resources needed to accomplish the change
91
incident report
documentation of the occurrence, nature and status of an incident
Also: deviation report, test incident report
See: defect report
92
incremental development model
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
independence of testing
separation of responsibilities which encourages the accomplishment of objective testing
94
informal group review
informal review performed by three or more persons
95
informal review
type of review without a formal documented procedure
96
input
data received by a component or system from an external source
97
inspection
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
installation guide
supplied instructions on any suitable media which guies installer through the installation process.
99
integration
process of combining components or systems into larger assemblies
100
integration testing
testing performed to expose defects in the interfaces and in the interactions between integrated components or systems
See: component/system integration testing
101
interoperability
degree to which two or more components or systems can exchange information and use the information that has been exchanged
102
interoperability testing
testing to determine the interoperability of a software product
Also: compatibility testing
103
iterative development model
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
keyword-driven testing
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
life cycle model
description of the processes, workflows and activities used in the development, delivery, maintenance and retirement of a system
106
load testing
type of performance test conducted to evaluate the behaviour of a component/system under varying loads (low, typical, peak usage)
107
low-level test case
test case with concrete values for input data and expected results
Also: concrete test case
108
maintainability
degree to which a component/system can be modified by the intended maintainers
109
maintenance
process of modifying a component/system after delivery to correct defects, improve quality attributes or adapt to a changed environment
110
maintenance testing
testing the changes to an operational system or the impact of a changed environment to an operational system
111
master test plan
test plan used to coordinate multiple test levels or test types
112
maturity
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
measure
number or category assigned to an attribute of an entity by making a measurement
114
measurement
process of assigning a number category to an entity to describe an attribute of that entity
115
memory leak
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
metric
measurement scale and the method used for measurement
117
milestone
point in time in a project at which defined (intermediate) deliverables and results should be ready
118
model-based testing (MBT)
testing based on or involving models
119
moderator
neutral person who conducts a usability test session.
see: facilitator
120
monitoring tool
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
non-functional requirement
requirement that describes how well the component or system will do what it is intended to do
122
non-functional testing
testing conducted to evaluate the compliance of a component or system with non-functional requirements
123
operational acceptance testing
focus on operational aspects like recoverability, resource-behavior, installability and technical compliance
124
operational environment
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
output
data transmitted by a component/system to an external destination
126
pass
actual result matches its expected result
127
path
sequence of events, i.e. executable statements, of a component/system from an entry point to an exit point
Also: control flow path
128
peer review
for of review of work products performed by others qualified to do the same work
129
performance efficiency
degree to which a component/system uses time, resources and capacity when accomplishing its designated functions
Also: time behavior, performance
