1 | RTEMS Testsuite Configuration |
---|
2 | ============================= |
---|
3 | |
---|
4 | The RTEMS Testsuite lets you configure the tests for a BSP. Every BSP can have |
---|
5 | a test configuration data file and this file is read when building the |
---|
6 | tests. The test configuration data can control what tests are build and now the |
---|
7 | tests are built. |
---|
8 | |
---|
9 | The test configuration data files have a `.tcfg` file extension. You can |
---|
10 | include other test configuration data files reducing repeated test |
---|
11 | sequences. There is also a global test configuration data file for global |
---|
12 | configurations. |
---|
13 | |
---|
14 | Command |
---|
15 | ------- |
---|
16 | |
---|
17 | The build system invokes the test check tool to determine what it does. |
---|
18 | |
---|
19 | rtems-test-check mode bsp testconfig includepaths test[s] |
---|
20 | |
---|
21 | Mode (mode) |
---|
22 | ~~~~~~~~~~~ |
---|
23 | |
---|
24 | The check command modes are: |
---|
25 | |
---|
26 | 1. `exclude`: The input list of tests is checked against the excluded tests |
---|
27 | and the tests that are not excluded are printed. |
---|
28 | |
---|
29 | 2. `flags': The test build flags are returned. These flags can enumerate a |
---|
30 | test in a specific way. |
---|
31 | |
---|
32 | BSP (bsp) |
---|
33 | ~~~~~~~~~ |
---|
34 | |
---|
35 | The name of the BSP. |
---|
36 | |
---|
37 | Test Configuration (testconfig) |
---|
38 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
---|
39 | |
---|
40 | The path to the BSP's test configration file. If the file does not exist the |
---|
41 | input list of tests is returned and there are no special build flags. |
---|
42 | |
---|
43 | Include Paths (inputpaths) |
---|
44 | ~~~~~~~~~~~~~~~~~~~~~~~~~~ |
---|
45 | |
---|
46 | A colon (`:`) separated list of paths test configuration files are search |
---|
47 | for. |
---|
48 | |
---|
49 | Tests (test[s]) |
---|
50 | ~~~~~~~~~~~~~~~ |
---|
51 | |
---|
52 | If the mode is `exclude` this argument is a list of tests to be checked. If the |
---|
53 | mode is `flags` a single test is required and the flags for the test are returned. |
---|
54 | |
---|
55 | File Format |
---|
56 | ----------- |
---|
57 | |
---|
58 | The file is an ASCII text file of lines. And text after and including the `#` |
---|
59 | character is removed. Empty lines are ignored. |
---|
60 | |
---|
61 | A line is either the `include` directive or a test state. The states are: |
---|
62 | |
---|
63 | exclude : Exclude the test from being built. |
---|
64 | expected-fail : The test is built but expected to fail. |
---|
65 | user-input : The test requires user input and may be aborted when running |
---|
66 | the tests. |
---|
67 | indeterminate : The test result is indeterminate. This means the test may pass |
---|
68 | or may fail therefore it cannot be included in the regression |
---|
69 | results. |
---|
70 | benchmark : The test is a benchmark and maybe is aborted when running the |
---|
71 | tests because of the load and time the test may take to run. |
---|
72 | Performance changes are currently not viewed as a regression. |
---|