Skip to content

Tests pass despite GD.PrintErr(...) or GD.PushError(...) #148

Locked Answered by MikeSchulze
bjkarasek asked this question in Q&A
Discussion options

You must be logged in to vote

Update

The exceptions can now be tracked by using these two attributes on test level.
Will be available in the upcoming release 4.4.0

/// <summary>
///     Indicates that a test method or class should monitor exceptions that occur during Godot's main thread execution.
///     This attribute enables monitoring of exceptions that are caught by CSharpInstanceBridge.Call, which handles
///     exceptions from Godot callbacks and scene tree processing.
/// </summary>
/// <remarks>
///     This attribute is particularly useful for:
///     <list type="bullet">
///         <li>Testing exception handling in Godot node callbacks (_Ready, _Process, etc.)</li>
///         <li>Verifying exceptions du…

Replies: 3 comments 15 replies

Comment options

You must be logged in to vote
10 replies
@bjkarasek
Comment options

@MikeSchulze
Comment options

@bjkarasek
Comment options

@MikeSchulze
Comment options

@bjkarasek
Comment options

Comment options

You must be logged in to vote
5 replies
@MikeSchulze
Comment options

@bjkarasek
Comment options

@MikeSchulze
Comment options

@MikeSchulze
Comment options

@MikeSchulze
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by MikeSchulze
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
enhancement New feature or request help wanted Extra attention is needed gdunit4.api Issue is related to the `gdunit4.api`
2 participants