Seems too similar to the Decode the Morse Code. I just ran into this myself, creating a kata before realizing it really is almost an exact duplicate of another kata, albeit with stricter performance requirements and thorough random tests etc. Looks like you're in a similar situation.. a better test layout but still the same basic thing. Maybe morph it into something different? Not morse code but Cyrillic or something? Or your own invention, and then add a twist? (We do already have quite a few 'translate the...' katas.)
EmptyEncodeTest check Decode input.
The test case is checking for an uppercase as the first character eventhough the discription states case insensitive. As this was noted three months ago and has yet to be fixed this is another reminder.
This comment is hidden because it contains spoiler information about the solution
It is really necessary for us to make the whole dictionary ourselves? That's very annoying and is a big pile of hot garbage.
Please provide something in Preloaded.
Example test has I can write in morse code as expected result but the spec says the decode will always decode to lower case.
I can write in morse code
the decode will always decode to lower case
Also, there is no test on the case insensitiveness of the encoder in the actual tests.
I did try searching for previous morse code examples but I must have still had the beta filter on. I know, it's different but the same, not sure what the policy is on this over here?
No idea how I manage this everytime! Think I've corrected it.
This is exactly the combination of:
. Not sure if I should raise this as an issue, so I'll just leave it like this now.
Phantom JS version again!
Cheers, English never was my forte!
You never know I might have to give it a go! haha
I fixed some spelllng errors as well.
Next kata, Unconformity Inc? :P
Fair play, apparently I hadn't considered it much either! I've updated the Kata to (hopefully) provide a more accurate description of the problem.