From 3d737693cb8895a6e25fef11c2db023007635ecb Mon Sep 17 00:00:00 2001 From: Tobias Schuhmacher Date: Fri, 26 Jan 2024 14:50:54 +0100 Subject: [PATCH] add execution table --- docs/contributor/testing-strategy.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/contributor/testing-strategy.md b/docs/contributor/testing-strategy.md index e0f445f8..2be31357 100644 --- a/docs/contributor/testing-strategy.md +++ b/docs/contributor/testing-strategy.md @@ -52,6 +52,12 @@ For each layer is a dedicated testing approach used: 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 Approach|Per Commit|Per PR|Per Release|In intervals| +|--|--|--|--|--| +|Unit Testing|X|X||Only long running tests daily| +|Integration Testing||X||Only long running tests daily| +|End-to-End Testing|||X|Daily| + ### Testing Tools and Frameworks Use the following tools and frameworks to implement the above-mentioned testing levels: