Skip to content

Steps

To test a newly added test or existing tests locally, follow the steps

  • Clone the repo
  • Build the certsuite binary

    make build
    
  • Create or edit config/certsuite_config.yml. For example, to deploy partner workloads in a custom namespace:

    targetNameSpaces:
      - name: mynamespace
    
  • Skip intrusive tests if you do not want scaling or pod-recreation checks

    ./certsuite run --intrusive=false
    
  • Set K8s config of the cluster where test pods are running

    export KUBECONFIG=<<mypath/.kube/config>>
    
  • Execute the test suite. For example, to run networking tests:

    ./certsuite run -l networking --config-file=config/certsuite_config.yml
    
  • List matching test cases without running them:

    ./certsuite info -t networking --list
    
  • Run unit tests and linters before opening a pull request:

    make test
    make lint
    

See Runtime environment variables and Test Configuration for more options.

Dependencies on other PR

If you have dependencies on other Pull Requests, you can add a comment like that:

Depends-On: <url of the PR>

and the dependent PR will automatically be extracted and injected in your change during the GitHub Action CI jobs and the DCI jobs.

Linters for the Codebase