From d848dd076272adee6659fe255be8d811142434ab Mon Sep 17 00:00:00 2001
From: Li Haoyi <haoyi.sg@gmail.com>
Date: Tue, 31 Dec 2024 22:55:25 +0800
Subject: [PATCH] .

---
 blog/modules/ROOT/pages/4-flaky-tests.adoc | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/blog/modules/ROOT/pages/4-flaky-tests.adoc b/blog/modules/ROOT/pages/4-flaky-tests.adoc
index b3ab913626b..8ce6a45f38e 100644
--- a/blog/modules/ROOT/pages/4-flaky-tests.adoc
+++ b/blog/modules/ROOT/pages/4-flaky-tests.adoc
@@ -214,6 +214,10 @@ unhelpful when you are dealing with flaky tests.
 
 ### Preventing Flaky Tests From Being Introduced Is Hard
 
+It can be tempting to try and "https://en.wikipedia.org/wiki/Shift-left_testing[Shift Left]"
+your flaky test management, to try and catch them before they end up landing in your codebase.
+But doing so ends up being surprisingly difficult.
+
 Consider the example we used earlier: 10,000 tests, with 1% of them flaky, each failing 1% of
 the time.