upgrade_test

README

Test Upgrading a Zarf package and Zarf itself

Note: For this test case, we first deploy the podinfo package (from this directory) with version 6.3.3, then build a 6.3.4 package. This package is then deployed to an upgraded cluster with the new zarf version and the new zarf version builds and deploys a 6.3.5 version.

This directory holds the tests that verify Zarf can perform these upgrade actions and that any deploy deprecations work as expected.

Running Tests Locally

Dependencies

Running the tests locally have the same prerequisites as running and building Zarf:

1. GoLang >= 1.19.x
2. Make
3. Access to a cluster to test against
4. The zarf.yaml created and deployed with PODINFO_VERSION 6.3.3
5. The zarf.yaml created with PODINFO_VERSION 6.3.4

Actually Running The Test

Here are a few different ways to run the tests, based on your specific situation:

# The default way, from the root directory of the repo. This will automatically build any Zarf related resources if they don't already exist (i.e. binary, init-package, example packages):
make test-upgrade

# If you are in the root folder of the repository and already have everything built (i.e., the binary, the init-package and the flux-test example package):
go test ./src/test/upgrade-test/...

Documentation

Overview

Package upgrade_test provides a test for the upgrade flow.