Skip to main content

Akka Concepts - Testing Actor Systems

Remember that actors interact only using message passing. In order to check actors behavior you can do it through the messages sent to them and back from them.  So how do you test actors? You send them messages :)
To test actors that communicate only with messages, you need to send it a message and get reply back and check it.
akka has a TestProbe
val p = TestProbe(); // record incoming messages in queue so you can assert and verify them.
Creating actor system for tests:
implicit val system = ActorSystem("TestSys")
val toggle = system.actorOf(Props[Toggle]) // this is the actor we are going to test.
val p = TestProbe() // this is the test client actor which will record the messages.

p.send(toggle, "How are you") // probe --> tested actor: how are you?
p.exepectMsg("happy") // assert result is happy.
To have the probe actor created for you:
new TestKit(ActorSystem("TestSys")) with ImplicitSender { // we are in probe actor.
  val toggle = system.actorOf(Props[Toggle])
  toggle ! "how are you?" // we are already in probe actor.
}
managing external dependencies
Some of your actors might need to access database what do you do it?
  1. Dependency Injection
  2. Just Override - Add overridable factory methods
class DBManager extends Actor {
  def props: Props = Props[DBWorker] // Override this method when you want a fakeDB!
  
  def receive = {
    ...
    // Do not use context.actorOf(Props[DBWorker]) instead use the factory method see below:
    val dbworker = context.actorOf(props, "dbworker") // So we can override the def!
    ...
  }
}
In our case we have used def props and we refer to it when creating the actor.
How to probe messages sent to parent?
The parent is the Guardian actor if the system created it for us.
So we need a StepParent which forwards all messages to probe.
class StepParent(child: Props, probe: ActorRef) extends Actor {
  contex.actorOf(child, "child")
  def receive = {
    case msg => probe.tell(msg, sender) // forward all messages to probe!
  }
}
In a similar way we can create FosterParent actor which listens to all messages in both directions from child to parent and vice versa.
Define your test class
class GetterSpec extends TestKit(ActorSystem("GetterSpec")) with ImplicitSender ...
A test case snippet:
system.actorOf(Props(new StepParent(fakeDBWorker, testActor), "name")) // testActor is given by framework it's the probe.
expectMsg(IDidMyWorkMsg) // we expect a message IDidMyWorkMsg
So in general you send messages to your actors and you use expectMsg to check the messages they send back.
BOOK: the best book I have found for working with akka actors, it's surprisingly much better than all others, as it drives you through of a flow of building an app, making mistakes and the continuously improving the design of your app.  The book is: "Mastering Akka"


Comments

Popular posts from this blog

Keychron Q1 vs GMMK Pro: A Comparative Review

Introduction Mechanical keyboards have become increasingly popular in recent years, and with a plethora of options available on the market, choosing the right keyboard can be a daunting task. In this blog post, I will be comparing two highly rated 75% mechanical keyboards - the Keychron Q1 and the GMMK Pro. Build Quality and Sound Profile The GMMK Pro has a stiff plate and does not move, making it suitable for mechanical switches that bottom out. This creates a noisy ring on the brass plate, especially with double-shot SA caps that produce a higher pitched metallic sound when bottoming out. The Q1, on the other hand, features a plate that sits on spongy spacers, which absorb the shock from typing, resulting in a smoother and softer typing experience. The plate also moves slightly when bottoming out, which is a unique feeling. When it comes to sound, both keyboards are not significantly different, but the GMMK Pro tends to be a little more hollow due to its stiffer plate. The K

Dev OnCall Patterns

Introduction Being On-Call is not easy. So does writing software. Being On-Call is not just a magic solution, anyone who has been On-Call can tell you that, it's a stressful, you could be woken up at the middle of the night, and be undress stress, there are way's to mitigate that. White having software developers as On-Calls has its benefits, in order to preserve the benefits you should take special measurements in order to mitigate the stress and lack of sleep missing work-life balance that comes along with it. Many software developers can tell you that even if they were not being contacted the thought of being available 24/7 had its toll on them. But on the contrary a software developer who is an On-Call's gains many insights into troubleshooting, responsibility and deeper understanding of the code that he and his peers wrote. Being an On-Call all has become a natural part of software development. Please note I do not call software development software engineering b

LeetCode 51 N Queens

The problem Input integer n Place n queens on n x n  board Q  means queen at cell .  Means empty space Queen can move in any direction Horizontally Up Down Diagonal neg + pos The Trick, let's say for 4x4 Understanding Notice that each and every queen has to be in a different row ! Notice that each and every queen has to be in a different column ! Notice that each and every queen has to be in a different positive diagonal ! Notice that each and every queen has to be in a different negative diagonal ! State - Set - is queen in column, posDiag (row-col), negDiag (row+col) Which rows have queen - do not have to store in state we just loop the rows Which columns have queen - store in state ! Which posDiag have queen - store in state! Which negDiag have queen - store in state! Trick posDiag -> row - column = constant Every time we increase row we increase column negDiag -> row + column = constant Every time we increase row we decrease column Loop 1st queen 1st row Can put first q