I forgot to run the tests when I made the change.
I updated the test and had to copy some utilities we had in private/testing since I couldn't find an easy way to expose it in adev

Yeah better to copy what's not part of the public api

you shouldn't await if you use autotick

IIRC , it's still necessary; autoTick prevented time from accumulating (depending on how many setTimeouts we have, more would accumulate, which would be a waste of resources).

I would expect a jasmine.clock().tick(300) here.

We can change it, but it would have to be the equivalent of using a microtask flush , otherwise we'll get an error

jasmine.clock().tick(300)
await Promise.resolve()

or using only await timeout(300)

My issue is that waiting 300ms is too long (as it can add up if we do this on multiple tests).
Having a await Promise.resolve() is fine as it doesn't wait for long.

I understand, that’s exactly what autoTick is for. It avoids the main drawback of “waiting” and lets the timeout utility (which uses setTimeout under the hood) run synchronously

Using autoTick with timeout is equivalent to

jasmine.clock().tick(300)
await Promise.resolve()