Patch Set 2: > Do we have any tests for this yet?
IIUC the conn does close after a given timeout. To test in ttcn3 we would need to choose a timeout that is smaller than the conn fsm timeout. That is opening doors to false positives, if ttcn3 ends up slightly slower than osmo-msc so that osmo-msc still responds in time. What do you think? The subscr_conn FSM timeout is 5 seconds. That should be sufficiently large for the ttcn3 tests to distinguish between immediate release and timeout, right? -- To view, visit https://gerrit.osmocom.org/6503 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: Idfa39fdbe5bb764f8ea2bbf8c5442e15e01cadbb Gerrit-PatchSet: 2 Gerrit-Project: osmo-msc Gerrit-Branch: master Gerrit-Owner: daniel <dwillm...@sysmocom.de> Gerrit-Reviewer: Harald Welte <lafo...@gnumonks.org> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: Neels Hofmeyr <nhofm...@sysmocom.de> Gerrit-HasComments: No
