Controlled exception-based routing protocol validation

1. A method of testing an implementation of a routing protocol in a device, the method comprising:

providing a sequence of protocol messages;

introducing a specific playback delay between at least one pair of adjacent protocol messages in the sequence of protocol messages; and

testing how the device reacts to the sequence of protocol messages with the specific playback delay;

wherein the specific playback delay is to cause a protocol state transition in the device which differs from an expected protocol state transition absent the specific playback delay.

2. The method of claim 1 wherein the specific playback delay is introduced for a specific message in the sequence of protocol messages.

3. The method of claim 1 wherein the specific playback delay is introduced between a protocol state change in the device.

4. The method of claim 1 wherein the specific playback delay is introduced during a protocol state change in the device.

5. A method of testing an implementation of a routing protocol in a device, the method comprising:

generating a first message having a specified message size which is intentionally out-of-conformance with the routing protocol;

testing how the device reacts to the first message;

generating a second message having a repeated protocol field;

testing how the device reacts to the second message;

generating a third message absent a mandatory protocol field;

testing how the device reacts to the third message;

generating a fourth message having an incorrect order of protocol fields;

testing how the device reacts to the fourth message;

providing a first sequence of protocol messages;

introducing a specific playback delay between at least one pair of adjacent protocol messages in the first sequence of protocol messages;

testing how the device reacts to the first sequence of protocol messages with the specific playback delay;

providing a second sequence of protocol messages;

testing how the device reacts to a specific playback rate for the second sequence of protocol messages;

recording a third sequence of protocol messages exchanged between the device and a network node;

modifying an order of the protocol messages in the third sequence to form a test sequence of the protocol messages;

testing how the device reacts to the test sequence;

providing a plurality of sequences of protocol messages;

introducing a specific playback delay between adjacent sequences in the plurality of sequences of protocol messages; and

testing how the device reacts to the plurality of sequences with the specific playback delay.

6. A system for testing an implementation of a routing protocol in a device, the system comprising:

a playout manager to generate a sequence of protocol messages with a specific playback rate; and

a message capture component to test how the device reacts to the specific playback rate for the sequence of protocol messages;

wherein the specific playback rate is to cause a protocol state transition in the device which differs from an expected protocol state transition absent a specific playback delay.

7. The system of claim 6 wherein the specific playback rate is introduced between a protocol state change in the device.

8. The system of claim 6 wherein the specific playback rate is introduced during a protocol state change in the device.

9. A system for testing an implementation of a routing protocol in a device, the system comprising:

a message exchange recorder to record a sequence of protocol messages exchanged between the device and a network node;

an editor to modify an order of the protocol messages in the sequence to form a test sequence of the protocol messages;

a playout manager to generate the test sequence of the protocol messages; and

a message capture component to test how the device reacts to the test sequence.

10. A system for testing an implementation of a routing protocol in a device, the system comprising:

a first testing device which couples the device to a first network, the first testing device including:

a message exchange recorder to record a first sequence of protocol messages exchanged between the device and the first network;

a synchronization component; a

playout manager to generate a first test sequence of messages based on the first sequence, wherein the messages in the first test sequence are generated with a timing based on the synchronization component; and

a message capture component to test how the device reacts to the first test sequence;

a second testing device which couples the device to a second network, the second testing device including:

a message exchange recorder to record a second sequence of protocol messages exchanged between the device and the second network contemporaneously with the first sequence of protocol messages;

a synchronization component whose timing is influenced by the synchronization component of the first testing device;

a playout manager to generate a second test sequence of messages based on the second sequence, wherein the messages in the second test sequence are generated with a timing based on the synchronization component; and

a message capture component to test how the device reacts to the second test sequence.

11. The system of claim 10 wherein the first network and the second network are in communication, and wherein the first and second sequences of protocol messages are correlated.

12. The system of claim 10 wherein the first test sequence and the second test sequence are generated to non-coherently provide the recorded messages to the device.

13. The system of claim 10 wherein the first test sequence and the second test sequence are generated to provide conflicting messages to the device.

14. The system of claim 10 wherein the first test sequence and the second test sequence are generated to introduce an expected event to the device after an unexpected delay.

15. The system of claim 10 wherein the first test sequence and the second test sequence are generated to introduce incorrect topology information to the device.

16. A method of testing an implementation of a routing protocol in a device, the method comprising:

recording a first sequence of protocol messages exchanged between the device and a first network;

recording a second sequence of protocol messages exchanged between the device and a second network contemporaneously with the first sequence of protocol messages;

contemporaneously generating a first test sequence of messages based on the first sequence and a second test sequence of messages based on the second sequence; and

testing how the device reacts to the first test sequence and the second test sequence.

17. The method of claim 16 wherein the first network and the second network are in communication, and wherein the first and second sequences of protocol messages are correlated.

18. The method of claim 16 wherein the first test sequence and the second test sequence are generated to non-coherently provide the recorded messages to the device.

19. The method of claim 16 wherein the first test sequence and the second test sequence are generated to provide conflicting messages to the device.

20. The method of claim 16 wherein the first test sequence and the second test sequence are generated to introduce an expected event to the device after an unexpected delay.

21. The method of claim 16 wherein the first test sequence and the second test sequence are generated to introduce incorrect topology information to the device.