15 Implementation Flashcards

1
Q

Top-Down Integration

A

Starting with user-facing shit, and working down. Major faults show up early, but low-level things might not be tested well.

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

Starting with user-facing shit, and working down.

A

Top-Down Integration

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

Bottom-Up Integration

A

Work from system-facing towards user-facing shit. Everything is tested well, but major design flaws might not appear until the end.

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

Work from system-facing towards user-facing shit.

A

Bottom-Up Integration

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

Doing both bottom-up and top-down integration at once.

A

Sandwich Integration

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

Implementation test workflow

A

Unit testing, product testing, acceptance testing

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

Testing to Spec, AKA

A

Black Box Testing

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

Black Box Testing, AKA

A

Testing to Spec

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

Testing to Code, AKA

A

Glass Box Testing

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

Glass Box Testing, AKA

A

Testing to Code

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

Test-to-Spec

A

Use specifications to define test cases. Test every possible set of values within specs.

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

Equivalence Testing

A

Test in-range, and just outside/inside range.

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

Testing in-range, and just outside/inside range.

A

Equivalence Testing

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

Glass Box test coverage

A

Statement, Branch, Path

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

Linear Code Sequences

A

Points where control flow might jump

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

Points where control flow might jump

A

Linear Code Sequences

17
Q

All-Definition-Use-Path Coverage

A

Test all paths between variable declaration and use, as IDed by a CASE tool.

18
Q

Measures of code complexity

A

LOC or Cyclomatic complexity

19
Q

Testing when you’re ready to add a new module

A

Integration Testing

20
Q

Integration Testing

A

Testing when you’re ready to add a new module

21
Q

Testing customer does when they get the product

A

Acceptance Testing

22
Q

Testing under load

A

Stress Testing

23
Q

Stress Testing

A

Testing under load

24
Q

Testing with very large files

A

Volume Testing

25
Q

Volume Testing

A

Testing with very large files

26
Q

Bit of code you can’t execute whatsoever

A

Infeasible Code

27
Q

Infeasible Code

A

Bit of code you can’t execute whatsoever

28
Q

Cyclomatic Complexity

A

Roughly, number of paths/branches

29
Q

Correctness

A

Does the right action

30
Q

Does the right action

A

Correctness

31
Q

Robustness

A

Runs on a variety of systems and hardware

32
Q

Runs on a variety of systems and hardware

A

Robustness

33
Q

Performance

A

Speed

34
Q

Speed

A

Performance