Great kata on object oriented programming and test driven development, well done.

The low rating is probably due to the incomplete description. Otherwise, it is a very good kata and quite satisfying.

Very satisfying..:)

Katas without specs and sample tests that is obviously not puzzle is not acceptable.

This kata is meant to emulate the real world where requirements change over time. This kata does not provide a specification for the final end-state up front. Instead, it walks you through a series of requirements, modifying and extending them via test cases as you go. This kata is about the journey, not the destination. Your ability to write maintainable and extendable code will affect how difficult this kata is.

This is a bullshit excuse. Either you don't have tests (then there should be design specs instead) or you do, in which case every sane person would instead ask you to send the entire test suite and read the code to understand the requirements, because it's faster and more productive. You're arbitrarily fencing people for no reasons.

The technical challenge of this kata is good and fun, but 80% of my time was spent trying to figure out what that challenge actually is. Do I need member revenue of > $1000:

1. in any one department that has > $10000 revenue?
2. summed across each department that has > $10000 revenue?
3. summed across all departments that cumulatively have > $10000 revenue?

(for anyone looking for clarification, it's #2)

I think using more specific language and adding an example scenario would increase the clarity, and thus overall satisfaction rating, of this kata.

Marked it as issue (wrong testcases, only checked for Javascript), please see your/my comment at:
https://www.codewars.com/kata/586a1af1c66d18ad81000134/discuss#58c7e1e2ad8232f52a000217

EDIT: Submitted a Python solution too, seems to me there are similar problems;-)...

I can only assume that one of your tests took more than 60 attempts. The test class simply allows the user upto 60 tries after that it will now fail the test. This should let you know why the code is failing :-)

Thanks for solving this and "Guess Who?"...please could you rank and rate both, especially "Guess Who?" becuase I think that will only need one more rank before it will pass out of beta :-). I've you've already done this, please ignore me :-)

Love the idea of this kata.

Suggesting this as an improvement because I'm not sure whether it's a bug or something on my end.

I could always get game.check() to return an array of 4 "Black"s in less than 60 calls, but the tests would never be considered passing. After submitting many times in a row without changing my solution, it did eventually pass. Any ideas why this might happen?

Nice!

Oh wow. That's embarassing. Thanks!

25 + 22 = 47.

I'm not understanding something or one of the examples is incorrect.

basket = 50
pile = 'dust83dust 45 25 22 46'
Test.assert_equals(pack_basket(basket,pile),'The basket weighs 47 kilograms')

You cannot make 47 from any combination of 83, 45, 25, 22, and 46. What gives?

@pschoenfelder,

I really enjoyed this kata and how it was implemented. Working through step-by-step was a fun experience.

I would usually say "needs random tests" but I'm a bit on the fence since the tests are already quite extensive. This may be a good example of a kata that doesn't need random tests (as has been mentioned before by @suic).

Thanks for this kata!