A couple suggestions:

1. Description

• Typo in the word "emotion" ("...message based on emotoion:")
• Make the task read more like "...message based on emotion (example output is given for greeting = "Hello"):" to help generalize the task; unless "Hello.", "HELLO!", and "hello." are supposed to be the fixed output for the three lambdas, regardless of the greeting, in which case that should be specified.

2. Test cases

• Add a few more test cases, e.g., have msg be "Goodbye", "Hola", "Aloha", "'sup" (this would make things more difficult, though), and maybe some random strings.

Needs more test cases so that users can't hardcode strings inside the lambdas.

Failed test cases should give hints about what inputs were provided. Please don't leave them out "on purpose". It makes it frustrating, not challenging in a positive sense, for kata authors to consistently not provide feedback on failed tests.

Or if not display the exact input, at least give a hint as to what sort of input is causing the failure.

I had this problem too. Either the instructions or the test case needs to be fixed. Kata authors need to be aware that this makes their katas annoying and unenjoyable. Please be explicit about what you expect out of our code and be consistent in your test cases!!

When a solution fails a test, it would be helpful to display the input that caused the failure.

This is a good exercise, but I thought the instructions were difficult to understand and I think they need to be more explicit.