I too noticed this.

But the test cases don't actually check if an error is thrown.

Seeing the ins, outs, and expected is great, as is having an established test base to examine. However, you've made it trivially easy to write a program that goes "If [turtle sentence] return 3.67, if [book] return -1.06 [etc.]" In addition to the tests you have, it's good to have randomized tests (perhaps built Mad Libs style, in this case, so the sentences/words aren't total garbage).

I'd say this kata is already way too easy for 3 kyu, and there's no simpler version of this problem that would be interesting.

this is codewars not codekindergarten ;-)

I would even go a step further with refactoring the name of the method and call it 'santa_clausable?'.

also, this method returns a boolean and so it should end with a "?" like "is_santa_clausable?"

haha, goal reached :D

You're absolutely right. Thanks for letting me know, should be fixed now.

Thanks—though I actually quite like to see all the tests when I'm doing a kata. I find it frustrating when a test I cannot see is failing.

thanks! Edited :)

ehm, yes, of course ... I will update it, thanks ;)

Yepp, that was also the reason for me to pick "6 kyu" as estimated rank.

Thanks for the feedback, I'll state that it should be case-insensitive and add a decent test case.