It would be nice to be able to trigger repeated messages with a generator (Producer).
instead of
tc.trigger(new Msg(1), port);
tc.trigger(new Msg(2), port);
tc.trigger(new Msg(3), port);
I might want to write:
tc.repeat(5).body();
tc.trigger(newMsg(), port);
tc.end();

Also I might want to do a one request multi response type of behaviour. So I would like the future from the answerRequest to be able to be used as a generator(Producer) for my messages.

Currently the future trick for 1 request multi response doesn't work because in

once the future gets invoked you set the event and thus future invocations will see the event set already.

From @o-alex on April 25, 2017 13:48

Direct.Requests need to be triggered from a component so that they get their origin set.
Example failing test:
https://github.com/o-alex/kompics-testkit/tree/master/src/test/java/se/sics/kompics/testkit/directreqresp

Copied from original issue: iffyio/kompics-testkit#1

From @o-alex on April 25, 2017 13:49

An exception thrown within Kompics is not handled by framework. The following test throws and exception and the test finished correctly, even though the exception was unexcepted

Example test:
https://github.com/o-alex/kompics-testkit/tree/master/src/test/java/se/sics/kompics/testkit/directreqresp

Copied from original issue: iffyio/kompics-testkit#2

We need to do the same in the testing framework that I did in Kompics Java, back, when I first wrote Kompics Scala, that is separate out what the (test-)runtime requires to be able to interact with the CUT into an interface or abstract class (or multiple) and then select whether to use a Java or Scala implementation of this abstraction based on the the actual runtime type of the CUT.

Otherwise we won't ever be able to have a working Scala DSL, or even just use the testing framework with Kompics Scala components.

Since the semantics for interleaving inspect with expect and triggers in the Kompics model are unclear now, inspect should be removed until clearer semantics can be implemented.

See the Slack History on Inspect Issue.txt for the conversation detailing this issue.