> Thu Aug 11 11:12:14 CEST 2022 - Setting config debug off
> ./set_config.sh: line 128: ./bin/config_debug.pl: No such file or directory
Change-Id: Ie53102256ef331318ef05b2bf3c78220b84208df
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
* bin/provide_scenario.sh: point of entry of provisioning
* bin/get_domains.pl: script helper to get domains defined at
scenario.yml
Change-Id: Ib1440f074b6f588c8a9dfac5dcf29d6b7459fb42
* single point of entry to get valid scenarios depending on PROFILE
GROUP and obeying SCENARIOS environment variable
Change-Id: I3dabf2b14c0c68f802287e1355f208ccb14224f6
* check for dirs with a scenario.yml file
* remove some shellcheck warnings:
SC2207: Prefer mapfile or read -a to split command output (or quote to avoid splitting).
Change-Id: I88b48fcc9668c3be26755472d6001f630a341fca
After JSON_KAM was enabled by default in commit 8618aa8 we lost
the possibility to disable it if necessary.
The option -J of bin/check.sh script now do the opposite: it is
used to disable JSON_KAM preference. Due to this change, the -J has
been removed from the script call in get_results.sh
Change-Id: I8ccc9d832ba808c72494dc27526e66ceff802a95
If retransmission skip is enabled (-r option) an additional check
with the previous json file (previous SIP message) is done in case
of tap issues. This is useful when wrong packet ordering or
timing issues occur.
Additionally:
* improved logs lines in oreder to be more readable.
* fixed inconsistencies in the coding style.
Change-Id: I20a026fab33e2a56f23bdccef8ee3aa3e27de732
* Original option '-c' in run_tests.sh has been modified
in '-C'
* Add new option '-c' in run_tests.sh to execute a query on MySQL
after each test to extract the generated CDRs.
* Add new option '-c' in get_results.sh to compare the extracted
CDRs with the referece provided in the scenario (cdr_test.yml.tt2).
* Modified option 'mediator.interval' from 10 to 1 during the test
execution in order to speedup the cdrs generation.
* Updated README file with the latest changes.
* Added basic cdr_test for all the scenarios.
Change-Id: Ifffd686003fa5e3a1ac4ba76c502011d7fdb21bb
Added option "-r" to run_tests and get_results script to activate
retransmission checks. If option is activated:
* at the end of the each test, json files will be checked and,
if a retransmission is found, the files will be renamed and
renumbered. This will help to detect most of the retransmission cases.
* In case a retransmission is not detected in the previous step,
if a scenario fails, it will be compared with the next json file.
This is an additional help to detect retransmissions.
* In case the transmission is detected and properly healed, no error
code is returned. Otherwise the script will exit 1 as before.
Change-Id: I5eaa7bdb920be869099440c295e0bfd75c2bf107
Fixing the test -z -n mess I notice
that ./run_test.sh needed a missing -J
for creating the initial KAM_DIR (cfgtest)
Change-Id: Ic0832c977657248852f5795cd35851f881299cf9
- fix check.py comparation when int -> string
- disable tcpdump by default ( new option -K to enable it)
- fix graph_flow for json ( new option --json )
Change-Id: I25f49ef6303b4e2e28c34fefd7860c744e6c3250
Alessio Garzi
Victor Seva
donat zenichev
Marco Capetta
Michael Prokop