Software Acceptance Testing Flashcards

1
Q

is intended to show that a program does what it is intended to do and to discover program defects before it is put into use.

A

Program Testing

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

2 PROGRAM TESTING GOALS

A
  1. To demonstrate to the developer and the customer that the software meets requirements. (LEADS TO VALIDATION TESTING)
  2. To discover situations in which the behavior of the software is incorrect, undesirable or does not conform its specification. (LEADS TO DEFECT TESTING)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

is concerned with rooting out undesirable system behavior.

A

Defect Testing

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

Are designed to expose defects

A

Test Cases

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

is also called a defect or bug. It is a erroneous hardware or software element of a system that cause the system to fail.

A

Fault

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

every step in the development process must start with a plan of how to verify the results meets a goal.

A

Test-Driven Development (TDD)

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

is a particular choice of input data to be used in testing a program and the expected output or behavior.

A

Test Case

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

is a finite collection of test cases.

A

Test

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

2 TYPES OF TESTING

A
  1. White Box Testing
  2. Black Box Testing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

exploits structure within the program.

A

White Box Testing

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

explores input space of functionality defined by an interface specification.

A

Black Box Testing

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

measures the degree to which the specification or code of a software program has been exercised by tests.

A

Test Coverage

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

focuses on the coverage of the input space, without necessarily testing each part of the software

A

“Big Picture” Specification Testing

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

measures the degree to which the elements of the program source code have been tested.

A

“Implementation Details” Code Coverage

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

is a black box testing method that divides the space of all possible inputs into equivalence groups such that the program is expected to behave the some on each input from the group.

A

Equivalence Testing

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

2 TYPES OF EQUIVALENCE TESTING

A
  1. State-Based Testing
  2. Integration Testing