Run SOME/IP tests on target

To run the SOME/IP tests from the vsomeip package, you should upload the files to these recommended locations on your target board. If you choose to use different directories, ensure that the JSON files and executables are in a separate folder and include the directory where the executables are in your PATH environment variable:

Steps to run tests on the target

To run the tests on the target, follow these steps and use the instructions for each test described in the “About the vsomeip tests” section:
  1. Connect to the target board using a serial connection (debug port), terminal via a network connection (telnet or ssh), or a terminal from the QNX Momentics IDE.
  2. Verify that you have a /tmp directory on the target, if not, create it. This folder is required for the tests to run; otherwise an error occurs when you run the test. You might need to make your filesystem writable first. (e.g., mount -uw /base)
  3. From the root level of the target, set up VSOMEIP_APPLICATION_NAME and VSOMEIP_CONFIGURATION environment variables to specify the test and corresponding configuration file (JSON file), and then modify the related configuration file (if required).
  4. Based on the test you want to run, make any necessary configuration file tests as indicated in the Test configuration and requirements section for each test.
  5. Based on the tests you want run, follow the steps in the Steps to run test section for each test, and then validate the results.

About the vsomeip tests

You can run these tests to verify that SOME/IP works as expected on your target board. For each test, you usually configure the following items before each test:
  • VSOMEIP_APPLICATION_NAME and VSOMEIP_CONFIGURATION environment variables
  • test configuration files, which are specific JSON files for each test. Within each JSON file, you typically modify the top-level unicast attribute to specify the IP address of the target that runs the test (referred to as the host on the vsomeip website) and the unicast attribute within the servicesgroups array. Usually, the last unicast attribute is used to specify the remote or local IP address for the test. For more information about the file structure of the JSON files, see the vsomeip documentation at http://docs.projects.genivi.org/vSomeIP/2.0.1/html/README.html.
  • Depending on the test, run the test commands (executable binaries) on one more terminal windows connected to one target, or two separate targets – again, this depends on the test that you run.
  • After you run a test (unless it's noted), you should see PASSED or succeeded in the terminal window or both terminal windows if you have run the test with multiple connections. If you see FAILED or failed, the message also indicates the source of the failure.
.
Note: Don't run the tests from the same folder where you put the JSON files on the target, otherwise the tests fails. For example, if you are using the reference image, don't run the tests from the /etc/vsomeip directory.
Test #1 — configuration_tests
Test configuration and requirements: You require one target for this test. No changes to the configuration file are required. Both the configuration_test_deprecated.json and configuration_test.json files should be located in the same directory where you run configuration_tests because setting VSOMEIP_CONFIGURATION doesn't work.
Steps to run the test: Open a terminal window to the target and then run the following command:
configuration_tests
You should see succeeded for all tests. It's expected that you may see failures for these tests:
  • SD INITIAL DELAY MIN
  • SD INITIAL DELAY MAX
  • SD INITIAL REPETITION BASE DELAY
  • SD INITIAL REPETITION MAX
  • SD INITIAL DELAY MIN
  • SD INITIAL SD CYCLIC OFFER DELAY
  • SD RESPONSE REQUEST DELAY
Test #2 — magic_cookies_test
Test configuration and requirements: You require two targets. The following configuration file changes are required:
  • On Target #1, in the /etc/vsomeip/magic_cookies_service.json file, change the first unicast attribute in the file to the IP address of Target #1.
  • On Target #2, you must make two changes. In the /etc/vsomeip/magic_cookies_client.json file change the first unicast to the IP address of Target #2, and then within the servicegroups array, change the unicast to the IP address of Target #1.
Steps to run the test: Open one terminal window on Target #1, one terminal window on Target #2, and then perform the following steps:
  1. In the terminal window to Target #1, run the following commands: 
    export VSOMEIP_APPLICATION_NAME=magic_cookies_test_service
export VSOMEIP_CONFIGURATION =/etc/vsomeip/magic_cookies_test_service.json
magic_cookies_test_service  --tcp --static-routing
  2. In the terminal window to Target #2, run the following commands: 
    export VSOMEIP_APPLICATION_NAME=magic_cookies_test_client
export VSOMEIP_CONFIGURATION =/etc/vsomeip/magic_cookies_test_client.json
magic_cookies_test_client
Test #3 — header_factory_test
Test configuration and requirements: You require one target for this test. No changes are required to the configuration file on the target.
Steps to run the test: Open a terminal window to the target and run the following command: 
header_factory_test
Test #4 — header_factory_test_send_receive
Test configuration and requirements: You require one target for this test. No changes are required to the configuration file on the target.
Steps to run the test: Open two terminal windows to the same target and perform the following steps:
  1. In Terminal #1, run the following commands: 
    export VSOMEIP_APPLICATION_NAME=header_factory_test_service
export VSOMEIP_CONFIGURATION=/etc/vsomeip/header_factory_test_service.json
header_factory_test_service
  2. In Terminal #2, run the following commands:
    export VSOMEIP_APPLICATION_NAME=header_factory_test_client
export VSOMEIP_CONFIGURATION=/etc/vsomeip/header_factory_test_client.json
header_factory_test_client
Test #5 — local_routing_test
Test configuration and requirements: You require one target for this test. No changes are required to the configuration on the target.
Steps to run the test: Open two terminal windows to the target and perform the following steps:
  1. In Terminal #1, run the following commands:
    export VSOMEIP_APPLICATION_NAME=local_routing_test_service
export VSOMEIP_CONFIGURATION =/etc/vsomeip/local_routing_test_service.json
local_routing_test_service
  2. In Terminal #2, run the following commands:
    export VSOMEIP_APPLICATION_NAME=local_routing_test_client
export VSOMEIP_CONFIGURATION =/etc/vsomeip/local_routing_test_client.json
local_routing_test_client
Test #6 — external_local_routing_test
Test configuration and requirements: You require two targets for this test. The following configuration file changes are required:
  • On Target #1, in the /etc/vsomeip/external_local_routing_test_service.json file, change the first unicast attribute to be the IP address configured for the target.
  • On Target #2, in the /etc/vsomeip/external_local_routing_test_client_external.json, change the first unicast attribute to IP Address of Target #2, and then within the servicegroups array, change the unicast attribute to the IP address of Target #1
Steps to run the test: Open two terminal windows to Target #1 and perform these steps:
  1. In Terminal #1, run the following commands:
    export VSOMEIP_APPLICATION_NAME=external_local_routing_test_service
export VSOMEIP_CONFIGURATION =/etc/vsomeip/external_local_routing_test_service.json
external_local_routing_test_service
  2. In Terminal #2, run the following commands: 
    export VSOMEIP_APPLICATION_NAME=local_routing_test_client
export VSOMEIP_CONFIGURATION =/etc/vsomeip/local_routing_test_client.json
local_routing_test_client

    You should see [PASSED] 1 test on the Terminal #2.

  3. Open a terminal window on Target #2 and run the following commands: 
    export VSOMEIP_APPLICATION_NAME=external_local_routing_test_client_external
export VSOMEIP_CONFIGURATION =/etc/vsomeip/external_local_routing_test_client_external.json
local_routing_test_client
Test #7 — local_payload_test
Test configuration and requirements: You require one target for this test. No changes to configuration files are required.
Steps to run the test: Open two terminal windows to the target and perform these steps:
  1. On Terminal #1, run these commands: 
    export VSOMEIP_APPLICATION_NAME=local_payload_test_service
export VSOMEIP_CONFIGURATION =/etc/vsomeip/local_payload_test_service.json
payload_test_service
  2. On Terminal #2, run the following commands: 
    export VSOMEIP_APPLICATION_NAME=local_payload_test_client
export VSOMEIP_CONFIGURATION =/etc/vsomeip/local_payload_test_client.json
payload_test_client
Test #8 — external_local_payload_test_client_local
Test configuration and requirements: One target is required for this test. Make the following changes to the configuration files:
  • In the /etc/vsomeip/external_local_payload_test_service.json file, change the value of the first unicast attribute to the IP address assigned to Target #1.
  • In the /etc/vsomeip/external_local_payload_test_client_local.json file, change the unicast attribute inside the servicegroups array to the IP assigned to Target #1.
Steps to run the test: Open two terminal windows to a target and perform the following steps:
  1. In Terminal #1, run the following commands: 
    export VSOMEIP_APPLICATION_NAME=external_local_payload_test_service
export VSOMEIP_CONFIGURATION =/etc/vsomeip/external_local_payload_test_service.json
payload_test_service
  2. In Terminal #2, run the following commands: 
    export VSOMEIP_APPLICATION_NAME=external_local_payload_test_client_local
export VSOMEIP_CONFIGURATION =/etc/vsomeip/external_local_payload_test_client_local.json
payload_test_client
Test #9 — external_local_payload_test_client_external
Test configuration and requirements: You require two targets. The following configuration file changes are required:
  • On Target #1, in the /etc/vsomeip/external_local_payload_test_service.json file, change the first unicast attribute in the file to the IP address of Target #1.
  • On Target #2, you must make two changes. In the /etc/vsomeip/external_local_payload_test_client_external.json file change the first unicast to the IP Address of Target #2, and then within the servicegroups array, change the unicast to the IP address of Target #1.
Steps to run the test: Open a terminal window on Target #1, open a terminal window on Target #2, and then perform the following steps:
  1. In the terminal window on Target #1, run the following commands: 
    export VSOMEIP_APPLICATION_NAME=external_local_payload_test_service
export VSOMEIP_CONFIGURATION =/etc/vsomeip/external_local_payload_test_service.json
payload_test_service --udp
  2. In the terminal window on Target #2, run the following commands: 
    export VSOMEIP_APPLICATION_NAME=external_local_payload_test_client_external
export VSOMEIP_CONFIGURATION =/etc/vsomeip/external_local_payload_test_client_external.json
payload_test_client --udp --max-payload-size UDP
  3. Then, run the TCP tests using these steps:
    • On the terminal window to Target #1, run the following command: 
      payload_test_service --tcp
    • On the terminal window to Target #2, run the following command: 
      payload_test_client --tcp --max-payload-size TCP
Test #10 — external_local_payload_test_client_local_and_external
Test configuration and requirements: This test basically runs Test #8 (external_local_payload_test_client_local) and Test #9 (external_local_payload_test_client_external). Running this test isn't necessary.
Steps to run the test: If you want to run this test, you can run a shell script from the vsomeip package you downloaded. The script is located at test/payload_tests/external_local_payload_test_client_local_and_external_starter.sh. To run the script, you must type sh in front of the script name.
Test #11 — application_tests
Test configuration and requirements: You require one target for this test. No changes are required to the application_test_no_dispatch_threads.json file on the target.
Steps to run the test: Open a terminal window to the target and run the following commands: 
export VSOMEIP_APPLICATION_NAME=application_tests
export VSOMEIP_CONFIGURATION=/etc/vsomeip/application_test_no_dispatch_threads.json
application_tests
export VSOMEIP_CONFIGURATION=/etc/vsomeip/application_test.json
application_tests
Test #12 — big_payload_test_local
Test configuration and requirements: You require two terminal connections on one target. No changes are required to the big_payload_test_local.json file on the target.
Steps to run the test: On the terminals to the target, perform the following steps:
  1. In Terminal #1, run the following commands: 
    export VSOMEIP_APPLICATION_NAME=big_payload_test_service            
export VSOMEIP_CONFIGURATION =/etc/vsomeip/big_payload_test_local.json
big_payload_test_service
  2. On Terminal #2, run the following commands: 
    export VSOMEIP_APPLICATION_NAME=big_payload_test_client
export VSOMEIP_CONFIGURATION =/etc/vsomeip/big_payload_test_local.json
big_payload_test_client
Test #13 — big_payload_test_external
This test doesn't run on this product.
Test #14 — client_id_test
This test doesn't run on this product.

Example of running Test #1 — configuration_tests

This is an example of running a basic configuration test on the target. In this case, no environment variables need to be set and no configuration file changes are required.:

Note: The errors you see in the example below are expected. The expected failures are described in the test description, previously.
# configuration_tests
/////////////////////////////////
// CHECKING CONFIGURATION FILE //
/////////////////////////////////
2016-06-05 14:47:50.069125 [info] Test "UNICAST ADDRESS" succeeded.
2016-06-05 14:47:50.076125 [info] Test "HAS CONSOLE" succeeded.
2016-06-05 14:47:50.076125 [info] Test "HAS FILE" succeeded.
2016-06-05 14:47:50.077125 [info] Test "HAS DLT" succeeded.
2016-06-05 14:47:50.077125 [info] Test "LOGFILE" succeeded.
2016-06-05 14:47:50.078125 [info] Test "LOGLEVEL" succeeded.
2016-06-05 14:47:50.078125 [info] Test "UNICAST_ADDRESS_1234_0022" succeeded.
2016-06-05 14:47:50.079125 [info] Test "RELIABLE_PORT_1234_0022" succeeded.
2016-06-05 14:47:50.080125 [info] Test "UNRELIABLE_PORT_1234_0022" succeeded.
2016-06-05 14:47:50.080125 [info] Test "UNICAST_ADDRESS_1234_0023" succeeded.
2016-06-05 14:47:50.081125 [info] Test "RELIABLE_PORT_1234_0023" succeeded.
2016-06-05 14:47:50.081125 [info] Test "UNRELIABLE_PORT_1234_0023" succeeded.
2016-06-05 14:47:50.082125 [info] Test "UNICAST_ADDRESS_2277_0022" succeeded.
2016-06-05 14:47:50.083125 [info] Test "RELIABLE_PORT_2277_0022" succeeded.
2016-06-05 14:47:50.083125 [info] Test "UNRELIABLE_PORT_2277_0022" succeeded.
2016-06-05 14:47:50.084125 [info] Test "UNICAST_ADDRESS_2266_0022" succeeded.
2016-06-05 14:47:50.085125 [info] Test "RELIABLE_PORT_2266_0022" succeeded.
2016-06-05 14:47:50.085125 [info] Test "UNRELIABLE_PORT_2266_0022" succeeded.
2016-06-05 14:47:50.086125 [info] Test "UNICAST_ADDRESS_4466_0321" succeeded.
2016-06-05 14:47:50.086125 [info] Test "RELIABLE_PORT_4466_0321" succeeded.
2016-06-05 14:47:50.087125 [info] Test "UNRELIABLE_PORT_4466_0321" succeeded.
2016-06-05 14:47:50.087125 [info] Test "SD ENABLED" succeeded.
2016-06-05 14:47:50.088125 [info] Test "SD PROTOCOL" succeeded.
2016-06-05 14:47:50.088125 [info] Test "SD MULTICAST" succeeded.
2016-06-05 14:47:50.089125 [info] Test "SD PORT" succeeded.
2016-06-05 14:47:50.089125 [info] Test "SD INITIAL DELAY MIN" succeeded.
2016-06-05 14:47:50.090125 [info] Test "SD INITIAL DELAY MAX" succeeded.
2016-06-05 14:47:50.091125 [info] Test "SD REPETITION BASE DELAY" succeeded.
2016-06-05 14:47:50.091125 [info] Test "SD REPETITION MAX" succeeded.
2016-06-05 14:47:50.092125 [info] Test "SD TTL" succeeded.
2016-06-05 14:47:50.092125 [info] Test "SD CYCLIC OFFER DELAY" succeeded.
2016-06-05 14:47:50.093125 [info] Test "SD RESPONSE REQUEST DELAY" succeeded.
////////////////////////////////////////////
// CHECKING DEPRECATED CONFIGURATION FILE //
////////////////////////////////////////////
2016-06-05 14:47:50.105125 [info] Test "UNICAST ADDRESS" succeeded.
2016-06-05 14:47:50.105125 [info] Test "HAS CONSOLE" succeeded.
2016-06-05 14:47:50.106125 [info] Test "HAS FILE" succeeded.
2016-06-05 14:47:50.106125 [info] Test "HAS DLT" succeeded.
2016-06-05 14:47:50.107125 [info] Test "LOGFILE" succeeded.
2016-06-05 14:47:50.108125 [info] Test "LOGLEVEL" succeeded.
2016-06-05 14:47:50.108125 [info] Test "UNICAST_ADDRESS_1234_0022" succeeded.
2016-06-05 14:47:50.109125 [info] Test "RELIABLE_PORT_1234_0022" succeeded.
2016-06-05 14:47:50.109125 [info] Test "UNRELIABLE_PORT_1234_0022" succeeded.
2016-06-05 14:47:50.110125 [info] Test "UNICAST_ADDRESS_1234_0023" succeeded.
2016-06-05 14:47:50.110125 [info] Test "RELIABLE_PORT_1234_0023" succeeded.
2016-06-05 14:47:50.111125 [info] Test "UNRELIABLE_PORT_1234_0023" succeeded.
2016-06-05 14:47:50.112125 [info] Test "UNICAST_ADDRESS_2277_0022" succeeded.
2016-06-05 14:47:50.112125 [info] Test "RELIABLE_PORT_2277_0022" succeeded.
2016-06-05 14:47:50.113125 [info] Test "UNRELIABLE_PORT_2277_0022" succeeded.
2016-06-05 14:47:50.113125 [info] Test "UNICAST_ADDRESS_2266_0022" succeeded.
2016-06-05 14:47:50.114125 [info] Test "RELIABLE_PORT_2266_0022" succeeded.
2016-06-05 14:47:50.115125 [info] Test "UNRELIABLE_PORT_2266_0022" succeeded.
2016-06-05 14:47:50.115125 [info] Test "UNICAST_ADDRESS_4466_0321" succeeded.
2016-06-05 14:47:50.116125 [info] Test "RELIABLE_PORT_4466_0321" succeeded.
2016-06-05 14:47:50.116125 [info] Test "UNRELIABLE_PORT_4466_0321" succeeded.
2016-06-05 14:47:50.117125 [info] Test "SD ENABLED" succeeded.
2016-06-05 14:47:50.118125 [info] Test "SD PROTOCOL" succeeded.
2016-06-05 14:47:50.118125 [info] Test "SD MULTICAST" succeeded.
2016-06-05 14:47:50.119125 [info] Test "SD PORT" succeeded.
2016-06-05 14:47:50.119125 [error] Test "SD INITIAL DELAY MIN" succeeded.
2016-06-05 14:47:50.121125 [error] Test "SD INITIAL DELAY MAX" succeeded.
2016-06-05 14:47:50.122125 [error] Test "SD REPETITION BASE DELAY" succeeded.
2016-06-05 14:47:50.122125 [error] Test "SD REPETITION MAX" succeeded.
2016-06-05 14:47:50.123125 [info] Test "SD TTL" succeeded.
2016-06-05 14:47:50.123125 [error] Test "SD CYCLIC OFFER DELAY" succeeded.
2016-06-05 14:47:50.124125 [error] Test "SD RESPONSE REQUEST DELAY" succeeded.
# cd /etc/vsomeip/
# ./configuration_tests
/////////////////////////////////
// CHECKING CONFIGURATION FILE //
/////////////////////////////////
2016-06-05 14:48:00.710115 [info] Test "UNICAST ADDRESS" succeeded.
2016-06-05 14:48:00.717115 [info] Test "HAS CONSOLE" succeeded.
2016-06-05 14:48:00.717115 [info] Test "HAS FILE" succeeded.
2016-06-05 14:48:00.718115 [info] Test "HAS DLT" succeeded.
2016-06-05 14:48:00.718115 [info] Test "LOGFILE" succeeded.
2016-06-05 14:48:00.719115 [info] Test "LOGLEVEL" succeeded.
2016-06-05 14:48:00.719115 [info] Test "UNICAST_ADDRESS_1234_0022" succeeded.
2016-06-05 14:48:00.720115 [info] Test "RELIABLE_PORT_1234_0022" succeeded.
2016-06-05 14:48:00.720115 [info] Test "UNRELIABLE_PORT_1234_0022" succeeded.
2016-06-05 14:48:00.721115 [info] Test "UNICAST_ADDRESS_1234_0023" succeeded.
2016-06-05 14:48:00.722115 [info] Test "RELIABLE_PORT_1234_0023" succeeded.
2016-06-05 14:48:00.722115 [info] Test "UNRELIABLE_PORT_1234_0023" succeeded.
2016-06-05 14:48:00.723115 [info] Test "UNICAST_ADDRESS_2277_0022" succeeded.
2016-06-05 14:48:00.723115 [info] Test "RELIABLE_PORT_2277_0022" succeeded.
2016-06-05 14:48:00.724115 [info] Test "UNRELIABLE_PORT_2277_0022" succeeded.
2016-06-05 14:48:00.724115 [info] Test "UNICAST_ADDRESS_2266_0022" succeeded.
2016-06-05 14:48:00.725115 [info] Test "RELIABLE_PORT_2266_0022" succeeded.
2016-06-05 14:48:00.726115 [info] Test "UNRELIABLE_PORT_2266_0022" succeeded.
2016-06-05 14:48:00.726115 [info] Test "UNICAST_ADDRESS_4466_0321" succeeded.
2016-06-05 14:48:00.727115 [info] Test "RELIABLE_PORT_4466_0321" succeeded.
2016-06-05 14:48:00.727115 [info] Test "UNRELIABLE_PORT_4466_0321" succeeded.
2016-06-05 14:48:00.728115 [info] Test "SD ENABLED" succeeded.
2016-06-05 14:48:00.728115 [info] Test "SD PROTOCOL" succeeded.
2016-06-05 14:48:00.729115 [info] Test "SD MULTICAST" succeeded.
2016-06-05 14:48:00.729115 [info] Test "SD PORT" succeeded.
2016-06-05 14:48:00.730115 [info] Test "SD INITIAL DELAY MIN" succeeded.
2016-06-05 14:48:00.731115 [info] Test "SD INITIAL DELAY MAX" succeeded.
2016-06-05 14:48:00.731115 [info] Test "SD REPETITION BASE DELAY" succeeded.
2016-06-05 14:48:00.732115 [info] Test "SD REPETITION MAX" succeeded.
2016-06-05 14:48:00.732115 [info] Test "SD TTL" succeeded.
2016-06-05 14:48:00.733115 [info] Test "SD CYCLIC OFFER DELAY" succeeded.
2016-06-05 14:48:00.733115 [info] Test "SD RESPONSE REQUEST DELAY" succeeded.
////////////////////////////////////////////
// CHECKING DEPRECATED CONFIGURATION FILE //
////////////////////////////////////////////
2016-06-05 14:48:00.745115 [info] Test "UNICAST ADDRESS" succeeded.
2016-06-05 14:48:00.746115 [info] Test "HAS CONSOLE" succeeded.
2016-06-05 14:48:00.746115 [info] Test "HAS FILE" succeeded.
2016-06-05 14:48:00.747115 [info] Test "HAS DLT" succeeded.
2016-06-05 14:48:00.747115 [info] Test "LOGFILE" succeeded.
2016-06-05 14:48:00.748115 [info] Test "LOGLEVEL" succeeded.
2016-06-05 14:48:00.749115 [info] Test "UNICAST_ADDRESS_1234_0022" succeeded.
2016-06-05 14:48:00.749115 [info] Test "RELIABLE_PORT_1234_0022" succeeded.
2016-06-05 14:48:00.750115 [info] Test "UNRELIABLE_PORT_1234_0022" succeeded.
2016-06-05 14:48:00.750115 [info] Test "UNICAST_ADDRESS_1234_0023" succeeded.
2016-06-05 14:48:00.751115 [info] Test "RELIABLE_PORT_1234_0023" succeeded.
2016-06-05 14:48:00.752115 [info] Test "UNRELIABLE_PORT_1234_0023" succeeded.
2016-06-05 14:48:00.752115 [info] Test "UNICAST_ADDRESS_2277_0022" succeeded.
2016-06-05 14:48:00.753115 [info] Test "RELIABLE_PORT_2277_0022" succeeded.
2016-06-05 14:48:00.753115 [info] Test "UNRELIABLE_PORT_2277_0022" succeeded.
2016-06-05 14:48:00.754115 [info] Test "UNICAST_ADDRESS_2266_0022" succeeded.
2016-06-05 14:48:00.754115 [info] Test "RELIABLE_PORT_2266_0022" succeeded.
2016-06-05 14:48:00.755115 [info] Test "UNRELIABLE_PORT_2266_0022" succeeded.
2016-06-05 14:48:00.756115 [info] Test "UNICAST_ADDRESS_4466_0321" succeeded.
2016-06-05 14:48:00.756115 [info] Test "RELIABLE_PORT_4466_0321" succeeded.
2016-06-05 14:48:00.757115 [info] Test "UNRELIABLE_PORT_4466_0321" succeeded.
2016-06-05 14:48:00.757115 [info] Test "SD ENABLED" succeeded.
2016-06-05 14:48:00.758115 [info] Test "SD PROTOCOL" succeeded.
2016-06-05 14:48:00.758115 [info] Test "SD MULTICAST" succeeded.
2016-06-05 14:48:00.759115 [info] Test "SD PORT" succeeded.
2016-06-05 14:47:50.119125 [error] Test "SD INITIAL DELAY MIN" failed! (100 != 10)
2016-06-05 14:47:50.121125 [error] Test "SD INITIAL DELAY MAX" failed! (200 != 100)
2016-06-05 14:47:50.122125 [error] Test "SD REPETITION BASE DELAY" failed! (300 != 200)
2016-06-05 14:47:50.122125 [error] Test "SD REPETITION MAX" failed! ( != )
2016-06-05 14:47:50.123125 [info] Test "SD TTL" succeeded.
2016-06-05 14:47:50.123125 [error] Test "SD CYCLIC OFFER DELAY" failed! (2500 != 2132)
2016-06-05 14:47:50.124125 [error] Test "SD RESPONSE REQUEST DELAY" failed! (2221 != 2001)

Example of running Test #4 — header_factory_test_send_receive

For this test, you must set environment variables and run the test on two separate terminal windows (Terminal #1 and Terminal #2) on the same target. You can confirm that you have sshd running on the target in a serial connection, a terminal via a network connection (telnet), or a terminal from the QNX Momentics IDE to validate that you can use ssh to connect to your target. For Windows hosts, you are required to get a third-party SSH client. Here's how the test is run:

On your target, in Terminal #1, set the VSOMEIP_APPLICATION_NAME and VSOMEIP_CONFIGURATION environment variables and run header_factory_test_service as show here 
# export VSOMEIP_APPLICATION_NAME=header_factory_test_service
# export VSOMEIP_CONFIGURATION=/etc/vsomeip/header_factory_test_service.json
# header_factory_test_service
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from someip_header_factory_test
[ RUN      ] someip_header_factory_test.reveice_message_ten_times_test
2016-06-05 14:50:03.654992 [info] Initializing vsomeip application "header_factory_test_service"
2016-06-05 14:50:03.661992 [info] Using configuration file: "/etc/vsomeip/header_factory_test_service.json"
2016-06-05 14:50:03.671992 [debug] Routing endpoint at /tmp/vsomeip-0
2016-06-05 14:50:03.680992 [info] Service Discovery disabled. Using static routing information.
2016-06-05 14:50:03.681992 [debug] Application(header_factory_test_service, 1277) is initialized (uses 0 dispatcher threads).
2016-06-05 14:50:03.684992 [info] Static routing ON
2016-06-05 14:50:03.685992 [info] Starting...
2016-06-05 14:50:03.689992 [info] Application header_factory_test_service is registered.
2016-06-05 14:50:03.690992 [info] Starting vsomeip application "header_factory_test_service"
2016-06-05 14:50:36.110959 [debug] Application/Client 1343 got registered!
2016-06-05 14:50:36.121959 [info] Received a message with Client/Session [1343/0001]
2016-06-05 14:50:36.125959 [info] Received a message with Client/Session [1343/0002]
2016-06-05 14:50:36.126959 [info] Received a message with Client/Session [1343/0003]
2016-06-05 14:50:36.128959 [info] Received a message with Client/Session [1343/0004]
2016-06-05 14:50:36.130959 [info] Received a message with Client/Session [1343/0005]
2016-06-05 14:50:36.133959 [info] Received a message with Client/Session [1343/0006]
2016-06-05 14:50:36.134959 [info] Received a message with Client/Session [1343/0007]
2016-06-05 14:50:36.137959 [info] Received a message with Client/Session [1343/0008]
2016-06-05 14:50:36.138959 [info] Received a message with Client/Session [1343/0009]
2016-06-05 14:50:36.142959 [info] Received a message with Client/Session [1343/000a]
2016-06-05 14:50:36.167959 [error] Local endpoint received message (End of file)
2016-06-05 14:50:41.145954 [info] Stopping vsomeip application "header_factory_test_service"
2016-06-05 14:50:41.146954 [info] Application header_factory_test_service is deregistered.
[       OK ] someip_header_factory_test.reveice_message_ten_times_test (37552 ms)
[----------] 1 test from someip_header_factory_test (37553 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (37558 ms total)
[  PASSED  ] 1 test.
In Terminal #2, set the VSOMEIP_APPLICATION_NAME and VSOMEIP_CONFIGURATION environment variables and run header_factory_test_client as shown here:
# export VSOMEIP_APPLICATION_NAME=header_factory_test_client
# export VSOMEIP_CONFIGURATION=/etc/vsomeip/header_factory_test_client.json
# header_factory_test_client
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from someip_header_factory_test
[ RUN      ] someip_header_factory_test.send_message_ten_times_test
2016-06-05 14:50:36.090959 [info] Initializing vsomeip application "header_factory_test_client"
2016-06-05 14:50:36.093959 [info] Using configuration file: "/etc/vsomeip/header_factory_test_client.json"
2016-06-05 14:50:36.096959 [debug] Connecting to [0] at /tmp/vsomeip-0
2016-06-05 14:50:36.099959 [debug] Listening at /tmp/vsomeip-1343
2016-06-05 14:50:36.099959 [debug] Application(header_factory_test_client, 1343) is initialized (uses 0 dispatcher threads).
2016-06-05 14:50:36.101959 [info] Service [1234.5678] is NOT available.
2016-06-05 14:50:36.102959 [info] Starting...
2016-06-05 14:50:36.106959 [info] Starting vsomeip application "header_factory_test_client"
2016-06-05 14:50:36.113959 [info] Service [1234.5678] is available.
2016-06-05 14:50:36.114959 [info] Client/Session [1343/0001] sent a request to Service [1234.5678]
2016-06-05 14:50:36.115959 [info] Client/Session [1343/0002] sent a request to Service [1234.5678]
2016-06-05 14:50:36.116959 [info] Client/Session [1343/0003] sent a request to Service [1234.5678]
2016-06-05 14:50:36.119959 [info] Client/Session [1343/0004] sent a request to Service [1234.5678]
2016-06-05 14:50:36.119959 [info] Client/Session [1343/0005] sent a request to Service [1234.5678]
2016-06-05 14:50:36.120959 [info] Client/Session [1343/0006] sent a request to Service [1234.5678]
2016-06-05 14:50:36.122959 [info] Client/Session [1343/0007] sent a request to Service [1234.5678]
2016-06-05 14:50:36.123959 [info] Client/Session [1343/0008] sent a request to Service [1234.5678]
2016-06-05 14:50:36.124959 [info] Client/Session [1343/0009] sent a request to Service [1234.5678]
2016-06-05 14:50:36.125959 [info] Client/Session [1343/000a] sent a request to Service [1234.5678]
2016-06-05 14:50:36.130959 [info] Received a response from Service [1234.5678] to Client/Session [1343/0001]
2016-06-05 14:50:36.135959 [info] Received a response from Service [1234.5678] to Client/Session [1343/0002]
2016-06-05 14:50:36.139959 [info] Received a response from Service [1234.5678] to Client/Session [1343/0003]
2016-06-05 14:50:36.141959 [info] Received a response from Service [1234.5678] to Client/Session [1343/0004]
2016-06-05 14:50:36.145959 [info] Received a response from Service [1234.5678] to Client/Session [1343/0005]
2016-06-05 14:50:36.146959 [info] Received a response from Service [1234.5678] to Client/Session [1343/0006]
2016-06-05 14:50:36.148959 [info] Received a response from Service [1234.5678] to Client/Session [1343/0007]
2016-06-05 14:50:36.149959 [info] Received a response from Service [1234.5678] to Client/Session [1343/0008]
2016-06-05 14:50:36.151959 [info] Received a response from Service [1234.5678] to Client/Session [1343/0009]
2016-06-05 14:50:36.152959 [info] Received a response from Service [1234.5678] to Client/Session [1343/000a]
2016-06-05 14:50:36.153959 [info] Stopping...
2016-06-05 14:50:36.153959 [info] Stopping vsomeip application "header_factory_test_client"
[       OK ] someip_header_factory_test.send_message_ten_times_test (80 ms)
[----------] 1 test from someip_header_factory_test (82 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (85 ms total)
[  PASSED  ] 1 test.
After you run the command in the second console, you should see the following PASSED message in Terminal #1: 
2016-06-01 17:12:54.474025 [debug] Application/Client 1343 got registered!
                2016-06-01 17:12:54.478025 [info] Received a message with Client/Session [1343/0001]
                2016-06-01 17:12:54.481025 [info] Received a message with Client/Session [1343/0002]
                2016-06-01 17:12:54.482025 [info] Received a message with Client/Session [1343/0003]
                2016-06-01 17:12:54.483025 [info] Received a message with Client/Session [1343/0004]
                2016-06-01 17:12:54.484025 [info] Received a message with Client/Session [1343/0005]
                2016-06-01 17:12:54.484025 [info] Received a message with Client/Session [1343/0006]
                2016-06-01 17:12:54.485025 [info] Received a message with Client/Session [1343/0007]
                2016-06-01 17:12:54.487025 [info] Received a message with Client/Session [1343/0008]
                2016-06-01 17:12:54.487025 [info] Received a message with Client/Session [1343/0009]
                2016-06-01 17:12:54.488025 [info] Received a message with Client/Session [1343/000a]
                2016-06-01 17:12:54.489025 [info] Application header_factory_test_service is deregistered.
                [       OK ] someip_header_factory_test.reveice_message_ten_times_test (34153 ms)
                [----------] 1 test from someip_header_factory_test (34155 ms total)
                
                [----------] Global test environment tear-down
                [==========] 1 test from 1 test case ran. (34162 ms total)
                [  PASSED  ] 1 test.

Example of running Test #6 — external_local_routing_test

In this example, you must run tests on two separate targets. Target #1 requires two terminal windows and Target #2 requires one terminal window.

On Target #1, in the Terminal #1, edit the file /etc/vsomeip/external_local_routing_test_service.json and change the first unicast attribute to 10.122.17.84.

On Target #1, in Terminal #1, set the VSOMEIP_APPLICATION_NAME and VSOMEIP_CONFIGURATION environment variables and run the external_local_routing_test_service as show here:
export VSOMEIP_APPLICATION_NAME=external_local_routing_test_service
export VSOMEIP_CONFIGURATION=/etc/vsomeip/external_local_routing_test_service.json
external_local_routing_test_service
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from someip_external_local_routing_test
[ RUN      ] someip_external_local_routing_test.receive_ten_messages_over_local_and_external_socket
2016-06-04 16:33:21.230198 [info] Using configuration file: /etc/vsomeip/external_local_routing_test_service.json
2016-06-04 16:33:21.244198 [debug] Routing endpoint at /tmp/vsomeip-0
2016-06-04 16:33:21.252198 [info] Service Discovery disabled. Using static routing information.
2016-06-04 16:33:21.253198 [debug] Application(external_local_routing_test_service, 1277) is initialized (uses 0 dispatcher threads).
2016-06-04 16:33:21.255198 [info] Static routing ON
2016-06-04 16:33:21.255198 [info] Starting...
2016-06-04 16:33:21.257198 [info] Application external_local_routing_test_service is registered.
Then on Target #1, in Terminal #2, set the VSOMEIP_APPLICATION_NAME and VSOMEIP_CONFIGURATION environment variables and then run local_routing_test_client as shown here to run the test:
# export VSOMEIP_APPLICATION_NAME=local_routing_test_client
# export VSOMEIP_CONFIGURATION=/etc/vsomeip/local_routing_test_client.json
# local_routing_test_client
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from someip_local_routing_test
[ RUN      ] someip_local_routing_test.send_ten_messages_to_service_and_receive_reply
2016-06-05 14:52:40.260835 [info] Initializing vsomeip application "local_routing_test_client"
2016-06-05 14:52:40.262835 [info] Using configuration file: "/etc/vsomeip/local_routing_test_client.json"
2016-06-05 14:52:40.266835 [debug] Connecting to [0] at /tmp/vsomeip-0
2016-06-05 14:52:40.269835 [debug] Listening at /tmp/vsomeip-1343
2016-06-05 14:52:40.269835 [debug] Application(local_routing_test_client, 1343) is initialized (uses 0 dispatcher threads).
2016-06-05 14:52:40.271835 [info] Service [1234.5678] is NOT available.
2016-06-05 14:52:40.272835 [info] Starting...
2016-06-05 14:52:40.276835 [info] Starting vsomeip application "local_routing_test_client"
2016-06-05 14:52:40.284835 [info] Service [1234.5678] is available.
2016-06-05 14:52:40.284835 [info] Client/Session [1343/0001] sent a request to Service [1234.5678]
2016-06-05 14:52:40.285835 [info] Client/Session [1343/0002] sent a request to Service [1234.5678]
2016-06-05 14:52:40.286835 [info] Client/Session [1343/0003] sent a request to Service [1234.5678]
2016-06-05 14:52:40.287835 [info] Client/Session [1343/0004] sent a request to Service [1234.5678]
2016-06-05 14:52:40.288835 [info] Client/Session [1343/0005] sent a request to Service [1234.5678]
2016-06-05 14:52:40.289835 [info] Client/Session [1343/0006] sent a request to Service [1234.5678]
2016-06-05 14:52:40.290835 [info] Client/Session [1343/0007] sent a request to Service [1234.5678]
2016-06-05 14:52:40.291835 [info] Client/Session [1343/0008] sent a request to Service [1234.5678]
2016-06-05 14:52:40.293835 [info] Client/Session [1343/0009] sent a request to Service [1234.5678]
2016-06-05 14:52:40.294835 [info] Client/Session [1343/000a] sent a request to Service [1234.5678]
2016-06-05 14:52:40.300835 [info] Received a response from Service [1234.5678] to Client/Session [1343/0001]
2016-06-05 14:52:40.304835 [info] Received a response from Service [1234.5678] to Client/Session [1343/0002]
2016-06-05 14:52:40.307835 [info] Received a response from Service [1234.5678] to Client/Session [1343/0003]
2016-06-05 14:52:40.311835 [info] Received a response from Service [1234.5678] to Client/Session [1343/0004]
2016-06-05 14:52:40.315835 [info] Received a response from Service [1234.5678] to Client/Session [1343/0005]
2016-06-05 14:52:40.318835 [info] Received a response from Service [1234.5678] to Client/Session [1343/0006]
2016-06-05 14:52:40.320835 [info] Received a response from Service [1234.5678] to Client/Session [1343/0007]
2016-06-05 14:52:40.321835 [info] Received a response from Service [1234.5678] to Client/Session [1343/0008]
2016-06-05 14:52:40.322835 [info] Received a response from Service [1234.5678] to Client/Session [1343/0009]
2016-06-05 14:52:40.324835 [info] Received a response from Service [1234.5678] to Client/Session [1343/000a]
2016-06-05 14:52:40.325835 [info] Stopping...
2016-06-05 14:52:40.325835 [info] Stopping vsomeip application "local_routing_test_client"
[       OK ] someip_local_routing_test.send_ten_messages_to_service_and_receive_reply (79 ms)
[----------] 1 test from someip_local_routing_test (80 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (83 ms total)
[  PASSED  ] 1 test.
Then on Target #2, modify the /etc/vsomeip/external_local_routing_test_client_external.json file. In the file change the first unicast attribute to the IP Address of Target #2, and then within the servicegroups array, change the unicast attribute to the IP Address of Target #1.
After you complete the configuration changes on Target #2, set the VSOMEIP_APPLICATION_NAME and VSOMEIP_CONFIGURATION environment variables and then run local_routing_test_client as shown here to run the test:
# export VSOMEIP_APPLICATION_NAME=external_local_routing_test_client_external
# export VSOMEIP_CONFIGURATION=/etc/vsomeip/external_local_routing_test_client_external.json
# local_routing_test_client
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from someip_local_routing_test
[ RUN      ] someip_local_routing_test.send_ten_messages_to_service_and_receive_reply
2016-06-01 12:10:39.425160 [info] Initializing vsomeip application "external_local_routing_test_client_e"
2016-06-01 12:10:39.432160 [info] Using configuration file: "/etc/vsomeip/external_local_routing_test_cl"
2016-06-01 12:10:39.440160 [debug] Routing endpoint at /tmp/vsomeip-0
2016-06-01 12:10:39.450160 [info] Service Discovery disabled. Using static routing information.
2016-06-01 12:10:39.463160 [debug] Application(external_local_routing_test_client_external, 1344) is ini.
2016-06-01 12:10:39.464160 [info] Service [1234.5678] is available.
2016-06-01 12:10:39.466160 [info] Starting...
2016-06-01 12:10:39.469160 [info] Client/Session [1344/0001] sent a request to Service [1234.5678]
2016-06-01 12:10:39.470160 [info] Client/Session [1344/0002] sent a request to Service [1234.5678]
2016-06-01 12:10:39.470160 [info] Client/Session [1344/0003] sent a request to Service [1234.5678]
2016-06-01 12:10:39.470160 [info] Client/Session [1344/0004] sent a request to Service [1234.5678]
2016-06-01 12:10:39.471160 [info] Client/Session [1344/0005] sent a request to Service [1234.5678]
2016-06-01 12:10:39.471160 [info] Starting vsomeip application "external_local_routing_test_client_exter"
2016-06-01 12:10:39.471160 [info] Client/Session [1344/0006] sent a request to Service [1234.5678]
2016-06-01 12:10:39.472160 [info] Client/Session [1344/0007] sent a request to Service [1234.5678]
2016-06-01 12:10:39.472160 [info] Client/Session [1344/0008] sent a request to Service [1234.5678]
2016-06-01 12:10:39.472160 [info] Client/Session [1344/0009] sent a request to Service [1234.5678]
2016-06-01 12:10:39.473160 [info] Client/Session [1344/000a] sent a request to Service [1234.5678]
2016-06-01 12:10:39.479160 [info] Received a response from Service [1234.5678] to Client/Session [1344/0]
2016-06-01 12:10:39.480160 [info] Received a response from Service [1234.5678] to Client/Session [1344/0]
2016-06-01 12:10:39.482160 [info] Received a response from Service [1234.5678] to Client/Session [1344/0]
2016-06-01 12:10:39.484160 [info] Received a response from Service [1234.5678] to Client/Session [1344/0]
2016-06-01 12:10:39.485160 [info] Received a response from Service [1234.5678] to Client/Session [1344/0]
2016-06-01 12:10:39.486160 [info] Received a response from Service [1234.5678] to Client/Session [1344/0]
2016-06-01 12:10:39.488160 [info] Received a response from Service [1234.5678] to Client/Session [1344/0]
2016-06-01 12:10:39.489160 [info] Received a response from Service [1234.5678] to Client/Session [1344/0]
2016-06-01 12:10:39.491160 [info] Received a response from Service [1234.5678] to Client/Session [1344/0]
2016-06-01 12:10:39.492160 [info] Received a response from Service [1234.5678] to Client/Session [1344/0]
2016-06-01 12:10:39.628160 [info] Stopping...
2016-06-01 12:10:39.628160 [info] Stopping vsomeip application "external_local_routing_test_client_exter"
[       OK ] someip_local_routing_test.send_ten_messages_to_service_and_receive_reply (262 ms)
[----------] 1 test from someip_local_routing_test (263 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (266 ms total)
[  PASSED  ] 1 test.
On Target #1, in Terminal #1, you should also see a PASSED message as follows:
[       OK ] someip_external_local_routing_test.receive_ten_messages_over_local_and_external_socket (11440 ms)
[----------] 1 test from someip_external_local_routing_test (11441 ms total)
[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (11447 ms total)
[  PASSED  ] 1 test.