L11 - Testing Flashcards Preview

EIST (IN0006) > L11 - Testing > Flashcards

Flashcards in L11 - Testing Deck (26):
1

System Testing

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

2

Error

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

3

Integration Testing

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

4

Fault Detection

testing + debugging + monitoring

5

SUT

'System under Test': part of the system model

6

Failure

Deviation of observed behavior from specified behavior.

7

Unit Testing

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

8

Object-Oriented Test Modeling

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

9

A Test Model contains ...

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

10

Fault Tolerance

exception handling + modular redundancy

11

Types of Integration Testing

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

12

Dynamic Analysis

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

13

Mock Object

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

14

Dummy Object

Object that gets passed around but never actually gets used.

15

Pros/Cons Top Down Integration

no drivers BUT: stubs needed

16

Stub

provides same answer always

17

Fault

Mechanical or algorithmic cause of an error.

18

Validation

Checks if actual behavior meets the needs of the stakeholders.

19

Verification

Checks if observed behavior complies with specified behavior.


20

Pros/Cons Bottom Up Integration

no stubs/useful for OOS/RTS BUT: drivers

21

Advantages of Vertical Integration

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

22

Fake Object

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

23

Static Analysis

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

24

Acceptance Testing

Test entire system in target environment (client involved)

25

Fault Avoidance

reduce complexity + use config management + apply verification

26

Pros/Cons Sandwich Testing/BU+TD

parallel BUT: no thorough interface test