Skip to content

GDScript: Change test generation command #11874

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

Draft
HolonProduction wants to merge 1 commit into
base: master
Choose a base branch
from
+2 −2
Draft

GDScript: Change test generation command #11874

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions engine_details/architecture/unit_testing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -415,7 +415,7 @@ Therefore, the process of writing integration tests for GDScript is the followin

.. code-block:: shell

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

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
Expand All @@ -435,7 +435,7 @@ If no errors are printed and everything goes well, you're done!
.. warning::

Make sure the output does have the expected values before submitting a pull
request. If ``--gdscript-generate-tests`` produces ``*.out`` files which are
request. If ``gdscript-generate-tests`` produces ``*.out`` files which are
unrelated to newly added tests, you should revert those files back and
only commit ``*.out`` files for new tests.

Expand Down
Loading