osmo-ttcn3-hacks/bsc
Harald Welte 20a58c6d6f generalize shared code from regen_makefile.sh into shared helper script
Change-Id: I86a738420851a7d9e3bdb2671f6862c3d505a4ba
2017-12-13 01:04:42 +01:00
..
BSC_Tests.cfg BSC_Tests.cfg: Use 'control' section as default test suite 2017-12-10 18:28:21 +01:00
BSC_Tests.ttcn BSC_Tests: Ensure that PCH load indications suppress further paging 2017-12-13 00:50:11 +01:00
BSSAP_Adapter.ttcn BSC_Tests: Start with much simpler tests at BSSAP / SCCP level 2017-12-09 01:03:01 +01:00
BTS_Simulation.ttcn bsc-tests: Add BTS_Simulation, RSL_Tests and .cfg file 2017-12-08 14:01:43 +01:00
MSC_ConnectionHandler.ttcn ts_BSSMAP_HandoReq: Hand in raw list as argument, not IE type 2017-11-25 15:01:16 +01:00
README.txt bsc-tests: Add BTS_Simulation, RSL_Tests and .cfg file 2017-12-08 14:01:43 +01:00
RSL_Tests.ttcn bsc-tests: Add BTS_Simulation, RSL_Tests and .cfg file 2017-12-08 14:01:43 +01:00
gen_links.sh Makefile: clone dependencies into 'deps' folder 2017-12-12 16:30:53 +01:00
osmo-bsc.cfg Add osmo-bsc.cfg and osmo-stp.cfg for this test case 2017-12-11 19:53:35 +01:00
osmo-stp.cfg Add osmo-bsc.cfg and osmo-stp.cfg for this test case 2017-12-11 19:53:35 +01:00
regen_makefile.sh generalize shared code from regen_makefile.sh into shared helper script 2017-12-13 01:04:42 +01:00

README.txt

Integration Tests for OsmoBSC which we can perform from TTCN-3

= exhaustion of resources

* send many CHAN RQD (any) and count if all channels get actually allocated
** verify BTS_CTR_CHREQ_TOTAL reflects number sent on RSL
** verify how quickly they get released again
** verify that CHAN RQD with same RA + FN get only on allocation
* verify that we get IMM_ASS_REJ once channels are exhausted
** verify BTS_CTR_CHREQ_NO_CHANNEL increments accordigly
* verify for particular channel type / cause values
* verify that IMM.ASS.REJ has increasing back-off
* verify how BSC reacts to AGCH overload (DELETE IND)


= paging

* page by TMSI vs. page by IMSI
* verify if CCCH_LOAD_IND(PCH) slot count is observed
* verify paging expiration
* paging with different identity (lac/cgi/...) on A interface -> expect on right BSC(s)

= hand-over

* intra-BSC HO
* handover detect when not expected

= erroneous channel release

* no response to CHAN ACT
* CONN FAIL IND from BTS
** verify counter increment of BTS_CTR_CHAN_RF_FAIL
* no (or late?) response to RF CHAN REL
* no (or late?) response to RLL RELEASE REQ
* RLL messages on not-activated channels

= misc

* SMS-CB
* behavior in case of CHAN ACT NACK
* EST REQ for SAPI3 originating from core
* behavior of BSC in various error cases  (ERR IND)
** BTS_CTR_CHAN_RLL_ERR increment on T200_EXPIRED
* MODE MODIFY with ACK / NACK / no response

= IPA voice related

* expect IPA CRCX, send UDP flows, expect them on AoIP
* expect RTCP 
* missing RTP flow?
* missing RTCP?
* missing / drop-outs in RTP flow[s]
* no response to IPA CRCX / MDCX / DLCX

= counters

* test each and every counter in BSC, validate via CTRL interface
** RSL/OML failure: drop link, expect BTS_CTR_BTS_xxx_FAIL +1
** paging
*** send PAGING from MSC side
*** expect BSC_CTR_PAGING_ATTEMPTED increase by one
*** expect BSC_CTR_PAGING_EXPIRED on T3113 expiration
** BTS_CTR_CODEC_* on CHAN_ACT_ACK
* new counter ideas
** number of SCCP CR timeouts
** number of incoming RESET from MSC

= VTY based/corresponding tests

* changes in BCCH FILLING
* changes in SACCH FILLING