godot/modules/gdscript/tests/scripts/project.godot

; This is not an actual project.
; This config only exists to properly set up the test environment.
; It also helps for opening Godot to edit the scripts, but please don't
; let the editor changes be saved.

config_version=5

[application]

config/name="GDScript Integration Test Suite"

[debug]

settings/gdscript/always_track_call_stacks=true

[input]

test_input_action={
"deadzone": 0.2,
"events": []
}
Add runner for GDScript testing This is meant for testing the GDScript implementation, not for testing user scripts nor testing the engine using scripts. Tests consists in a GDScript file and a .out file with the expected output. The .out file format is: expected status (based on the enum GDScriptTest::TestStatus) on the first line, followed by either an error message or the resulting output. Warnings are added after the first line, before the output (or compiler errors) if the parser pass without any error. The test script must have a function called `test()` which takes no argument. Such function will be called by the test runner. The test should not have any dependency unless it's part of the test too. Global classes (using `class_name`) are registered before the runner starts, so those should work if needed. Use the command `godot --gdscript-generate-tests godot-source/modules/gdscript/tests/scripts` to update the .out files with the current output (make sure the output are the expected values before committing). The tests themselves are part of the doctest suite so those can be executed with `godot --test`. Co-authored-by: Andrii Doroshenko (Xrayez) <xrayez@gmail.com> 2021-04-07 10:12:51 -03:00			`; This is not an actual project.`
			`; This config only exists to properly set up the test environment.`
			`; It also helps for opening Godot to edit the scripts, but please don't`
			`; let the editor changes be saved.`

Add unit test runner for autocompletion 2023-11-21 16:06:43 +01:00			`config_version=5`
Add runner for GDScript testing This is meant for testing the GDScript implementation, not for testing user scripts nor testing the engine using scripts. Tests consists in a GDScript file and a .out file with the expected output. The .out file format is: expected status (based on the enum GDScriptTest::TestStatus) on the first line, followed by either an error message or the resulting output. Warnings are added after the first line, before the output (or compiler errors) if the parser pass without any error. The test script must have a function called `test()` which takes no argument. Such function will be called by the test runner. The test should not have any dependency unless it's part of the test too. Global classes (using `class_name`) are registered before the runner starts, so those should work if needed. Use the command `godot --gdscript-generate-tests godot-source/modules/gdscript/tests/scripts` to update the .out files with the current output (make sure the output are the expected values before committing). The tests themselves are part of the doctest suite so those can be executed with `godot --test`. Co-authored-by: Andrii Doroshenko (Xrayez) <xrayez@gmail.com> 2021-04-07 10:12:51 -03:00
			`[application]`

			`config/name="GDScript Integration Test Suite"`
Autocompletion: Add support for string name option in more places 2024-06-11 22:28:18 +02:00
GDScript: Update `get_stack()`, `print_stack()`, and `print_debug()` 2025-04-26 21:10:41 +03:00			`[debug]`

			`settings/gdscript/always_track_call_stacks=true`

Autocompletion: Add support for string name option in more places 2024-06-11 22:28:18 +02:00			`[input]`

			`test_input_action={`
Changed the default deadzone value for new actions from 0.5 to 0.2 2024-09-21 17:11:00 +04:00			`"deadzone": 0.2,`
Autocompletion: Add support for string name option in more places 2024-06-11 22:28:18 +02:00			`"events": []`
			`}`