Terms Flashcards

1
Q

acceptance criteria

A

The criteria needed to satisfy acceptance

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

acceptance testing

A

Testing of requirements to determine whether or not a system satisfies the acceptance criteria

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

accessibility

A

Component or system can used by people with the widest range of characteristics and capabilities (disabilities).

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

accessibility testing

A

Testing to determine 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

ad hoc reviewing

A

Review technique carried out by independent reviewers informally, without a structured process.

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

Agile software development

A

A software engineering methodology where core practices are programming in pairs, doing extensive code review, unit testing of all code, and simplicity and clarity in code.

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

alpha testing

A

Testing conducted in the 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

Anoaly

A

Any condition that deviates from expectation.

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

audit

A

Independent examination of a work product, process, or set of processes that is performed by a third party.

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 required for use.

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

behavior

A

The response to a 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

Testing conducted at an external site, by roles outside the development organization.

Synonym: field testing

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

black-box test technique

A

Testing the functionality of an application without looking into the code.

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

boundary value

A

A minimum or maximum value of an ordered equivalence partition.

EX: Only for ages 18-56

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

boundary value analysis

A

A black-box test technique in which test cases are designed based on boundary values.

EX: Only for ages 18-56. Check before 18 and after 56.

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

burndown chart

A

Chart that depicts the effort versus time in an iteration. It shows the status and trend of completing the tasks of the iteration.
X-axis typically represents days in the sprint.
Y-axis is the remaining effort
Public

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

checklist-based reviewing

A

Review guided by a list of questions or required attributes.

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

checklist-based testing

A

Experience-based test where the experienced tester uses a high-level list of items to be noted, checked, 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
19
Q

code coverage

A

Analysis method which 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.

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

commercial off-the-shelf (COTS)

A

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.

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

compatibility

A

When a component or system can exchange information with other components or systems.

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

complexity

A

When a component or system has a structure that is difficult to understand, maintain and verify.

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

compliance

A

The need for software to adhere to standards, conventions or regulations in laws.

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

component

A

A minimal part of a system that can be tested in isolation.

Synonym: module , unit

25
Q

component integration testing

A

Testing performed to expose defects between integrated components.

26
Q

component specification

A

A component’s function in terms of its output values for specified input values under specified conditions, and required non-functional behavior.

27
Q

component testing

A

The testing of individual hardware or software components.

Synonyms: module testing , unit testing

28
Q

condition

A

A logical expression that can be evaluated as True or False.

29
Q

configuration

A

The composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.

30
Q

condition

A

A logical expression that can be evaluated as True or False.

31
Q

configuration

A

The composition of a components as defined by the number, nature, and interconnections of its constituent parts.

32
Q

configuration item

A

component that is managed in order to delivered an IT service.

33
Q

confirmation testing

A

Dynamic testing conducted after fixing defects with the objective to confirm that failures caused by those defects do not occur anymore.

Synonym: re-testing

34
Q

contractual acceptance testing

A

Acceptance testing conducted to verify whether a system satisfies its contractual requirements.

35
Q

control flow

A

The sequence in which operations are performed during the execution of a test item.

36
Q

cost of quality

A

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

37
Q

coverage

A

The degree to which specified coverage items have been determined or have been exercised by a test suite expressed as a percentage.

38
Q

coverage item

A

An attribute or combination of attributes that is derived from one or more test conditions by using a test technique that enables the measurement of the thoroughness of the test execution.

39
Q

coverage tool

A

A tool that provides objective measures of what structural elements, e.g., statements, branches have been exercised by a test suite.

40
Q

data flow

A

An abstract representation of the sequence and possible changes of the state of data objects, where the state of an object is any of creation, usage, or destruction.

41
Q

data-driven testing

A

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 testing is often used to support the application of test execution tools such as capture/playback tools.

42
Q

debugging

A

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

43
Q

decision

A

A type of statement in which a choice between two or more possible outcomes controls which set of actions will result.

44
Q

decision coverage

A

The coverage of decision outcomes.

45
Q

decision outcome

A

The result of a decision that determines the next statement to be executed.

46
Q

decision table

A

A table used to show sets of conditions and the actions resulting from them.

47
Q

decision table testing

A

A black-box test technique in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table.

Synonym: cause-effect decision table

48
Q

decision testing

A

A white-box test technique in which test cases are designed to execute decision outcomes.

49
Q

defect

A

An imperfection or deficiency in a work product where it does not meet its requirements or specifications.

Synonym: bug , fault

50
Q

defect density

A

The number of defects per unit size of a work product.

51
Q

defect management

A

The process of recognizing and recording defects, classifying them, investigating them, taking action to resolve them, and disposing of them when resolved.

52
Q

defect management tool

A

A tool that facilitates the recording and status tracking of defects.

53
Q

defect report

A

Documentation of the occurrence, nature, and status of a defect.

54
Q

driver

A

A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system.

55
Q

dynamic analysis

A

The process of evaluating behavior, e.g., memory performance, CPU usage, of a system or component during execution.

56
Q

dynamic analysis tool

A

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 monitor the allocation, use and de-allocation of memory and to flag memory leaks.

57
Q

dynamic testing

A

Testing that involves the execution of the software of a component or system.

58
Q

effectiveness

A

Extent to which correct and complete goals are achieved.