• In solution setup provides a function with a different name than expected by tests.
• there is no random tests.

Suggestions:

• The dotest in its current form is a very thin wrapper which does not provide much value. It would be more useful if it did something more, for example present a useful failure message helpful for debugging.

Please see LUA translations of kata from this collection for some ideas.

You would put the random tests in the Test Cases panel of the editor. You could use a crate such as rand in order to generate random values for the tests.

I removed the test entirely, should be working fine.

Example tests contain a invalid expected result:

        assert_eq!(
            word_transformer("hello", "world", &["hella", "hollo", "hallo", "hullo", "wello", "werld", "world"]),
            vec!["hello", "hallo", "hollo", "hullo", "wello", "werld", "world"]
        );

The actual tests are fine, so it's probably just example tests that are outdated.

Kata got retired.

Surely this is a duplicate. I just can't find the kata quickly.

Needs random tests.

Rust gives warning for c is not used.

yes but ruby probably created like 1 million objects under the hood which is why this is the slowest lol

just return hello 5 each time

no way this is real lol

use a spoiler tag, eh