mirrors/ladybird
0
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-09-09 11:06:10 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 13

Documentation: Remove outdated comment on using the Qt UI for WPT

Browse source 
We now run the tests headlessly.
This commit is contained in:
Timothy Flynn 2025-03-15 17:14:21 -04:00 • committed by Tim Flynn
commit d94bb99c50
Notes: github-actions[bot] 2025-03-15 23:58:33 +00:00
1 changed files with 4 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

15
Documentation/Testing.md
View file

@ -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 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. 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: Example usage:
```sh ```sh
@ -123,16 +116,16 @@ That is, you give `./Meta/WPT.sh import` the path part of any `http://wpt.live/`
## Writing tests ## 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 `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., 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/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", `Tests/LibWeb/Ref/reference/your-new-test-name.txt` for a Ref test. The accepted `test_types` are "Text",
"Ref", "Screenshot", and "Layout". "Ref", "Screenshot", and "Layout".
If you make a new Text or Layout test, after you update/replace the generated boilerplate in your 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 `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` `./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. 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. If you add a new Ref or Screenshot test, you'll need to supply the equivalently rendering HTML manually.