5 kyu
Thinking & Testing : Wind whispers
Loading description...
Puzzles
Games
View
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
JS fork
Broke my mind))))
Approved
Error message plainly shows that I am returning the expected output, but it is marked as incorrect.
Are you sure? there is 6 person solved this kata. Can you paste the result or code here?
Sure, here's what I'm getting:
✘ Expected: Can you hear me? hear me r me me e e..., instead got: Can you hear me? hear me r me me e e...
Am I overlooking something there? They look the same to me. I'm confused!
Looks very strange...
Can you paste the code here? and mark as having spoiler content
This comment has been hidden.
I can't submit solution.... When I submit, an Error post, about "SSLv3", don't know why...
I thought I had found the culprit: an extra space after the question mark. But I have checked my code and even added an extra .trim() for good measure, but this problem still persists. My actual output matches the expected output, but is being marked as incorrect.
or
Thanks for that help. I'm not good with regular expressions. (I avoid them like the plague.)
These tips got me a little farther, but now I'm failing on various random tests. My code is turning into a mess, so I think I need to take a fresh approach to the whole thing. I think that is exactly the cool thing about your Thinking & Testing katas: As you discover more conditions, the challenge is to go back and refactor your code to account for them from the start, instead of just patching it up with more and more specific tests.
Thanks for the help. It might take me some time to come up with my new approach to this one.
Good luck ;-)