Kata

Sorry, but I haven't understood. Where do you get the bug?

a maze: w _ w w w w w w w w w _ w w w w w w w w w _ w w w w w w w w w a _ _ _ _ _ _ _ w w b _ _ _ _ _ _ _ w w c _ _ _ _ _ _ _ x w w w w w w w w w w

modified maze araay at a ， then point b and c will Change together (my English so bad...)

I'm sorry but I still didn't fully get the issue... I have personally tried to randomly generate as many mazes as I could, but never encountered any issue.

Thanks for the appreciation, Katbow! The array of values '_'ending with 'x' should be quite useful for the codewarrior to debug the solution. Getting the right path is the most valuable info of course, and most of the tests check the path rather than the array. But you still need to get the values array right to pass this kata.

Hi andrewMacmurray!

• the test cases first verify your solution for the first maze (1st group of tests), and then repeats the same group of tests for different mazes (including some randomly generated ones). The description of the group of tests says "testing for 'n'th maze".
• The group of tests first verifies the format of your solution (independent from the maze), and then checks the content of your solution (dependent on the maze).
• Anyway, I tried just now submitting a solution as follows, matching the result in your comment.

  function getToX(maze){
  var path, values;
  return {path:[[0,0],[0,1],[0,2],[1,2],[2,2],[3,2],[4,2],[4,3],[4,4],[4,5]], values:["_","_","_","_","_","_","_","_","_","x"]};
  }
  

  You're right, it is a perfectly fitting solution for the maze in the 1st group of tests (same as in description) and, therefore, has passed all tests for that maze (1st test group). However, the same solution is not correct for all possible mazes of course, and will not pass for the second group of tests.

Ahhh that makes sense, will try it with some different mazes.

It looks a bit misleading when the errors come up as even loging the maze to the console doesn't show the random mazes generated (it just looks like it's saying the first maze is hitting a wall or never getting to x). Maybe you could update the tests to show the random mazes?

Great Kata, early beginnings of a game engine!

That's a great idea! I just remembered that CodeWars JS runs on Node, so I can just console.log the maze on Codewars! The only issue is that some of the 12 random mazes will be too big and cumbersome to be visualized properly in the console (up to 100x100 arrays!). I updated the cases so that the first two mazes (of fixed content and sizes) plus the random ones which will are smaller than 15x15 will be logged. Let me know if you find this reasonable.

Ahh forogt that N could go up to 100! (that would be a pretty ridiculous output!) could you add a conditional statement for the log? Something like

if (N < 20) {
  console.log(maze);
}

So that you wouldn't get the super huge mazes.

Yeah, that's what the tests have now (for n<16). I don't know what the optimum n is.

I see what you mean, just struggling to come up with a maze which fails my current code

For the moment I can increment n to 40. Worst case you can copy-paste the maze in a text editor on a large-enough screen (??).

Thanks! So this is an interesting output:

[
   ['_', '_', '_', 'W', '_', '_'],
   ['W', 'W', '_', 'W', '_', '_'],
   ['W', 'W', '_', '_', 'W', '_'],
   ['_', 'W', '_', '_', '_', 'W'],
   ['_', '_', '_', '_', '_', 'x'],
   ['W', 'W', 'W', 'W', 'W', 'W']
]
[
   ['W', 'W', 'W', 'W', 'W', 'W'],
   ['W', 'W', 'W', 'W', 'W', 'W'],
   ['W', 'W', 'W', 'W', 'W', 'W'],
   ['W', 'W', 'W', 'W', 'W', 'W'],
   ['W', 'W', 'W', 'W', 'W', 'W'],
   ['W', 'W', 'W', 'W', 'W', 'W']
]

Is that intentional?

Yeah, the test was checking if your path was going in steps of 1, but the error message was wrong. I confirm that you do need to start from [0,0]. Thank you for spotting it out!