Skip to content

6.5.0

Compare
Choose a tag to compare
@bitwes bitwes released this 08 Jul 15:56
e9dbee6

Fixes

  • Bug fix by Xrayez to ensure that the command line tool always sets the return code properly. Before it was only setting it if Gut was configured to exit when done.
  • Fixed an issue where the command line tool wasn't setting options correctly when the .gutconfig.json file was present. All options are now applied correctly based on order of precedence (default < gutconfig < cmd line). I also added the -gpo command line option to print out all option values from all sources and what value would be used when running Gut. This will make debugging theses issues easier later.

Features

  • We have two new asserts thanks to hbergren. These asserts make it easier to assert if a value is within or outside of a +/- range of a value. These are especially useful when comparing floats that the engine insists aren't equal due to rounding errors.
    • assert_almost_eq(got, expected, error_interval, text='') - Asserts that got is within the range of expected +/- error_interval. The upper and lower bounds are included in the check. Verified to work with integers, floats, and Vector2. Should work with anything that can be added/subtracted. Examples
    • assert_almost_ne(got, expected, error_interval, text='') - This is the inverse of assert_almost_eq. This will pass if got is outside the range of expected +/- error_interval. Examples
  • Xrayez contributed a new option to maximize the Gut window upon launch. The option can be set in the editor, .gutconfig, or at the command line.
  • Added the -gpo command line option to print out all option values from all sources and what value would be used when running Gut. This will make debugging option issues much easier.

Other

Some housekeeping. Removed some commented out and unreachable code. Renamed a lot of tests in test_test.gd since it now uses Inner Test Classes which allows for better names. They were setting a bad example for PRs.