e2e

E2E testing

This folder contains test suites to run e2e tests on live kargo instance.

Instance and other configurations can be configured in YAML files in the envs directory. See example dev.env and home_config.env

Tests can be run as go test <package_name> with access to kargo instance set up in envs.

To run tests using your home-directory kargo config, aquired with kargo login command:

go test <package_name> -args -env-file=home_config.yaml

Writing tests

This module is using sigs.k8s.io/e2e-framework to configure and run tests.

We recommend organizing each feature into its own package.

Each test package should configure the following TestMain:

package my_package_test

import "github.com/akuity/kargo/hack/test/e2e/utils"

func TestMain(m *testing.M) {
	utils.InitEnv(m)
}

Test feature

Test functions should configure e2e-framework features:

func TestMyFeature(t *testing.T) {
	feature := features.New("Example feature")
	feature.Setup(...)
	feature.Teardown(...)
	feature.Assess(...)

	utils.TestEnv.Test(t, feature.Feature())
}

It's possivle to create YAML fixtures for each test by placing them in the testdata folder in the test project and adding SetupKargoFixtures and TeardownKargoFixtures callbacks:

func TestMyFeature(t *testing.T) {
	feature := features.New("Example kargo promotion")
	
	feature.Setup(utils.RequireKargoCli)
	feature.Setup(utils.SetupKargoFixtures)
	feature.Teardown(utils.TeardownKargoFixtures)

	feature.Assess(...)

	utils.TestEnv.Test(t, feature.Feature())
}

Please see kargo_promotion_fail as an example for running promotions in a project.

Test environments

envs folder contains YAML files with configurations accessible to the tests, each go test run can be run with a particular environment. Environment configurations mainly used by the environment configuration functions in the envfuncs package.

Dependency modules

This folder contains the main e2e test module github.com/akuity/kargo/hack/test/e2e and a few helper packages, each in its own module: envs, envfuncs, funcsloader.

The purpose of that is to be able to override envs and funcsloader in dependent e2e test modules to provide different environment configuration and setup/teardown functions to test in more environments than this package provides.

We mostly use that in Kargo Enterprise.