Your sample test is missing the end paren and semicolon!

Sorry for the late reply. It says the test cases can no longer be edited, so I'm not sure what to do about that o-o

This doesn't seem like an issue with the kata, so I'm going to resolve it unless anyone offers further insights

It seems like your output is lacking spaces in several places, like "consecteturadipiscing" in the second row and "Aliquamnec" in the third row

Well it looks to me like when list.next immediately returns false (when there's only one list item), your function never calls [].concat and therefore never creates an array.

It's been a month and no one else has reported this error, even though you reported it to happen every time a solution is submitted. I'm going to mark this issue as resolved for now.

Ah, I see. I got rid of the "None" test case. Thanks!

I don't see a blank list in any of the test cases. Which language is this, and was it a fixed or random test case?

It happens every time? That can't be right; I haven't seen the random tester generate a single word longer than 10 characters. Your failure message is also incongruous with what I see... it shouldn't be displaying any text between "Testing width 10" and "Failure! You returned:" I have to conclude either the two of us are experiencing different version of the kata or something in your solution is messing up the tester.

I can't figure it out. I've been unable to reproduce the error (even if I make the tester choose width = 10 every time) and I can't find a mistake in the code. MMMAAANNN even designed the text generator to return a custom error message if it detects any words longer than 10 characters.

Maybe you somehow used an old version of the kata, or it's been fixed between then and now. Can you try to reproduce the error?

The random text generator isn't supposed to generate any words that are longer than the provided width. I'll see if i can find out what's wrong ASAP

Which language is this?

i dont think any of the cases ask for an empty list, but ill mention it in the description

good idea! changed it to 'next'

gonna go ahead and resolve this issue