Fix test event listener for nested and unlabeled tests

[hobovsky]

Fixes #1 .

Supports:

• Nested tests.
• Tests without labels.

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

Test output:

<IT::>Top level test case

<FAILED::>not equal

<COMPLETEDIN::>

<DESCRIBE::>Test Odd

<IT::>Should return false for 1

<PASSED::>Test passed

<COMPLETEDIN::>

<IT::>Should return false for 7

<PASSED::>Test passed

<COMPLETEDIN::>

<COMPLETEDIN::>

<DESCRIBE::>Test even

<IT::>Should return true for 100

<PASSED::>Test passed

<COMPLETEDIN::>

<IT::>Should return true for 42

<PASSED::>Test passed

<COMPLETEDIN::>

<COMPLETEDIN::>

<DESCRIBE::>Test edge cases

<DESCRIBE::>Test zero

<IT::>Should return true for 0

<PASSED::>Test passed

<COMPLETEDIN::>

<COMPLETEDIN::>

<DESCRIBE::>Test -1

<IT::>Should return false for -1

<PASSED::>Test passed

<COMPLETEDIN::>

<COMPLETEDIN::>

<COMPLETEDIN::>

<DESCRIBE::>Unlabeled tests

<IT::>

<FAILED::>Incorrect answer for n=100<:LF:>not equal

<COMPLETEDIN::>

<IT::>

<FAILED::>Incorrect answer for n=100<:LF:>not equal

<COMPLETEDIN::>

<DESCRIBE::>

<IT::>

<FAILED::>Incorrect answer for n=100<:LF:>not equal

<COMPLETEDIN::>

<IT::>

<FAILED::>Incorrect answer for n=100<:LF:>not equal

<COMPLETEDIN::>

<COMPLETEDIN::>

<COMPLETEDIN::>

Current output panel:

Output panel with updated listener:

[monadius]

function should only be used when there is a pattern-matching for the last argument. This function (and many other functions) should be written as

let cw_print_success () = print_endline "\n<PASSED::>Test passed"

Unnecessary parentheses should also be removed.

[monadius]

Don't create mutually recursive functions here (and).

[hobovsky]

They are mutually recursive tho, did not get a good idea yet how to decouple them.

[monadius]

Then everything is fine here. I missed run_tests in dispatch_test_group.

[hobovsky]

Btw this mutually recursive functions construct struck me as odd. I know some languages need it, but majority is fine with just some declaration and no special marker for recursive, or mutually recursive, functions.

Would you have any insight why ocaml, fsharp, maybe some other languages, need it? Is it just syntax, or is it relevant from compilers point of view, or anything else?

[monadius]

It is just syntax. The only real difference is that functions without rec (or and) can shadow functions (or constants) with the same name defined earlier and call old functions in their body. Compiling non-mutual recursive functions may be a little faster also.

[monadius]

Instead of pairs (label, test_case) it is better to use separate arguments:

let dispatch_test_case label test_case =

[hobovsky]

Yeah, randomly spraying parentheses and semicolons is my way of dealing with syntax errors and type mismatches.

I am noob.

[monadius]

Can I edit this PR somehow? Everything works fine but some small changes are required to make the code cleaner.

[hobovsky]

Can I edit this PR somehow? Everything works fine but some small changes are required to make the code cleaner.

You can even steal the code to your repo.
Maybe I could make you contributor or something, just don't know how.

[hobovsky]

Can I edit this PR somehow? Everything works fine but some small changes are required to make the code cleaner.

I made you a collaborator in my repo, but I dont know if it helps anything :)

[monadius]

I will push my changes to your repository. Then you will be able to update this PR.

[kazk]

@monadius I gave you Write permission, so you should be able to push to this PR. Maintainers of upstream project can write to PRs unless the author opted out if I remember correctly.

[monadius]

I successfully pushed my changes to this PR.