test/

Running the Nephe tests

Nephe test suite

We run 2 different categories of tests. The table below shows the different categories of tests and indicates how to run them locally:

Unit Test

Unit tests are placed under same directories with the implementations. The test package name is PACKAGE_test. For instance, the unit test files xxx_test.go under pkg/cloud-provider have the package name of cloudprovider_test. Unit tests uses go mock to generate mock packages. To generate mock code for a package, the package must implement interfaces, and add package/interfaces to mockgen.

To generate mock:

make mock

To run unit tests:

make unit-test

Integration Test

The test/integration directory contains all the integration tests. It uses Ginkgo as the underlying framework. The integration tests can be run on a kind cluster or on a AKS/EKS cluster. The keywords focusAws, focusAzure and focusCloud are used in descriptions on any level of a test spec, to indicate if this test spec should be run in zero or more test suites.

Dependencies

1. Install ginkgo v2.9.5.

   go install github.com/onsi/ginkgo/v2@v2.9.5
   export PATH=$PATH:$(go env GOPATH)/bin
   

2. Download the below docker images.

   docker pull kennethreitz/httpbin
   docker pull byrnedo/alpine-curl
   

3. Create a Kind cluster

   ci/kind/kind-setup.sh create kind
   

Running AWS Integration Test

Set the following variables to allow terraform scripts to create a compute VPC with 3 VMs.

export AWS_ACCESS_KEY_ID=<YOUR_AWS_KEY>
export AWS_SECRET_ACCESS_KEY=<YOUR_AWS_KEY_SECRET>
export AWS_DEFAULT_REGION=<YOUR_AWS_REGION>
export TF_VAR_aws_key_pair_name=<YOU_AWS_KEY_PAIR>
export TF_VAR_owner=<YOUR_NAME>

To run integration test,

make integration-test-aws

Running Azure Integration Test

Set the following variables to allow terraform scripts to create a compute VNET with 3 VMs.

export TF_VAR_azure_client_id=<YOUR_AZURE_CLIENT_ID>
export TF_VAR_azure_client_subscription_id=<YOUR_AZURE_CLIENT_SUBSCRIPTION_ID>
export TF_VAR_azure_client_secret=<YOUR_AZURE_CLIENT_SECRET>
export TF_VAR_azure_client_tenant_id=<YOUR_AZURE_TENANT_ID>

To run integration test:

make integration-test-azure

Running Integration Test on an existing Kind cluster

make
kind load docker-image antrea/nephe:latest
make integration-test-aws
make integration-test-azure

Running Integration Test on Cloud cluster

• Deploy Nephe on an EKS cluster using the EKS installation guide.

  • Run integration tests on EKS cluster.

    ci/bin/integration.test -ginkgo.v -ginkgo.focus=".*test-cloud-cluster.*" -kubeconfig=$HOME/tmp/terraform-eks/kubeconfig -cloud-provider=AWS -cloud-cluster
    

    Note: If you want to run the test using AWS IAM role, set the variable.

    export TF_VAR_nephe_controller_role_arn=<YOUR_IAM_ROLE>
    

  • Run integration tests with agented VMs on EKS cluster.

    ci/bin/integration.test -ginkgo.v -ginkgo.focus=".*test-with-agent.*" -kubeconfig=$HOME/tmp/terraform-eks/kubeconfig -cloud-provider=AWS -cloud-cluster -with-agent=true
    

• Deploy Nephe on an AKS cluster using the AKS installation guide.

  • Run integration tests on AKS cluster.

    ci/bin/integration.test -ginkgo.v -ginkgo.focus=".*test-cloud-cluster.*" -kubeconfig=$HOME/tmp/terraform-aks/kubeconfig -cloud-provider=Azure -cloud-cluster
    

  • Run integration tests with agented VMs on AKS cluster.

    ci/bin/integration.test -ginkgo.v -ginkgo.focus=".*test-with-agent.*" -kubeconfig=$HOME/tmp/terraform-aks/kubeconfig -cloud-provider=Azure -cloud-cluster -with-agent=true
    

Note: If Cloud cluster is not created using nephe terraform scripts, then update the -kubeconfig argument with your kubeconfig file.