can somebody explain to me how or where the optimal index is passed on for the iteration through the next line. It seems like each iteration of j passes the optimal place And value at once. Is pyramid used then as a object with multiple properties? Ie the counting and the index? Thanks!

Your code is wrong, read the error messages:

You should 'pig' "O tempora o mores !" - Expected: 'Oay emporatay oay oresmay !', instead got: 'Oay emporatay oay oresmay !ay'

Leave punctuation marks untouched.

ok thanks. Retyping this worked. Now I am not sure if opening an issue makes sense. Do you know what might have coused this issue. I think I had a similar bug before. Is this a global problem?

Could you try typing the whole return line again? The tests your code is failing are the ones that contain spaces. If that doesn't work, sure, open an issue.

Ive tried Node v8.1.3 and
Node v8.1.3/Babel. The other ones can be selected. Should I create an github issue?

That's weird, try selecting a Node version to see if that changes anything.

Your code works (I've copied and pasted it), I don't see any error message.

I thought this is a problem since my outputs that were logged by the tests match the ones which were expected exactly.
Thanks for the guidline-refresher.
Sorry, I forgot to post the output:

Test Passed: Value == 'emocleW'
Expected: 'Hey wollef sroirraw', instead got: 'Hey wollef sroirraw'
Expected: 'This is a test', instead got: 'This is a test'
Expected: 'This is rehtona test', instead got: 'This is rehtona test'
Expected: 'You are tsomla to the last test', instead got: 'You are tsomla to the last test'
Expected: 'Just gniddik ereht is llits one more', instead got: 'Just gniddik ereht is llits one more'
Expected: 'ylsuoireS this is the last one', instead got: 'ylsuoireS this is the last one'

Check if the string your function is returning doesn't have trailing spaces.

Hi,

Not an issue, a question. Generic message below:

Seems you're "rather new" to cw, so here are some general guidelines about the comments:

• Issue: problem in the kata itself (description, wrong tests, wrong internal solution...)
• Suggestions: well, I guess that part is clear
• Question anything else that is related to you having a problem solving a kata -> that's you, currently.

When you post issues:

• provide ALL the useful information:
  • language
  • input
  • outputs (actual expected) when relevant
  • error message when relevant
• check, DOUBLE check that this IS an issue, meaning that the problem is in the kata itself and not in your code. If it's in your code, post rather a question
• if you pass this step, you still have to prove/explain what the issue is (and if you can provide fixes, it's even better)

When you post a question: well, most of the above apply too x)

When you post code, use proper github markdown, so that it's readable.

And for your current problem, did you check what are the inputs/outputs to try to debug your code on your own?

cheers