Likewise. Very frustrating.

The description says:

(return a positive integer unless conditions are not fulfilled in which case return -1)

Besides that example gives : h = 3, **bounce = 1**, window = 1.5, result is -1 where you can see that the condition on bounce is not fulfilled hence -1

I felt exactly the same when I was working on this Kata - never thought those "conditions" are not range of input.

Think this could be improved by giving a more explicit explaination like "validatation of those input to see if they fulfill the conditions are necessary".

It seams to me description was written by 5yo girl with some serious brain damage.

Damn, I also have toString() after the toFixed method. Good thing I read this!

Can't unfortunately change anything now, too many codewarriors passed the kata:-(

My pleasure man and let me know if I might be of further help :)

I jax and bravo for properly using a spoiler tag; it is rather difficult to guide you without robbing you of the fun of solving it yourself, but may I suggest you to add a console.log statement to print all the steps and try to get what does not work?

Good suggestion; I've tweaked the explanation to be less misleading hopefully. Let me know how it works for you.

As for the ambiguous test message, unfortunately it looks like the tests are locked, now. Sorry about that.