Ok, the fact that "your output" is considered [] here is because not any of the words you returned are actually part of the expected output (actually, they aren't even what should be considered words, here, see below).

In the assumptions it says: A word is a string of letters (A to Z) optionally containing one or more apostrophes (') in ASCII. (No need to handle fancy punctuation.)

That requirement is telling you what should be considered a word, and not of what is made the input. The sentence about punctuation just means that not any punctuation will be part of a "word", not even an apostroph. I guess I should just removed/reword that sentence (you're not the first one to get trapped by this). So, for now, most of your "words" aren't actually:

VyOmbs;!.VyOmbs--_:VyOmbs/:_OXbFe;!;.,OXbFe-/,VyOmbs_- ;/ZYNVztSUZ/ VyOmbs!;, ,VyOmbs.:.
......   ......    ......   .....     .....   ......     .........  ......     ......         <<< what you should actually match, according to the description

'Hope this helps...

cheers

Hi,

Python, I see (according to your profile). I can tell you, there's no issue in python. The random tests are generating random strings, with random "words". Random chars, actually. So nothing abnomal here.

General note about the local definition here, on cw (generic message, some parts don't apply here, but, just to let you know).

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.

cheers