osmo-ttcn3-hacks - First steps for some Osmocom testing code in TTCN-3 (Eclipse Titan)

Age	Commit message (Collapse)	Author	Files	Lines
2018-07-27	detect VTY TELNET port connection failures (attempt #2)	Stefan Sperling	1	-0/+1
	Pass the CTRL_DETECT_CONNECTION_ESTABLISHMENT_RESULT parameter to the TELNET port by default. This allows tests to make progress into an error handling path if they are started while the osmo-* program they want to connect on VTY is not running. Observed with osmo-ggsn tests, where if the one test runs into a VTY connection failure the subsequent test would get stuck forever in a map() call on the VTY TELNET port. Teach the function f_vty_wait_for_prompt() about connection reports by the TELNET module. We may now receive an integer which represents the socket file descriptor for the telnet connection. This case was not handled by the previous change made in commit cb111b21aba1d5881da1a1d3f19754cbd15b3779. As a result, BSC tests started failing with "VTY Timeout for prompt" because the alt-statement in f_vty_wait_for_prompt() would not progress past the integer sitting on the VTY port's receive queue. Change-Id: I56925f93af6c55e93f3f417099db135744da6a40 Related: OS#3149
2018-07-27	Revert "detect VTY TELNET port connection failures in TTCN3 tests"	Neels Hofmeyr	1	-1/+0
	With this patch, I see all ttcn3-bsc-tests failing with "Verdict: fail reason: VTY Timeout for prompt" This reverts commit cb111b21aba1d5881da1a1d3f19754cbd15b3779. Change-Id: I215d7ab5eee75cf6d3afaac760af64356c943140
2018-07-27	detect VTY TELNET port connection failures in TTCN3 tests	Stefan Sperling	1	-0/+1
	Pass the CTRL_DETECT_CONNECTION_ESTABLISHMENT_RESULT parameter to the TELNET port by default. This allows tests to make progress into an error handling path if they are started while the osmo-* program they want to connect on VTY is not running. Observed with osmo-ggsn tests, where if the one test runs into a VTY connection failure the subsequent test would get stuck forever in a map() call on the VTY TELNET port. Change-Id: I9acf7793d5d68aec6d087cff254a10d8b673dab1 Related: OS#3149
2018-06-12	*.default: change logging filemask from ERROR \| WARNING to += PARALLEL \| ↵	Alexander Couzens	1	-2/+2
	VERDICTOP PARALLEL \| VERDICTOP will log when the port is dying or when other components will change to fail. This helped to find a timeout in the SGSN tests where a function call message timed out. Change-Id: I770ac964dc37e2752e7d35e493f707b091c739b0
2018-03-26	More progress on osmo-sip-connector tests	Harald Welte	1	-2/+2
	Change-Id: I34a5d7929264c7f5f21d3868a5f919874ffa106c
2018-03-22	sip: Add SIP_Emulation and first osmo-sip-connector test case	Harald Welte	1	-0/+30
	Change-Id: Ifd47b0d48c609b4a678ea47aa7f89f5c12e6c0d2