osmo-ttcn3-hacks - Osmocom test suites in TTCN-3 (Eclipse Titan)

Age	Commit message (Collapse)	Author	Files	Lines
2021-02-26	StatsD_Checker: Enable by default	Pau Espin Pedrol	1	-1/+0
	It was previously disabled by default in order to avoid test breakage with older versions of osmocom projects not supporting them. Since we just did a new release, all -latest contian now master which should work fine. Don't remove the moduleparam yet in order to avoid breakage with some cfg files in docker-playground.git still setting it to true. Related: OS#5042 Change-Id: I4e2049c109986906d3c985ca2282174b1abff581
2020-08-13	bsc: Add statsd checker and use it in TC_assignment_sign	Daniel Willmann	1	-0/+10
	Related: SYS#4877 Change-Id: I8526b645dc4af59adcc1855699421a026f505c1d
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	-5/+5
	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-06-03	bsc: Disable verbose logging of MGCP encoder/decoder	Harald Welte	1	-0/+1
	Change-Id: I8147029a20828e762819be35ffebd801b22d2b6b
2018-03-13	remove .default from [EXECUTE] in .default files	Harald Welte	1	-1/+0
	The problem is that the .cfg file cannot override the [EXECUTE] provided list of tests Change-Id: I7e1e0499b3b32014b25ae4b515263f57a4ea6daf
2018-02-14	re-organize configuration files; add tcpdump integration	Harald Welte	1	-0/+23
	Let's make sure we share common configuration between the test suites and split the config file into a "default" part which is used (but not copied) in the Docker images, and a "local" part which is basically those overrides that the user (or docker image) wants to do from the default. Change-Id: I3db452e24e5238aa05254d903739c64d202e61db