Timing issue with tests

Regarding our discussion here, there is a still a timing issue of some sort with the tests.

Yes, lastState exists, but stateNumber console twice when stateNumber===1. I don’t know why it executes twice, but this is the reason for the tes

It doesn’t run twice for stateNumber===1 - I was able to change it back without problems and the test still runs green… it’s what I mentioned earlier - there is some kind of timing issue still, and somehow, calling console.log at the right moment fixes the problem.

So console.log somehow has side-effects affecting the timing here - I don’t have an explanation, but it’s completely repeatable: remove the console.log statement and the test fails - leave it in there and it passes. This is a real JavaScript moment. I can feel my brain melting. 😶

[mindplay-dk]

Let’s leave this issue here until we see if tape changes anything.

[yisar]

I suspect this is a unique bug of jest. console.log is a time-consuming behavior, which plays a role of delaying time.

Unfortunately, I can’t find the reason of it. We temporarily hack it, and then spend some time waiting for the reason to be revealed