raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

make available TestKitLight without implicit ActorRef

Browse source
This commit is contained in:
Roland 2011-05-29 22:47:55 +02:00
parent 6b6ec0df72
commit 2852e1a763
2 changed files with 23 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

17
akka-docs/scala/testing.rst
View file

@ -387,6 +387,23 @@ invariably lead to spurious test failures on the heavily loaded Jenkins server
internally scaled by a factor taken from ``akka.conf``,
``akka.test.timefactor``, which defaults to 1.
Resolving Conflicts with Implicit ActorRef
------------------------------------------
The :class:`TestKit` trait contains an implicit value of type :class:`ActorRef`
to enable the magic reply handling. This value is named ``self`` so that e.g.
anonymous actors may be declared within a test class without having to care
about the ambiguous implicit issues which would otherwise arise. If you find
yourself in a situation where the implicit you need comes from a different
trait than :class:`TestKit` and is not named ``self``, then use
:class:`TestKitLight`, which differs only in not having any implicit members.
You would then need to make an implicit available in locally confined scopes
which need it, e.g. different test cases. If this cannot be done, you will need
to resort to explicitly specifying the sender reference::
val actor = actorOf[MyWorker].start()
actor.!(msg)(testActor)
Using Multiple Probe Actors
---------------------------