seems like you solved it soooo...

What about now?

Hi,

MMmmmhh... I guess that means you either didn't see or didn't understood the stuff logged to the console, telling what team is tested at what point...
Mmmmmmmhhh... Let's rebuild this with it blocks.

Note: those assertions need Test.assert_equals, if you wanna have the expected/actual thing in the error message.

Hi,

Well... errr... first, there is no Test.expect in the "attempt" part of the tests. If you see this, that means it's in the sample tests. Then, we aren't in your mind and we don't see your code. So... How are we supposed to help you, here? x)

I just tested my code on the sample tests and everything is going smoothly, so the error is somewhere in your code/algo. In this kind of case, the first step for you would be "pen & paper": retrace by hand what's happening to see what you forgot/misunderstood.

Generic message below, about the local terminology:

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.

Closing the "issue" aspect & cheers

Sorry, it's now fixed!