test environment, SUT, DUT and TG specifics; - Used commonly across multiple L2 KWs; - Performance and functional tests: - L1 KWs (KeyWords) are implemented as RF libraries and Python libraries; - Performance TG L1 KWs: - All L1 KWs are implemented as Python libraries: - Support for TRex only today; - Performance data plane traffic profiles: - TG-specific stream profiles provide full control of: - Packet definition – layers, MACs, IPs, ports, combinations thereof e.g. IPs and UDP ports; - Stream definitions - different streams can run together, delayed, one after each other; - Stream profiles are independent of CSIT framework and can be used in any T-rex setup, can be sent anywhere to repeat tests with exactly the same setup; - Easily extensible – one can create a new stream profile that meets tests requirements; - Same stream profile can be used for different tests with the same traffic needs; - Functional data plane traffic scripts: - Scapy specific traffic scripts; 1. Level-2 libraries - Robot resource files - Higher level CSIT libraries abstracting required functions for executing tests; - L2 KWs are classified into the following functional categories: - Configuration, test, verification, state report; - Suite setup, suite teardown; - Test setup, test teardown; 1. Tests - Robot - Device tests using containerized environment with SR-IOV access to a NIC; - VPP; - Performance tests using physical testbed environment: - VPP; - DPDK-Testpmd; - DPDK-L3Fwd; - Tools: - Documentation generator; - Report generator; - Testbed environment setup ansible playbooks; - Operational debugging scripts; ## Directory Structure ### Tests ``` . └── tests    ├── dpdk    │   ├── dpdk_scripts # DPDK helper scripts    │   └── perf # DPDK performance tests    └── vpp    ├── device # VPP device tests    └── perf # VPP performance tests ``` ### Keywords ``` . resources └── libraries    ├── bash # Contains a dependency of KubernetesUtils   │   ├── config # Config for KubernetesUtils dependency    │   ├── entry # Main bootstrap entry directory    │   ├── function # Bootstrap function library    │   └── shell # Various functions for KubernetesUtils    ├── python # Python L1 KWs    └── robot # Robot Framework L2 KWs ``` ### Other Resources ``` . ├── docs # Main documentaion ├── PyPI # PyPI packages provided by CSIT │   ├── jumpavg │   └── MLRsearch ├── resources │   ├── templates # Templates (vpp_api_test, kubernetes, ...) │   ├── test_data # Robot Test configuration │   ├── tools │   │   ├── disk-image-builder # Utilities for building (DCR, VM) images │   │   ├── doc_gen # Code documentation generator │   │   ├── papi # PAPI driver │   │   ├── presentation # Report generator │   │   ├── scripts # Various tools │   │   ├── testbed-setup # Physical testbed setup scripts │   │   ├── topology # Helper scripts for topology manipulation │   │   ├── trex # TRex driver │   │   ├── vagrant # VPP device vagrant environment │   │   └── wrk # WRK driver │   ├── topology_schemas │   ├── traffic_profiles # Performance tests traffic profiles │   │   ├── trex │   │   └── wrk │   └── traffic_scripts # Functional tests traffic profiles │   ├── dhcp │   └── lisp └── topologies # Linux Foundation topology files ├── available └── enabled ``` ## Quickstart ### Vagrant [Vagrant environment preparation](docs/testing_in_vagrant.rst) documentaion is describing local VPP Device functional testing. ### Physical Testbed [Physical testbed preparation](resources/tools/testbed-setup/README.rst) documentation is describing PXE and Ansible setup process. All the software requirements for running Performance Teste are part of Ansible playbooks. ## Report [CSIT Report](https://docs.fd.io/csit/master/report/). ## Trending [CSIT Trending](https://docs.fd.io/csit/master/trending/). ## Code Documentation [CSIT Code Documentation](https://docs.fd.io/csit/master/doc/). ## Coding Guidelines If you are interested in contributing, please see the [coding guidelines](docs/test_code_guidelines.rst).