The used Godot version: 3.3

OS including version: Windows 10

Describe the bug After upgrading to v1.0.0, the addons/gdunit3 directory gets wiped out.

Steps to Reproduce

• Install gdUnit from the assetlib. You get version v0.9.7-rc
• Activate it. You get a prompt to upgrade.
• Upgrade
• Wait

Expected: the plugin upgrades itself Actual: the plugin wipes out the addons/gdunit3 directory

You could also update the assetlib version to v1.0.0 to temporarily work around this problem.

The used Godot version: 3.3.rc6

OS including version: Ubuntu 20.04 x64 x11 GTX 1650M (proprietary drives)

Describe the bug I just cloned the master and copied gdUnit3 and GdCommons to /addons folders. When I started godot on my existing project, the following error shows up: Request for nonexistent project setting: gdunit/report/error_notification.

When testing on a new clean project, there are two more erros:

 Request for nonexistent project setting: gdunit/report/error_notification.
 Couldn't create an ENet multiplayer server.
 modules/gdscript/gdscript_functions.cpp:803 - Can't establish server, error code: 20

Steps to Reproduce Steps to reproduce the behavior:

1. Open the test project
2. See error Request for nonexistent project setting: gdunit/report/error_notification.

Minimal reproduction project: test_project.zip

Version 1.0.0

The used Godot version: v3.3.2.stable.arch_linux

OS including version: Manjaro, kernel 5.20.49-1 (64 bit)

Describe the bug When the code under test has a compilation error, running the tests normally (not in debug mode) will return green. This means that these test results are actually lying to us, because non-compiling code can by definition not complete the test :).

Running the tests in debug mode does break at the compilation error, so currently I only run tests this way. The runtest.sh -a command does also break at the error and opens a debug prompt. However running with the -c option wont continue the testing (probably another bug report).

Steps to Reproduce

1. Open the test_gdunit project.
2. Run the tests in the test folder.
3. Note how the tests return green.
4. Run the tests in debug mode.
5. Note how line 6 in Main.gd does not actually compile. Meaning that the green test results from the non-debug run were actually lying to us.

Minimal reproduction project: test_gdunit.zip

The used Godot version: v3.3.2.stable.arch_linux

OS including version: Manjaro, kernel 5.10.49-1 (64-bit) Windows 10 (#113 )

Describe the bug After running the auto-update, the addons directory is empty. The runtest.cmd and runtest.sh scripts are still there.

Steps to Reproduce

1. Start a new Godot project.
2. Go to the "AssetLib" tab ad install GdUnit3. At the moment (2021-07-22) this installs 0.9.7-rc (which I'm guessing will soon change to 1.0.0). Don't uncheck any files when installing.
3. Enable the plugin.
4. The updater pops up as expected. And notifies that v1.0.0 is available.
5. Click update
6. The update bar will show that the download is successful and the installation is complete.
7. Look in the addons folder, the plugin is no longer there. An update.zip sits in the project directory, with the files for v1.0.0 inside.

Workaround As workaround you have to reinstall and press cancel on the upgrade screen

The used Godot version: 3.3-rc6

OS including version: Ubuntu 20.04 x64 x11 GTX 1650M (proprietary drives)

Describe the bug When trying to mock a script which has a snake_case.gd naming convention, gdUnit3 tries to use the file name to find the class, so if I'm trying to mock a class, named main_player.gd or mob.gd, gdUnit3 will extends main_player and mob classes, which doesn't exists.

Since snake_case is the convention recomended by godot style guide, many users will have the same problem.

Steps to Reproduce

1. Create a new script using snake_case.gd
2. Try to create a mock of this script
3. Run any tests and the error will appear

Minimal reproduction project: N/A

The used Godot version: v3.5.1.stable.official [6fed1ffa3]

OS including version: Windows 11

Describe the bug I'm using a dictionary in a parameterised test in GdUnit3 2.3.1. The dictionary contains key/value pairs of type string/double. When I define my expected value dictionary, I define the values using whole numbers (i.e. without the decimal point). The difference report shows the actual values are identical to the expected values (see image). The expected values in the above test run were defined as { left = 50, top = 50, right = 50, bottom = 50 }. As a workaround, if I define my expected values as { left = 50.0, top = 50.0, right = 50.0, bottom = 50.0 } then the test passes.

Steps to Reproduce

1. Create a parameterised test containing a Dictionary expected value containing key/value pairs of type string/double.
2. Create a test parameter containing valid integer values
3. Run the test
4. Observe the assert fails but the "expecting" is the same as the "actual" in the report.

The used Godot version: 3.5

OS including version: Max OS, Windows

Describe the bug https://github.com/MikeSchulze/gdUnit3/blob/master/addons/gdUnit3/src/core/GdUnitExecutor.gd#L375 duplicate fails sometimes. I bumped the timeout for tests and it looks like that resolved the issue. This leads me to believe this is related to timeout logic. Maybe it deletes the node which causes duplicate to fail. I have not had time to investigate further yet.

Steps to Reproduce

• Run this simple test that times out

extends GdUnitTestSuite

func test_timeout(timeout=1500):
	var node := Node.new()
	node.filename = "does_not_exist"
	add_child(node)
	yield(get_tree().create_timer(60), "timeout")

Errors:

Reaults:

A node must have an valid filename. Means the file must exists or you have to set to an empty string.

Minimal reproduction project:

The used Godot version: all

OS including version: all

Describe the bug I am trying to spy on an instance, the spy object has invalid/unset variables.

Steps to Reproduce

• Create a simple class and initialize a variable in the constructor.
• create a spy on this instance
• check the variable on the spy object The variable is not set.

Minimal reproduction project:

res://addons/gdUnit3/test/mocker/resources/TestPersion.gd

extends Object


var _name

func _init(name :String):
	_name = name

func name() -> String:
	return _name

func test_spy_copied_class_members():
	var instance = auto_free(load("res://addons/gdUnit3/test/mocker/resources/TestPersion.gd").new("user-x"))
	assert_str(instance.name()).is_equal("user-x")
	
	# spy it
	var spy_instance = spy(instance)
	
	# verify members are inital copied 
	assert_str(spy_instance.name()).is_equal("user-x") <--- Fails

Hi,

As we discussed in a previous issue, you can run gdUnit3 tests in "Debug" mode (fails if the code throws an error).

How do I run it in this mode, when running the tests as part of a build? Currently, I'm using this code:

./Godot_v3.4.2-stable_linux_headless.64 -s addons/gdUnit3/bin/GdUnitCmdTool.gd --add tests/test_cases/gdunit

I just noticed that several tests are failing due to a refactoring change. (The game code is correct, but the test code refers to variables that no longer exist.) But, the build still passes, and shows that all tests are passing. Sure enough, if I use "Run tests" in Godot, I see everything pass; if I use "Debug tests," I see errors (not failures).

Is there a way to make the build fail in this scenario? I think a lot of other test frameworks (e.g. NUnit) return a status code on exit indicating a failure. That would be helpful here (tests look like they pass, but there are errors).

Now that im following unit testing best practices and aiming for higher code coverage i end up with lots of tests within the same suite, which makes it a little hard to read. I noticed that you can collapse the tests by their testing suite, I was wondering if there is a way to nest or group related suites. So that the ui allows to go from this:

> my suite
  - test a1
  - test a2
  - test a3
  - test b1
  - test b2

To this:

> my suite
  > a test suite
    - test a1
    - test a2
    - test a3
  > b test suite
    - test b1
    - test b2

I'm testing with Godot-3.3-rc8 and ran into Slow Create Resource Dialog in a project with a lot of class_names having only this plugin.

We have ~240 class_name items.

So this is not a bug but it takes ~10 sec to get this Resource dropdowns to open.

It seems not being fixed before Godot-4 :-(

Discussed in https://github.com/MikeSchulze/gdUnit3/discussions/361

A Task is not a bug or feature request

Description

Document the new settings #345 #347

Document diverenze between runtime and debug test execution. #349

Document SceneRunner changes #365