2 Commits (fb347c10f2d180f6f66a9f89385e0e9d6ff8ce0c)

Author	SHA1	Message	Date
Victor Seva	493423a911	TT#116101 align sipp checks filename to sipp scenario files ... * sipp_scenario00.xml => sipp_scenario00.msg sipp_scenario_responder00.xml => sipp_scenario_responder00.msg so sipp_scenario00_test.yml.tt2 and sipp_scenario_reponder00_test.yml.tt2 makes more sense Change-Id: Iab9db5122774dbc32101195e639ab6fef9b23236	5 years ago
donat zenichev	e110dd346b	TT#116101 Parsing of SIP messages expected/gotten result using sipp log ... We are adding a new approach/tool used to check out SIP messages received, and unlike the existing way of doing that (using what has come/gone in front of the Proxy), the usage of sipp logs will be introduced. The idea is that we are looking for received SIP messages at both the originator(s) and recipient(s) side, and then using what we've gotten, run checks based on _test.yml.tt2 templates prepared in advance for each scenario, example: * sip_messages00_test.yml.tt2 * sip_messages_responder00_test.yml.tt2 - add missing options to help command - bin/check.sh: use T option to select what to do with checks - get_results.sh: remove deprecated -P -T options Change-Id: I2d0084fa59694ffd009736205a092a35f6864669	5 years ago