The description could clarify that no parameter x is provided, instead, it simply refers to the common sum of all rows/columns/diagonals if such exists (i.e. the user has to figure out some value x to compare to).

Nice point.

Not used to this testing framework.

Thanks for info, should be fixed!

I hope that i managed to fix it all now.

Improved description, used some of your wording.

Hope that now it is more clear.

The following three explanation points are unclear, what square are we talking about or comparing with????

• For example above, if gap would be 1: square would be valid.

• If expected gap would be 2 or other value - the square would NOT be valid.

• Progression (gap between numbers in sequence) has to be equal to given function param: gap. (Solvers can get confused with the sequence being vertical, horizontal or diagonal, which is not, instead, it's the arrangement of all numerical inputs in the 2D array in sequential order)

The other kata does not require to check for arithmetic progression with a given gap and also accepts duplicates.

Log message is reversed (expected true to equal false if I return false) for JavaScript and TypeScript.

Hi,

Sounds good, now. Some tiny things to change:

• the "Invalid cases should be detected (manual tests)" tests should be put before random tests (because that's the way it's usually done on CW)
• missing sample test(s) and fixed tests (in the full test suite) involving the gap argument
• the last batch of random tests should be merged with the batch about gaps. Ideally, a list of all kind of generator functions should be built, then shuffled, then used to make the different tests (do you see what I mean?). That way, yu can control how many random tests of each kind you will do (and currently, there aren't enough invalid gaps tests

Cheers

Should be fixed ;)

Should properly remove character by class & spec: expected [ Array(15) ] to deeply equal [ Array(15) ]

You need to set chai.config.truncateThreshold = 0 like this:

import { assert, config } from "chai";
config.truncateThreshold = 0;

Posted by mistake, wanted to check it, why it is passing current validation...

Updated description, tests and function declaration

Added test case which invalidates it.. but i also don't know kind of magic this is ;)

Change requirements of kata, so.. it also invalidates this (and others) solutions.

Updated description, hope it will be now clear.

Oh, now i understand what you meant.

Today i learned one more thing about js. Thanks. Will fix.