Replies: 2 comments 1 reply
-
I also thought about whether it is really necessary to always use Godot as an execution program for tests. From a unit test perspective, it should not be necessary to use the Godot engine as long as no core functions are used that have runtime dependencies. Therefore, a stricter distinction would have to be made between unit and integration tests. To achieve this, a test would first have to be scanned to determine whether it uses such code paths in order to decide whether it is a unit or integration test. There is an open feature request to support test filters, #27 I can do a prototype in the next week to verify I can run unit tests without using Godot engine, by using test category |
Beta Was this translation helpful? Give feedback.
-
Sounds great, thanks! |
Beta Was this translation helpful? Give feedback.
-
Thanks for your work on this tool, it's very useful.
Is there a way to launch gdUnit4Net tests without the test run automatically launching an instance of Godot? I ask because I have internal logic not coupled to Godot I'd like to test without the performance overhead.
I've tried separate .NET projects for pure unit tests and gdUnit4Net integration tests and have had issues with that. If that's the preferred approach I can dig further into that.
Beta Was this translation helpful? Give feedback.
All reactions