From 59fdae61bd39cfed854232929bf4d4dc8e039e16 Mon Sep 17 00:00:00 2001 From: Tobias Schuhmacher Date: Fri, 26 Jan 2024 14:41:10 +0100 Subject: [PATCH] extend E2E test description --- docs/contributor/testing-strategy.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/contributor/testing-strategy.md b/docs/contributor/testing-strategy.md index 41c0fc78..c977fe0e 100644 --- a/docs/contributor/testing-strategy.md +++ b/docs/contributor/testing-strategy.md @@ -47,7 +47,8 @@ For each layer is a dedicated testing approach used: ### End-to-End Testing 1. Use Helm to create, deploy, and manage test clusters and environments that closely resemble the productive execution context. -2. Run regularly, but at least once per release, a performance test that measures product KPIs to indicate KPI violations or performance differences between release candidates. +2. For shot living Kubernetes clusters, use K3d or other lightweight Kubernetes cluster providers. +3. Run regularly, but at least once per release, a performance test that measures product KPIs to indicate KPI violations or performance differences between release candidates. ### Testing Tools and Frameworks Use the following tools and frameworks to implement the above-mentioned testing levels: