ForID.runWith(Sink.foreach { e => e.event })
// Simply waiting for the result will blow up with an exception if we
couldn't deserialize.
Await.result(res, 300.millis)
}
Await.result(allPersistenceIDs.runWith(Sink.seq), 5.seconds)
}
On Wednesday, October 12, 2016 at 4:43:39 PM UTC-7, Spe
Hello all,
In order to test that no unaccounted-for serialization changes have happen
before we deploy our service, I need some way for us to *attempt* to
deserialize all currently stored events in our event journal and snapshots.
Currently, we just use the local leveldb plugin with local
this is a scenario someone else would've run into somewhere,
but I'm not finding any useful information while searching. Any advice is
appreciated.
On Thursday, April 28, 2016 at 10:16:25 AM UTC-7, Spencer Judge wrote:
>
> Whoops, forgot to change a name, that CLFSM in the second snippet
Whoops, forgot to change a name, that CLFSM in the second snippet should be
"MyClass", and the first snippet is defined in "MyClass"'s companion object.
On Thursday, April 28, 2016 at 10:15:23 AM UTC-7, Spencer Judge wrote:
>
> Hi all,
>
> The section here:
>
Hi all,
The section here:
http://doc.akka.io/docs/akka/2.4.4/scala/testing.html#Testing_parent-child_relationships
Has some good advice on doing child creation via dep injection so I could
pass in mock children during testing. That's great, but the example is a
bit of a toy because you can't
n
> simultaneously. Some times you need isolation though, I wouldn't say that
> in itself is a smell. If no single actor in your entire app can be tested
> without being isolated it may be something to think twice about though.
>
> I hope this helps!
> --
> Johan Andrén
> Akka Team,
I started writing some tests using the TestKit, and it's quite nice - but I
quickly realized the ActorSystem persists between tests. This seems a bit
odd to me, since it introduces potential coupling between the order of test
execution and their results. It doesn't feel like what I would expect
Thanks for the info Johan! I'll take a look at the suggestions. I also
think I have an alternate design where I may be able to avoid the problem
entirely. I've convinced my team to at least start a prototype with Akka
and I'm looking forward to it.
One other question - I've seen the Typsafe
Hello all,
I haven't used Akka before, and I'm considering using it to replace some
code my team recently wrote that we're finding is too complex to understand
well, and I'd like us to use a more formal structure. Akka fits our use
case very well (I'd use Erlang, but we depend on too many Java
