G08 S22

Terminology

• Error is when the observed behavior is not equal to the expected behavior

• Verification is the activity of checking for deviations from the specified behavior of the system

• When the system has an error, any further processing could lead to failure

Unit Testing

• Black box testing is done using analysis knowledge to discover new features

• White box testing tests what is done instead of what should be done

• During unit testing developers test groups of subsystems

Integration Testing

• During integration testing, the developers test the complete system and how well all the components are integrated together

• A driver acts as a replacement of the actual subsystem and provides the same interface

• Later integration exposes the system to higher risks of unexpected failures, vertical integration is therefore used to build, integrate and test subsystems as early and as frequently as possible

System Testing

• During system testing, the complete system is examined in the target environment to see whether it meets the client’s requirements or not

• Fuzzing refers to running a program on many random, abnormal inputs to detect deviations from the expected behavior

• White box fuzzing generates input without any knowledge of the program

Model Based Testing

• The Oracle contains all data that is required for the test case execution

• With automated testing, it is possible to test a system completely

• It's helpful to separate developers from testers

Object Oriented Testing

• Mock objects replace the behavior of a real object and returns hardcoded values

• Mock objects are often used to fill parameter lists, passed around and never actually used

• Mock objects simulate the behavior of existing code