The repository contains a set of test cases that run different test scenarios from cnf-certification-test project and verifies if these scenarios behave correctly under different environment conditions.

The cnfcert-tests-verification project is based on golang+ginkgo framework.

cnfcert-tests-verification project triggers the same test scenario from cnf-certification-test several times using different pre-configured OCP environment.

Once the triggered scenario is completed, the test case processes the report and verifies that the scenario is completed with the excepted result: skip/fail/pass.

The tests are run on the OCP cluster with certain requirements that are listed below.

Bare-minimum requirements consists of a OCP cluster with 3 nodes where 2 are cnf-worker nodes and 1 worker node.

The following test features are can run selectively or altogether.

• accesscontrol
• affiliatedcertification
• lifecycle
• networking
• observability
• platformalteration
• performance
• operator
• preflight

Choose the variant that suits you best:

make test-features - will only run tests for the features that were defined in the FEATURES environment variable make test-all - will run the test suite for all features

The following environment variables are used to configure the test setup.

Make sure docker or podman is running on the local machine. You could consider using Colima - container runtime on macOS (and Linux) with minimal setup.

git clone https://github.com/test-network-function/cnfcert-tests-verification.git
cd cnfcert-tests-verification

make install

• testconfig.yaml inside the config directory stores the local environment related information. Update tnf_config_dir and tnf_report_dir, and docker_config_dir as specific to your local workspace.

Optionally, update tnf_image, test_image, and tnf_image_tag as per needs.

# Sample configurations snippet
general:
  tnf_config_dir: "/Users/bmandal/rhdev/github.com/cnfcert-tests-verification/tnf_config"
  tnf_report_dir: "/Users/bmandal/rhdev/github.com/cnfcert-tests-verification/tnf_report"
  tnf_image: "quay.io/testnetworkfunction/cnf-certification-test"
  tnf_image_tag: "unstable"
  docker_config_dir: "/tmp"

• To use this test config file, you need to set LOCAL_TESTING environment variable while running the test.

Mac Users : Set NON_LINUX_ENV= to signal the repo code that the suite is run against the non Linux local env.

• To run all tests

# Mac User
TNF_REPO_PATH=/path/to/repo/cnf-certification-test  KUBECONFIG=/path/to/kubeconfig LOCAL_TESTING= NON_LINUX_ENV= make test-all
# Linux User
TNF_REPO_PATH=/path/to/repo/cnf-certification-test  KUBECONFIG=/path/to/kubeconfig LOCAL_TESTING= make test-all

• To run a specific feature

# Mac User
FEATURES=platformalteration TNF_REPO_PATH=/path/to/repo/cnf-certification-test  KUBECONFIG=/path/to/kubeconfig LOCAL_TESTING= NON_LINUX_ENV= make test-features
# Linux User
FEATURES=platformalteration TNF_REPO_PATH=/path/to/repo/cnf-certification-test  KUBECONFIG=/path/to/kubeconfig LOCAL_TESTING= make test-features

• To debug

Use DEBUG_TNF=true and TNF_LOG_LEVEL=trace while running the above commands. This would create a Debug folder containing suites folders with TNF logs for each of the tests.

# Mac User
FEATURES=platformalteration TNF_LOG_LEVEL=trace DEBUG_TNF=true TNF_REPO_PATH=/path/to/repo/cnf-certification-test  KUBECONFIG=/path/to/kubeconfig LOCAL_TESTING= NON_LINUX_ENV= make test-features
# Linux User
FEATURES=platformalteration TNF_LOG_LEVEL=trace DEBUG_TNF=true TNF_REPO_PATH=/path/to/repo/cnf-certification-test  KUBECONFIG=/path/to/kubeconfig LOCAL_TESTING= make test-features

Fork the repo, create a new branch and create a PR with your changes.

CNF Certification Test Partner is copyright Red Hat, Inc. and available under an Apache 2 license.