nope, not anymore x) (the first comment of a thread is the only removable one, but only as long as there is no answer. So.... too late x) )

(me puts down his tin-foil hat...) oh now you're just being paranoid! :)

Hey, thanks for feedback.

In general

• Yes, I keep my example tests short and treat them pretty much as "sanity" tests.
• Yes, I do often put tricky stuff only in the "hidden" tests. It's deliberate:
  • Main reason is to train the habit to read instructions carefully.
  • Second main reason is my evil twin enjoys the thought of people bashing their head on the keyboard when they find they jumped to some wrong conclusion by not reading the spec
  • Also the CW "Validate" button makes it easy to author things that way...

FYI - I do all my coding only in CW editor - maybe I am old-school, but I don't want some machine to think for me. That sounds too much like skynet. Code auto-completion is probably step 1 of their master plan.

And those working straight from the CW editors are just bad-ass. I can't live without intellisense right now ... :D

I just printed the track layout at the start of every run and copy pasted that in text files... :-)

OK. I changed the description. Thanks for the feedback.

BEFORE

It must be possible to follow the line with no ambiguity (lookahead of just one step).

AFTER

It must be possible to follow the line with no ambiguity (lookahead of just one step, and never treading on the same spot twice).

Fixed. Thank you for raising this issue.

I agree. I don't know what TestTools is, exactly. In order to work on this offline, I had to rewrite the tests to use CollectionAssert instead. Katas should not have external dependencies that aren't provided. Maybe TestTools is something that Codewars offers, but I just can't locate.

there are no performances requirements, here. So I'd say you didn't understand what to do with the data?