Version 12 (modified by bennylp, 14 years ago) (diff)


Automated Testing

Screenshot of PJSIP Dashboard

Table of Contents

  1. Introduction
  2. Installation
  3. Configuring and Running Test Scenarios
  4. Performing Automated Continuous and Nightly Builds and Tests
  5. Automatically Regenerating The Scenarios
  6. Appendix: The Templates
    1. gnu.xml.template
    2. gnu-ipp.xml.template
    3. iphone.xml.template
    4. msvc.xml.template
    5. symbian.xml.template
    6. symbian-aps.xml.template
    7. symbian-vas.xml.template

PJSIP has been equipped with an automated testing script (called test scenarios) since version 1.6. This article explains what it is and how to configure it.


The automated testing framework automatically and continuously updates, configures, builds, and performs various unit tests on PJSIP distribution, and submit the result to PJSIP's CDash test dashboard. The scenario uses CCDash (client for CDash; note the extra "c") framework to automate the tasks.

Supported targets:


  1. Checkout PJSIP source code from SVN
  2. Download and install CCDash (click the link for the info)
  3. Download and install any features to be used/tested, e.g. Intel IPP, Symbian APS/VAS plugin, etc.

Configuring and Running Test Scenarios

The general steps to configure automated test script on a platform are as follows:

  1. Go to directory tests/automated inside pjsip distribution.
  2. Choose the appropriate scenario template for your target/test objective. A template is an XML file containing ccdash commands to perform automated tests for a particular target. The PJSIP distribution have been equipped with the following templates:
Target platform Template file name Description Requirements
Makefile based (Linux, Mac OS X) gnu.xml.template Default settings -
Linux, Mac OS X with IPP gnu-ipp.xml.template Intel IPP Intel IPP and samples
MSVC/Win32 inc. WM msvc.xml.template Default settings -
Symbian/S60 3rd Ed symbian.xml.template Default settings -
Symbian/S60 3rd Ed symbian-aps.xml.template Nokia APS and APS-Direct Nokia APS plugin
Symbian/S60 3rd Ed symbian-vas.xml.template Nokia VAS and VAS-Direct Nokia VAS plugin
iPhone iphone.xml.template iPhoneOS one iPhone SDK must be installed
all prepare.xml.template See Automatically Regenerating The Scenarios below See inside the file
  1. From the template, you will then create the actual scenario file by running This is needed to instantiate the template using configurations that are specific to your host. Sample session:
     $ cd tests/automated
     $ ./ -o gnu.xml gnu.xml.template
    The above command will produce gnu.xml scenario file.
  2. For testing, run the scenario by running:
     $ ./ gnu.xml
    This will perform the automated tests and submit the result under "Experimental" group on CDash. Depending on which test is being run, it may take between two minutes to two hours to complete. You may press Ctrl-C to stop the execution.

Performing Automated Continuous and Nightly Builds and Tests

Once you're satisfied that the scenario(s) will work correctly, the next step is to run a script to automatically do the Continuous and Nightly builds. The script continuously monitors the repository for changes, and perform the builds and tests when it does. It also performs Nightly builds at every 00:00:00 GMT.

The script takes the scenario file(s) as argument:

  $ ./ gnu.xml [iphone.xml ...]

However there is a problem with the above invocation, namely if the scenario template changes, it won't be picked up by, since we need to re-run for that. This will be discussed below.

Automatically Regenerating The Scenarios

Use prepare.xml.template template scenario to generate prepare.xml scenario. The prepare.xml scenario contains commands to run for all other scenarios, effectively regenerating them. To use this:

  1. Instantiate prepare.xml from prepare.xml.template:
    $ ./ -t gnu -o prepare.xml prepare.xml.template
  2. Edit the prepare.xml file, and remove scenarios (each scenario is represented as a <Test> item) which you don't want to run.
  3. For each scenario that you do want to run, make sure the requirements are met. For example, you'd need to set some environment variables before running the prepare.xml scenario.
  4. Run the prepare.xml scenario to regenerate other scenarios:
    $ ./ prepare.xml
  5. Now you can run prepare.xml scenario before other scenarios in
      $ ./ prepare.xml gnu.xml [iphone.xml ...]

Appendix: The Templates

The detailed steps to configure each template will be explained below.


This configures, build, and tests with default settings. To perform this test:

 $ ./ -t gnu -o gnu.xml gnu.xml.template
 $ ./ gnu.xml


Template for testing IPP.


  • Intel IPP and samples
  • Environment variables:
    • IPPARCH (optional)
  • IPP path added to LD_LIBRARY_PATH

Sample session:

 $ export IPPROOT=/opt/intel/ipp/
 $ export IPPSAMPLES=/home/bennylp/Desktop/opt/ipp-samples
 $ (optional) export IPPARCH=em64t
 $ export LD_LIBRARY_PATH='$LD_LIBRARY_PATH:/opt/intel/ipp/'
 $ ./ -t gnu -o gnu-ipp.xml gnu-ipp.xml.template
 $ ./ gnu-ipp.xml


Template for testing iPhone.


  • on Mac OS X
  • at least one iPhone SDK must be installed

Sample session:

 $ ./ -o iphone.xml iphone.xml.template
 $ ./ iphone.xml


  • currently there's no way to select which iPhone SDK to use, as the automatically picks up the latest version of SDK installed.


Visual Studio targets.


  1. Visual Studio tools (cl.exe, vcbuild.exe) are set in PATH

Sample session:

 C:> python msvc.xml msvc.xml.template
      .. and answer the configure question ..
 C:> python msvc.xml


Symbian S60 targets. Set EPOCROOT environment variable to point to the SDK location before running

Sample session:

 C:> set EPOCROOT=\S60\devices\S60_5th_Edition_SDK_v1.0
 C:> python -t s60 -o symbian.xml symbian.xml.template
      .. and answer the configure question ..
 C:> python symbian.xml


Symbian S60 with APS target.



Symbian S60 with VAS target.


Attachments (3)