1 This explains how the automatic testing works with profile support. 2 3 Profiles help users maintaining sets of tests for specific requirements. 4 Each profile is defined in a file. 5 All profiles are stored in the <RT_TESTS_ROOT>/profile/ directory. 6 7 8 I. Automated tests in specific test-diretory. 9 10 Tests can be run for one directory by running ./run_auto.sh in the wanted dir. 11 run_auto.sh is customizable and contains a command line for each test to be run. 12 (see template run_auto.sh.tpl in this dir) 13 run_auto.sh can be invoked with an argument which is the profile to use. 14 profile/ dir holds a file for each defined profile. 15 A profile has a number of lines for which each test executable can be run 16 with different arguments. 17 Invoking run_auto.sh with no arg uses the default profile. 18 Currently, the default profile does not alter the default values defined 19 individually in each test. 20 21 Example: 22 In dir func/prio-preempt, user runs ./run_auto.sh prf1 23 Since run_auto.sh contains this line: 24 $SCRIPTS_DIR/run_c_files.sh $profile prio-preempt 25 26 run_c_files.sh will look into profile/prf1 for lines like this: 27 func/prio-preempt prio-preempt -c 2 -j 28 func/prio-preempt prio-preempt -c 1 29 30 and run the following commands from the func/prio-preempt dir: 31 prio-preempt -c 2 -j 32 prio-preempt -c 1 33 34 35 36 II. All automated tests 37 38 Tests can also be run with <RT_TESTS_ROOT>/run.sh. User may choose whatever 39 test range he wants. (all, func, perf... see README) 40 run.sh searches for run_auto.sh files in the wanted area and runs them one 41 by one. 42 To use a profile other than default, use argument '-p <myprofile>'. 43 44 Examples: 45 ./run.sh -p prf1 -t func # Uses prf1 profile 46 ./run.sh -t func # Uses default profile 47
