This kata is brilliant, it took me quite some time to pass all the tests. Well done!

Similar to my solution, but more elegant! I like it!

This Kata is one of the best ones yet! I enjoyed it a lot! Good job mate!

Thanks for the response. What I noticed is that the test actually looks like this:

assert.strictEqual(expected, next(), "No modify expected variable");

If this is the case, it means that I need to return previous value of expected, not next, since expected was already executed, right?

This is truly interesting kata, but if this is the case then the whole kata is a bit missleading.

I will try to solve it either way!

The description actually said enough, it's on you to be creative and try to figure out what is happening. In realaity you rarely have 100% information of the problem, but instead you get only small portion of it and need to figure out a solution ;)

I can't pass No modify expected variable test, even though right before the return I see in the logs the correct value!

And I am not modifing the expected value so the error description makes no sense.

Can I get a hint what might be wrong? I am pretty sure that my solution should work.

wow...

Just wanted to express my disappointment with level of this kata. The kata is actually interesting, but wrong level.

Why is this 5 kyu? It can be solved in literly 1 minute...

The most annoying challenge ever.... Wasted 1h of building a solution, only to fail to handle 100 different unexplained cases of difference spacing... The challanges should be focising on logic, not spacing and design IMO....

This is a classic function hijacking kata. I misunderstood it, since I though that "spyOn" should actually spy a function, instead of returning a modified version of provided function(with ability to count args etc). By "actual spying", I mean that once function is provided to "spyOn", you call original function and read the result from the spy instance.

I'll make sure to read the description more carefully next time ;)