|
@@ -319,18 +319,24 @@ Therefore, the process of writing integration tests for GDScript is the followin
|
|
if true # Missing colon here.
|
|
if true # Missing colon here.
|
|
print("true")
|
|
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
|
|
.. 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
|
|
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
|
|
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
|
|
hard crashes, you can use this option to quickly find which test file causes
|
|
the crash and debug from there.
|
|
the crash and debug from there.
|
|
|
|
|
|
-4. Run GDScript tests with:
|
|
|
|
|
|
+5. Run GDScript tests with:
|
|
|
|
|
|
.. code-block:: shell
|
|
.. code-block:: shell
|
|
|
|
|