Adam Fraser
Adam Fraser
Why not just have? ```scala suite("my suite")( suite("unit tests")( ??? ) @@ around(setupDatabase)(teardownDatabase), suite("integration tests")( ??? ) @@ aroundAll(setupDatabase)(teardownDatabase) )
@drawntotheflame Updated now!
@joroKr21 I don't think that is correct. The `TestClock` contains specific logic to sure that all fibers in the test have entered a suspended state before advancing the clock. So...
The `TestClock` monitors all fibers forked within the test and waits for them to complete or enter a suspended state before advancing the test clock. So I'm not sure what...
So is it really about this `metered` operator? What happens if you do this? ```scala def process(service: TestService, exit: Exit[String, Int]) = for { fiber ZIO.done(exit)).fork _
Right. That is the expected behavior. The `TestClock` waits for the fibers in the test to enter a suspended state before advancing the clock. I'm not surprised since there are...
Okay. Thanks for reporting. Is `zio-logging` what you are using? Happy to take a look with you when you have more time.
@joroKr21 We don't need to look at all the fibers, only the fiber that is executing that test and any fibers that it forks. So in your test for example...
Yes. If the aspect is not being applied at all that would definitely explain the problem you are seeing in your test. As far as the example where you do...
@fanf Thank you! Your issue has given me some good inspiration. Should have something soon!