payment: Fix instability in `fast` tests where we don't reset the clock
It is unclear whether resetting the clock is best done after we initialize the stack - I would think before
but this is what we typically in other part of the code, so I wanted to keep in homogeneous.
@@ -163,6 +163,7 @@ public abstract class PaymentTestSuiteNoDB extends GuicyKillbillTestSuiteNoDB {
paymentExecutors.initialize();
((MockPaymentDao) paymentDao).reset();
Profiling.resetPerThreadProfilingData();
+ clock.resetDeltaFromReality();
}
@AfterMethod(groups = "fast")
