Sorry for being so generic but I did not want to spoil anything.

But now as I went back to look up a specific example of a failed testcase I got the problem and I could fixed it. It was just me renaiming a variable name during the skript. Sorry for bothering

how are we supposed to know if you don't give any useful info about the "possible" problem?

Generic message:

• 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.

so?

My solutuion behaves odd since sometimes it passes all test and sometimes it does not. If it produces wrong results, I check the final formular mannually and it seems to be correct. Someone running into similar issues?