diff options
| author | Stefan Sperling <ssperling@sysmocom.de> | 2018-04-09 11:24:22 +0200 |
|---|---|---|
| committer | Stefan Sperling <ssperling@sysmocom.de> | 2018-04-09 11:33:21 +0200 |
| commit | 7c096874565eaba911c26151b80409b991395425 (patch) | |
| tree | 0483b14754249cac107314ad0c5261372cf24c33 /hlr | |
| parent | 94e0c3428e45f4f4092ff01f4d5f765d917be711 (diff) | |
improve failure diagnostics in TC_vty_msisdn_isd HLR test
Check for reception of an Insert Subscriber Data with outdated MSISDN.
This happened to me while working on a fix for issue OS#2785, and it
seems to be an easy mistake implementations can make. Catch this
situation in the test and log an explicit message about the problem.
Related: OS#2785
Change-Id: Ib0809617cca621cc22f29b078828057fd49f27e5
Diffstat (limited to 'hlr')
| -rw-r--r-- | hlr/HLR_Tests.ttcn | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/hlr/HLR_Tests.ttcn b/hlr/HLR_Tests.ttcn index 8b216266..90a00bfe 100644 --- a/hlr/HLR_Tests.ttcn +++ b/hlr/HLR_Tests.ttcn @@ -480,6 +480,10 @@ testcase TC_vty_msisdn_isd() runs on test_CT { sub.msisdn := new_msisdn; setverdict(pass); } + [] GSUP.receive(tr_GSUP_ISD_REQ(sub.imsi, sub.msisdn)) { + log("received ISD req with old MSISDN"); + setverdict(fail); + } [] GSUP.receive { repeat; } [] T.timeout { setverdict(fail, "Timeout waiting for ISD.req"); |