-
Notifications
You must be signed in to change notification settings - Fork 140
BetaReleaseRegressionTests
Adam edited this page Jan 15, 2013
·
11 revisions
'''Regression Tests'''
This page describes how each feature was tested. This document identifies the test number, notes the test developer that wrote each test, describes the test in detail, identifies the location in the automated regression suite that calls the test, lists any known bugs with the test, and provides the date when the task was completed.
All of the following tests should be conducted under CentOS 4.4. All tests should be tested on kernel versions XXX with both non-SMP and SMP versions.
- Owner :
- Description :
- Location :
- Regression suite :
- Known bugs/issues :
- Status
- Target Release :
- Due date :
- Owner :
- Description :
nf2.ko should be installed in /lib/modules/`uname -r`/kernel/drivers/nf2.ko
- Location :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
Test using ls /sys/class/net and searching for nf2c
Test using ifconfig -a and searching for nf2c
- Prerequisites :
- Location :
- Regression suite :
- Release :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
Note: Driver loading on boot uses modprobe. A success for test " nf2c[0-3] interfaces present in system with one NetFPGA card " implies success for this test.
- Invocation :
- Output :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
On a system with at least 1 NetFPGA card and the driver installed, run:
ifconfig nf2c0
One of the lines should display the MTU. The MTU should state 1500 bytes. Example:
UP BROADCAST RUNNING MULTICAST <b>MTU:1500</b> Metric:1
- Location :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
reference_router/regress/test_interface
- Output :
Testing IP assignment to nf2c0...Success Testing IP assignment to nf2c1...Success Testing IP assignment to nf2c2...Success Testing IP assignment to nf2c3...Success
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Invocation :
cd ${NF2_ROOT}/projects/reference_nic/regress/test_loopback_random
./run
- Output :
Test PASSES.
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Invocation :
cd ${NF2_ROOT}/projects/reference_nic/regress/test_loopback_maxsize
./run
- Output :
Test PASSES.
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Invocation :
cd ${NF2_ROOT}/projects/reference_nic/regress/test_loopback_minsize
./run
- Output :
Test PASSES.
- Regression suite :
- Known bugs/issues :
- Due date :
Test 2.1.4: Tx/Rx Random Length Packets and with bad CRCs Check Tx/Rx Counters and Drop Counters Using PHY Loopback
- Owner :
- Description :
Send packets 10000 random length (60-1514 w/o CRC) packets from software out to the device with the PHY set in external loopback back mode and the MAC set to not generate the CRC. Check that the packet/byte Tx/Rx counters are correct and that all these packets were dropped.
Reenable CRC generation and send packets 10000 random length (60-1514 w/o CRC) packets from software out to the device with the PHY set in external loopback back mode. Check that the packet/byte Tx/Rx counters are correct and that none of these packets were dropped.
- Prerequisites :
- Invocation :
cd ${NF2_ROOT}/projects/reference_nic/regress/test_loopback_crc
./run
- Output :
Test PASSES.
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Set PHY to loopback via MDIO
- Disable output queues
- Send in 10,000 maximum sized packets (1514 bytes) equally distributed between all four ports. This should be sufficient to fill up all SRAM queues. (1,514 * 10,000 = 15,140,000 bytes = 15 MB approx).
- Read byte counters and verify:
- Number of bytes received is correct
- Number of bytes arriving at SRAM output queues is identical to bytes exiting Ethernet MAC queues
- Number of bytes dropped + number of bytes stored = number of bytes sent
- Verify that packets can still be sent/received through NetFPGA interfaces
- Location :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Invocation :
cd ${NF2_ROOT}/projects/reference_nic/regress/test_interface
./run
- Output :
Testing IP assignment to nf2c0...Success Testing IP assignment to nf2c1...Success Testing IP assignment to nf2c2...Success Testing IP assignment to nf2c3...Success
- Regression suite : Yes
- Target : Alpha
- Known bugs/issues :
- Due date : Complete
- Owner :
- Description :
- Connect nf2c0 to eth1 and nf2c1 to eth2
- put the PHY for ports 2 and 3 in internal loopback mode
- Send 10000 packets of random lengths out of the nf2cX interfaces
- Check that all packets were received at eth1/2 for packets sent out of nf2c0/1
- Check that all packets were received at nf2c2/3 for packets sent out of nf2c2/3 (due to loopback and LPM miss)
- Check that the Tx MAC counters show 10000 packets sent on each port
- Check that the Tx MAC counters show the correct number of bytes sent on each port
- Check that output port lookup counters show 40000 packets sent from the CPU
- Prerequisites :
- Location :
- Output :
Test PASSES
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Initialize netfpga hardware
- Send 300 packet with wrong DA with random size from external ethernet port to router port
- Get the drop counter for the router port.
- Check that drop counter is 300.
- Repeat test for other router port.
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Initialize netfpga hardware
- Send 300 packet with EtherType= 0x802 with random size from external ethernet port to router port
- Get the drop counter for the router port.
- Check that packet are forwarded to CPU
- Check that drop counter is 300.
- Repeat test for other router port.
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Initialize netfpga hardware
- Send 300 packet with IP_Version = 0x5 with random size from external ethernet port to router port
- Check that packet are forwarded to CPU
- Get the drop counter for the router port.
- Check that drop counter is 300.
- Repeat test for other router port.
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Initialize netfpga hardware
- Send 300 packet with TTL = 0x0 with random size from external ethernet port to router port
- Check that packet are forwarded to CPU
- Get the drop counter for the router port.
- Check that drop counter is 300.
- Repeat test for other router port.
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Initialize netfpga hardware
- Send 300 packet with bad ip checksum with random size from external ethernet port to router port
- Get the drop counter for the router port.
- Check that drop counter is 300.
- Repeat test for other router port.
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner : Surender
- Description :
- Prerequisites :
- Location :
- Output :
SUCCESS
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Location :
- Output :
SUCCESS!
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Set PHY to loopback via MDIO
- Disable output queues
- Send in 1000 maximum sized packets (1514 bytes) equally distributed between all four ports. This should be sufficient to fill up all SRAM queues. (1,514 * 1000 = 1,514,000 bytes = 1.5 MB approx. Each queue is 512 KB).
- Read byte counters and verify:
- Number of bytes received is correct
- Number of bytes arriving at SRAM output queues is identical to bytes exiting Ethernet MAC queues
- Number of bytes dropped + number of bytes stored = number of bytes sent
- Verify that packets can still be sent/received through NetFPGA interfaces
- Location :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner : Jad
- Description :
- Set the maximum number of packets in the output queues to 10
- Disable servicing the output queues
- Send 10 packets that should be forwarded out of each port
- Check the counters to verify that there are 10 packets in each output queue
- Send 10 more packets to each output queue
- Enable the output queues to receive the first 10 packets sent
- Check the counters to verify that 10 packets were dropped at each output queue
- Reset the output queues limits to 0xffffffff
- Prerequisites :
- Location :
- Output :
Test PASSES
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Insert 192.168.4.1, 192.168.5.1, and 143.123.123.123 into the IP Destination Address Filter table
- Send 10 packets to each of these IP addresses on each port.
- Check that the packets are received by the CPU from each port
- Remove 192.168.4.1 from the table, and add it in the routing table and the ARP table.
- Repeat step 2, and check that the packets destined to 192.168.4.1 are forwarded.
- Prerequisites :
- Location :
- Output :
Test PASSES
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Clear the ARP table and the Routing Table
- Set nf2c2 and nf2c3 PHYs in the loopback mode
- Clear all four CPU Output Queues' dropped packet counter and dequeued packet counter
- Set all four CPU Output Queue sizes to 12KB each. Disable CPU Output Queue dequeuing service
- Generate 9 packets for each interface of eth1, eth2, nf2c2, nf2c3. Every packet is of size (1024-8)=1016 bytes. Send these packets out of the interfaces eth1, eth2, nf2c2, nf2c3
- Check each CPU Output Queue stored packet counter is 8 packet and the dropped packet counter is 1
- Then enable all four CPU Output Queue dequeuing service, check each CPU Output Queue dequeued packet counter is 8, and the first 8 packets sent out at eth1, eth2, nf2c2, nf2c3 match the 8 packets which the driver receives from the CPU Output Queues for nf2c0, nf2c1, nf2c2, nf2c3
- Prerequisites :
- Location :
- Output :
Test PASSES
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Clear the ARP table and the Routing Table
- Set nf2c2 and nf2c3 PHYs in the loopback mode
- Clear all four MAC Output Queues' dropped packet counter and dequeued packet counter
- Set all four MAC Output Queue sizes to 8KB each. Disable MAC Output Queue dequeuing service
- Generate 5 packets for each interface of nf2c0, nf2c1, nf2c2, nf2c3. Every packet is of size (1024-8)=1016 bytes. Make the driver send these packets out of the interfaces nf2c0, nf2c1, nf2c2, nf2c3
- Check each MAC Output Queue stored packet counter is 4 packet and the dropped packet counter is 1
- Then enable all four MAC Output Queue dequeuing service, check each MAC Output Queue dequeued packet counter is 4, and the first 4 packets the driver sent out at nf2c0, nf2c1, nf2c2, nf2c3 match the 4 packets which the driver receives from eth1, eth2 and CPU Output Queues for nf2c2, nf2c3
- Prerequisites :
- Location :
- Output :
Test PASSES
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Clear the ARP table and the routing Table
- Set all ports to loopback mode
- Clear all MAC counters
- Set ARP table and routing table to loop packets within an interface, until TTL goes to zero
- Send 128B packets for up to (timeout) seconds, attempting to load each queue to 75% full
- Send packets, attempting to maintain each queue at 75% full
- Wait for packets to finish looping
- Print statistics for each interface
- Reset PHY
- Prerequisites :
- Location :
- Output :
Test PASSES
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Clear the ARP table and the routing Table
- Set all ports to loopback mode
- Clear all MAC counters
- Set ARP table and routing table to loop packets within an interface, until TTL goes to zero
- Send 512B packets for up to (timeout) seconds, attempting to load each queue to 75% full
- Send packets, attempting to maintain each queue at 75% full
- Wait for packets to finish looping
- Print statistics for each interface
- Reset PHY
- Prerequisites :
- Location :
- Output :
Test PASSES
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Clear the ARP table and the routing Table
- Set all ports to loopback mode
- Clear all MAC counters
- Set ARP table and routing table to loop packets within an interface, until TTL goes to zero
- Send 1496B packets for up to (timeout) seconds, attempting to load each queue to 75% full
- Send packets, attempting to maintain each queue at 75% full
- Wait for packets to finish looping
- Print statistics for each interface
- Reset PHY
- Prerequisites :
- Location :
- Output :
Test PASSES
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Pseudocode
- Location :
- Output :
- Regression suite :
- Target :
- Test issues :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Completed
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Owner :
- Description :
- Pseudocode
- Location :
- Output :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Commands to Enter
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Location :
- Regression suite :
- Target :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Location :
- Output :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Location :
- Output :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Location :
- Output :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Location :
- Output :
- Regression suite :
- Known bugs/issues :
- Due date :
- Owner :
- Description :
- Prerequisites :
- Location :
- Output :
- Regression suite :
- Known bugs/issues :
- Due date :