Synchronous testing checks an actor in isolation through sequential execution and deterministic effects. It uses a controlled environment rather than exercising asynchronous interactions among real actors. section 4.0 section 4.2
Use synchronous testing to inspect:
- Effects produced by the actor instance. section 4.2
- Messages received by the actor. section 4.2
- Logs emitted during execution. section 4.2
- A BehaviorTestKit to access execution effects and a TestInbox as a probe ActorRef. section 4.1 section 4.1
This is a white-box technique for internal actor logic, not a substitute for integration testing. It cannot test asynchronous calls, interaction with real actor implementations, timers, or the scheduler. section 4.2 section 4.1
