Butch Wesley

The new setters and getters are named `@_setter`, `@_getter` ``` print(inst.has_method('@has_setter_setter')) print(inst.has_method('@has_getter_getter')) ```

### `assert_set_get` * The assert no longer needs to verify that the methods were called. * The assert no longer needs setter and getter method name parameters. * The assert...

I looked into using `--time-scale` option on the command line awhile ago, see #120. I got mixed results using this with tests on various projects. Altering this value caused some...

You get more detailed messages on the other asserts. `assert_eq` will say "expected [expected] got [got]". I guess `assert_true` should say "expected true but got false" and vice versa for...

Ahhh. I like this idea, but this would be a bigger change than you might think. GUT does not parse any of the source code for a test script. It...

That is a reasonable middle ground. I won't have any time to address this in the near future, most of my GUT time is being used for Godot 4. PR's...

It appears the compiler knows when a function has an `await` in it and requires that any calls that that function use `await`. It is not clear what happens if...

When `awaiting` a coroutine you just put `await` in front of the call. Unlike with `yield` you are not waiting on the `completed` signal. Ex: `var ret_val = await foo(bar)`

Since the new await uses `.` all old `yields` using the `YIELD` constant in `test.gd` will not work. We will have to add the `timeout` signal to `test.gd` and all...

`await` must be used on a method that contains an `await` only if you are using the return value. If you are not using the return value then you don't...