Test framework with a set of unit tests for Kamailio SIP Server. It targets the use within a Docker container.

Read more about Kamailio at:

• https://www.kamailio.org

The tests can be run using the command line tool ktestsctl. Run it without any parameter in order to see available options.

A unit test is stored in its own directory inside the subfolder units/. The name of the directory is considered to be the name of the unit.

The name of a unit test has the format txxxxxnnnn, the rules being:

• t - the first character in the name (t from test)
• xxxx - any five characters (use lower case letters) that should identify a group of tests (e.g., cfgxx is used to identify tests related to default kamailio.cfg)
• nnnn - four digits to assign to different unit tests in the same group, use zeros to pad in order to have always four digits (e.g., 0001)

Example of full unit test name: tcfgxx0001.

Inside each unit directory should be at least two files:

• unitname.sh - an executable shell script to be used to run the unit (e.g., tcfgxx0001.sh)
• README.md - to contain the description for the unit test

The shell script is executed inside the unit directory by ktestsctl.

The README.md is a text file in markdown format. It should have a line that starts with Summary: and provides a short description of the unit test. The text in the line after Summary: is used by ktestsctl when writing the unit tests execution report.

The framework has a configuration file located at etc/config. This is a shell script expected to have lines with VARIABLE=value, allowing to set paths to the applications used by unit scripts.

Useful shell functions that might be handy to use in units are stored inside files from lib subfolder, like:

• lib/utils - common utility functions

The Dockerfiles that can be used to build Docker images to run the unit tests are located in docker subfolder. These are:

• docker/Dockerfile.debian10 - container build with Debian 10.x (Buster) deploying Kamailio installed from source code. The directory with Kamailio source code is copied from local disk into the container
• docker/Dockerfile.debian9 - container build with Debian 9.x (Stretch) deploying Kamailio installed from source code. The directory with Kamailio source code is copied from local disk into the container
• docker/Dockerfile.centos7 - container build with CentOS 7 deploying Kamailio installed from source code. The directory with Kamailio source code is copied from local disk into the container

Following tools are installed inside the container and can be used to create test units:

• awk
• coreutils package
• curl
• gdb (requires to run docker with --cap-add=SYS_PTRACE)
• grep
• jq
• sed
• sipp (sip-tester)
• sipsak (installed from git)

• docker - it has to be installed in order to follow the next instructions

• create a directory where to store the resources and go to it

mkdir kamailio-testing
cd kamailio-testing

• clone the kamailio-tests git repository

git clone https://github.com/kamailio/kamailio-tests

• clone the kamailio git repository

git clone https://github.com/kamailio/kamailio

• copy desired Dockerfile in the current folder

Next example shows the use of the docker file for Debian 9.x.

cp kamailio-tests/docker/Dockerfile.debian9 Dockerfile

• build the Docker image

The name of the image can be changed, next example sets a name suggesting it is based on Debian 9.x:

docker build -t kamailio-tests-deb9x .

The Dockerfile defines the ENTRYPOINT to the path of ktestsctl:

ENTRYPOINT ["/usr/local/src/kamailio-tests/ktestsctl"]

With the default Dockerfile, the next command is running all unit tests:

docker run kamailio-tests-deb9x

The default option is -m (create mysql database).

You can specify other options for ktestsctl by passing them to the Docker run command.

For example, run the unit tests in silent mode:

docker run kamailio-tests-deb9x -q run

Example running only default kamailio.cfg related unit tests:

docker run kamailio-tests-deb9x run tcfgxx

Running ktestsctl with -w option requires to use docker in interactive mode:

docker run -i kamailio-tests-deb9x run -w

To stop a running container:

docker ps
docker stop <containerid>

You can exclude some units to be launched by listing them, one per line, in etc/excludeunits.txt.DISTRIBUTION (e.g. etc/excludeunits.txt.centos7), and then rebuilding the image.

Contributions are more than welcome, recommended way is to do pull requests.

Mailing list:

• <sr-users [at] lists.kamailio.org>