neels has uploaded this change for review. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/28971 )

Change subject: f_tc_mt_t310: detect MNCC failure explicitly ......................................................................

f_tc_mt_t310: detect MNCC failure explicitly

Helped me find a failure cause: instead of T_guard timeout, immediately show an unexpected MNCC event.

Related: SYS#5066 Change-Id: I49a15142a4b6c51ca767a884c0574f96e01d7cb1 --- M msc/MSC_Tests.ttcn 1 file changed, 6 insertions(+), 0 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-ttcn3-hacks refs/changes/71/28971/1

diff --git a/msc/MSC_Tests.ttcn b/msc/MSC_Tests.ttcn index 79221d7..7dc668f 100644 --- a/msc/MSC_Tests.ttcn +++ b/msc/MSC_Tests.ttcn @@ -1798,6 +1798,7 @@ * the MSC would stop T310. However, the idea is to verify T310 expiration * here, so grab some popcorn and wait for MNCC DISC.ind. */ T310.start(30.0 + 2.0); + var template MNCC_PDU mncc_pdu := ?; alt { [] T310.timeout { setverdict(fail, "Timeout waiting for MNCC DISC.ind due to T310"); @@ -1808,6 +1809,11 @@ log("Rx MNCC DISC.ind, T310.read yelds ", T310.read); setverdict(pass); } + [] MNCC.receive(mncc_pdu) -> value mncc_rx { + log("Rx ", mncc_rx); + setverdict(fail, "Expected MNCC DISC.ind, got some other MNCC message instead"); + mtc.stop; + } }

BSSAP.receive(tr_PDU_DTAP_MT(tr_ML3_MT_CC_DISC(cpars.transaction_id)));