Fix running tests in template builds

[AThousandShips]

No description provided.

[akien-mga]

I did some testing and it doesn't really make sense to have tests enabled with export, will look at disabling it completely for this as well

What are the issues? In theory it seems useful to me that we can run unit tests on non-tools builds (especially the release template), to validate that the API behaves as intended even in release builds.

It's not something we would enable for official export templates of course, but ideally we would run such tests on CI. If some tests depend on editor-only functionality, they should be #ifdef TOOLS_ENABLED away.

[AThousandShips]

Indeed, will look deeper into the specific issues, but there are some tests that simply won't work without even being in the correct directory, but will leave this for later digging and not add it here

Note that we couldn't use it in CI unless we do an export completely as the template binary can't be run then

[akien-mga]

Note that we couldn't use it in CI unless we do an export completely as the template binary can't be run then

--test is a standalone command, it seems to work fine on a template build (aside from it currently running a single test suite, which segfaults):

./bin/godot.linuxbsd.template_debug.dev.x86_64.mono --test
[doctest] doctest version is "2.4.11"
[doctest] run with "--help" for options
===============================================================================
./modules/gdscript/tests/gdscript_test_runner_suite.h:41:
TEST SUITE: [Modules][GDScript]
TEST CASE:  Script compilation and runtime

./modules/gdscript/tests/gdscript_test_runner_suite.h:41: FATAL ERROR: test case CRASHED: SIGSEGV - Segmentation violation signal

===============================================================================
[doctest] test cases:  1 |  0 passed | 1 failed | 866 skipped
[doctest] assertions: 25 | 25 passed | 0 failed |
[doctest] Status: FAILURE!
Segmentation fault (core dumped)

[AThousandShips]

That's strange it popped up the dialog for me first, you're right it works fine in that case, then no worries here, then I'll just leave it as such for now :)

[akien-mga]

Well actually in second thought, since dev_mode is for engine developers, I do think we should have tests enabled by default in dev builds even for templates. We just need to fix the bugs with running tests, by disabling the tests which can't work.

[AThousandShips]

I'll take a look :)

[AThousandShips]

Identified the first issue, the file modules/gdscript/tests/scripts/analyzer/errors/cyclic_ref_override.gd crashes on release builds, unsure how to fix that, will see if I can get better output details

[AThousandShips]

For now I'm disabling some of the offending GDScript tests, to be fixed later, and fixing some other tests and improving them, will push soon

[AThousandShips]

There, some temporary fixes in there but this makes it possible to generally run tests, with some improvements

There are still some test cases that fail on disable_3d builds but will look into those specifically in a separate PR as they're a bit trickier, and have some more complex cases

[akien-mga]

Thanks!

[AThousandShips]

Thank you!