repowisegodot-gdunit-labs/gdunit4

godot-gdunit-labs / gdunit4

Embedded unit testing framework for Godot 4 supporting GDScript and C#. Features test-driven development, embedded test inspector, extensive assertions, mocking, scene testing.

GDScript★ 1,250
Use in your agentAsk this codebase

github.com/godot-gdunit-labs/gdunit4Indexed at 24f51caUp to date with upstream

What is gdunit4?

gdunit4 is an embedded unit testing framework for testing GDScript, C# scripts, and scenes in the Godot editor. It lets developers create and run tests, including test-driven development workflows, through Godot. The project is primarily written in GDScript and also supports C# through gdUnit4.api and gdunit4.test.adapter.

Written by a model from the README and the source

128 files and 57 symbols in 5 modules, led by Shell (12 files) and C# (8).

Start reading

Code health

9.8out of 10Excellent

This codebase scores 9.8 out of 10 for code health, which we rate excellent. It also scores maintainability 9.8 and static performance 10.0 out of 10. The three are scored separately and never blended into one number.

Full health report

Use godot-gdunit-labs/gdunit4 in your agent

Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.

  1. 1.In Claude, open Customize → Connectors, click +, then Add custom connector. On a Team or Enterprise plan an owner adds it first under Organization settings → Connectors.
  2. 2.Paste the server URL below as the Remote MCP server URL, then click Add.
  3. 3.Click Connect. A Repowise sign-in window opens. Approve access.
  4. 4.Repowise's tools are now available in your Claude chats.

Connect with one click. Sign in with Repowise (OAuth), no API key to copy. Works in Claude on the web, desktop, and mobile.

Docs
bash
https://api.repowise.dev/mcp/godot-gdunit-labs/gdunit4
Editors need an API key: sign in to create one.Sign in to connect

This repo is public, so anyone with a Repowise account and an API key can connect.

Try asking

  • get_overview()
  • get_answer("how is gdunit4 put together?")
  • get_why("why is gdunit4 structured this way?")

Explore gdunit4

Key features of gdunit4

  • gdunit4 supports writing and executing tests in GDScript and C#.
  • gdunit4 provides an embedded test inspector with runtime test discovery in the Godot editor.
  • gdunit4 offers fluent test syntax, assertions, argument matchers, Unicode text support, and variadic argument support.
  • gdunit4 supports parameterized tests, test fuzzing, session hooks, mocking, and spying.
  • gdunit4 can test scenes with simulated mouse, keyboard, touch, and custom input actions.
  • gdunit4 provides command line execution and HTML and JUnit XML test reports for continuous integration.

How godot-gdunit-labs/gdunit4 works

Tests enter gdunit4 through the Godot editor or its command line tool. The addons directory provides the embedded framework and editor integration, including the test inspector and runtime test discovery. Test suites use GdUnitTestSuite and assertion APIs to verify code, scene behavior, outputs, and function calls. The documentation directory describes installation, C# setup, and the API. The command line tool runs tests outside the editor and can produce HTML and JUnit XML reports. The gdUnit4.api and gdunit4.test.adapter components connect C# tests with VSTest environments.

The codebase has 128 files and 57 symbols in 5 modules, led by Shell, C# and JavaScript. Code health is 9.8 out of 10, rated excellent.

godot-gdunit-labs/gdunit4 FAQ

What is gdunit4?

gdunit4 is an embedded unit testing framework for testing GDScript, C# scripts, and scenes in the Godot editor. gdunit4 also supports test-driven development.

How does gdunit4 work?

gdunit4 discovers and runs tests through the Godot editor or command line tool. gdunit4 uses test suites, assertions, mocks, spies, and scene testing to verify behavior.

What language is gdunit4 written in?

gdunit4 is primarily written in GDScript. gdunit4 also supports C# tests through gdUnit4.api and gdunit4.test.adapter.

How is the gdunit4 code organized?

gdunit4 organizes its editor framework and integration in addons, with documentation in documentation. gdunit4 includes C# support through gdUnit4.api and gdunit4.test.adapter.

When should I use gdunit4?

Use gdunit4 when testing GDScript, C# scripts, or Godot scenes. gdunit4 supports automated tests, test-driven development, editor workflows, and continuous integration.

What license does gdunit4 use?

gdunit4 uses the MIT license.

The summary, features and answers on this page are written by a model from the README and the source, and refreshed with each index.

About this page

Get a page like this for your own codebase

Repowise built this map of godot-gdunit-labs/gdunit4 from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Index your repo freeSee how Repowise worksFree for 2 public repos, with a page like this one.

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.