From e81ef42d05659d5cb4ddffa029fac113bc33db3f Mon Sep 17 00:00:00 2001 From: Neels Hofmeyr Date: Sun, 7 Aug 2022 14:33:06 +0200 Subject: msc: 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 --- msc/MSC_Tests.ttcn | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'msc/MSC_Tests.ttcn') diff --git a/msc/MSC_Tests.ttcn b/msc/MSC_Tests.ttcn index d6e0aba8..e6d270d0 100644 --- a/msc/MSC_Tests.ttcn +++ b/msc/MSC_Tests.ttcn @@ -1804,6 +1804,7 @@ friend function f_tc_mt_t310(charstring id, BSC_ConnHdlrPars pars) runs on BSC_C * 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 MNCC_PDU mncc_rx; alt { [] T310.timeout { setverdict(fail, "Timeout waiting for MNCC DISC.ind due to T310"); @@ -1814,6 +1815,11 @@ friend function f_tc_mt_t310(charstring id, BSC_ConnHdlrPars pars) runs on BSC_C 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))); -- cgit v1.2.3