From d94bb99c50fbc85a6d83aee607fcfeef9d8a20e0 Mon Sep 17 00:00:00 2001
From: Timothy Flynn <trflynn89@pm.me>
Date: Sat, 15 Mar 2025 17:14:21 -0400
Subject: [PATCH] Documentation: Remove outdated comment on using the Qt UI for
 WPT

We now run the tests headlessly.
---
 Documentation/Testing.md | 15 ++++-----------
 1 file changed, 4 insertions(+), 11 deletions(-)

diff --git a/Documentation/Testing.md b/Documentation/Testing.md
index 83f53ee155a..9fc396d36b6 100644
--- a/Documentation/Testing.md
+++ b/Documentation/Testing.md
@@ -87,13 +87,6 @@ CTEST_OUTPUT_ON_FAILURE=1 LADYBIRD_SOURCE_DIR=${PWD}/../.. ninja test
 The Web Platform Tests can be run with the `WPT.sh` script. This script can also be used to compare the results of two
 test runs.
 
-Enabling the Qt chrome is recommended when running the Web Platform Tests on MacOS. This can be done by running the
-following command:
-
-```sh
-cmake -GNinja Build/release -DENABLE_QT=ON
-```
-
 Example usage:
 
 ```sh
@@ -123,16 +116,16 @@ That is, you give `./Meta/WPT.sh import` the path part of any `http://wpt.live/`
 
 ## Writing tests
 
-Running `Tests/LibWeb/add_libweb_test.py your-new-test-name test_type` will create a new test HTML file in 
+Running `Tests/LibWeb/add_libweb_test.py your-new-test-name test_type` will create a new test HTML file in
 `Tests/LibWeb/test_type(/input)` (`/input` is appended for Text and Layout tests) with the correct boilerplate
 code for a `test_type` test — along with a corresponding expectations file in the appropriate directory, e.g.,
 `Tests/LibWeb/Text/expected/your-new-test-name.txt`, for a Text test, or
 `Tests/LibWeb/Ref/reference/your-new-test-name.txt` for a Ref test. The accepted `test_types` are "Text",
 "Ref", "Screenshot", and "Layout".
 
-If you make a new Text or Layout test, after you update/replace the generated boilerplate in your 
-`your-new-test-name.html` test file with your actual test, running 
-`./Meta/ladybird.sh run headless-browser --run-tests "./Tests/LibWeb" --rebaseline -f Text/input/foobar.html` 
+If you make a new Text or Layout test, after you update/replace the generated boilerplate in your
+`your-new-test-name.html` test file with your actual test, running
+`./Meta/ladybird.sh run headless-browser --run-tests "./Tests/LibWeb" --rebaseline -f Text/input/foobar.html`
 will regenerate the corresponding expectations file to match the actual output from your updated test.
 
 If you add a new Ref or Screenshot test, you'll need to supply the equivalently rendering HTML manually.