On Wed, Apr 23, 2014 at 12:12 PM, Ryan Tanner <[email protected]> wrote:
> We like to isolate side effects (DB, S3 stuff, etc) in their own actors > and include them in the constructor of the actor doing the actual work. > Then we can just use TestProbes when we construct the worker actor in unit > tests. > > In our integration tests, we use concrete actors for everything and let > them actually hit S3 and a MySQL instance on our CI server. > +1, essentially -- I maintain a separate Persistence Actor for each major category of the work, and pass around a factory interface for creating them. This produces the real DB-based ActorRefs in real code, and stub Actors for low-level testing... -- >>>>>>>>>> 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.
