 |
 |
 |
 |
 |
 |
 |
 |
 |
OSS ORDERING SUBSYSTEM FUNCTIONAL...
Comnet has performed functional verification of
the ordering subsystems for a major OSS manufacturer. The
system-under-test is implemented in Java using an N-tier architecture.
Comnet has provided an independent test team to verify the functionality
in an ongoing program of releases. The Comnet team is responsible for both
the testing of new features and regression testing the existing
functionality.
Two
strategies are used to provide customers with test labs. Comnet has
established a testing lab at its facility in Chennai. Much of the testing
uses this "local" lab. In addition the Comnet team tests remotely using
the customer's testing lab in North America. The necessary communications
facilities consist of Virtual Private Network (VPN) connections between
Chennai and North America.
Comnet engineers not only test the Graphical User Interface (GUI) functionality provided by the product but also verify the functionality of a CORBA-based Application Programming Interface
(API). The Comnet team has developed automated testing tools to automate this API testing. Using a Java-based test client and Mercury Interactive's WinRunner, a fully automated test suite has been implemented for testing this API.
OSS
Service Assurance System Functional Verification
Comnet has undertaken the independent testing of a
major OSS vendor's system for defining a Service Level Agreement offer,
negotiating the SLA on a customer-by-customer basis and then monitoring
the resulting delivery of service.
The project began with a period of on-site
training at the customer facility. Testing was then transitioned to
Comnet's development center in Chennai. The testing team in Chennai
accessed the system lab remotely for the majority of the testing. Tests
that required physical presence in the system lab (real mobile station
testing) were handled by Comnet's on-site staff from Chennai who visited
the customer facility on a rotating basis.
The initial testing was "Product Evaluation"
regression testing. This testing ensured that the basic wireless
functionality was not broken during the development of new functionality
in each new Customer Delivery. Customer-supplied testing tools were used
to support the testing. Testing drivers consisted of real mobile stations
as well as network elements simulators. Over 35 customer deliveries were
successfully tested.
As
a result of the Comnet team's success with Product Evaluation testing, the
team's responsibility was expanded to include Stability Testing. This
testing assessed the system-level stability of the MSC. Testing was
carried out by deploying the Alcatel 8610 as a Call Load Generator
incorporating various call/message load scenarios to load the MSC.
Additional selected functional scenarios were executed on top of this
background load. On average, two stability runs were conducted for each
customer delivery.
While
the initial Product Evaluation testing involved the execution of manual
procedures, the Comnet test team also worked with the customer to
implement an automated testing program. The team implemented and validated
high-level software functions and test scripts to automate the testing
process using the customer's Automated Testing System. This Automated
Testing System allowed the test script writer to develop object-oriented
tests using the object-oriented TCL scripting language. On the order of
150 high level software functions were developed to facilitate test script
development and over 400 test scripts were implemented and verified. This
test automation effort reduced testing time and thereby increased the
productivity, test coverage and cost savings per customer delivery by
automating approximately 70 percent of the tests executed. Many of the
software functions were subsequently reused by the customer to support the
testing of an evolving UMTS MSC.
 | |||
| copyright © 2007 Comnet |  |
||