I tried this problem some time ago but I could not succeed. I thought it was a skill issue. I'm back, definitely skill issue, but it doesn't take away from the fact that it's a horrendous problem.

0 is the 1st even number,
2 is the 2nd even number,
4 is the 3rd even number; and so on

OP solved it, closing

Approved

• Missing fixed test: empty string.
• Since the kata is 8 kyu and aimed at total newbies, let's make their lives easier: please make the initial solution compilable, for example by returning some dummy value (like an empty string, or "Implement me" or anything).
• > Basic test hello - make sure that when you present string values, they are quoted. It should be > Basic test "hello"
• Again, for sake of newbies, make sure that the submission tests help them on failure. Make sure that fixed and fuxxed tests present inputs in some convenient way. Fuzzers do this out of the box, but for fixed tests you probably need to put inputs in test titles (there is no assertions with custom failure messages, are there?).

i'll fork this for cr7.
SIUUUUU

cat

Elm translation

Almost done. I cannot approach the random test.
Sorry, I underestimated doing testing lol

Okay now I think I see the idea behind formatting of fixed tests, but I admit I am not a fan. If anything, I think I would like something with vertical tab stops more:

[ test "3 *"   <| \_ -> repeatStr 3 "*"   |> Expect.equal "***",
  test "5 #"   <| \_ -> repeatStr 5 "#"   |> Expect.equal "#####",
  test "2 ha " <| \_ -> repeatStr 2 "ha " |> Expect.equal "ha ha " ]

Please see Elm translations form this collection, and see if any patterns presented there would be applicable to this translation. For example:

• Reconsider formatting of fixed tests and example tests into something with at least consistent indentation.
• Since there is quite a few fixed tests, see if they could be composed in a more data-driven fashion, like, for example a list of [{ str, repeats, expected, title }], and mapit into a list oftest`.
• Since the kata is targeted at absolute beginners, consider adding example tests for some edge cases: 0 repeats of a non-empty string, non-zero repeats of an empty string, one repeat of a non-empty string, etc. Make sure that there are fixed tests in the full test suite which correspond to such edge cases.

Elm translation translation added :)

i cannot believe i solved this lol