What is Object-Oriented Testing ?

Object-Oriented Testing

The system is tested to ensure that errors in requirements are uncovered. There are three types of testing related to OO context are:

1. Unit Testing
2. Integration Testing
3. Validation Testing

1.      Unit Testing

• When object-oriented software is considered, rather than testing an individual module, the smallest testable unit is the encapsulated class or object. A class can contain a number of different operations and a particular operation may exist as part of a number of different classes. Thus class testing for OO software is driven by the operations encapsulated by the class and state behavior of the class. 

2.      Integration Testing

• There are two different strategies for integration testing of OO systems. The first, thread-based testing, integrates the set of classes required to response to one input or event for the system. Each thread is integrated and tested individually. The second integration approach, use-based testing, begins the construction of the system by testing those classes (called independent classes) that use very few (if any) of server classes. After the independent classes are tested, the next layer of classes, called dependent classes, that use the independent classes are tested. This sequence of testing layers of dependent classes continues until the entire system is constructed.

3.      Validation Testing

• The validation of OO software focuses on user-visible actions and user-recognizable output from the system. To begin the validation tests, the tester should draw upon the use-cases that are part of the analysis model. The use-cases provide a description of how the system will be used. It also provides a scenario that has a high likelihood of uncovered errors in user interaction requirements.