Try to separate your login between internal business actors that you can unit test and a gateway sub-system to connect to external systems. The gateway would translate all the connection logic from the external domain to your internal domain, including errors and other possible states. You could need to handle state and/or any kind of retry logic/failure compensation etc.
The external system (http) would appear as a message-driven actor to your bounded context, speaking your domain language, thus being unit testable. The gateway subsystem will be independently integration-tested. You could have a mock http server in your integration tests to verify the external calls and the translation. Cheers G On Sunday, 24 May 2015 10:52:10 UTC+2, Avi wrote: > > Hi , > I have an actor that is sending outbound http request. > I would like top test that actor ,is there an option to mock that call ? > what is the correct way for doing that ? > > Best > Avi > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
