Topic: Interoperability Testing,

Message

   Interoperability Testing

Interoperability testing is the activity of proving that end-to-end
functionality between (at least) two systems
(application/communicating) is as required by those base systems'
standards.

The important factors characterizing interoperability testing are:

●the Equipment Under Test (EUT) and the Qualified Equipment (QE) together define the boundaries for testing;

  ●the EUT and QE come from different suppliers (or, at least, different product lines);

  ●interoperability tests are performed at interfaces that offer only normal user control and observation;

 ●interoperability tests are based on functionality as experienced
by a user (i.e., they are not specified at the protocol level). In this
 context a user may be human or a software application;

 ●the tests are performed and observed at functional interfaces
such as Man-Machine Interfaces (MMIs), protocol service interfaces and
Application Programming Interfaces (APIs).

The fact that interoperability tests are performed at the end points
and at functional interfaces means that interoperability test cases can
only specify functional behaviour. They cannot explicitly cause or test
protocol error behaviour. 

Mutual Testing

Mutation testing is verifying the testing procedure itself. It may also
be used to predict how many issues are yet to be found within the
system. To conduct Mutation testing one needs to purposely seed some
issues into the product (beware to remember each one). The amount of
found seeded defects indicates the level of testing coverage.

Verifying testing thoroughness

Suppose you have seeded 10 issues into different parts of system
and then provided it to the next testing stage. After completing
testing stage you have found 100 issues, 8 of which are from the seeded
sample. This means that defect removal efficiency of this stage is
about 80%.

DRE = DTF / DTS = 8 / 10 = 0.8

DRE - Defects removal efficiency

DS - Defects seeded

DSF - Seeded defects found

Determining the total amount of defect (including not found)

With example above, knowing that you have found 8 of 10 seeded
issues enables you to suppose that the total amount is proportional to
the amount of found issue at about the same ratio. Building a simple
proportion will give you a formula for determining the total amount of
defects:

DT = DTF * DS / DSF = 100 * 10 / 8 = 125

DT - Total defects (predicted)

This means you've got about 25 issues remaining not found.

Determining areas of weak coverage

Another possible application of this method is indicating the areas
when you would probably require more testing. Just look where, what
part of product, the not-found-seeded-issues are and add tests to those
areas.
_________________

Author	Message
vidhya Senior Member Joined: 24Mar2007 Online Status: Offline Posts: 114	Topic: Interoperability Testing, Posted: 28Mar2007 at 5:38am
	Interoperability Testing Interoperability testing is the activity of proving that end-to-end functionality between (at least) two systems (application/communicating) is as required by those base systems' standards. The important factors characterizing interoperability testing are: ●the Equipment Under Test (EUT) and the Qualified Equipment (QE) together define the boundaries for testing; ●the EUT and QE come from different suppliers (or, at least, different product lines); ●interoperability tests are performed at interfaces that offer only normal user control and observation; ●interoperability tests are based on functionality as experienced by a user (i.e., they are not specified at the protocol level). In this context a user may be human or a software application; ●the tests are performed and observed at functional interfaces such as Man-Machine Interfaces (MMIs), protocol service interfaces and Application Programming Interfaces (APIs). The fact that interoperability tests are performed at the end points and at functional interfaces means that interoperability test cases can only specify functional behaviour. They cannot explicitly cause or test protocol error behaviour. Mutual Testing Mutation testing is verifying the testing procedure itself. It may also be used to predict how many issues are yet to be found within the system. To conduct Mutation testing one needs to purposely seed some issues into the product (beware to remember each one). The amount of found seeded defects indicates the level of testing coverage. Verifying testing thoroughness Suppose you have seeded 10 issues into different parts of system and then provided it to the next testing stage. After completing testing stage you have found 100 issues, 8 of which are from the seeded sample. This means that defect removal efficiency of this stage is about 80%. DRE = DTF / DTS = 8 / 10 = 0.8 DRE - Defects removal efficiency DS - Defects seeded DSF - Seeded defects found Determining the total amount of defect (including not found) With example above, knowing that you have found 8 of 10 seeded issues enables you to suppose that the total amount is proportional to the amount of found issue at about the same ratio. Building a simple proportion will give you a formula for determining the total amount of defects: DT = DTF * DS / DSF = 100 * 10 / 8 = 125 DT - Total defects (predicted) This means you've got about 25 issues remaining not found. Determining areas of weak coverage Another possible application of this method is indicating the areas when you would probably require more testing. Just look where, what part of product, the not-found-seeded-issues are and add tests to those areas. _________________
	MBA Examination papers Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Software Testing @ OneStopTesting : Beginners @ OneStopTesting