-------------------------
CSIT Honeycomb functional tests are executed on virtualized topologies created
-using Virtual Internet Routing Lab (VIRL) simulation platform contributed by
-Cisco. VIRL runs on physical baremetal servers hosted by LF FD.io project. All
-tests are executed in two node logical test topology - Traffic Generator (TG)
-node and Systems Under Test (SUT1) node connected in a loop. Logical test
-topology is shown in the figure below.
-
-::
+using :abbr:`VIRL (Virtual Internet Routing Lab)` simulation platform
+contributed by Cisco. VIRL runs on physical baremetal servers hosted by LF FD.io
+project. All tests are executed in two node logical test topology - Traffic
+Generator (TG) node and Systems Under Test (SUT1) node connected in a loop.
+Logical test topology is shown in the figure below.::
+------------------------+
| |
Functional Tests Coverage
-------------------------
-The following Honeycomb functional test areas are included in the CSIT |release|
+The following Honeycomb functional test areas are included in the |csit-release|
with results listed in this report:
- **Basic interface management** - CRUD for interface state,
- ipv4/ipv6 address, ipv4 neighbor, MTU value.
- - Test case count: 7
+ - Test case count: 14
- **L2BD** - CRUD for L2 Bridge-Domain, interface assignment.
- Create up to two bridge domains with all implemented functions turned on.
- (flooding, unknown-unicast flooding, forwarding, learning, arp-termination)
- Toggle interface state separately for super-interface and sub-interface.
- Configure IP address and bridge domain assignment on sub-interface.
- Configure VLAN tag rewrite on sub-interface.
- - Test case count: 17
+ - Test case count: 24
- **ACL** - CRD for low-level classifiers: table and session management,
- interface assignment.
- Configure up to 2 classify tables.
- Test case count: 9
- **PBB** - CRD for provider backbone bridge sub-interface.
- Configure, modify and remove a PBB sub-interface over a physical interface.
- - Test case count: 9
+ - Test case count: 8
- **NSH_SFC** - CRD for NSH maps and entries, using NSH_SFC plugin.
- Configure up to 2 NSH entries.
- Configure up to 2 NSH maps.
- Configure and delete Lisp mapping as local and remote.
- Configure and delete Lisp adjacency mapping
- Configure and delete Lisp map resolver, proxy ITR.
- - Test case count: 11
+ - Test case count: 18
+- **LISP GPE** - CRUD for LISP GPE mappings.
+ - Toggle Lisp GPE feature status.
+ - Configure Lisp GPE mappings.
+ - Traffic test verifying encapsulation.
+ - Test case count: 12
- **NAT** - CRD for NAT entries, interface assignment.
- Configure and delete up to two NAT entries.
- Assign NAT entries to a physical interface.
- Configure SPAN port mirroring on a physical interface, mirroring
- up to 2 interfaces.
- Remove SPAN configuration from interfaces.
- - Test case count: 3
+ - Test case count: 14
- **ACL-PLUGIN** - CRD for high-level classifier
- MAC + IP address classification.
- IPv4, IPv6 address classification.
- Configure blackhole route.
- IPv4 and IPv6 variants.
- Test case count: 6
+- **Policer** - CRD for traffic policing feature.
+ - Configure Policing rules.
+ - Assign to interface.
+ - Test case count: 6
+- **Border Gateway Protocol** - CRUD and functional tests for BGP.
+ - Configure peers and routes
+ - Check interactions with another BGP peer.
+ - Test case count: 13
- **Honeycomb Infractructure** - configuration persistence,
- Netconf notifications for interface events,
- Netconf negative tests aimed at specific issues
+ - Netconf/Restconf northbound over IPv6
+ - Test case count: 12
-Total 158 Honeycomb tests in the CSIT |release|.
+Total 219 Honeycomb functional tests in the |csit-release|.
Operational data in Honeycomb should mirror configuration data at all times.
Because of this, test cases follow this general pattern:
#. modify configuration of the feature using restconf.
#. verify changes to operational data using restconf.
#. verify changes using VPP API dump, OR
-#. send a packet to VPP node and observe behaviour to verify configuration
+#. send a packet to VPP node and observe behaviour to verify configuration.
Test cases involving network interfaces utilize the first two interfaces on
the DUT node.
Functional Tests Naming
-----------------------
-CSIT |release| introduced a common structured naming convention for all
+CSIT-17.01 introduced a common structured naming convention for all
performance and functional tests. This change was driven by substantially
growing number and type of CSIT test cases. Firstly, the original practice did
not always follow any strict naming convention. Secondly test names did not
#. **Physical port to physical port - a.k.a. NIC-to-NIC, Phy-to-Phy, P2P**
- - *eth2p-ethip4-ip4base-func.robot* => 2 ports of Ethernet, IPv4 baseline
- routed forwarding, functional tests.
+ - *eth2p-ethip4-ip4base-func.robot* => 2 ports of Ethernet, IPv4 baseline
+ routed forwarding, functional tests.
#. **Physical port to VM (or VM chain) to physical port - a.k.a. NIC2VM2NIC,
P2V2P, NIC2VMchain2NIC, P2V2V2P**
- - *eth2p-ethip4vxlan-l2bdbasemaclrn-eth-2vhost-1vm-func.robot* => 2 ports of
- Ethernet, IPv4 VXLAN Ethernet, L2 bridge-domain switching to/from two vhost
- interfaces and one VM, functional tests.
+ - *eth2p-ethip4vxlan-l2bdbasemaclrn-eth-2vhost-1vm-func.robot* => 2 ports of
+ Ethernet, IPv4 VXLAN Ethernet, L2 bridge-domain switching to/from two vhost
+ interfaces and one VM, functional tests.
Code Review / csit.git / blobdiff