I'd like function expected to look more like a single unit, but the random tests and the generators do look a lot better. :]

i have fixed it to give the debug info:

Compilation for class failed because it had one or more errors:

fixed that too sorry i missed it

Compilation failed for class 'FixedClass' ==> expected: <0> but was: <2>

This failure message looks confusing with these magic numbers.

Thanks for the feedback!

I've refactored the random test framework and moved the generators into helper functions. The random tests block now only runs the generated cases.

Let me know if there are any further improvements you would suggest.

There is still ExampleMethod in the description.

i removed the anticheat because i dont believe the preloaded is useful to the solver (correct me if i am wrong here). therefore the example tests will still use it

fixed lol mb

    // muliply a and b

speeling erorr: "multiply"

Why would you even forbid using Preloaded? Don't put anything useful ( to solvers ) in there - that's not what it's for. Put it in the tests.

If you can't make your Example tests work with that, do the best you can there and do the real checking in Submit tests.

Please clean up your random test framework a bit. Factor out random generators from the testing setup itself.

Also, newlines within functions do not necessarily make those more readable - they just spread out content until, eventually, it no longer even fits on one screen. No function should be longer than one screen, and not all screens are huge. If there's a pressing need to separate functionality within a function - factor it out.

Yep, I'll reach to you on discord

@korindou, I made this kata five years ago, could never write decent random tests for it, and could not find anybody knowing enough TH to do it for me.

I still don't know the first thing about TH. Would you care to take a look at the tests of that, see if you could do something similar there as you did here? Please?

I'd call HoSpecGen Preloaded and leave the snippet out of the submit tests.

Using explicit exports and imports ( well, maybe not for Test.Hspec and stuff like TH ) is always a good idea.

An import Preloaded (genHoCases) is quite readable, and when people can see the Submit tests, they can see Preloaded.

A kata can't be unretired. You could make a new one, with all fixes included from the beginning, but I doubt it would survive. It's just not interesting and novel enough.