From 32d71d52b7f1ecd5bf3cbd1cdf6c61ec4c6f1bab Mon Sep 17 00:00:00 2001
From: uNetworkingAB <110806833+uNetworkingAB@users.noreply.github.com>
Date: Tue, 1 Nov 2022 05:59:16 +0100
Subject: [PATCH] Update README.md

---
 tests/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tests/README.md b/tests/README.md
index f4d4c93..d4f7120 100644
--- a/tests/README.md
+++ b/tests/README.md
@@ -1,10 +1,10 @@
 # Testing
-A serious project needs extensive testing. If this folder looks empty to you, or lacking - mind you this is only the unit tests (which are a growing number).
+This folder holds some unit tests and a smoke test. These are run by GitHub Actions on every push. There are more tests in fuzzing, benchmarks folders and elsewhere.
 
 * We test with 500+ **standards conformance tests** known as the Autobahn|Testsuite where we get a full perfect score.
 * In the fuzzing folder you will find extensive **security fuzz testing** under AddressSanitizer, MemoySanitizer, UndefinedBehaviorSanitizer executed by Google on a daily basis.
 * In benchmarks folder you can find **performance testing** - we've done extensive performance testing of every commit since before we even had a single line of code.
-* We are working on a set of **integration smoke tests** for testing basic features against real-world web browsers (some browsers don't fully follow standards but we still want to play along).
+* A set of **integration smoke tests** for testing basic features against real-world "web browsers" (Deno, Node.js and Bun are the "web browsers").
 * And of course in this folder you can find the very **module unit tests** that check individual modules.
 * Customers and users indirectly feed us with **real world, high scale production testing**.
 * Semmle perform **static code analysis** and security testing for us, where we get the perfect A+ score.