Attention is currently required from: jolly, laforge, pespin.

fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33979 )

Change subject: ASCI: Add tests for voice group/broadcast calls at MSC ......................................................................

Patch Set 2:

(1 comment)

File msc/BSC_ConnectionHandler.ttcn:

https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/33979/comment/c1f203c9_8cc7b... PS2, Line 68: inout charstring, CallParameters, ASCI_Event;

... Sounds simple, but then also means that they need their own f_init* etc. functions wrapping those of the components derived of to set up that port.

Adding module-local f_init* etc. functions is not really needed if you derive a new component from an already existing component (using the `extends` keyword). For instance:

``` type component FooBarCT extends FooCT, BarCT { ... };

function f_foo() runs on FooCT { ... } ```

In this example function `f_foo` can not only be called from component `FooCT`, but also from component `FooBarCT`, because the later inherits all fields/ports from the former. So all `f_init*` functions and altsteps from module `MSC_Tests` would still be usable for `MSC_Tests_ASCI`, even if it derives its own `TestCT`.

Furthermore, AFAICS, setting up the COORD ports currently needs to be done manually in each testcase spawning more than one child component. The `f_init*` functions are not involved in this process.