Problems & Solutions

This section lists known problems and possible solutions/workarounds.

Problems

• Script/Resource Errors after the plugin is installed
• Modifying the Game Engine State ‘mainLoop.Paused = true’ during Tests
• Export Failures with GdUnit4 Plugin Installed

---

Script/Resource Errors after the plugin is installed

When installing the GdUnit4 plugin and activating it, you may encounter a lot of script and resource loading errors. These errors occur due to a cache problem in the Godot Engine.

Solution

To solve the errors, you need to restart the Godot Editor. If this does not help, you may need to manually delete the Godot cache folder:

1. Close the Godot Editor.
2. Delete the .godot folder from your working directory.
3. Start the Godot Editor (you may still see loading errors).
4. Close and restart the Godot Editor. The loading errors should no longer occur.

---

Modifying the Game Engine State ‘mainLoop.Paused = true’ during Tests

When a test modifies the game engine state Paused on the SceneTree, it can affect the test execution. Setting the main loop to paused will stop the engine running, including the test execution running in the main loop, causing the GdUnit4 test window to remain open even after tests are complete.

Solution

When you modify engine states during tests, ensure you restore them to their previous values when the test is finished. You can achieve this by adding an “after test” stage to your test suite.

• GDScript
• C#

• # Reset the paused mode back to false after each test
  func after_test() -> void:
      Engine.get_main_loop().paused = false
  
  # Simple example test to modify the game state
  func test_game_paused() -> void:
      var mainLoop :SceneTree = Engine.get_main_loop()
  
      assert_that(mainLoop.paused).is_false()
      # The following lines cause the GdUnit4 test window to remain open even after tests are complete
      mainLoop.paused = true
      assert_that(mainLoop.paused).is_true()
  

• // Reset the paused mode back to false after each test
  [AfterTest]
  public void TearDown() =>
      ((SceneTree)Engine.GetMainLoop()).Paused = false;
  
  
  [TestCase]
  public void GamePaused()
  {
      var mainLoop = (SceneTree)Engine.GetMainLoop();
  
      AssertThat(mainLoop.Paused).IsFalse();
  
      // The following lines cause the GdUnit4 test window to remain open even after tests are complete
      mainLoop.Paused = true;
      AssertThat(mainLoop.Paused).IsTrue();
  }
  

---

Export Failures with GdUnit4 Plugin Installed

When exporting games with the GdUnit4 plugin installed, you may encounter crashes during the export process, particularly in CI/CD environments. The crash typically shows a “Program crashed with signal 11” error and occurs because Godot has issues when exporting projects that include editor-only plugins like GdUnit4.

Solution

The recommended solution is to exclude the GdUnit4 addon from the export rather than disabling the plugin entirely. This allows you to keep the plugin active for development while ensuring clean exports.

Exclude GdUnit4 from Export Settings

1. Open your project in the Godot Editor
2. Go to Project > Export…
3. Select your export preset (e.g., “Windows Desktop”, “macOS”, etc.)
4. In the Resources tab, locate the Filters to exclude files/folders from project section
5. Add the following filter to exclude the GdUnit4 addon:

   addons/gdunit4/*
   

   

6. Export your game - the crash should no longer occur

Important Notes:

• The export exclusion method is preferred over disabling the plugin because it keeps GdUnit4 functional during development
• The GdUnit4 addon is designed for development and testing environments and should not be included in production builds
• After applying the exclusion filters, test your export to ensure it works correctly

---

document version v5.0.0