RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-07-27 11:37:34 +00:00
Code Issues Activity Actions

Everywhere: Move tests to /home/anon/Tests

Browse source
This commit is contained in:
Brian Gianforcaro 2022-03-20 11:55:50 -07:00 • committed by Andreas Kling
parent 16bee0ba79
commit 95b295971d
4 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

6
Documentation/RunningTests.md
View file

@ -69,7 +69,7 @@ Tests built for the SerenityOS target get installed either into `/usr/Tests` or
some system tests are installed into `/bin` for historical reasons.
The easiest way to run all of the known tests in the system is to use the `run-tests-and-shutdown.sh` script that gets
installed into `/home/anon/tests`. When running in CI, the environment variable `$DO_SHUTDOWN_AFTER_TESTS` is set, which
installed into `/home/anon/Tests`. When running in CI, the environment variable `$DO_SHUTDOWN_AFTER_TESTS` is set, which
will run `shutdown -n` after running all the tests.
For completeness, a basic on-target test run will need the SerenityOS image built and run via QEMU.
@ -84,7 +84,7 @@ ninja install && ninja image && ninja run
In the initial terminal, one can easily run the test runner script:
```
courage ~ $ ./tests/run-tests-and-shutdown.sh
courage ~ $ ./Tests/run-tests-and-shutdown.sh
=== Running Tests on SerenityOS ===
...
```
@ -96,7 +96,7 @@ The system server entry looks as below:
```ini
[TestRunner@ttyS0]
Executable=/home/anon/tests/run-tests-and-shutdown.sh
Executable=/home/anon/Tests/run-tests-and-shutdown.sh
StdIO=/dev/ttyS0
Environment=DO_SHUTDOWN_AFTER_TESTS=1 TERM=xterm PATH=/usr/local/bin:/usr/bin:/bin
User=anon