It doesn't now.

The server initialization should fail if max_connections is not a positive integer.

But this is not checked properly, just checking if the input is a Numeric is enough to pass the tests.

Ah, I just noticed that the Server class initializer uses keyword arguments…

That test will initialize a server object with max_connections set and attempt to exhaust the number of connections, recieving an error when no more connections are allowed.

What's meant by 'should be configurable' for a failing test?
I'm working in the Ruby version and the Server object can in fact be set up with a given number of possible connectins. (Also all other tests pass…)

What am I (possibly) missing?

This is a beginner kata.

Added a more detailed explanation in the description, I hope it will be enough, without removing the curiosity of the puzzle...

Description needs to be more clear how the initial state grows in size.

Off by one error here. downs should default to 0.

There definately need to be more edge test cases. My code has a bug where if the team does not get to 10 yards in the first three downs it will return false, even if it got past 10 in the fourth. But it still passes all the tests.

Done, thanks!

To help with the spacing issues, you should code format all input and output examples.

Example: "GOOG 300 542.0 B"
Vs
Example: "GOOG 300 542.0 B"

And

"Buy: 263 Sell: 11802; Badly formed 2: CLH16.NYM 50 56 S ;OWW 1000 11 S ;"
"Buy: 100 Sell: 56041; Badly formed 1: ZNGA 1300 2.66 ;"

Vs

"Buy: 263 Sell: 11802; Badly formed 2: CLH16.NYM 50 56 S ;OWW 1000 11 S ;"
"Buy: 100 Sell: 56041; Badly formed 1: ZNGA 1300 2.66 ;"

I'm kind of miffed that my recursive solutions were too slow, oh well.

But there really should be better feedback on that than "Expected -1, got 23 instead".