Question 5
5.1
Conventional Unit Testing
1. Module interfaces are tested for proper information flow.
2. Local data are examined to ensure that integrity is maintained.
3. Boundary conditions are tested.
4. Basis (independent) path are tested.
5. All error handling paths should be tested.
6. Drivers and/or stubs need to be developed to test incomplete software.
Object-Oriented Unit Testing
1. Smallest testable unit is the encapsulated class or object.
2. Similar to system testing of conventional software.
3. Do not test operations in isolation from one another.
4. Driven by class operations and state behaviour, not algorithmic detail and data flow across module interface.
5.2.1
Validation Testing
Focuses on visible user actions and user recognizable outputs from the system.
5.2.2
1. Validation tests are based on the use-case scenarios, the behaviour model, and the event flow diagram created in the analysis model.
a. Must ensure that each function or performance characteristic conforms to its specification.
b. Deviations (deficiencies) must be negotiated with the customer to establish a means for resolving the errors.
2. Configuration review or audit is used to ensure that all elements of the software configuration have been properly developed, cataloged, and documented to allow its support during its maintenance phase.
