Protocol Testing/Protocol Testing Tools

 

Testing Tools Used for Protocol Testing
1	Glomosim simulator	To Test 100 nodes on single CPU
2	Abacus5000	To Test SIP
3	Etherpeek	To Test IP
4	Nethawk	For SS7 testing
5	Wireshasrk	For SS7/IP testing
6	K1297	For Testing G20(tektronics).
Various Domain in Telecom Testing
1	Protocol Testing
2	Network Testing
3	NMS/EMS Testing
4	VOIP Testing
5	SIP Testing
Roles for Telecom Testing
1	Telecom Test Engineer
2	Sr.Telecom Test Engineer
3	Telecom Test Lead
4	Quality Analyst
List of Some reputed Companies Developing/Testing software for Telecom Products
1	SASKEN	15- ALCATEL
2	WIPRO	16- SUBEX TECHNOLOGIES
3	TECH MAHINDRA	17-HELLOSOFT
4	TCS	18-LG
5	SATYAM	19-INFOSYS
6	ADVENTENT	20-PT Pure Testing Software Pvt Ltd
7	COGNIZANT	21-QUALCOMM
8	IBM	22-GLOBALHUNT
9	AVAYA	22-CISCO
10	SIEMENS	23-KODIAK NETWORKS
11	NOKIA	24-COLLABERA TECHNOLOGIES LTD
12	ZTE	25. SYMBIOSIS NETWORK
13	HCL	26.Brocade Communication Systems Pvt Ltd
14	GlobalLogic India Pvt Ltd	…………………..Many more
Need Practical and Hands on
1	LAB EXERCISE
2	TOOLS HANDS -ON
3	Protocol Log Analysis and Debugging
Development Tools & Languages
1	Protocol Debugging Tools: NetHawk Tracers, Wire shark
2	Variance of C, C++ in Telecom protocol development
3	Configuration Management Tools: SVN, CVS*, Clear case
4	LINUX Basics, LINUX administration*
5	Scripting Languages: PERL, EXPECT, Shell.
6	Project on telecom with C/C++.
Post Training Activities
1	Resume drafting
2	Technical group discussion
3	Technical Seminars
4	Mock interviews
5	Placement Assistance

Telecom Testing /Protocol Testing

Telecom Testing

Telecom lifecycle is different from the software lifecycle and a testing strategy based on the telecom lifecycle is required to address the issues of converged space. V, X and proactive testing models do not address the challenges of telecom end-to-end business in the converged world as it is non-standard and lacks a common industry acceptance. Issues in telecom testing are taken up in more detail as challenges under each view of telecom lifecycle.

 

The telecom testing lifecycle is based on the NGOSS telecom lifecycle defined in GB927. The testing lifecycle consists of four views. The business and deployment view is concerned with the service provider while the System / Architecture and Implementation view correspond to the Service Developer. As shown in figure 1, each view in the telecom testing lifecycle generates a set of artifacts. The artifacts in each view serve as input to the succeeding views. Any customer request or service development / enhancement can be categorized as a business requirement. The testing lifecycle starts once the business requirement is analyzed. Once a decision is made on developing the requirement, testing then moves to the system / architecture view where the service developer works on defining a technology- neutral method of implementing the requirement. This is followed by the Implementation view where the requirement is implemented. The implementation view in itself would involve certain amount of integration of the component developed in stages. The major view where a telecom-based testing pays off is in the deployment view where multiple implementations are integrated during deployment. In a multi-service, heterogeneous, multi-vendor environment, the test artifacts and their execution results for the other views serve as input to generation of deployment artifacts that result in providing new service offerings with a higher degree of flexibility and a shorter time-to-market with minimal or zero failures during operation

The test artifacts developed in different views can be test plan, test case or even a test model for the specific telecom scenario.

Figure 2 shows the items that make up the test artifacts developed in each view.

|

5. Views in the Testing Lifecycle

5.1 Business View

This view handles investigation of the requirements and Proof of Concept before taking up the requirements. The

investigation of the requirements starts with elicitation and ends with specification. Based on requirement specification artifacts, a proof of concept (PoC) is developed to assess the feasibility of taking the requirement to service developers based on current infrastructure and products.

List of Companies Developing/Testing software for Telecom Products

SASKEN
WIPRO
TCS
ADVENTNET
HCL
SATYAM
TECH MAHINDRA