Yeah, you're totally right! I must have missed that part... )

It's been years...but I will still fix it later today.

It will seem that way! Some of the tests have tickets that are just pretending to be newly created. Once a ticket has been used, remember to block it from being changed manually. The point of this is to prevent a situation where hackers would try to take a used ticket and manually change ticket.used from true to false so they can reuse the same ticket. I hope this helps!

Cool. Thanks. Someone's marked it as having a "major issue", but trying to track that person down is proving impossible... Almost makes me want to scrap this and just copy it over to a fresh kata, to let it get through. /sigh/

Trying to get this through Beta; any more problems I can help you with?

Are there any outstanding issues I can fix for you?

Ah-- sorry about that. I've tweaked the description and added a few tests for this.

Thanks for your help.

Good point. Changed this down the line, but forgot to change the description. Thanks.

And perhaps randomise the order of the ones already there.

The test cases are not random to ensure that corner cases are covered, as you stated. The correct answer to ["8", "A", "A"] is indeed 20. If you answered 10 that is incorrect. According to the spec the result must be the highest score less than or equal to 21.

Fixed. It says "Assert: a1=1" instead of "Assert: a1===1".

Ah, I see. I saw the problem in the example text fixture but missed it in the regular test cases. I hope that's all fixed now?

Ah. Took me a while to figure out which test cases you were referring to, but I think I've fixed it now?