Hi there,

I'm extending the Godot engine for my own needs, so I'm reusing the application as is (scene panel, toolbars, etc), and then adding new panels and such to the editor.

I was just wondering how Godot handles testing the actual engine UI?
I know GUT is available for scenes/game ui, but it's not what I'm looking for (unless there's a way to use that to accomplish what I need).

Any advice is welcomed, thanks!

  • DoronD Or perhaps it's not done in that way?

    Yeah I'm not aware of unit testing being utilized by the core devs. That is not to say that they don't do it, they might but it's not obvious from the outside looking in. Your best bet would be to go check in with them and ask this from them via the contributor chat on rocket.chat

12 days later

No one here tests the Godot Engine UI?

The Godot Engine UI is built in Godot Engine, with the same components you can use in a game.

So I guess you could prototype in the editor and then port that to C++ after you get it to work.

    DoronD

    Development tips

    To iterate quickly on the editor, we recommend to set up a test project and open it from the command line after compiling the editor. This way, you don't have to go through the project manager every time you start Godot.

    DoronD Not much info there, sadly

    There's also other parts of the documentation worth checking out such as:
    https://docs.godotengine.org/en/stable/development/cpp/introduction_to_godot_development.html

      4 days later

      Megalomaniak Thats the Arch of the engine, which is a good reference, but still doesn't say if there's a proper way to test the engine UI itself, however

        DoronD There's 2 quotes in that post, the first one with the big header in it is from the page I originally linked. It literally says and I quote again:

        To iterate quickly on the editor, we recommend to set up a test project and open it from the command line after compiling the editor.


        Godot editor is built with godot itself, the godot editor UI is built with the UI 'engine' if you will of the godot engine(control type nodes extending the control class), or if by testing the engine UI you mean that you want to modify the editor itself then again you would test it by the same means.

        If you mean to ask about unit testing the engine tools build("the editor") that's a whole other thing. You can search for and read about building unit tests for c/c++ I guess, since that's what the engine is primarily programmed in.

          Megalomaniak I've already built upon the editor, as that's not the issue. The issue like you mentioned at the end, is the unit testing of the editor itself, as I don't see it anywhere in the code, so was wondering how the actual editor is tested and/or who does it?

          Or perhaps it's not done in that way?

            DoronD Or perhaps it's not done in that way?

            Yeah I'm not aware of unit testing being utilized by the core devs. That is not to say that they don't do it, they might but it's not obvious from the outside looking in. Your best bet would be to go check in with them and ask this from them via the contributor chat on rocket.chat

              6 days later