As can be seen [1], it happens quite often that a test case gets
stuck and runs forever. Most of the existing test suites have
the guard timeout to prevent this. Let's make use of it here too.
[1] https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-remsim-test-latest/190/
Build has been executing for 1 day 23 hr!
Change-Id: I3897efd2a97c3e0d487057aa7bdc2967f3424dd8
osmo-remsim-client-shell allows to send C-APDU via STDIN of the program
and receive R-APDU via STDOUT. We can attach to that using the PIPEasp
TTCN3 port, and hence test a [local] osmo-remsim-client-shell
transceiving APDUs from/to a simulated bankd in the test case.
The only sad part about this is that we now will need to have the
implementation under test (osmo-remsim-client-shell binary) in the
same container as the TTCN-3 test, as it will fork/exec it.
This is why we disable it by default and a modulepar must be used to
enable those particular tests.
Change-Id: I3a69c692cf3e6bbe04ce58594050b20da0c37d16
This extends remsim-client test coverage to situations where the
server removes an existing/established mapping, and possibly later
establishes a new mapping.
Change-Id: I8df29a91718b6b2829415fc040b647a58eb71292
Related: OS#4399
Vadim Yanitskiy
Harald Welte