argo-cd/test
2019-04-04 08:30:35 -07:00
..
e2e Issue #1012 - kubectl v1.13 fails to convert extensions/NetworkPolicy (#1360) 2019-04-04 08:30:35 -07:00
manifests Issue #1135 - Run e2e tests in throw-away kubernetes cluster (#1318) 2019-03-24 07:35:57 -07:00
manifests_test.go Enables default lint checks, fixes lint and bugs (#1330) 2019-03-28 13:37:53 -07:00
README.md Issue #1135 - Run e2e tests in throw-away kubernetes cluster (#1318) 2019-03-24 07:35:57 -07:00
testdata.go Refactor packr box usage into new assets library. Add faster DEV_IMAGE build (#1073) 2019-02-01 13:12:52 -08:00
testutil.go Switch to k8s recommended app.kubernetes.io/instance label (#857) 2018-11-30 23:54:01 -08:00

E2E tests

The directory contains E2E tests and test applications. Tests assume that Argo CD services are installed into argocd-e2e namespace or cluster in current context. One throw-away namespace argocd-e2e*** is created prior to tests execute. The throw-away namespace is used as a target namespace for test applications.

The test/e2e/testdata directory contains various Argo CD applications. Before test execution directory is copies into /tmp/argocd-e2e*** temp directory and used in tests as a git repository via file url: file:///tmp/argocd-e2e***.

Use the following steps to run tests locally:

  1. (Do it once) Create namespace argocd-e2e and apply base manifests: kubectl create ns -n argocd-e2e && kustomize build test/manifests/base | kubectl apply -n argocd-e2e -f -
  2. Change kubectl context namespace to argocd-e2e and start services using goreman start
  3. Keep Argo CD services running and run tests using make test-e2e

The tests are executed by Argo Workflow defined at .argo-ci/ci.yaml. CI job The build argo cd image, deploy argo cd components into throw-away kubernetes cluster provisioned using k3s and run e2e tests against it.