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

Cleanup of TestActorRef constructor, see #2728

Browse source 
* Don't expose internal classes in public constructor
This commit is contained in:
Patrik Nordwall 2013-04-08 12:02:21 +02:00
parent 90905907c5
commit 9bf46e476c
3 changed files with 10 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -82,11 +82,10 @@ Due to a limitation in Scala’s type inference, there is only the factory metho
shown above, so you will probably write code like ``TestFSMRef(new MyFSM)``
instead of the hypothetical :class:`ActorRef`-inspired ``TestFSMRef[MyFSM]``.
All methods shown above directly access the FSM state without any
synchronization; this is perfectly alright if the
:class:`CallingThreadDispatcher` is used (which is the default for
:class:`TestFSMRef`) and no other threads are involved, but it may lead to
surprises if you were to actually exercise timer events, because those are
executed on the :obj:`Scheduler` thread.
synchronization; this is perfectly alright if the :class:`CallingThreadDispatcher`
is used and no other threads are involved, but it may lead to surprises if you
were to actually exercise timer events, because those are executed on the
:obj:`Scheduler` thread.
Testing the Actor's Behavior
----------------------------