Let´s talk about testing. Tests are intended to show that a program does what it intends to do and discover the flaws of the program before putting it into use. On this post we will talk about how to test Object Oriented systems and/or structures. Let´s remember that Object Oriented based is not as intuitive as other paradigms, since all data is represented in objects, obviously. This means that each object contains data as well as information about the executable file needed to interpret the data without mentioning encapsulation, heritage, polymorphism, abstract and generic classes. Let´s segment out Object Oriented for testing.
The Object Oriented Segments.
This type of testing is also known as “unit testing”. In class testing, every individual classes are teste for errors and possible bugs. It ensures that the attributes of a class are implemented as per the design and specifications. It can also check whether the interfaces and methods are error free or not.
Inter-class testing, also known as integration or subsystem testing, involves the testing of modules or sub.systems and their coordination with other modules.
In the system testing, the system itself is tested as a whole and primarily functional testing techniques are used to test the system. Non-functional requirements such as performance, reliability, usability and test.ability are also tested.
Object Oriented based systems are kind of complex, not in a difficulty sense but content wise. For testing, you can segment your Object Oriented based system in Classes for units of the system , Inter-class for subsystems that at the same time are made of units and System, that involves the whole structure that at the same time the system can be made of subsystems.