GdUnit3 v2.0.0-Beta Feedback

[MikeSchulze]

Hi GdUnit3 V2.0.0 Beta users,

You are invited to give me feedback on the GdUnit3 with C# beta support.

Please note that C# test support is currently still in beta and not feature complete. If you have any problems or find any bugs, please report them.

Please describe what you like and what you don't ;)
If you found bugs, please report them in the issue section of GitHib.
Also feel free to create feature requests.

Thanks in advance
Mike

[ZodmanPerth]

I'm a first time user of GdUnit3, and a long time writer of unit tests. First up, let me say GdUnit3 is fantastic and is fulfilling my needs so far. Please accept my heart-felt appreciation. ❤️

Here's my setup:

• GdUnit3 v2.3.0
• Godot v3.5.1.stable.official [6fed1ffa3]
• Windows 11 22H2
• a fairly beefy Windows machine (Surface Studio i7 with 16Gb RAM)

Now for some feedback:

1. I have a performance issue. I have a parameterised gdscript unit test with 49 items in the parameter array. The test takes 24 seconds to start running after I press "run unit tests" (or even "rerun unit tests") and about 825 milliseconds to execute all 49 cases.
   The long delay before starting is hard to take, especially when doing fast TDD cycles.
   The test method takes 4 parameters (String, Vector2, int, int).
   Any idea why there is such a long delay? Any pointers on how I can diagnose?

2. When I right-click a parameterised test entry in the GdUnit3 tab and select either the Debug Test or Run Test option, after an eternity (i.e. the 24 second delay from feedback 1) the test runner returns immediately with no results. Is this a bug?

Before:

After:

3. When the tests finish running it collapses the tree in the GdUnit3 tab. Can we please get an setting/option to leave the expand/collapse state of the tests as is before testing?

4. When there is a compile error in either the test function or the system under test (the code it is testing), the runner executes and goes green but nothing actually happens. It's hard to tell that there is an error because of the way the tree collapses in feedback item 3.
   a. Can we not show the root test node as green in this case (so I know there is an issue)?
   b. Is it possible to show an error message?
   I have to recognise there is an error (which is hard when the root node is green), debug the tests, to get the run-time error.

[ZodmanPerth]

2. I've created feature request GD-337: Start an individual parameterised test from the GdUnit3 tab context menu #337

[ZodmanPerth]

3. Thanks. Should I make a feature request for that too?

[ZodmanPerth]

Compilation errors at runtime are not handled by Godot. They are simply ignored.

I see. Thanks.

To detect compilation errors at runtime, I implemented an error detection that must be enabled.
If this detection does not report your compile error as an error, please create a ticket with information and add steps to reproduce it.

The errors are reported during a debug run. Nothing more to do here.

[MikeSchulze]

Thank you, i will have a look and provide a fix.
Merry Christmas

[ZodmanPerth]

And to you! 🎁 🎅 🤶