Loading collection data...
Collections are a way for you to organize kata so that you can create your own training routines. Every collection you create is public and automatically sharable with other warriors. After you have added a few kata to a collection you and others can train on the kata contained within the collection.
Get started now by creating a new collection.
Fixed and sample tests below should be added across all languages to prevent specific range of divisor-checking solutions from passing
576992/143832
JS:
Node 18. (
mocha
+chai
) should be enabledThe
it
block message for random test block uses the wrong function name... -->Testing for mixed_fraction(${s})
Broken image link in the kata description.
The parameter name in all languages for
month
is kinda misleading because the format given is inMMYYYY
It's assumed that you should return an array of arrays with n names in it, but:
Why there is
three
in the description when each day array should containn
employee names?Description should be language-agnostic
python new test framework is required. updated in this fork
Scala translation
C#: method name should be
PascalCase
(Please refer to implementation of backward compatibility here )Floating point comparison should be used in all languages
C Translation (author inactive).
This kata is a subject to deduplication process here: https://github.com/codewars/content-issues/issues/165.
Please join the discussion to help us identify duplicate kata and retire them.
log statements in JS should be removed, with corresponding
chai
andassertion
frameworks importedPython new test framework should be used
Testing point [4658, -2364], vector [[2448, 1483], [-5715, -1431]]
1 should equal -1...
wait I think I am correct at this point... Can Someone explain it?
Tests are badly designed in all currently available languages (Python, CoffeeSCript, JS and Ruby): 18 real random tests, with a low probability of requiring result 0, and then 9 tests "Random point - on - vector line combinations", all expecting 0, and the user is clearly informed of this with test cases. This makes no sense, the inputs should be simply randomized, with a decent probability of having a point on the line.
Loading more items...