mirrors/ladybird
1
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-12-05 01:10:24 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Documentation: Update Testing.md to reflect changes in CMake presets

Browse Source
This commit is contained in:
Philipp Dreher
2025-06-24 07:41:11 +00:00
committed by Sam Atkins
parent 93ae57114d
commit dcc9318042
Notes: github-actions[bot] 2025-07-04 15:30:37 +00:00 
Author: https://github.com/PhilKTurner
Commit: https://github.com/LadybirdBrowser/ladybird/commit/dcc93180428
Pull-request: https://github.com/LadybirdBrowser/ladybird/pull/5187
Reviewed-by: https://github.com/AtkinsSJ ✅
1 changed files with 11 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
Documentation/Testing.md
View File

@@ -16,27 +16,25 @@ The easiest way to run tests is to use the `ladybird.py` script. The LibWeb test
just the LibWeb tests with `Meta/ladybird.py test LibWeb`. The second way is to invoke the `test-web` test runner
directly with `Meta/ladybird.py run test-web`.
A third way is to invoke `ctest` directly. The simplest method is to use the `default` preset from `CMakePresets.json`:
A third way is to invoke `ctest` directly. The simplest method is to use the `Release` preset from `CMakePresets.json`:
```sh
cmake --preset default
cmake --build --preset default
ctest --preset default
cmake --preset Release
cmake --build --preset Release
ctest --preset Release
```
If you want to avoid building and running LibWeb tests, you can use a Lagom-only build.
```sh
cmake -GNinja -S Meta/Lagom -B Build/lagom
```
The tests can be run via ninja after doing a build. Note that `test-js` requires the `LADYBIRD_SOURCE_DIR` environment
variable to be set to the root of the ladybird source tree.
Note that some tests require the `LADYBIRD_SOURCE_DIR` environment variable to be set to the root of the ladybird source tree.
```sh
# /path/to/ladybird repository
export LADYBIRD_SOURCE_DIR=${PWD}
cd Build/lagom
```
The tests can be run via ninja after doing a build.
```sh
cd Build/release
ninja
ninja test
```