• Home
  • History
  • Annotate
  • only in /external/parameter-framework/upstream/test/functional-tests-legacy/
NameDateSize

..10-Aug-20184 KiB

ACTCampaignEngine.py10-Aug-20183.2 KiB

CMakeLists.txt10-Aug-20183.3 KiB

PfwTestCase/10-Aug-20184 KiB

README.md10-Aug-2018996

Util/10-Aug-20184 KiB

xml/10-Aug-20184 KiB

README.md

1#Functional test
2
3#What ?
4Create a test suite for all tests about SET/GET commands.
5Types,functions and Domains are tested.
6
7#How ?
8We set environment variables in the cmake.
9All temporary file are stored in the build directory.
10XML files depends on cmake variables so they are configured at build time and stored in {build_dir}/tmp.
11
12We launch the functional tests with ACTCampaignEngine.py. This script launch every test present in the PfwTestCase directory. Note that functional tests cannot be launched using directly the script.
13We finalize the environment setting in this script. isAlive and needResync are needed by the subsystem.
14To avoid dependancies between to consecutive test, we remove all the temporary files except XML files at the end of the tests.
15
16#Practical
17By default, the BUILD_TESTING flag is set to true.
18Once the makefile is created, we can launch the test by running :
19
20    'make && make test'
21
22Note that you can also use 'ctest -V' if you want to have the logs details.
23