aboutsummaryrefslogtreecommitdiffstats
path: root/meta-ivi-test/recipes-extended/common-api/capicxx-someip-native_3.1.5p2.bb
diff options
context:
space:
mode:
authorPavel Konopelko <pkonopel@visteon.com>2016-06-09 18:26:06 +0200
committerPavel Konopelko <pkonopel@visteon.com>2016-06-17 17:44:54 +0200
commit6bc055f6f8f9b6d1604a6c91002c7022eac981f4 (patch)
tree71b318b0636ed6a7d3a5ccdc41a318a1d49b52e5 /meta-ivi-test/recipes-extended/common-api/capicxx-someip-native_3.1.5p2.bb
parenta375592949562b5c2face34179b0718e8fb7d454 (diff)
downloadmeta-ivi-6bc055f6f8f9b6d1604a6c91002c7022eac981f4.tar.gz
meta-ivi-6bc055f6f8f9b6d1604a6c91002c7022eac981f4.tar.bz2
meta-ivi-6bc055f6f8f9b6d1604a6c91002c7022eac981f4.zip
common-api: add capicxx-perf test
The test includes capicxx-server and capicxx-client applications that use Common API C++ to connect via D-Bus. The client invokes a method on the server, waits for the server to respond and repeats this sequence multiple times. The code generation is performed automatically as a build step and depends on capicxx-{core|dbus}-native recipes. The following transcript illustrates the usage: root@qemux86-64:~# dbus-run-session -- sh root@qemux86-64:~# capicxx-server & root@qemux86-64:~# Started capicxx-server capicxx-server heartbeat 1200s... root@qemux86-64:~# capicxx-client Started capicxx-client starting test... test completed message payload [bytes]: 0 sync messages sent: 10000 messages per [s]: 344.59 exiting capicxx-client root@qemux86-64:~# Signed-off-by: Pavel Konopelko <pkonopel@visteon.com>
Diffstat (limited to 'meta-ivi-test/recipes-extended/common-api/capicxx-someip-native_3.1.5p2.bb')
0 files changed, 0 insertions, 0 deletions