OK, same result.
In DEV (using the Shared environment) and with a NEW deployment, the trigger did kick off as expected and the tests passed.
In TEST (using M10 cluster), the trigger did not kick off when the tests ran.
So for whatever reason, there seems to be more of a delay in the TEST project…