Protocol Testing Course Details

This protocol testing course is recommended for audience with a background in networking, passed CCNA/CCNP, Network and System administrators looking for role change. The course focuses on Layer 2 and Layer 3 protocol and features. The role of a L2/L3 protocol testing engineer is to test and validate the functionality of the protocol and features on networking devices like routers and switches. The protocol testing engineer is required to have a sound knowledge on the functionality of the feature and protocol which is to be tested. Protocol testing can be grouped in two categories: Stress & Reliability Tests and Functional Tests.

  • Stress and Reliability Tests include Performance Testing, Load Testing, Stress Testing, Line Speed Testing and Robustness or Security Testing.
  • Functional Tests include Negative Testing, Inopportune Testing, Conformance/Compliance Testing, Syntax and Semantic Testing, Interoperability Testing and Deep-path Testing.

Protocol Testing Course Highlights

Course Duration

1 month

8 Weekends



Delivery Mode

Class Room Training

Apply Online

Click Now
Project Managers 80%
Students 70%
Developers 40%
Financial Analyst 50%
Data Analyst 70%
Data Miners 40%
Specialist 80%

Basic Computer Networking Course

sl no Contents
Networking Fundamentals
  • Introduction to networking and networking concepts
  • Computer Fundamentals
  • Hardware Configuration
  • The 7 Layer architecture
  • TCP/IP Stack
  • Connecting devices Repeaters, Hubs, Switches, Bridges, Routers Hubs vs Switches
  • Introduction of NIC /HBA/CNACards, MAC Address
  • Introduction to various types of cables and connectors used in networking
  • LAN Standards – Ethernet CSMA/CD, Token Ring
  • Structured Cabling
  • IP Addressing and configuration of IP Address
Week-2 & 3
TCP/IP Fundamentals
  • TCP
  • UDP
  • Difference between TCP & UDP
  • Difference between Routed & Routing protocol
  • Difference between connection oriented & connectionless
  • Types of protocol and it uses (DV & LS & Hybrid)
3 L2/ Protocol
  • VLan
  • STP
  • RSTP
4 L3/ Protocol
  • IP
  • RIP
  • OSPF
5 Other Protocol
  • ARP
  • RARP
  • DNS
  • DHCP
  • ICMP

Basics of network security

sl no Contents
Manual Testing Course Content
Introduction to Software Testing
  • What is Software Testing
  • Why Testing is necessary
  • Today's IT World and Quality Assurance/Testing
Software Development Life cycle
  • Introduction
  • Feasibility study
  • Requirements analysis
  • Customer Requirements specification
  • Software Requirements specification
  • Functional Specification document
  • High Level Design
  • Low level design
  • Coding
  • Testing
  • Implementation and Maintenance
3 SDLC Models
  • Waterfall model
  • Spiral model
  • V-Model
1 Testing-Methods
    White Box Testing
  • Path testing
  • Loop testing
  • Condition testing
2 Black Box testing
3 Gray Box testing
4 Types of Testing (Black Box Testing)
1 Functional Testing
2 Integration Testing
  • Incremental Integration
  • Top down approach
  • Bottom up approach
5 System Testing
Test Case design Techniques
  • Error guessing
  • Equivalence Partition
  • Boundary Value Analysis
2 Test case writing
  • Functional Testcase
  • Integration Testcase
  • System Testcase
  • Review of Testcase
  • Walkthroughs
  • Inspection
  • Peer Review
  • Regression testing
  • Unit Regression
  • Regional Regression
  • Full Regression
3 Comparison of test cases, test scenarios
4 Test Scenarios
  • Business Scenarios
  • User Scenarios
6 Test Life Cycle
  • Requirements
  • System study
  • Test plan
  • Test Cases
  • Traceability Matrix
  • Test case execution
  • Defect tracking
  • Test Summary Report
7 Test Plan
  • objective
  • Scope
  • Approach
  • Methodologies
  • Deliverables
  • Test environment
  • Schedule and Resources
  • Effort and estimation
  • Entry and Exit criteria
  • Regional Regression
  • Risk
8 Checklists
  • How to create checklists
  • When to use checklists
    Requirement traceability Matrix
  • What is Traceability Matrix
  • How to map the requirements with Test cases
    Defect tracking
  • Defect life cycle
  • Severity, priority
  • Defect tracking Tool – Quality Center
  • Defect report
  • Defect Tracking Sheet
Week-5 ==Lab
Linux basics for Tester
  • Fundamentals of Linux
  • General commands
  • Linux file system
  • Piping and grep comands
  • Scope of using Linux for a tester
Basic Trouble shooting during the testing
Basic network troubleshooting (Network utilities)

Basic Computer Networking Course

1.Networking Fundamentals
alt_textIntroduction to networking and networking concepts
alt_textComputer Fundamentals
alt_textHardware Configuration
alt_textIntroduction to basic components of a typical PC
alt_textThe 7 Layer architecture
alt_textTCP/IP Stack
alt_textConnecting devices Repeaters, Hubs, Switches, Bridges, Routers Hubs vs Switches
alt_textIntroduction of NIC /HBA/CNACards, MAC Address
alt_textIntroduction to various types of cables and connectors used in networking
alt_textLAN Standards – Ethernet CSMA/CD, Token Ring
alt_textStructured Cabling
alt_text IP Addressing and configuration of IP Address
2. TCP/IP Fundamentals
alt_textDifference between TCP & UDP
alt_textDifference between Routed & Routing protocol
alt_textDifference between connection oriented & connectionless
alt_textTypes of protocol and it uses (DV & LS & Hybrid)
3.L2/ Protocol
5.L3/ Protocol
6.Other Protocol
Performance Testing 
process of verifying that the performance of the device under test meets an acceptable level. Performance testing is a superset of line speed testing in which performance applies to many aspects of a network device or application, and not just line speed.
Load Testing:
Load testing is used to determine how well a system will perform in a typical environment under a specific load. Load testing is useful when you are confident that the application is functionally sound, but you do not know how the application will perform under a specific load. The example of a load test is a call generator application that generates 1000 calls that a telephone switch must process. Does the switch continue to operate? Does its performance degrade or it crashes?
Stress Testing
 process of subjecting the device under test to out of boundary conditions. The device under test should report an error message, gracefully shut down, or reject the input in some other way. In no case, should the device under test crash, reboot, or cause any harm. An example of stress test can be 50 SNMP managers simultaneously querying one SNMP agent in the device under test. Normally, no more than one to three managers concurrently query an SNMP agent in a device. The device should perform an appropriate action.
Line Speed Testing
process of verifying that a device can operate at its rated line speed, when the bandwidth is 100% utilized or saturated. For example, if the device is rated as operating at 5 Giga bytes per second, then the device should be able to handle incoming traffic utilizing all the available bandwidth.
Syntax and Semantic Testing:
Protocol conformance testing requires testing both the syntax and the semantics (functionality) of the device under test. Semantic tests force the device under test into a certain condition or state. Often the test cannot verify the correct behavior; it must be verified by an operator. Its example can be a test for a router to check whether it is maintaining an accurate count of all erroneous incoming packets of a certain type requires a mechanism for generating the erroneous packets, counting them, directing them to the router, assuring they were received by the router, and then reading the actual counter in the router.
Negative Testing
process to verify that the device under test responds correctly to error conditions or unacceptable input conditions. Negative testing can be challenging because the number of incorrect conditions is unlimited. Example of a negative test would be using a security protocol for authentication with an incorrect parameter.
Inopportune Testing
process to verify that the device under test is able to react properly when an unexpected protocol event occurs. The event is syntactically correct, but occurs when not expected. Inopportune testing is a specific instance of negative protocol conformance testing. An example of inopportune testing is a BYE response to a SIP INVITE. The SIP INVITE is expecting a 100 Trying response, but not a BYE response.
Protocol Conformance Testing
process of systematically selecting each requirement in a standards document and then testing to see if the device under test operates according to that requirement. This is done by creating a series of single function tests for each requirement, resulting in thousands of tests. Conformance testing for computer networking protocol is defined in ISO/IEC 9646-1:1994(E) as "testing both the capabilities and behavior of an implementation, and checking what is observed against the conformance requirements in the relevant International Standards." An example of a conformance test is to check if the “ping” command operates correctly.
Robustness Testing
process of subjecting a device under test to particular input streams. The input streams may be one of three types:
  • alt_textRandom input streams
  • alt_text Valid input streams
  • alt_text Invalid input streams
Robustness testing is a form of security testing. Security testing is more broadly defined to include monitoring / surveillance and the detection of specific exploits like IP spoofing or phishing etc. The example of intelligent robustness test can be adding a trailing dot to the DNS name in the SIP URL. This is legal, but perhaps unexpected. The SIP implementation in the receiving device should process this correctly.
Interoperability Testing
process of testing devices from multiple manufacturers by interacting in such a manner as to exercise the network protocol under test. Interoperability testing is very useful in the early stages of a new product or new protocol. As products mature, interoperability testing becomes less valuable as it does not uncover enough new bugs to warrant the cost of setting up, configuring and managing network equipment from various manufacturers.
Deep-path testing
process of exercising every path through the code, not just the main path through the code. This is done by maintaining and tracking the protocol conversation very precisely, in a controlled way. Deep-path testing is useful for forcing a particular path through code that is very difficult to exercise but very important for correct operation.