Mastery12 Object-Oriented Testing

Mastery12

Hello there, and welcome to the next topic. Today I will tell you something about testing in Object-Oriented Testing. Once again, I have a nice song for you so, play it and enjoy the post.

Today’s topic is the Object-Oriented Testing (OOT). We have already talked about testing in general, as a phase in the Life Cycle of Software. Object-Oriented Testing differs from the conventional testing and I will write about the OOT and explain the differences to the Conventional Testing. 

When do we use OOT, well, -attention, attention, captain obvious steps on deck- when you use object-oriented systems. More specific, when you don’t use the Waterfall model, what this means will be answered later. In the OOT you have three levels of testing.

1. Unit Testing

In this level, the individual classes are tested. The application engineer -who implements the structure- tests the class attributes for the correct implementation as per design and whether the methods are error-free.

2. Subsystem Testing

This level, is testing –captain obvious back again- subsystems and modules. The responsible person is the subsystem lead engineer. Therefore, the interaction of the subsystem with the outside and the associations with the subsystems are tested. 

3. System Testing

The third and last level, is testing the system as a whole, which is the responsibility of the quality-assurance team. 

So, beside the levels, there are also OOT Techniques.

Grey Box Testing is such a technique. The aim is to test defects due to improper usage of applications. But why is it called Gray Box Testing? Black + White = ? 
Black Box Tester is unaware of the internal structure of the application to be tested. A
White Box Tester has access to the internal structure of the application. Now, Gray Box Tester partially knows the internal structure, which includes access to the documentation of internal data structures as well as the algorithms used. It’s a combination out of the Black- and White Box Tester.

A technique for the Subsystem Testing is the Thread Base Testing, in which all classes that are needed to realize a single use case in a subsystem are integrated and tested.

A System Testing technique would be the Alpha Testing. Therefore, bugs are identified before the release of the product to real users. Internal employees test the the product using the White Box Testing and Black Box testing in a testing environment or a lab. 

What is the difference between OOT and Conventional testing?

The Conventional Testing is realized in the Waterfall Lifecycle Model and the OOT is realized for the different Models like Agile or Incremental.
Conventional Testing focuses on  three levels of testing (system, integration and unit), compared to that, the OOT uses much smaller units compared to the Conventional one. 

Well, well it won’t get any better than that! So as always, thank you for sticking around. I hope you enjoyed the song, it’s my favorite right now.
See you on my next post. 
-SolidSnake8