I'm working on the JS kata and have reached the following hurdle.
Given the following grid of characters:

[ 'JXVXXWJEAZDUYGSFIMWN',
'JITTHJXNEVXXWGKPNHGA',
'FAKBSDKHEJEQQKOGLYBY',
'GRLMRZATFBJCDCIWOJFI',
'ZVVKXIHPENDLIAKJSYXR',
'ZBADZXHDKOIFBQUXWFPQ',
'PTCWMZLXANXMRHZACDCT',
'FAPGXBPPPYJZQITYMHNV',
'BFGZTKHCLFWZGDNXORYL',
'XYTTPFAGIWIRAWPQCVRA',
'PQBVZUNVLSLXESIBYFJK',
'KXUKTRYHJAUDZSVCFNVT',
'XWWCQCMICCECQINOPBNG',
'FHSHXLZUCUQDCWZDPXMM',
'XNYWNJEBTBUKDNNKYFOA',
'CPBSBNPZNPPNQAKHHGYX',
'ZMTOKDMZIMCNEHCLFBDI',
'WZVKQAJLRDKXLECCATMH',
'ZNHQTJDQPZNFDBACQYGO',
'VNLUZFLQHPOXKXCNEDOZ' ]

and the random test string of 'NHQTJDQPZNFDBACQYGO', my solution found a horizontal match at [18, 1]... the second last row and first column.
The expected result is "Word not found". Not sure what I'm missing here. I've reviewed the kata details multiple times and can't quite seem to figure out what I'm doing wrong.

Thanks!

From what I could find, there is one in Python only that is quite similar which I didn't see before, sorry! - https://www.codewars.com/kata/word-search-grid

There is also one in Javascript but with rather different parameters and solution required - https://www.codewars.com/kata/word-search-puzzle

Hopefully it's unique enough (and bug-free!) If you have any more feedback with the random tests added just let me know. =)

So it's approved now;-)!

I've now added the random tests :)

I have now added an extra 25 random tests for each validation.

Same with "https://www.codewars.com/kata/route-calculator" which is approved as 4kyu since yesterday(?)... ;-) It's sometimes "difficult" to say "a duplicate";-)...

Aren't there already several of these kind of "search words in a rectangle of words" katas?

Waiting for random tests ;-)

I'm working on it and hoping to add random tests sometime in the next few days.

total fail there :)

The chart is reduced now to a .6 - 1.4 range.

Sure :)

(Also you should reply on the comments by clicking the Reply button under the comment, so that everything is gathered inside a single thread.)

Hi Voile,

There is no reason the chart in the Kata needs to go beyond 1.4 bar which is the max safe range for normal recreational diving. I guess I included the wider range because the idea is that the chart is an external source of information the programme needs to reference, and it is published with wider ranges. So in a real life programming scenario, if you were writing code for a dive computer, you would need to limit the range of the input data to suit your programe.

However, as it's confusing I can remove this easily and will do so now. (In writing this Kata I realized how complicated diving physics and safety is!)

If we're only ever allowing oxygen level to reach 1.35 before declaring it's unsafe, why the chart has values up to 1.8?