L11 - Testing

Question 1

System Testing

Answer 1

Test entire system: Functional Testing (functional requirements) + Structure Testing (subsystem decomposition) + Performance Testing (non-functional requirements) + Acceptance Testing (client expectation)

Question 2

Error

Answer 2

System in a state where further processing can lead to failure.

Question 3

Integration Testing

Answer 3

tests all interfaces between subsystems and the interaction + intends to create failures intentionally

Question 4

Fault Detection

Answer 4

testing + debugging + monitoring

Question 5

SUT

Answer 5

‘System under Test’: part of the system model

Question 6

Failure

Answer 6

Deviation of observed behavior from specified behavior.

Question 7

Unit Testing

Answer 7

Test individual units (via Java framework: JUnit) - carried out to confirm correct code and show intended functionality

Question 8

Object-Oriented Test Modeling

Answer 8

Start with system model (system > SUT) - test model derived from SUT - add objects (test doubles) to test model - doubles are substitutes for the collaborators during testing

Question 9

A Test Model contains …

Answer 9

test driver (program that executes test cases) + input data (consists of data needed for test cases) + oracle (compares expected output with actual test output) + test harness (framework that allows to run tests under varying conditions) + test cases

Question 10

Fault Tolerance

Answer 10

exception handling + modular redundancy

Question 11

Types of Integration Testing

Answer 11

Big Bang Integration + Bottom Up + Top Down + Sandwich Testing/BU+TD + Vertical Integration

Question 12

Dynamic Analysis

Answer 12

Black-Box (tests input/output): does not discover extra use cases & White-Box (tests implementation): cannot detect missing use cases

Question 13

Mock Object

Answer 13

able to mimic the behavior of real objects (‘record-replay metaphor’: orchestra + choir)

Question 14

Dummy Object

Answer 14

Object that gets passed around but never actually gets used.

Question 15

Pros/Cons Top Down Integration

Answer 15

no drivers BUT: stubs needed

Question 16

Stub

Answer 16

provides same answer always

Question 17

Fault

Answer 17

Mechanical or algorithmic cause of an error.

Question 18

Validation

Answer 18

Checks if actual behavior meets the needs of the stakeholders.

Question 19

Verification

Answer 19

Checks if observed behavior complies with specified behavior.


Question 20

Pros/Cons Bottom Up Integration

Answer 20

no stubs/useful for OOS/RTS BUT: drivers

Question 21

Advantages of Vertical Integration

Answer 21

no stubs/drivers - build as early as possible —> always an executable program available

Question 22

Fake Object

Answer 22

working implementation but not suitable for production code (database on hard disk instead of web server)

Question 23

Static Analysis

Answer 23

hand execution: finds only 5-10% of software quality problems but cheap

Question 24

Acceptance Testing

Answer 24

Test entire system in target environment (client involved)

Question 25

Fault Avoidance

Answer 25

reduce complexity + use config management + apply verification

Question 26

Pros/Cons Sandwich Testing/BU+TD

Answer 26

parallel BUT: no thorough interface test