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