Interoperability Testing(IOT)

Interoperability Testing:

This is one type of Manual Testing type. In normal system testing we will test the functionalities of the product against one device/OS version or may be more.

For example in case of mobile application testing on Android platform :

We will perform the mobile application testing on any of the Android devices/OS version or may be more.So Testing may be performed on Android device from Samsung vendor and on particular version Android 4.4.

In case of Interoperability testing we must ensure that the application is working good in all of the Android versions and the vendors(These details may be sometimes depend on the input provided by client.

At sometimes we may face the issues that might be observed on some Android devices only and on other Android devices it will be working fine. So to uncover these issues we need to perform the Interoperability Testing.

The final test summary report should consists of the all passed/failed cases against the all Android devices that need to be tested. Interoperability testing can be performed along with System Testing.
In some companies there will be different teams for both System and Interoperability Testing. Where as some times same testing team might be performed by one team only.

As per customer point of view this testing is very important as we cannot control which Android/OS version the customer will work. If the interoperability testing is not performed then the issues will be found from the users side which will effect the client business.

White Box Testing types

White Box Testing:

This is a process of validating internal components or structures. So one must be having good knowledge on internal components or structure of a System.

We can divide white box testing in to two types called,

1.Static Testing.

2.Dynamic Testing.


1.Static Testing:

Testing performed without executing the source code.


2.Dynamic Testing:

Testing performed by executing the source code.


Static Testing types will be covered in next articles.

Under Dynamic Testing mostly 3 types of testing was performed.

1.Statement Coverage.

2.Branch Coverage.

3.Path Coverage.


1.Statement Coverage:

A Statement is a line of code which get executed after compilation. This method is to find whether all the statements in source code are executed at least once.

Example:

int A;
int B;
int C;

C=A+B

if(C>70)
print "True"

So how many test cases are required to test verify all the statements in the above code get executed or not.?

1 Test case is enough right?

Lets see how it is...

Suppose consider we gave input 'A' and 'B' as 40 and 50 then the value of 'C' becomes 90.

So the condition (90>70) becomes True and it will print "True" at output screen.

Is the above Test case is enough to cover all the conditions?..

Absolutely not!!!

Let's consider if we gave the input as 10 and 20 then the value of 'C' becomes 30 the condition will fail and the print statement will not get executed. In that case not all statements get executed. This method cannot cover the all the possible scenarios.




 

Manual Vs Automation Testing

As we should not compare both Manual and Automation each type has its own Advantages & Disadvantages. Manual Testing is the base for Automation Testing.

Manual Testing:

It is a way of testing which is performed by humans. In this we will design the test cases or test scenarios based on Requirement specifications, And we will start executing the test cases.

Advantages:

1.The initial testing has to be performed in the manual way, Because the product will not be stable initially and we should not automate the product that is not stable.

2.We can think of different scenarios on the go while testing the product which we find more issues.

3.It will eliminate the use of Automation tools.

4.Useful for small projects.

5.No need of learning the tools.

Automation Testing:

It is the way of performing the testing by means of Automation tools. In this we will write the scripts which will direct the tools to perform testing.

Some Automation tools support Record and Play Option which is an easy process. In this we will start recording our testing process i.e how we are interacting with the application and it will be Played to replicate the action that we performed earlier.In this case it will automatically creates the script.

Advantages:

1.Takes less time.

2.Good for large projects.

3.More reliable.

4.Coverage is more.

5.Reduces the man power required.

Disadvantages:

1.One needs to learn the tool.

2.Scripting knowledge is required.

3.Costly.

4.Cannot perform until the product is stable.

Here are the some list of Automation Tools:

QTP

Selenium

Load Runner

J Meter etc.,