Neels Hofmeyr has submitted this change and it was merged. ( 
https://gerrit.osmocom.org/11659 )

Change subject: bsc: TC_chan_act_ack_est_ind_noreply: use f_expect_chan_rel
......................................................................

bsc: TC_chan_act_ack_est_ind_noreply: use f_expect_chan_rel

Instead of placing an own set of channel release expectations, just use the
common f_expect_chan_rel() that exists for exactly this purpose.

This will also be in line with upcoming changes to tighten checking of the
lchan release messages.

Related: OS#3413
Change-Id: Ib7dd886472337e2deb968e6f9de6cecdb7855319
---
M bsc/BSC_Tests.ttcn
1 file changed, 1 insertion(+), 9 deletions(-)

Approvals:
  Harald Welte: Looks good to me, approved
  Jenkins Builder: Verified



diff --git a/bsc/BSC_Tests.ttcn b/bsc/BSC_Tests.ttcn
index 551ffe0..a2a3378 100644
--- a/bsc/BSC_Tests.ttcn
+++ b/bsc/BSC_Tests.ttcn
@@ -429,15 +429,7 @@

        /* expect BSC to disable the channel again if there's no response from 
MSC */
        /* MS waits 20s (T3210) at LU; 10s (T3230) at CM SERV REQ and 5s 
(T3220) AT detach */
-       IPA_RSL[0].clear;
-       alt {
-       [] IPA_RSL[0].receive(tr_ASP_RSL_UD(sid, 
tr_RSL_MsgTypeD(RSL_MT_RF_CHAN_REL))) -> value rx_rsl_ud { }
-       [] IPA_RSL[0].receive(tr_ASP_RSL_UD(sid, tr_RSL_REL_REQ(chan_nr, ?))) 
-> value rx_rsl_ud {
-               f_ipa_tx(0, ts_RSL_REL_CONF(chan_nr, main_dcch));
-               repeat;
-               }
-       }
-
+       f_expect_chan_rel(0, chan_nr);
        setverdict(pass);
 }


--
To view, visit https://gerrit.osmocom.org/11659
To unsubscribe, or for help writing mail filters, visit 
https://gerrit.osmocom.org/settings

Gerrit-Project: osmo-ttcn3-hacks
Gerrit-Branch: master
Gerrit-MessageType: merged
Gerrit-Change-Id: Ib7dd886472337e2deb968e6f9de6cecdb7855319
Gerrit-Change-Number: 11659
Gerrit-PatchSet: 2
Gerrit-Owner: Neels Hofmeyr <[email protected]>
Gerrit-Reviewer: Harald Welte <[email protected]>
Gerrit-Reviewer: Jenkins Builder (1000002)
Gerrit-Reviewer: Neels Hofmeyr <[email protected]>

Reply via email to