Software Testing Preliminaries Flashcards

1
Q

How is correctness established?

A

Mathematical Proofs

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

What is the purpose of testing?

A

To find defects in the software

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

What is branch testing?

A

Execute each outcome of each decision point in a program

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

A review of a software work product, following defined procedures, by peers of the producers of the product for the purpose of identifying defects and improvements

A

Peer reviews

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

Selective retesting of a system or component to verify that modifications have not caused unintended effects and that the system or component still complies with its specified requirements

A

Regression Testing

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

The degree to which a system, component, or

process meets specified requirements

A

Quality

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

A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement

A

Test case

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

All the planned and systematic activities implemented within the quality system, and demonstrated as needed, to provide adequate confidence that an entity will fulfill requirements for quality

A

Quality assurance

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

Is the purpose of testing to demonstrate that software works?

A

No, it is to find defects in the software.

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

The “normal” development process will remove about __% of defects before they are ever counted

A

50

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

A person makes a _____ which becomes a ____ resulting at execution in a ____ which is wrong with some degree of ____

A

Mistake, fault, failure, error

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

Formal proof of program correctness

A

Verification

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

____ methods allow sets of requirements to be examined for completeness, consistency, and equivalence to another requirement set

A

Formal

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

____ methods result in ____ ____

A

Formal, formal, specifications

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

Quality attributes that refer to the code and related documentation

A

Static

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

Black-Box Testing

A

Functional Testing. Ignores the internal mechanism

17
Q

White-Box Testing

A

Internal mechanism is known

18
Q

Statement Testing

A

Execute each statement of a program

19
Q

A static analysis technique in which a designer or programmer leads members of the development team and other interested parties through a segment of documentation or code, and the participants ask questions and make comments about possible errors, violation of development standards, and other problems

A

Walkthrough

20
Q

Testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements

A

System Testing

21
Q

Testing in which software components, hardware components, or both are combined and tested to evaluate the interaction between them

A

Integration Testing

22
Q

Quality attributes that refer to the behavior of the application while in use

23
Q

What is exhaustive testing?

A

Testing a program on all possible inputs

24
Q

What is needed for a program to be considered correct?

A

Behaves as expected on each element of its input domain

25
A static analysis technique that relies on visual examination of development products to detect errors, violations of development standards, and other problems
Inspection
26
Formal testing conducted to determine whether or not a system satisfies its acceptance criteria and to enable the customer to whether or not to accept the system
Acceptance Testing
27
Testing of individual hardware of software units or groups of related units
Unit Testing
28
The process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements
Validation
29
The process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase
Verification
30
Path Testing
Execute all or selected paths through a program
31
What is a black-box testing measure?
percentage of requirements covered
32
What is a white-box testing measure?
percentage of statements, decisions, conditions covered
33
T/F Program testing can be used to show the presence of bugs, but never to show their absence
T
34
T/F Knuth said "Beware of bugs in the above code; I have only proved it correct, not tried it"
T
35
A systematic examination of the requirements, design, or implementation of a system, or any part of it, by qualified personnel
Structured walkthrough
36
A technique for expressing requirements in a manner that allows the requirements to be studied mathematically
Formal methods
37
T/F Formal methods allow sets of requirements to be examined for completeness, consistency, and equivalency to another requirement set
T
38
What do formal methods result in?
Formal specifications
39
A collection of test cases
Test set