How to do interoperability testing?
Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Beginners @ OneStopTesting
Forum Discription: New to the Club...!!! Don't Worry, We are here for you...!!! Learn the very basics of Software Testing and other pertinent Informations.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=494
Printed Date: 20Jul2025 at 11:08am
Topic: How to do interoperability testing?
Posted By: suma
Subject: How to do interoperability testing?
Date Posted: 02Apr2007 at 10:01pm
How to do Interoperability testing?
For What is Interoperability Testing,
Interoperability Testing Methodology#1
The components and the steps for developing an interoperability test specification are:
● specify the Abstract Architecture;
● prepare draft Interoperable Functions Statement (IFS);
● specify Test Suite Structure (TSS);
● write Test Purposes (TP) and place them into the TSS;
● write Test Cases and place them into a Test Suite according to the TSS;
● validate Test Cases;
● finalize IFS.
Terms Explained
What is Abstract Architecture?
An abstract testing architecture provides a general framework within
which specific test arrangements must fit in order to perform the
specified suite of tests. Defining this architecture at an early stage
should help to provide a structure for the test cases specified later.
What is Interoperable Functions Statement?
An Interoperable Functions Statement (IFS) identifies those
standardized functions that an Equipment Under Test (EUT) must support,
those that are optional and those that are conditional on the presence
of other functions . Although not strictly part of the interoperability
test suite, the IFS helps to provide a structure to the suite of tests.
In addition, the IFS can be used as a proforma by a manufacturer
in identifying the functions an EUT will support when interoperating
with corresponding equipment from other manufacturers.
If one exists, the ideal starting point in the development of an
IFS is the Protocol Implementation Conformance Statement (PICS) which
should clearly identify the tested protocol's options and conditions.
Like the PICS, the IFS should be considered part of the base protocol
specification and not a testing document.
What is Test Suite Structure?
The Test Suite Structure is a logical division of the test suite
into Test Groups. The Test Suite Structure provides the categories into
which both Test Purposes and Test Cases are placed.
The Test Purposes
Before writing the individual steps that are required to complete a
Test Case, a full description of the objective of each Test Case should
be specified in its Test Purpose. Without this objective, it may not be
clear how the test should be defined. The following example explains
the intent of the associated Test Case in enough detail that there
should be no ambiguity for the test writer.
| Quote: | | Test
Purpose: To verify that a call can be established successfully to User
B by User A and that speech communication is possible between User A
and User B. |
Test Cases
An Interoperability Test Case is the detailed set of instructions (or
steps) that need to be taken in order to perform the test. In the case
where the test driver is a human operator, these instructions will be
in natural language . In the case where the tests are automated, they
may be written in a programming or test language such as C++. The
combined Test Cases should cover all events at each of the available
Test Interfaces.
Test Suite
An interoperability test suite is the collection of test cases
designed to prove the ability of two (or more) systems to interoperate.
The test cases are organized in a hierarchy by the Test Suite Structure.
_________________
I ♡ software testing!
|
|