Go translation

.

Thx, fixed.

yay thats look cool! a bug tho: 'all chars' calls wrong generator

Thanks, I've updated the translation.

• It("", func() { - I would suggest using non-empty titles, even if they would be a repeated title of a Describe block. I am not sure if the fallback value is specified and guaranteed to be provided.
• While assertion message provides descriptive values for expected and actual values, these two do not make life easier for users and do not help with recreating failing test cases and debugging users solutions. I would suggest using assertion messages, or some other means if found to work better, to present inputs fed by tests into user solution, like in the example shown by akar-0 below. This way, the output would be something like:

Incorrect answer for input="gykjgljgvyvkyuhl8nGCPakytfti;iouihmnjghyiukoi"
Expected
    <string>: "...8nGCPakytft..."
to equal               |
    <string>: "...8nGCPkytfts..."

what would hopefully make reacting to failures easier for users.

It does, one can use format strings, something like this :

     Expect(actual).To(Equal(expected), "With s = \"%s\"", s)

An easy way is to use a function to do it for all tests, fixed and random.

Thanks for your remarks.
Added fixed tests for input with only/no vowels. Fixed re-seeding.

I think default Ginko output for failed test is pretty descriptive, for example:

Expected
    <string>: "...8nGCPakytft..."
to equal               |
    <string>: "...8nGCPkytfts..."

Issues:

• Does Ginko allow for custom assertion messages? It would be good to have more information when a test fails, in an assertion message, or in a test title.
• Needs fixed tests, and ideally randomly generated tests, for edge cases:
  • input with only vowels
  • input with no vowels
• Random generator should not be constantly re-seeded.

Go translation

Go translation

'alr approved some time ago'

Hi, Swift translation added.

Swift translation added - https://www.codewars.com/kumite/5f68e1598a3830002fc6564a