Testing

There are multiple ways to test Cilium functionality, including unit-testing and integration testing. In order to improve developer throughput, we provide ways to run both the unit and integration tests in your own workspace as opposed to being fully reliant on the Cilium CI infrastructure. We encourage all PRs to add unit tests and if necessary, integration tests. Consult the following pages to see how to run the variety of tests that have been written for Cilium, and information about Cilium’s CI infrastructure.

• CI / GitHub Actions
  • Triggering Smoke Tests
  • Triggering Platform Tests
  • Using GitHub Actions for testing
  • CI Failure Triage
• End-To-End Connectivity Testing
  • Introduction
  • Running End-To-End Connectivity Tests
• End-To-End Testing Framework (Legacy)
  • Introduction
  • Running End-To-End Tests
  • Test Reports
  • Best Practices for Writing Tests
  • Ginkgo Extensions
  • Debugging:
  • Running End-To-End Tests In Other Environments via kubeconfig
  • Running End-To-End Tests In Other Environments via SSH
  • VMs for Testing
  • VM images
  • Known Issues and Workarounds
  • Further Assistance
• Integration Testing
  • Prerequisites
  • Running all tests
  • Testing individual packages
  • Automatically run unit tests on code changes
  • Migrating tests off of gopkg.in/check.v1
• BPF Unit and Integration Testing
  • Running tests
  • Writing tests

The best way to get help if you get stuck is to ask a question on the Cilium Slack. With Cilium contributors across the globe, there is almost always someone available to help.