I have updated tests to include more information about what is being tested. Hope that makes them more clear.

Alright, I resolved this issue. I was making the mistake of testing implementation rather than output. Math.random is no longer being stubbed.

Thanks for the input. I'll see what I can do about adding more expressive tests.

Thanks for the heads up!

Edit: This should be resolved. Thanks again!

This is issue is definitely related to the EmptyList at the end of the LL being changed. If you run into this issue make sure it isn't being modified anywhere. Don't just check your remove method. That test really needs to be updated to be more clear.

Would be great if there were accurate stack traces. It makes debugging complex problems nearly impossible.

Your codewars avatar will match your github avatar once you link your github account through the codewars account settings page. It might use avatars from other social media too, but I can only confirm that it works with github.

There should be away to save progress for kata. So if you need to come back later to finish a kata you can. I have noticed that sometimes if I close the kata and go back to it later my work will still be there, but other times it won't. There needs to be a way to save progress manually.

The kata was specifically for solving easy sudoku(as described in details). Solving harder puzzles would be a different kata.

There should really be some test cases where the string to decode is longer than 66 characters.

It would help if the rules were written in list format rather than written out in a paragraph. Just to make refrencing the rules a bit easier and faster.

This ended up being a bug.

"A single call should return the number passed in" is thrown if the test Test.expect(add(1) == 1) fails.

That test is passing in my test cases but failing in the kata test cases. The test is exactly the same so it has to be something in the run environment.

Because the instructions stated not to use dam or Hm.

excluding decameters and hectometers

This was probably to simplify the problem.