Mastery 12: Testing in OO

In all software-projects you will eventually going to have to do some form of testing, but especially in OO testing can be a bit different. But this doesn’t have to be a bad thing, some programmers say it is easier to do testing in OO and other say the opposite.

The whole object oriented testing revolves around the fundamental entity know as “class”. With the help of “class” concepts, larger systems can be divided into small well defined units which may then be implemented separately. The object oriented testing can be classified as like conventional systems. These are called as the levels for testing.

The levels of testing can be classified into 3 categories:

1. Class testing

Class testing is also known as unit testing, in class testing, every individual classes are tested for errors or bugs. Class testing ensures that the attributes of class are implemented as per the design and specifications. Also, it checks whether the interfaces and methods are error free or not.

2. Inter-Class testing

It is also known as integration or subsystem testing. Inter class testing involves the testing of modules or sub-systems and their coordination with other modules.

3. System testing

In system testing, the system is tested as whole and primarily functional testing techniques are used to test the system. Non-functional requirements like performance, reliability usability and test-ability are also tested.




Fyll i dina uppgifter nedan eller klicka på en ikon för att logga in: Logo

Du kommenterar med ditt Logga ut /  Ändra )


Du kommenterar med ditt Google-konto. Logga ut /  Ändra )


Du kommenterar med ditt Twitter-konto. Logga ut /  Ändra )


Du kommenterar med ditt Facebook-konto. Logga ut /  Ändra )

Ansluter till %s