From 98389f30af4ea7af0f2b49dce869470ea2310b1f Mon Sep 17 00:00:00 2001 From: Hasan Turken Date: Mon, 28 Nov 2022 12:36:52 +0300 Subject: [PATCH] Minor fixes in uptest integration guide. Signed-off-by: Hasan Turken --- build | 2 +- docs/integrating-uptest-for-e2e-testing.md | 13 +++++++++---- 2 files changed, 10 insertions(+), 5 deletions(-) diff --git a/build b/build index 2d1bdbe..207d7d1 160000 --- a/build +++ b/build @@ -1 +1 @@ -Subproject commit 2d1bdbe92eb98b78a5bf78543f26b9a7fe9f7f1b +Subproject commit 207d7d194db6a24862e0c8c6279a9ed5388541e7 diff --git a/docs/integrating-uptest-for-e2e-testing.md b/docs/integrating-uptest-for-e2e-testing.md index fc1b60e..4e10f03 100644 --- a/docs/integrating-uptest-for-e2e-testing.md +++ b/docs/integrating-uptest-for-e2e-testing.md @@ -1,8 +1,8 @@ # Integrating Uptest for End to End Testing In this tutorial, we will integrate [uptest](https://github.com/upbound/uptest) to a Github repository to automate end to end -testing managed resources. While we will use a `Provider` repository as an example, the process will be identical for a -`Configuration` repository. +testing managed resources. While we will use a `Provider` repository as an example, the process will be almost identical +for a `Configuration` repository. Starting with a provider repository with no end to end testing capability, we will end up having: - A make target to locally test examples end to end @@ -27,7 +27,7 @@ Starting with a provider repository with no end to end testing capability, we wi touch cluster/test/setup.sh chmod +x cluster/test/setup.sh - cat < cluster/test/setup.sh + cat < cluster/test/setup.sh #!/usr/bin/env bash set -aeuo pipefail @@ -55,7 +55,8 @@ Starting with a provider repository with no end to end testing capability, we wi name: provider-secret namespace: upbound-system key: credentials - EOF + EOF + EOF0 ``` 5. Now, please add the following lines to your Makefile which which will add `uptest` and `e2e` targets: @@ -75,6 +76,10 @@ Starting with a provider repository with no end to end testing capability, we wi e2e: build controlplane.up local.xpkg.deploy.provider.$(PROJECT_NAME) uptest ``` + > Note: If you're following this tutorial for a `Configuration` repository, you will need to add + > `local.xpkg.deploy.configuration.$(PROJECT_NAME)` instead of `local.xpkg.deploy.provider.$(PROJECT_NAME)` to the + > `e2e` target. + 6. Commit the changes we did so far. ```bash