Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
Seems like this solution is now obsolete, no?
Thanks for the fix, SteffenVogel_79! My solution passed the tests.
This comment is hidden because it contains spoiler information about the solution
Thank you for confirming that the ruby-test has an issue, SteffenVogel_79
Sorry to confuse. I deleted my response in that comment because I worked out GiacomoSorbi's example but shifted forward 8 iterations instead of backwards 8 iterations (-8).
My Ruby code above is copied and pasted exactly from the training area which produced the test result I noted above.
Edit: oops, moved forward in my original response. I see your point. Thanks.
Example of a failing random test that seems to be incorrect (unless I'm misunderstanding something, which is quite possible):
This comment is hidden because it contains spoiler information about the solution
It seems like I'm still experiencing this issue in the Ruby version. Is it possible that the Ruby version wasn't updated with this fix, GiacomoSorbi?
Or maybe it's a different problem. Basically, all of the regular tests pass fine, but the random ones fail (unless they pass just out of luck, for example don't have vowels in the strings). I'm wondering if there's something wrong with the random test generator for Ruby.
I may be missing something, but I'm terribly confused as to what that would be, since all of the regular tests pass.
The random test cases dont' make sense to me, e.g:
Testing for AUCUUAAGGACAAGCAUCUGUGUC
✘ It should work for random inputs too - Expected: "", instead got: "ILRTSICV"
It is unclear as to why this case should return an empty string rather than be translated. I'm probably missing something.
This seems like it should be clarified in the description.