CLEO testing library

[x87]

Goals:

• Focus on important things when writing unit tests.
• Standardize test structure.

Public API:

• test(name: string, callback: int) -- creates new test suite (collection of unit tests)
• it(expectation: string, callback: int) -- creates new individual test focusing on testing one thing
• before_each(callback: int) -- registers a callback that runs before each unit test (test setup)
• after_each(callback: int) -- registers a callback that runs after each unit test (test teardown)
• assert_eq(val1: int, val2: int) - checks if two int values are equal, otherwise stops the test execution
• assert_eqf(val1: int, val2: int) - same as above, but for floats
• assert_neq(val1: int, val2: int) - checks if two int values are not equal, otherwise stops the test execution
• assert_neqf(val1: int, val2: int) - same as above, but for floats
• assert(val: int) - checks if value is not 0, otherwise stops the test execution
• assert_ptr(val: int) - checks if value is a valid pointer, otherwise stops the test execution

Simple example:

{$CLEO}
test('test suite', @tests)
terminate_this_custom_script

function tests
  it('should be true', @test1)
  it('should be false', @test2)
  return true

  function test1
   assert_eq(true, true)
  end
  function test2
   assert_eq(false, false)
  end
end

[MiranDMC]

it( looks bad, almost like if
test -> test_suite/block/group
it -> test_case

[MiranDMC]

Please port some of file access opcodes. It will show use case of before_each (and lack of after_each?) functionality. At this moment I have no idea how the file handle is meant to be passed into testcase.

[x87]

Please port some of file access opcodes. It will show use case of before_each (and lack of after_each?) functionality. At this moment I have no idea how the file handle is meant to be passed into testcase.

added after_each, see example in 0AC8 (allocate/free)

it( looks bad, almost like if
test -> test_suite/block/group
it -> test_case

it is pretty much an industry standard, at least in web/mobile dev. also naturally easy to read: it("should ...

test suites are also often called describe.

what C++ libraries are used for unit testing? I can look into how they name things.

[MiranDMC]

what C++ libraries are used for unit testing? I can look into how they name things.

I used google tests. Visual Studio also has some built in support.

[MiranDMC]

How does the test output looks on the screen?
In my older tests I had multiple wait 0 commands between test actions to assure in case of game crash the info (of previous step) had chance to be written in to log.

[x87]

[MiranDMC]

Nice. I have finally to change debug utils plugin so it prints top-down, as current order is confusing.

[x87]

Nice. I have finally to change debug utils plugin so it prints top-down, as current order is confusing.

it looks fine to me, especially the fading away effect makes more sense in bottom-top direction, without shifting text back to top