osmo-ttcn3-hacks/bts
Max a199a2e0a2 Log all RA values which cause test failure
Previously the first timeout in TC_rach_content() caused test to
fail. Related TC_rach_count() test shows that there're some (13-16 out
of 1000) RA values which are problematic. Let's log all such values in
TC_rach_content() before failing the test to, hopefully, spot the
pattern which sets such RA values apart.

Change-Id: Ibfeb377101f406608c0193f08729c0e6d084281e
Related: OS#1854
2019-02-25 16:31:11 +01:00
..
BTS_Tests.cfg bts: Add second VTY connection to BSC 2018-09-16 12:41:11 +02:00
BTS_Tests.default bts: Add second VTY connection to BSC 2018-09-16 12:41:11 +02:00
BTS_Tests.ttcn Log all RA values which cause test failure 2019-02-25 16:31:11 +01:00
README.md Add README.md file for several suites 2018-06-14 18:55:36 +02:00
expected-results.xml update expected results 2019-01-23 12:44:42 +01:00
gen_links.sh BTS_Tests: Use Misc_Helpers.f_shutdown consistently 2018-10-24 15:10:13 +02:00
regen_makefile.sh bts: Add TELNET/VTY module so we can interact with BTS VTY 2018-02-27 22:32:54 +01:00

README.md

BTS_Tests.ttcn

  • external interfaces
    • A-bis side: RSL (emulates BSC-side server)
    • Um side: L1CTL to control MS
    • PCU side: pcu_socket

{% dot bts_tests.svg digraph G { rankdir=LR; { rank=same; BTS, BSC}; BTS [label="IUT\nosmo-bts-trx",shape="box"]; ATS [label="ATS\nBTS_Tests.ttcn"]; BSC [label="osmo-bsc\nOML only"]; BTS -> fake_trx [label="bursts"]; fake_trx -> trxcon [label="bursts"]; trxcon -> ATS [label="bursts"];

BTS -> BSC [label="A-bis OML"]; BTS -> ATS [label="A-bis RSL"];

ATS -> BTS [label="pcu_sock"]; ATS -> BSC [label="VTY"]; ATS -> BTS [label="CTRL"]; } %}