Currently, skipped tests are completely ignored. A message for skipped tests should be printed.

This kata skips one test conditionally but a message is not printed when the test is skipped.

It should be possible to have 3 separate files: preloaded.ml, solution.ml, and tests.ml. It will be necessary to manually import preloaded code with open Preloaded (or using the Preloaded. prefix) and solution with open Solution. But all line numbers in error and warning messages will be correct for both user code and tests.

After #2 gets improved or merged, the event listener could be extended with support for nested TestLabel tests (not to be confused with nested test groups):

"Nested labels" >::: [
          "Outer label" >: ("Inner label" >: ("Tests with nested labels" >::: [
            TestCase (fun _ -> assert_equal false (is_even 100) ~msg:"Incorrect answer for n=100" ~printer: string_of_bool);
            TestCase (fun _ -> assert_equal false (is_even 100) ~msg:"Incorrect answer for n=100" ~printer: string_of_bool);          
            
          ]))
        ]

Such construct should not be too common, nonetheless OUnit supports it, it should not be difficult to support it in the listener, and currently the listener omits outer labels and displays only the innermost one.

Test groups are not rendered correctly because <COMPLETDIN::> is missing.

Instead of 3 test groups, groups are nested:

See https://www.codewars.com/kumite/620a7361d746e5000f36a021

The new OUnit test framework invokes Gc.full_major () after each test when the function OUnit.perform_test is used to call tests (see this line of OUnitRunner and this line of OUnit where conf is created). This negatively impacts performance if huge data structures are created outside of test functions (see this kata: https://www.codewars.com/kata/60cc93db4ab0ae0026761232/ocaml).

It is possible to turn off the garbage collection step by setting the property OUnitRunner.run_gc_full_major to false. But I don't see any way to change the default configuration when OUnit.perform_test is used. It seems to be necessary to call OUnitCore.perform_test directly with an appropriate configuration.