Skip to content

Incorrect path in generating *.out tests command in integration tests documentation #8221

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 9, 2023
Merged

Incorrect path in generating *.out tests command in integration tests documentation #8221

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
799478b
fix generating *.out command in unit test doc
k0T0z Oct 11, 2023
b298d24
Apply suggestions from code review
Calinou Nov 9, 2023
318d9e1
Apply suggestions from code review
Calinou Nov 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions contributing/development/core_and_modules/unit_testing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -319,18 +319,24 @@ Therefore, the process of writing integration tests for GDScript is the followin
if true # Missing colon here.
print("true")

3. Generate ``*.out`` files to update the expected results from the output:
3. Change directory to the Godot source repository root.

.. code-block:: shell

./bin/<godot_binary> --gdscript-generate-tests godot-source/modules/gdscript/tests/scripts
cd godot

4. Generate ``*.out`` files to update the expected results from the output:

.. code-block:: shell

bin/<godot_binary> --gdscript-generate-tests modules/gdscript/tests/scripts

You may add the ``--print-filenames`` option to see filenames as their test
outputs are generated. If you are working on a new feature that is causing
hard crashes, you can use this option to quickly find which test file causes
the crash and debug from there.

4. Run GDScript tests with:
5. Run GDScript tests with:

.. code-block:: shell

Expand Down