Understanding this kata and how to solve it is pretty very challenging in fact.

textwrap module is forbidden in Python. Seems a good idea but restrictions must be stated clearly in the description.

In java, and only in the random tests.

The test is fine.

Read the rules again:

• Fit as many words as you can on a single line.
• Always try to break on spaces.

hello is 5 char long not 7, that confuses me

• in what language?
• with "test" or "attempt"?

(I thought I already fixed that... :s )

For the sample test ("this is a test", 4) , it says that the output should be "this\nis a\ntest" - this is wrong?? Instead should it not be "this\nis\natest"?

hello and world are two words, the limit is per line. "hello world" is 11 chars long, so your function should break it, what's misleading?

In the sample tests for python there is this example:
("hello world", 7) -> "hello\world"
Am I wrong or the counting here is misleading?
Obviously hello doesn't match the 7 limit.
This confusions sadly deter me from attempting the challenge

Heyo, in the random tests, some lines have trailing spaces in their solution. (i.e. a line in solution will look like "lSHG[(space)]") I don't believe this is intended as there are no regular tests for this feature, and when changing my solution to account for these "trailing spaces" the regular tests fail.

Really nice. Looks very simple at first and then you detect the edge cases.
Thanks! Big fun (after you fixed the test data bug :))

Nice one!

duh, sorry about that... (I introduced that problem yesterday when I quickly patched up some random tests)

handled.

The random also generates whitespace-only inputs sometimes.

So e.g. I'm getting:

' ' should equal ''

The inputs '␣', '␣␣', '␣␣␣'... clearly violate the task description:

Input text will be the empty string or a string consisting of one or more words separated by single spaces

The input foo␣␣bar is also not allowed by the spec. Yet still is occasionally given in the random test suite.

And of course, the test is being nay darn strict about the (unspecified) rules of whitespace processing. Couldn't it assert actual.strip() == expected.strip() at least?

... So nah thanks, I'll just skip this kata.