- make normal filters available for all four log levels
- allow filtering for
+ exact and complete message
+ start of message
+ regular expression
- keep count of occurrences if requested and verify correct count at end
of filterEvents/filterExceptions block
- remove akka.testkit.Testing (sleepFor replaced by Duration.dilated.sleep)
- remove Duration.timeFactor (needs config -> AkkaApplication)
- TestLatch needs config -> AkkaApplication (was forgotten because used
directly System.getProperty)
- lots of scaladoc for TestEventListener infrastructure
* TradingThroughputPerformanceSpec and microbench.TellThroughputPerformanceSpec for throughput with high load
* TradingLatencyPerformanceSpec and microbench.TellLatencyPerformanceSpec for latency with moderate load
* Removed usage of JUnit
* Removed all usage of latches for flow control, instead replies with ordinary tell. This means that trading sample generates 4 msg for each transaction.
* Removed req-rsp test from trading, since it adds complexity and isn't realistic
- revise timings to make them more robust (granularity changed in
general from 100ms to 500ms)
- make one test more deterministic by awaiting context.hasMessages,
which has been added for this purpose; is the same kind of “non-racy”
as isShutdown
- add static version of TestKit.awaitCond (checked that it does not
conflict, even when “import TestKit._” is used; seems like imports are
not even searched if the symbol is found locally)
It seems that 2.9.1 has a bug when a constructor argument is passed to
superclass which makes a public field out of it under the same name:
scalac got confused and generated invokespecial byte-code which is
rejected by the verifier. One could argue that the verifier is too
strict in this case ...
So, I changed the names of the constructor arguments by prepending an
underscore and thus avoiding the clash.
- make sure that needed log channels are subscribed
- do not .stop() applications within test cases, that’s no good for
following test cases (might change when we move to one app per case)
- re-enable and fix (adapting to message format changes) the life-cycle
logging spec
