From 7d2142be0a3c499c489588cce8ecf3bfc98f4859 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Thu, 26 Sep 2024 04:40:15 -0400
Subject: [PATCH] Connect maximum size with Updating reference images (#5022)

---
 tests/README.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/tests/README.md b/tests/README.md
index e7713eed3..d21784b61 100644
--- a/tests/README.md
+++ b/tests/README.md
@@ -87,6 +87,8 @@ There are, broadly speaking, three kinds of tests:
 
   To prevent bloat, it is important that the test images are kept as small as
   possible. To that effect, the test runner enforces a maximum size of 20 KiB.
+  If you're updating a test and hit `reference image size exceeds`, see
+  Updating reference images.
   If truly necessary, this limit can however be lifted by adding `// LARGE` as
   the first line of a test.
 
@@ -102,6 +104,9 @@ flag:
 testit --exact my-test-name --update
 ```
 
+This will generally generate compressed reference images (to remain within the
+above size limit).
+
 If you use the VS Code test helper extension (see the `tools` folder), you can
 alternatively use the save button to update the reference image.